The maximo.properties file is the 'key' file. It contains the JDBC connection string and the user/password information.
You have to update this file before executing any command like maxinst or buildmaximoear (maxinst accepts arguments to change the default location of the maximo.properties file; I failed to run buidmaximoear with another maximo.properties file).
To setup a second environment running on the same server, you should have two choices :
- (1) backup the data owned by the first maximo instance and restore it to a different user; then connect your test MXServer to this second instance
- (2) install a second MAXIMO database using maxinst command
I have not try the first solution. I guess you have to change some data after the restore.
The solution 2 is easier. The maxinst command sets up every thing in the database (use -imaximo option to configure an empty database). You only need to build the ear (be sure to update maximo.properties before) and deploy it to the second MXServer. If you plan to use the Integration Framework, you have to configure a different JMS bus and use it with the test MXServer (see the procedure on
http://maximotimes.com/maximo/setup-integration-framework-jms-queues-and-buses-in-websphere/ -- to be done before building the ear).
Once the test MXserver installed and running, you can use Migration Manager to report any configuration modification from one server to the second one.
Hope this helps.
