WebSphere brand IBM WebSphere Telecom Web Services Server, Version 7.1

Running the First Steps script interactively

You can run the First Steps script in interactive mode, responding to prompts as the configuration proceeds.

Before you begin
About this task

The configuration properties file is found at the following directory location: was_root/installableApps/TWSS-Base/firststeps/firststeps.properties. The First Steps script launches a wizard that updates this properties file with the values you specify.

Note: If you are migrating from an earlier version of TWSS, the First Steps script will migrate data only from a combined database, not from distributed databases. For information about migrating data when you use a distributed database configuration, see the topic Migrating data in a distributed database configuration.

Follow these steps to perform basic configuration for your newly installed TWSS components:

  1. Start the deployment manager and all associated node agents.
  2. On the deployment manager where the TWSS base components have been installed, log in using root or another valid ID.
  3. Navigate to the following directory: was_root/installableApps/TWSS-Base/firststeps.
  4. If the database is installed on the deployment manager server, issue an export command similar to one of the following examples to ensure that the Java classpath environment variable includes appropriate JDBC driver JAR files for your database.
    • DB2  export db2=/opt/ibm/db2/V9.5
    • DB2  export CLASSPATH=${CLASSPATH}:${db2}/java/db2java.zip:${db2}/java/db2jcc.jar:${db2}/java/db2jcc_license_cu.jar
    • Oracle  export CLASSPATH=${CLASSPATH}:/Oracle/opt/oracle/product/11.1.0/client_1/jdbc/lib
  5. If the database is installed on a separate server, follow these steps:
    1. On the deployment manager and on each TWSS node, create a new directory to hold the database driver files, for example /db2_driver or /oracle_driver.
    2. DB2 FTP or copy the following files from the DB2 server to each of the new directories you created:
      • db2jcc_license_cu.jar
      • db2jcc.jar
      • db2java.zip
    3. DB2 Issue an export command similar to the following:
       export CLASSPATH=${CLASSPATH}:/db2_driver/db2java.zip:/db2_driver/db2jcc.jar:/db2_driver/db2jcc_license_cu.jar
    4. Oracle FTP or copy the file ojdbc5.jar from the Oracle server to each of the new directories you created.
    5. Oracle Issue an export command similar to the following:
       export CLASSPATH=${CLASSPATH}:/oracle_drivers/ojdbc5.jar 
  6. Configure a target scope for the Access Gateway, the Service Platform, and the Service Policy Manager.

    Each of these components can be configured on a WebSphere® topology that is managed by the deployment manager on which you are running the First Steps script.

    • To configure a component on a cluster, type the cluster name in the appropriate target scope.
    • To configure a component on a server, either standalone or managed by the deployment manager, use the slash character–for example node/server.
    • To bypass configuration for the component altogether, type None.

    For example, by running the First Steps script just once, you can configure the Access Gateway on TWSSCluster_1 and the other two components on TWSSCluster_2, provided both clusters are managed by the same deployment manager. However, if the clusters are managed by two separate deployment managers, you must run the First Steps script twice–once on each deployment manager.

  7. Issue the following command to launch the First Steps script:
    ./firststeps.sh @firststeps.properties wsadmin_options 
    where wsadmin_options are optional parameters that will be passed to the wsadmin command, which is invoked by the script. For example, if WebSphere global security is enabled, you can supply the user name and password:-username wasadmin -password was123.
  8. In the Configuration Mode section, select the appropriate option:
    Initial Configuration Mode
    For a first-time or clean installation, initial values are provided for all configuration resources and properties. Existing values, if any, are overwritten.
    Note: Use this option only when you are deploying the Telecom Web Services Server components for the first time. This option completely drops all of the tables in the database and recreates them. For subsequent add-ons affecting any of the components, use the Update option.
    Migrate
    For upgrading from a previous version of the product, initial values are provided for the missing configuration information. Existing configuration resources and properties are retained whenever possible.
    Note: This option applies only if you used a consolidated database setup–rather than a distributed database setup–in the previous version of TWSS.
    Update
    This option should be used when deploying service add-ons to the existing setup. It also applies when making updates to an interim fix (iFix) or fix pack if you are so instructed by the Readme. Initial values are provided for missing configuration resources and properties, while existing configuration resources and properties are retained whenever possible. This option does not drop existing tables but creates the newly required tables in the database.
    Note: The existing database is retained only if all of the following values you supply in step 9 match the values for the existing database: server type, server host name, server port, and database name. If any of these values do not match, the First Steps script replaces the existing database.
    Note: If the Service Platform components are installed using the Initial option and you would like to add, for example, the Service Policy Manager or the Access Gateway using the same database, then you should use the Update option for the Service Policy Manager or the Access Gateway.
  9. In the Database Configuration section, complete the following fields:
    Database Server Type
    Either DB2 or Oracle. The default value is DB2.
    Database Server Access Mode
    One of the following:
    Local
    The database server is on the same machine as the deployment manager, and the only server instance is also on the same machine.
    Remote
    The database server is on another machine, and all nodes will access it remotely using the hostname. This is the default value.
    Note: The database NodeName for DB2 will be set to a constant RDBSRV for a remote database server, or local for a local database.
    Database Server Hostname
    The host name or IP address for the database server. The default value is localhost.
    Database Server Port
    The port number through which the application server will access the database server. The default value is 50000 for a DB2 server, and 1521 for an Oracle server.
    Database Driver Path
    The value you want to use for the two WebSphere environment variables.
    These examples assumes that the database is installed on the deployment manager server:
    • DB2  /opt/ibm/db2/V9.5
    • Oracle  /opt/oracle/product/11.1.0/client_1/jdbc/lib
    Note: The path is assumed to be the same for each node in a deployment. If different paths are used for different nodes, you will need to configure the WebSphere variables manually.
    Database Administrator Name
    The name of the Administrator user on the database server. This user name is used when initializing the database instance.
    Examples:
    • DB2 db2admin or db2inst1
    • Oracle SYSTEM
    Database Administrator Password
    Password for the Administrator user on the database server.
    Database User Name
    The name of the user that will access the database server during runtime, for example twssuser.
    Database User Password
    Password for the user that will access the database server during runtime.
    Database Name
    The name of the database, no more than 6 characters in length. The default value is TWSS71.

    This value will be appended with D to generate the full database name, and appended with A to generate the full alias name. The full name is limited by some databases to 7 or 8 characters.

    In a distributed database configuration, use the name of the database that applies to this cluster – for example, AGDB for the Access Gateway cluster or SPMDB for the Service Policy Manager cluster.

    Database Locale
    The locale string used to initialize the database. The default value is US.
  10. In the WAS Configuration section, complete the following fields to provide information about your WebSphere setup:
    WAS Administrator User Name
    The administrative user name for WebSphere Application Server. Required if WebSphere security is enabled.
    WAS Administrator Password
    The password for the administrative user. Required if WebSphere security is enabled.
    Access Gateway Target Scope
    The target scope for the Access Gateway: either the name of a cluster, a name in the form node/server, or None.
    Service Platform Target Scope
    The target scope for the Service Policy Manager: either the name of a cluster, a name in the form node/server, or None.
    Service Policy Manager Target Scope
    The target scope for the Service Platform components: either the name of a cluster, a name in the form node/server, or None.
    WC Default Host Port
    The port used by the Web container for Web service implementations. Use this port number in all URLs referenced in the configuration.

    The default value is 9080. However, you may need to specify 9081 or 9082 if there are other servers on the same physical machine.

    JMS Queue Mode
    If a file store or data store is used, the root path where the bus members store their data. The default value is filestore.
    JMS Queue Path
    The full path to a directory where file store JMS queues can be stored. In a clustered configuration, this directory must be on an NFS mounted file system so that it can be shared among all JMS queue engines. For a single node configuration, it can be a local directory. There is no default value.
    JMS Datastore JNDI Name
    The JNDI name of a JDBC data source where the data store's JMS queue data is stored. The default value is jdbc\TWSSDB.
    JMX Administrator User Name
    A user ID with WebSphere Application Server Administrator authority. This name is used by the Access Gateway and the Service Platform components to emit JMX notifications. Required if WebSphere security is enabled.
    JMX Administrator Password
    Password for the WebSphere Application Server Administrator user.
  11. In the TWSS Configuration section, complete the following fields to provide information about your Telecom Web Services Server (TWSS) setup:
    TWSS User Name
    A user ID used to access the Service Platform components and the Access Gateway from the PX Notification component Web service. Required if basic authentication is used to authenticate between the Service Platform components and the Access Gateway.
    TWSS User Password
    Password for the TWSS user.
    SPM Policy Access URL
    The endpoint URL for the Service Policy Manager Policy Access interface. The default value is http: //localhost:9080/SPM/Access/services/PolicyAccess.
    Group Resolution URL
    The endpoint URL for the Address List Management interface. The default value is http://localhost:9080/TWSS/ParlayX21/Admin/AddressListManagement/IMS/services/AddressListManagement.
    Privacy Implementation Enabled
    True if you are installing a privacy implementation, false if not. The default value is true.
    Access Gateway Root URL
    The service endpoint root for the Access Gateway, in the form hostname:port. This value is common to all services, and it will also be the URL for the load balancer if desired. The default value is http://localhost:9080.
    Service Platform Root URL
    The service endpoint root for the Service Platform components, in the form hostname:port. This value is common to all services. The default value is http://localhost:9080.
    Policy Administrator Group Name
    The group name from the user registry used for the PolicyAdministrator role.
    TWSS Administrator Group Name
    The group name from the user registry used for the TWSS Administration Console.
    Notify Mgmt Administrator Group Name
    The group name from the user registry used for the Notification Management Administration interface.
  12. Optional: If you want to save your values into a configuration properties file to be used for a silent installation at a later time, click Save.
  13. To start the configuration process, click Configure.
Results
The First Steps script performs all of the following configuration steps:
  • Initializes the necessary databases.
  • Configures the common WebSphere Application Server resources.
  • Configures the common Access Gateway resources.
  • Configures the common Service Platform resources.
  • Configures the resources for each installed Service Platform component and Web service implementation.
  • Performs the same configuration for all server instances associated with the cluster.
  • Configures the server and the node specific configuration items.
What to do next

When the script completes, it might be necessary to perform some additional configuration, depending on which Web service implementations you plan to deploy. For more information, refer to the topic Configuring connections for the Web service implementations.

To check the results of running the First Steps script, refer to the topic Verifying the completed configuration.




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