12.4 Moving a Dashboard Configuration

After configuring the Dashboard, you might want to move the Dashboard configuration to another machine. For example, you can first deploy the Dashboard in a test or development environment, then later move it to a production environment for general use.

12.4.1 Preparing to Move a Dashboard Configuration

To successfully move a the Dashboard configuration, there are two prerequisites:

  • Both the existing server and the target server must have the same version of the Dashboard, including the same patch bundles installed, and

  • The configuration settings in the Operations Center Dashboard Configuration Manager must be the same on both servers.

12.4.2 Moving a Dashboard Configuration

To move a Dashboard configuration:

  1. Shut down both the Dashboard servers.

  2. Copy /OperationsCenter_Dashboard_install_path/data/hsql/lportal.script from the existing server to the target server.

  3. Modify the server_profiles section of the target server’s /OperationsCenter_Dashboard_install_path/server/webapps/ManagedObjectsPortlets/WEB-INF/data/serverprofiles-ext.xml file for the server’s properties.

  4. Determine if any customizations were made to the existing server and if those customizations need to be made on the target server, as well.

    Some files that might have been customized are:

    • portal-ext.custom.properties: In /OperationsCenter_Dashboard_install_path/server/webapps/ROOT/WEB-INF/classes/, it is used for auto-login, persistent connection account, disabling of portlets, power user personal pages changes, or for overriding other liferay properties set in portal.properties.

      Note that any settings in portal-ext.custom.properties file takes precedence over those in the portal-ext.properties file. Do not customize portal-ext.properties and portal.properties files, as you might overwrite the files.

    • system-ext.properties: In /OperationsCenter_Dashboard_install_path/server/webapps/ROOT/WEB-INF/classes/, it is used for proxy server configuration.

    • web.xml: In /OperationsCenter_Dashboard_install_path/server/conf/, it is used for session management.

    • globals.xml: In /OperationsCenter_Dashboard_install_path/server/webapps/ManagedObjectsPortlets/WEB-INF/data/, it is used for global defaults for all Operations Center portlets.

  5. Make the necessary customizations on the target server.