The First Steps script takes
care of setting up database tables for Telecom Web Services Server (TWSS)
when you are using a consolidated or shared database. However, additional
steps may be required when you are using a distributed database configuration.
Before you begin
This procedure is a sub-procedure within the overall migration
process of your test (non-production) or production system. Make sure
that you have already installed TWSS version
7.1 components
and that you have performed the procedures described in one of the
following post-installation configuration topics:
- Creating and configuring the DB2 database server instance
- Creating and configuring the Oracle database server instance
Note that the First Steps script assumes
that all nodes in the cluster are at a TWSS version 7.1 level.
About this task
If a distributed or partitioned topology is used for databases,
you will encounter one of the following scenarios:
- One database per cluster. For example, you may have the Access Gateway running
in one cluster and the Service Platform components running
in another cluster, with each cluster having its own database. If
this is the case, when you run the First Steps script on
the Access Gateway cluster,
all of the database parameters should refer to the Access Gateway database
(typically named AGDB). Then when you run the script on the Service
Platform cluster, the database parameters should refer to the Service
Platform database (typically SPMDB). No additional special considerations
apply.
- More than one database per cluster. For example, you may
have a separate database for the WAP Push service on the same cluster
with the database for the Service Platform components. If this is
the case, use the procedure in this topic to create a temporary database
and then configure new databases to work with TWSS version 7.1.
To migrate a distributed database configuration when there
is more than one database per cluster, perform the following steps.
- On one of the nodes in the cluster, create
a temporary database by running the First Steps script with
the Initial Configuration Mode option pointing to
a new temporary database. For detailed information, see
the topic Running the First Steps configuration script. The First Steps script creates
the minimum necessary data sources to support a distributed topology
and points to the new single (temporary) database instance.
- Create additional data sources, as necessary,
and update the necessary JNDI bindings to the respective data sources.
- Drop the temporary database.
- Verify the new migrated environment by running any successful
service logic test case. Verify databases and logs.
Note: Migration of runtime data is generally not
supported, except in the cases of some Direct Connect-based
Web service implementations.
(For details, refer to the topic
Planning to migrate from the
previous version of Telecom Web Services Server.)
In these cases, be sure that you have copied all of the existing data
to the new database before deleting the old database and database
tables.
- Verify that the newly populated data coexists with the
previous data in cases where migration of runtime data is supported
for a given Web service or feature.
Note: When the First Steps script sets
up your configuration for running TWSS version 7.1,
it does not modify your existing configuration. Therefore, if you
made changes to the default configuration for a previous version of
TWSS, your changes are preserved during the migration process.