Lawson database server move checklist

We are in the process of moving our database from stand alone oracle database to an Exadata environment. We have not been able to keep the database name same as we thought initially, so along with the server name, the SID/serverName has changed. I am trying to find if there is a comprehensive list that would cover all the configuration files that need changed to make it work. Of course we have Landmark, LSF & MSCM applications on Oracle which get impacted. Any suggestions or recommendations are appreciated.

Find more posts tagged with

Comments

clara-tan

I don't have a list but Lawson references the Oracle TNSnames.ora file to use the DBSERVER name - you might be able to keep the name used by lawson in the ORACLE file under your $LAWDIRHOME/productline/ and change the paragraph contents to redirect to the new database (host port SID). One has to be careful updating any tnsnames.ora file; make a backup copy, use oracle's Net Configuration assistant, or edit carefully since SQLNET may not like tabs or other special characters.

serafino

You have to set $ORACLE_SID to match the SID in TNSnames.ora on the LSF server. Then you have to set the DBSERVER setting in $LAWDIR/<pl>/ORACLE to the new SID, as well as change the LOGINNAME and PASSWORD values to be valid. You also need to change $DATABASE if you are running BSI Tax Factory (other tax packages have their own environment variables). Other than this, there should be no impact on the LSF server. On the Landmark server(s), you need to verify these values in %LARUNDIR%<pl>db.cfg, and you may need to update the JDBC configurations in the Landmark Admin application if you are using JDBC. You will need to do this for GEN and for all installed productlines in all places. As far as I am aware, there is no impact on Mingle because it uses its own SQL server.

If you are running BI you will need to adjust these settings in the JNDIs defined for the services and products through WebSphere. There are a few other products that may use data connections from WebSphere - I can only speak for BI - and you will need to verify these as well. However, since the JNDI has the server name and Oracle SID as part of its connect string, there is no file within WAS that mimics the functionality of the TNSNames.ora file.

Legacy Contributor

Yes, we had these 2 places accounted for. Since the SID name was not defined in the Exadata environment, MSCM ran into issues & we had to learn it the hard way. Thank you

Legacy Contributor

Glad your list is much more updated. I do see some more references in install.cfg/ $DATABASE by each productline & maybe in bpm.properties file? I am hoping nothing else in WebSphere?

For Landmark, I have config.sh & db.cfg. We have not changed install.cfg but application is running without it. And we have changed the jdbc connections in system config for each data area.

And yes, we have MSCM & LBI. MSCM was the most painful to figure out, but now everything is working there as well.

Copyright © 2025 Infor. All rights reserved.