WebSphere brand IBM WebSphere Telecom Web Services Server, Version 7.1

Adding a node or server Instance

If you have a running system with the cluster name previously defined in the configuration, and you need to add a node or server instance, you will need to publish the Telecom Web Services Server (TWSS) components to the new server instance. This is done by invoking the First Steps script with the -syncServers option specified.

About this task

The processing of -syncServers makes use of the existing configuration and does not display the interactive configuration information window.

Follow these steps to publish the TWSS components to the new server instance:

  1. On the server where Telecom Web Services Server base components have been installed, log in as root or with another valid ID.
  2. Navigate to the following directory: was_root/installableApps/TWSS-Base/firststeps.
  3. Edit the firststeps.properties file.
    Specify the scope for the operation by making sure that the name of the target server or cluster is specified for each of the following parameters:
    • AGTargetScope
    • SPMTargetScope
    • SPTargetScope
    In brief, the scope parameters can be specified as follows:
    • 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 more details about the configuration parameters and their values, refer to the topic Performing the configuration silently.
    Note: You can find copies of the original and new properties files in the logs timestamp directory. This applies to all nodes.
  4. Perform the configuration by launching the First Steps script. Enter the command parameters on a single line:
    ./firststeps.sh @firststeps.properties -syncServers -DBServerAdminPass db_admin_pw 
    -DBServerUserPass db_user_pw -WASAdminPass was_admin_pw
    -JMXAdminPass jmx_admin_pw -TWSSUserPass twss_user_pw wsadmin_options
    Where:
    • firststeps.properties is the name of your saved configuration file.
    • db_admin_pw is the password for the Administrator user on the database server.
    • db_user_pw is the password for the user that will access the database server during runtime, for example twssuser.
    • was_admin_pw is the password for the WebSphere® Application Server Administrator user.
    • jmx_admin_pw is the password for the WebSphere Application Server Administrator user that you are using for JMX notifications. Required if WebSphere security is enabled. .
    • twss_user_pw is the password for the user ID that you will use 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.
    • 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
Results

The TWSS components are published to the target server instance, or to the server instances in the target cluster.

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.



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