WebSphere brand IBM WebSphere Telecom Web Services Server, Version 7.1

Migrating a non-production system to Telecom Web Services Server version 7.1

To migrate a non-production or test system from Telecom Web Services Server (TWSS) version 7.0 to version 7.1, begin by uninstalling the previous version of the product. Then install and configure the new version.

Before you begin
Become familiar with the planning information provided in the topic Planning to migrate from the previous version of Telecom Web Services Server.
About this task

When migrating an existing system to Telecom Web Services Server version 7.1, the program code is updated independently of your configuration data. Not all of the existing configuration data will necessarily apply to the new version 7.1 system. However, wherever possible, your existing configuration data can be brought forward to the new version level.

The following steps outline the process for migrating a non-production, or test, system to version 7.1.

  1. Verify the hardware topology. For details, refer to the topic Standard configurations for Telecom Web Services Server.

    In TWSS version 7.1 it is recommended–but no longer required–that you run the Access Gateway in a separate cluster from the other product components. As a result, you may choose to modify your clustering topology to use TWSS Version 7.1.

  2. Verify that the appropriate version of WebSphere® Application Server and all other prerequisite software is installed. For details, refer to the topic Software requirements.
  3. Stop all application servers, node agents, and deployment managers. For details, refer to the topic Stopping and starting the server.
  4. Remove applications and uninstall the program code for the old version of Telecom Web Services Server. For detailed instructions, refer to the Removing Telecom Web Services Server section of the information center for the product version you are replacing.

    The First Steps script will migrate data only from a consolidated or shared database, not from a distributed database. Verify that the Service Policy Manager tables, CONFIGPROPERTIES and CFGPROPERTIES (if Parlay is used), tables exist in the primary database before proceeding.

  5. Run the TWSS base installer to install version 7.1 program code on the new deployment manager, or on the single server instance if there is no deployment manager. For details, see the Installing Telecom Web Services Server base components section of this information center.
  6. Run the TWSS services installer to install version 7.1 program code for the Web service implementations on the new deployment manager, or on the single server instance if there is no deployment manager. For details, see the Installing Telecom Web Services Server services section of this information center.
  7. Start the deployment managers and all node agents. For details, refer to the topic Stopping and starting the server.
  8. Run the First Steps script to configure each deployment manager or server on which you installed the TWSS program code. The First Steps script has a Migrate option that enables you to migrate old policies and configuration data.

    In a distributed database configuration where there is one database per cluster, run the First Steps script, using the Migrate option, on each cluster. In each case, make sure that the database parameters refer to the database that pertains to that cluster–for example, AGDB for the Access Gateway cluster or SPMDB for the Service Policy Manager cluster.

    In a distributed database configuration where there is more than one database per cluster, create a new temporary database and run the First Steps script on each cluster. You will need to manually configure the data sources in the WebSphere Integrated Solutions Console to point to the right database after the First Steps is completed.

    For details, refer to the topic Migrating data in a distributed database configuration.

  9. Create additional data sources, as necessary, and update the necessary JNDI bindings to the respective data sources.
  10. Test the database connection and start the clusters or server instances.



Terms of use
(C) Copyright IBM Corporation 2009. All Rights Reserved.