Why need to update ADF BC connection details for ensuring deployment??
gauravsAug 26 2012 — edited Aug 27 2012I know it is a ADF question but still posting in this forum as it was encountered deploying a BPM application on OBPM 11.1.1.6. I get a bpm project from the internet and decide to test it out on my local. The objective was to populate the payload of the process dynamically i.e. based on the selection made by the participant on the UI (a ADF Business Component from a database table is created and rendered on the task form for the user to select). I imported the code on my JDev and changed the JDBCDataStore for both <Module>Local & <Module>Shared in the runtime configurations of the application module to point to a Data Source that I created on my WLS.
Assuming that's all was needed to test out, tried to deploy the application on my WLS. The deployment failed with a logon - usname/pws 'mismatch' issue. This was quite strange because I had tested the DataSource after creating it. It took a while for me to figure out that it wasn' the JDBCDataStore that was causing the issue but looks like the creator of the application had created a database connection to connect to his / her local database to create the business components for the application. I had to update correct 'uname/pwd' (i.e. the one on my local) to make the deployment work.
Now, coming to the question - I believe database connection is more a design time configuration to create the business components ?? Once they are created in the project, the deployment should be agnostic of the environment as long as we are updating our runtime configurations correctly? Somebody please help out understanding this. With my limited understanding of ADF I would rather have an expert comment and clarify this.
Thanks,
gsr