We are in progress of migrating the SD DB server to new server, I would like to know where these DB name will be configured in workflow,CASD after the migration.
Any help for Mohan?
The database server for CASD is configured using pdm_configure.
You did not say which workflow engine you are using, CAWF or PAM?
it is CAWF.
latest update:we have done with migration facing issues like our SQL db account is trying to connect to old instsnce still and no db activity is carried out.
The configuration for CAWF should be found in the pm.xml and wl.xml files in the folder $NX_ROOT\bopcfg\www\CATALINA_BASE_WF\conf\Catalina\localhost. The configuration for Service Desk is in NX.env in the folder $NX_ROOT.
Can you please let me know on which servers we need to do configure the new SQL db instance name(application/SQL server)?
Yes, on the primary Service Desk server and the server on which CAWF is running (which may be the same server). Without knowing your environment that is the best I can suggest. Have you run the pdm_configure command on the primary server and successfully gone through that?
In primary config. Went successful, but it is still trying to connect to the old SQL instance. Whether any configuration needs to be done in the new SQL DB server as well?
When you say "it" do you mean Service Desk or CAWF? How do you know it is trying to connect to the old SQL server?
Usually the only thing you need to do when you restore the mdb to another SQL server is reconnect the ServiceDesk login to the ServiceDesk user (see How to fix orphaned SQL Server users)
reagrding WF the answer ahve been provided by you. Now, the SQL DB account used for pdm_config is still trying to conncet to the old instance and not to the new instance in new server, am facing challenge in addressing the issue.anyboday have any idea on this.
Check the DB node info in NX_ROOT/site/config.properties file. Take a backup of the file change if and the re start pdm_configure
Thanks for your response. Do we need to make the changes in both the servers, in primary i can see that db node configured to old sql instance and in the secondary db node as secondary app server. Also, advise any other change in any place is required.Thansk in advance.
You can adjust it on both but its primary that impacts the main DB connection In conventional setup.
I have udpated the files but still no go. Can you please calrify , where all the new DB instance name needs to be configured for the DB server migration. we have CA WF,CA EEM.Also, please advise if anything needs to be done on the new SQL server.Thanks ina dvance.
For just SDM, once MDB backup/restore is completed on, the only thing you may need to do is fixing the Service Desk orphaned user. Some times even this step is not needed. There after you just run pdm_configure and on the pdm_configure screen you provide the new database server/instance name. Lindsay's post earlier was spot on.
What I'm now confused about is, the reference to "not working". When you run pdm_configure, you have the option to change the DBHost to the new host and once, you commit through and finish pdm_configure successfully there after, it'll remember the new databaase info. Are you referring to the old node info showing up on pdm_configure screen as "not working". This is mostly OK until after you have provided correct DB node info to pdm_configure and let it complete successfully.
Regarding CAWF, adjusting pm.xml and wl.xml files to use correct JDBC URL would address this as well. Lindsay referred to this one earlier too "The configuration for CAWF should be found in the pm.xml and wl.xml files in the folder $NX_ROOT\bopcfg\www\CATALINA_BASE_WF\conf\Catalina\localhost."
If you are still having some issues, we could definitely use some log files to understand what is not working and why. NX_ROOT/log directory is what I'd normally look for.
Hope this helps.
The steps mentioned by you have been carried out and also the pdm_configure went successful with the new DB host name but the SQL trace stating that SD SQL DB account is trying to access the existing instance.
Thanks for clarifying Mohan.
Maybe some SQL profiling can be done on those database IDs that are connecting to see what SQL they're running. Maybe its not SDM, but some other integration that needs to be changed as well?
If it is CAWF, then usually its just pm.xml and wl.xml that contains hard coded JDBC URL in it.
Retrieving data ...