WebSphere brand IBM WebSphere Telecom Web Services Server, Version 7.1

Performing the configuration silently

For subsequent installations after you have run the First Steps script, or simply as an alternative to using the interactive wizard, you can configure silently.

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.

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.
  1. Start the deployment manager and all associated node agents.
  2. On the deployment manager server where the Telecom Web Services Server base components have been installed, log in with the same WebSphere Administrator ID that was used for the installation.
  3. Navigate to the following directory: was_root/installableApps/TWSS-Base/firststeps.
  4. Open the firststeps.properties file in a text editor, then edit the configuration properties. The following table lists a representative sample of the configuration file parameters. The detailed descriptions for all of the parameters can be found in the configuration file itself.
    Note: Do not populate the password fields. You will supply all of the passwords as command-line parameters at runtime.
    Table 1. Configuration file properties
    Property Type Description
    PropertyOrder hidden A comma-delimited list (name1, name2, name3) of key values that define the presentation order of the properties in the Configuration Information Window. The default order is the order listed in this document.
    Firststeps Configuration NamedSeparator Separator bar with the value of Firststeps Configuration.
    ConfigurationMode choice One of the following:
    Initial
    First-time installation of Telecom Web Services Server. All configuration values are reset according to the data you specify. Associated policies, configuration data tables, and runtime state tables are reset.
    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
    Migration from a previous version. Existing configuration values are used whenever possible; new values are used when no existing values are found. Associated policies and configuration data tables are preserved, but runtime state tables are reset.
    Update
    Installation of a service update, such as an interim fix or fix pack. Use when instructed to do so in a readme file. Existing configuration values are used whenever possible; new values are used when no existing values are found. Associated policies, configuration data tables, and runtime state tables are preserved.
    Note: The existing database is retained only if all of the following values in the response file 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.
    DatabaseConfiguration named separator A separator bar with the value of Database Configuration.
    DatabaseServerType choice Either DB2 or Oracle. The default value is DB2.
    DatabaseServerAccessMode choice 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.
    DatabaseServerHostname string The host name or IP address for the database server. The default value is localhost.
    DatabaseServerPort integer 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.
    DatabaseDriverRootPath directory The full path to the directory that contains JDBC driver JAR files for the database client. Specify the same value as the WebSphere environment variable DB2UNIVERSAL_JDBC_DRIVER_PATH or ORACLE_JDBC_DRIVER_PATH.
    Examples:
    • 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.
    DatabaseServerAdministratorUsername string 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
    DatabaseServerAdministratorPassword password Do not populate this field.
    DatabaseServerUserName string The name of the user that will access the database server during runtime, for example twssuser.
    DatabaseServerUserPassword password Do not populate this field.
    DatabaseName string 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.

    DatabaseLocale string The locale string used to initialize the database. The default value is US.
    WASConfiguration named separator A separator bar with the value of WAS Configuration.
    WASAdminUserName string The Administrator user name for WebSphere® Application Server.
    WASAdminPassword password Do not populate this field.
    AGTargetScope string The target scope for the Access Gateway: either the name of a cluster, a name in the form node/server, or None.
    SPMTargetScope string The target scope for the Service Policy Manager: either the name of a cluster, a name in the form node/server, or None.
    SPTargetScope string The target scope for the Service Platform components: either the name of a cluster, a name in the form node/server, or None.
    WCDefaultHostPort integer 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.

    CommonRuntimeFiles hidden A comma-separated list of relative paths to runtime files that are copied to the deployment manager, used for publishing the files to all server instances. The paths are relative to was_root.
    Example:

    plugins/ com.ibm.soa.common.reservation_1.0.0.jar,
    lib/ext/common-statscache.jar
    lib/ext/spm-ws-access-client.jar,
    lib/ext/spm-ws-admin-client.jar,
    properties/version/TWSS.product,
    properties/version/TWSS.sp.component,
    properties/version/TWSS.esb.component,
    properties/version/TWSS.services.component,
    properties/version/nif/componentmaps/componentmap.twsscore.xml

    AGRuntimeFiles hidden A comma-separated list of relative paths to Access Gateway runtime files that are copied to the deployment manager, used for publishing the files to all server instances. The paths are relative to was_root.
    Example:

    lib/ext/addressmasking.jar,
    lib/ext/common-utils.jar,
    lib/ext/esb-common-utils.jar,
    lib/ext/esb-handlers.jar,
    lib/ext/jmxnotification.jar,
    lib/ext/msgelementremover.jar,
    lib/ext/groupresolution.jar,
    lib/ext/networkstatistics.jar,
    lib/ext/policyretrieval.jar,
    lib/ext/serviceauthorization.jar,
    lib/ext/serviceinvocation.jar

    JMSQueuePath directory 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.
    JMSQueueMode choice If a file store or data store is used, the root path where the bus members store their data. The default value is file store.
    JMSDatastoreJNDIName string The JNDI name of a JDBC data source where the data store's JMS queue data is stored. The default value is jdbc\TWSSDB.
    JMXAdminUserName string 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.
    JMXAdminPassword password Do not populate this field.
    TWSSConfiguration named separator A separator bar with the value of TWSS Configuration.
    TWSSUserName string 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.
    TWSSUserPassword password Do not populate this field.
    SPMPolicyAccessURL URL The endpoint URL for the Service Policy Manager Policy Access interface. The default value is http://hostname:port/SPM/Access/services/PolicyAccess.
    GroupResolutionURL URL The endpoint URL for the Address List Management interface. The default value is http://hostname:port/TWSS/ParlayX21/Admin/AddressListManagement/IMS/services/AddressListManagement.
    PrivacyImplementationEnabled Boolean true if you are installing a privacy implementation; false if not.
    AccessGatewayRootURL 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.
    ServicePlatformRootURL 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.
    PolicyAdminGroupName string The group name from the user registry used for the PolicyAdministrator role.
    TWSSAdminGroupName string The group name from the user registry used for the TWSS Administration Console.
    NotifyAdminGroupName string The group name from the user registry used for the Notification Management Administration interface.
  5. Save your changes and close the text editor.
  6. Perform the configuration by launching the First Steps script. Enter the command parameters on a single line:
    ./firststeps.sh @firststeps.properties -silent -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
    Note: If the silent option is provided, you must provide the passwords necessary for the setup. For example, you can use the database administrator password to create the tables. You must provide the passwords as command-line arguments.
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.