WebSphere brand IBM WebSphere Telecom Web Services Server, Version 7.1

Migrating a production system to Telecom Web Services Server version 7.1

To migrate a production system from Telecom Web Services Server (TWSS) version 7.0 to version 7.1, you should plan to run two separate systems in parallel. After the first system has been fully migrated, has been tested, and is up and running, you can move the workload from the older running system to the newer running system.

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 production system to TWSS version 7.1.

  1. Perform load balancing, or add new capacity, so that the workload for the system to be migrated is running at no more than half of the total capacity. This activity will probably require you to set up new nodes, with a new deployment manager.
  2. 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.

  3. Stop all application servers and node agents that are no longer needed for running the existing system. These servers and node agents, together with any new hardware that you have set up, are known in this procedure as migration elements. They will be used to run TWSS version 7.1 while the previous version is running on the old system.
  4. Create a new deployment manager for the migration elements. The new TWSS version 7.1 cluster should have the same fronting proxy or proxies as the old cluster.
  5. On each migration element, 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.
  6. Verify that WebSphere® Application Server and all other prerequisite software is installed on each migration element. For details, refer to the topic Software requirements.
  7. In the new cluster, run the TWSS base installer to install version 7.1 program code on the deployment manager, or on the single server instance if there is no deployment manager. The TWSS base installer installs the Access Gateway, the Service Policy Manager, the Service Platform components, and the Parlay Connector.

    For details, see the Installing Telecom Web Services Server base components section of this information center.

  8. In the new cluster, run the TWSS services installer to install version 7.1 program code for the Web service implementations on the 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.
  9. In the new cluster, start the deployment managers and all node agents. For details, refer to the topic Stopping and starting the server.
  10. For a shared database configuration, create a new database in the new cluster, following the procedures in the topic Preparing for the Telecom Web Services Server database.

    For a distributed database configuration, create a new database in each cluster–for example, AGDB for the Access Gateway cluster and SPMDB for the Service Policy Manager cluster. If you have multiple databases on each cluster, create a new temporary database and then configure the database appropriately. Refer to the topic Migrating data in a distributed database configuration.

    Note: For the Service Platform components (but not for the Web service implementations or any other components), you can preserve existing data by pointing to the existing database rather than creating a new database.
  11. Run the First Steps script to configure each deployment manager or server on which you installed the Telecom Web Services Server program code.

    In a distributed database configuration where there is one database per cluster, run the First Steps script on each cluster using the Initial Configuration Mode option (or the Migrate option if you are configuring an existing database). In each case, make sure that the database parameters refer to the database that is specific 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.

  12. Create additional data sources, as necessary, and update the necessary JNDI bindings to the respective data sources.
  13. On the proxy server or servers, specify the TWSS version 7.1 cluster as the default cluster, so that the new dialogs will be routed correctly.
  14. Test the database connection and start the clusters or server instances.
  15. Move the workload from the existing system to the new version 7.1 cluster:
    1. Using the WebSphere Performance Monitoring Infrastructure (PMI), monitor performance for the applications on the TWSS version 7.0 cluster. When the number of sessions reaches zero, or when it reaches a low enough level that you deem acceptable, stop the cluster.
    2. Remove the remaining nodes from the TWSS version 7.0 cluster and add them to the 7.1 cluster. These nodes can be added to the new cluster to provide additional capacity.
    3. Roll out the applications to the newly added nodes in the TWSS version 7.1 cluster.



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