Updating your production environment

You update your existing version of Decision Server Insights by installing the new version and running migration scripts on all of the servers in your production topology.

1. Stop any client applications that are sending in events.
2. Shut down each server in your topology.

   For each connectivity and catalog server, run the server stop command from the <InstallDirV871>/runtime/wlp/bin directory. For each runtime server, run the serverManager shutdown command from the <InstallDirV871>/runtime/ia/bin directory:

   1. Inbound servers
   2. Runtime servers
   3. Outbound servers
   4. Catalog servers
3. For each of the servers in your topology, do the following steps:
   1. Copy the existing <InstallDirV871>/runtime/wlp/usr directory to a new location, for example /opt/wlp/usr and create a WLP_USER_DIR environment variable to that path.
   2. Run Installation Manager to install Decision Server Insights V8.8 on the same computer as your existing installed version.
   3. Run the server migration script:

      • <InstallDirV88>/runtime/ia/bin/migrateConfig.bat on Windows

      • <InstallDirV88>/runtime/ia/bin/migrateConfig on Linux

      The script updates objectgrid.xml, and objectGridDeployment.xml files and removes the old solution references from server.xml.

4. If you use data persistence, do the following steps:
   1. Back up the V8.7.1 database.
   2. Create a new schema in the same database as your existing tables. For example, you can create a schema named TARGET to use as the destination of the migrated tables.
   3. Create the version 8.8.0 tables in your new schema. The SQL for creating the tables is in <InstallDirV88>/runtime/ia/persistence/sql/Oracle or <InstallDirV88>/runtime/ia/persistence/sql/DB2 for Oracle or DB2 databases. Modify the SQL file to specify the schema that you create in step 4b.
   4. Run the database migration script and provide the source schema name, target schema name, and all properties that are required to connect to your database. For more information about the migration script and the required parameters, see dataMigrationManager. The following example shows a command that locates a properties file name connection.properties: dataMigrationManager migrate --propertiesFile=/opt/ibm/connectivity/connection.properties.
   5. After the data migration is completed, modify the persistence configuration for the 8.8 servers to use the schema that is created in step 4b.
5. Update your client applications so that they include the new <InstallDir>/runtime/ia/gateway/*.jar and restConnector.jar files in the class path.
6. Update Decision Server Insights in your development environment, and follow the steps in Migrating solutions.
7. Deploy the migrated version of your solutions to the runtime servers.
8. Start the updated servers by running the server start command in the following order:
   1. Catalog servers
   2. Runtime servers
   3. Outbound connectivity servers
   4. Inbound connectivity servers
   Check the log files in the <InstallDirV88>/runtime/wlp/usr/servers/server_name/logs directory.
9. If you use data persistence, run the dataLoadManager autoload command from <InstallDirV88>/runtime/ia/bin.
10. Optional: Restart your client applications.