Environment
myMO 4.0
myMO 4.5
Situation
Purpose: This TID will identify the steps in migration of myMO from one server to another
Resolution
To successfully move a myMO configuration, there are two prerequisites:
1. Both the existing server and the target server must have the same version of myMO, including the same patch bundles installed, and
2. The configuration settings in the myMO Configuration Manager must be the same on both servers.
To move a myMO configuration, both myMO servers must be shut down. Then copy [myMO installation directory]/server/bin/lportal.script from the existing server to the target server. After copying the configuration, you will need to determine if any customizations were made to the existing server and if those customizations needs to be made on the target server as well.
Some files that may have been customized are:
§ portal-ext.properties in [myMO installation directory]/server/webapps/ROOT/WEB-INF/classes/ for auto-login, persistent connection account, disabling of portlets, power user personal pages changes, or Google maps portlet configuration
§ system-ext.properties in [myMO installation directory]/server/webapps/ROOT/WEB-INF/classes/ for proxy server configuration
§ web.xml in [myMO installation directory]/server/conf/ for session management
§ globals.xml in [myMO installation directory]/server/webapps/ManagedObjectsPortlets/WEB-INF/data/ for global defaults for all Managed Objects portlets
1. Both the existing server and the target server must have the same version of myMO, including the same patch bundles installed, and
2. The configuration settings in the myMO Configuration Manager must be the same on both servers.
To move a myMO configuration, both myMO servers must be shut down. Then copy [myMO installation directory]/server/bin/lportal.script from the existing server to the target server. After copying the configuration, you will need to determine if any customizations were made to the existing server and if those customizations needs to be made on the target server as well.
Some files that may have been customized are:
§ portal-ext.properties in [myMO installation directory]/server/webapps/ROOT/WEB-INF/classes/ for auto-login, persistent connection account, disabling of portlets, power user personal pages changes, or Google maps portlet configuration
§ system-ext.properties in [myMO installation directory]/server/webapps/ROOT/WEB-INF/classes/ for proxy server configuration
§ web.xml in [myMO installation directory]/server/conf/ for session management
§ globals.xml in [myMO installation directory]/server/webapps/ManagedObjectsPortlets/WEB-INF/data/ for global defaults for all Managed Objects portlets