Updates to TWSS Information Center documentation

News


Abstract

This technote contains corrections to the Information Center documentation found on the product CD for TWSS Version 6.2. The Information Center on the Web has been updated to include these corrections. It can be accessed at http://publib.boulder.ibm.com/infocenter/wtelecom/v6r2m0/index.jsp

Content

Updates to the procedures for creating clusters

The procedures for creating clusters for Access Gateway, Service Policy Manager, and Service Platform are updated to correct technical errors.


Creating the cluster for the Access Gateway (the corrected information can be found at http://publib.boulder.ibm.com/infocenter/wtelecom/v6r2m0/topic/com.ibm.twss.install.doc/cluster_esb_t.html):

The correct version number for WebSphere Application Server - Network Deployment is 6.0.2.19. Make the following changes in the procedure:

Replace step 1 with the following:

  1. On the server where you plan to install the deployment manager, install the following prerequisite software:
    1. Install WebSphere Enterprise Service Bus, Version 6.0.2.0. If you use the Launchpad installer, the WebSphere ESB installation will install the required version of WebSphere Application Server Network Deployment.
      Important: Do not attempt to install WebSphere Enterprise Service Bus to a directory path that includes National Language Characters. If the path contains National Language Characters, the installation will not complete.
    2. Install WebSphere Enterprise Service Bus, Version 6.0.2.2 (Fix Pack 2), using the detailed installation instructions provided with the fix pack. The following packages are contained in the fix pack and should be installed in the order listed:
      • 6.0.2 -WS-WAS- <platform> - FP0000019.pak
      • 6.0.2 -WS-WASjavaSDK- <platform> - FP0000019.pak
        Note: Note that the installation of this Java™ SDK package is a two-stage process. Follow the onscreen instructions carefully for this package.
      • 6.0.2.19-WS-WAS-IFPK24533.pak
      • 6.0.2.9-WS-WAS-IFPK35039.pak
      • 6.0.2.19-WS-WAS-IFPK44764.pak
      • 6.0.2.13-WS-WAS-IFPK33254.pak
      • 6.0.2.19-WS-WAS-IFPK45268.pak
      • 6.0.2.19-WS-WAS-IFPK44294.pak
      • 6.0.2-WS-WPS-ESB- <platform> FP0000002.pak
        Note: After you install this fix pack, WebSphere ESB will be at Version 6.0.2.2 and WebSphere Application Server Network Deployment will be at Version 6.2.0.19.
    3. Install the database client included with your database software onto the deployment manager server.

Replace step 4 with the following:

4. On each server where you plan to install application servers, install the following prerequisite software:
  1. Install WebSphere Enterprise Service Bus, Version 6.0.2.0. If you use the Launchpad installer, the WebSphere ESB installation will install the required version of WebSphere Application Server Network Deployment.
    Important: Do not attempt to install WebSphere Enterprise Service Bus to a directory path that includes National Language Characters. If the path contains National Language Characters, the installation will not complete.
  2. Install WebSphere Enterprise Service Bus, Version 6.0.2.2 (Fix Pack 2), using the detailed installation instructions provided with the fix pack. The following packages are contained in the fix pack and should be installed in the order listed:
    • 6.0.2 -WS-WAS- <platform> - FP0000019.pak
    • 6.0.2 -WS-WASjavaSDK- <platform> - FP0000019.pak
      Note: Note that the installation of this Java SDK package is a two-stage process. Follow the onscreen instructions carefully for this package.
    • 6.0.2.19-WS-WAS-IFPK24533.pak
    • 6.0.2.9-WS-WAS-IFPK35039.pak
    • 6.0.2.19-WS-WAS-IFPK44764.pak
    • 6.0.2.13-WS-WAS-IFPK33254.pak
    • 6.0.2.19-WS-WAS-IFPK45268.pak
    • 6.0.2.19-WS-WAS-IFPK44294.pak
    • 6.0.2-WS-WPS-ESB- <platform> FP0000002.pak
      Note: After you install this fix pack, WebSphere ESB will be at Version 6.0.2.2 and WebSphere Application Server Network Deployment will be at Version 6.2.0.19.
  3. Install the following service packs using the graphical interface or the command line:
    • PK29364
    • JR24879
    • PK32396

      For the latest information about service packs, check the WebSphere Telecom Web Services Server Support Web page. The additional service packs can be downloaded from the WebSphere Application Server Network Deployment Support Web page.
  4. Install the database client included with your database software on each server.


Note that step 7 (the AddNode command) should be repeated for each application server that will be added to the cell.


Creating the cluster for the Service Policy Manager (the corrected information can be found at http://publib.boulder.ibm.com/infocenter/wtelecom/v6r2m0/topic/com.ibm.twss.install.doc/cluster_spm_t.html):

This topic incorrectly describes the process for creating the cluster for the Service Policy Manager. The correct process resembles that for creating the Service Platform cluster.

Replace the entire contents of the existing topic with the following:

Creating the cluster for the Service Policy Manager

You must create a cluster for the Service Policy Manager. Before you create the cluster, you need to install the prerequisite software, create the deployment manager and application servers, and add the configured application servers to the deployment manager.
Before you begin, you must have completed the following steps:
  • Installed and configured the database server
  • Created the deployment manager and application servers
  • Federated the configured application server nodes to the deployment manager

Note: You should plan to deploy the Service Policy Manager on a different cluster from the Access Gateway. However, you can deploy it on the same cluster with the Service Platform components and the Web service implementations.

If possible, use the default profiles for WebSphere® Application Server Network Deployment. Also, avoid customizing the profile with the Profile Management Tool. If you need to use an advanced profile, do not select the for development profile. Doing so can cause problems with the WebSphere Application Server SIP container.

After you have installed the prerequisite software, you must federate the application server nodes into the deployment manager. Then, you can create the cluster using the Integrated Solutions Console. You can create the first cluster member from one of the application servers you federated into the deployment manager. After you have created each application server, you must add each application server to the network deployment manager cell. Additional cluster members can be added using the Integrated Solutions Console at a later time, as needed.
  1. On the physical server where you plan to install the deployment manger, install WebSphere Application Server Network Deployment, Version 6.1.0.0, using the launchpad:
    1. When prompted to select the WebSphere Application Server environments, select Cell (deployment manager and a managed node).
    2. Complete the installation.
    3. Install WebSphere Application Server Network Deployment, Version 6.1.0.11 (Fix Pack 11).
    4. Install the database client included with your database software onto the deployment manager server.
      Refer to the WebSphere Application Server information center for detailed information about the installation.
  2. On each physical server where you plan to install an application server, install WebSphere Application Server Network Deployment, Version 6.1.0.0 using the launchpad:
    1. When prompted to select the WebSphere Application Server environments, select Application Server.
    2. Complete the installation.
    3. Repeat this step for each application server that will be added to the cell.
    4. Install WebSphere Application Server Network Deployment, Version 6.1.0.11 (Fix Pack 11) on each physical server where application servers have been created.
    5. Install the following service pack:
      PK35193
      For the latest information about service packs, check the WebSphere Telecom Web Services Server Support Web page. A link is provided below.
    6. Install the database client included with your database software on each server.
      Refer to the WebSphere Application Server information center for detailed information about the installation.
  3. Before you can add the application servers to the deployment manager, you may need to update the hosts file on each physical server.
    1. Open the hosts file in a text editor. The hosts file is in the /etc/hosts directory.
    2. Verify that there is a unique entry for the IP address of the server. By default there is a localhost entry, such as:

      127.0.0.1 host_name.domain.com host_name localhost.localdomain localhost

      Replace the default entry with the following line:

      127.0.0.1 localhost.localdomain localhost
    3. Then add a new line that specifies the IP address of the server.

      ip_address host_name.domain.com host_name

      Where:
      ip_address is the IP address of the server.
      host_name is the host name of the server.
      domain is the domain of the server.
      For example:

      9.32.175.169 testbox.myco.com testbox
    4. Save and close the hosts file.
    5. Repeat this step for each application server.
  4. Use the addNode command to add the application server to the cell.
    1. On the physical server that you want to add to the deployment manager, change to the bin directory for the application server profile, such AppSrv01/bin. For example:

      cd was_profile_root/bin

      Note: To add subsequent nodes, follow the prescribed steps below:
    2. Run the addNode command. For example:

      ./addNode.sh dmgr.domain.com

      Where:
      dmgr.domain.com is the fully qualified host name of the deployment manager server.
    3. To verify that the application servers were added to the cell, review the addNode.log. When you run the addNodecommand, a message displays in the location where the addNode.log is stored, for example: was_profile_root/AppSrv01/logs
    4. Repeat this step for each application server that will be added to the cell.
  5. Start the deployment manager, nodes, and servers.
    1. Start the deployment manager. Run the following command:
      AIX was_profile_root/bin/startManager.sh -username user_name -password password
      Linux was_profile_root/bin/startManager.sh -username user_name -password password
      Note: The user_name and password parameters are required only when security is enabled.

      Where:
      profile_name within the was_profile_root path is the name of the deployment manager profile
      user_name represents your WebSphere Application Server administrator user ID.
      password represents the password associated with your user_name.
    2. Start the nodes. Run the following command:
      AIX was_profile_root/bin/startNode.sh -username user_name -password password
      Linux was_profile_root/bin/startNode.sh -username user_name -password password
      Note: The user_name and password parameters are required only when security is enabled.

      Where:
      profile_name within the was_profile_root path is the name of a federated node profile
      user_name represents your WebSphere Application Server administrator user ID.
      password represents the password associated with your user_name.
    3. Start the servers. Run the following command:
      AIX was_profile_root/bin/startServer.sh server_name -username user_name -password password
      Linux was_profile_root/bin/startServer.sh server_name -username user_name -password password
      Note: The user_name and password parameters are required only when security is enabled.

      Where:
      profile_name within the was_profile_root path is the name of the application server profile
      server_name is name of the application server.
      user_name represents your WebSphere Application Server administrator user ID.
      password represents the password associated with your user_name.
  6. Log in to the Integrated Solutions Console:
    1. Open a browser and navigate to the following URL: https://host_name:port/ibm/console.
      Where:
      host_name is the fully qualified host name of the server where the application or the network deployment manager is deployed.
      port is the secured port used to access the console. The default is 9043.
      Note: The default unsecured port is 9060. If you use 9060, you must have "http" instead of "https" in the URL.
    2. Enter an administrator user ID and password.
    3. Click Log in.
  7. Federate the application server into the deployment manager cell.
    1. If both server processes are running, use the administrative console of the deployment manager to add the application server node into the cell.
    2. Point your browser at http://localhost:9060/ibm/console for example, to start the administrative console. It can also be started from the First steps console of the deployment manager profile.
    3. Log in and click System administration > Nodes > Add Node, and follow the wizard to add the node into the cell. You can use localhost for the Host field if both processes are on the same machine.
      Note: The SOAP port for the application server node is 8880 unless you changed the port during profile creation.
  8. Create an HTTP proxy server and associate it with the cluster that you have created. Refer to the WebSphere Application Server information center for additional information about setting up the proxy server.


Creating the cluster for Service Platform components (the corrected information can be found at http://publib.boulder.ibm.com/infocenter/wtelecom/v6r2m0/topic/com.ibm.twss.install.doc/cluster_cc_t.html):

Make the following changes in the procedure:

Disregard step 1d. (Instead, you will install service pack PK35193 in step 2e.)

In step 9, it is necessary to create a SIP proxy server only if you intend to deploy SIP-based Web service implementations.


Clarification to procedures for creating database tables

The procedures for creating database tables are updated to clarify the sequence for changing the permissions for the database script (crtsrvDb2 or crtsrvOra) and running it. To change permissions, you must be logged in as root. To run the script, you should be a database administrator.

The following procedures for creating database tables contain the appropriate corrections.
The corrections should be applied to the Information Center on the product CD.

In all of these topics, replace steps 1 through 2a with the following:
  1. Log in to the database server as root.
  2. Run the following command to change the permissions on the script.
    chmod 755 crtsrvDb2.sh
  3. Create the Access Gateway tables:
    1. From the command line, switch to a user ID with database administrator authority, such as db2inst1. For example, type:
      su - db2inst1

Then continue with step 2b ("If you are not already...").

For the Web service implementations only, change step 4 to read as follows:
If you are installing only the following Web service implementations, skip to step 7. If you are installing any of the other Web service implementations, continue with step 5.

From this point, proceed with the instructions as documented in the information center.


Updates to documentation for the Terminal Location over MLP Web service implementation

Topic title: Default service policies for Parlay X Terminal Location over MLP (the corrected information can be found at
http://publib.boulder.ibm.com/infocenter/wtelecom/v6r2m0/topic/com.ibm.twss.services.doc/termlocationmlp_policies_r.html)
The following updates apply:
  • The policy name service.common.MaximumTargets is incorrect. The correct name is service.config.MaximumTargets.
  • For service.standard.MaximumNotificationFrequency, the correct default value is 60000.
  • For service.standard.MaximumNotificationAddresses, the correct default value is 10.

Topic title: Parlay X Terminal Location over MLP (in Developing section) (the corrected information can be found at
http://publib.boulder.ibm.com/infocenter/wtelecom/v6r2m0/topic/com.ibm.twss.services.doc/termlocationmlp_dev_c.html)
Under Call flows, delete item 6: XML based on the MLP DTD using StAX, retrieves the required output values.

Topic title: Administering Parlay X Terminal Location over MLP (the corrected information can be found at
http://publib.boulder.ibm.com/infocenter/wtelecom/v6r2m0/topic/com.ibm.twss.services.doc/termlocationmlp_admin_c.html)
The following updates apply:
  • Under Common Service settings, replace Enable Usage Records and its description with the following: Enable Group Resolution - Whether or not to resolve the group URI to member URIs
  • Network Resource Name should be listed under Common Service Settings rather than under Services.
  • Under Services, Maximum Notification Count should be Maximum Notifications Count.
  • Under Terminal Location Notification Web service, the description for Ignore Check Immediate should say: If false, then the terminal's location is checked while setting up the geographical notifications (default true).

Add the following altitude information:
MLP provides the alt_acc (accuracy of the altitude returned) tag for SLIR/TLRR requests. For a potential altitude value, the parameter alt is used. The response handles the altitude information as follows:
  1. If the extended location request is being opted (where altitude is also expected) and if the response does not contain altitude information, then 0.0 is added for altitude in the response.
  2. If the extended location request is being opted and the response does contain altitude information, then the actual altitude value is added in the response.
  3. If the extended location is not being opted and the MLP Location server sends the altitude information, then the altitude value is not considered for the response.
  4. If the extended location request is not being opted and the response does not contain altitude information, then the response contains no value for altitude.

Other information pertaining to this topic:
  • In TWSS version 6.2, the Terminal Location over MLP Web service implementation does not provide support for SIP URIs that include the context.
  • In MLP 3.1, only the following URI format is supported: sip:+358-555-1234567;postd=pp22@example.com;user=phone
  • In MLP 3.1, the following URI format is not supported: sip:+358-555-1234567;phone-context=5;tsp=a.b@example.com;user=phone

Topic title: Usage records for Parlay X Terminal Location over MLP (the corrected information can be found at
http://publib.boulder.ibm.com/infocenter/wtelecom/v6r2m0/topic/com.ibm.twss.services.doc/termlocationmlp_records_c.html)
The following updates apply:
  • In the usage record format table (Table 1), the STATUSCODE attribute has an additional value besides those listed: 16 = FAILED_TRAFFIC_SHAPING.
  • In the Service data table for get operations (Table 2), the LOCATION_TYPE attribute has an additional value besides those listed: LAST.


Updates to planning and reference topics for Parlay-based Web service implementations

Topic title: Planning to install Parlay X Terminal Status over Parlay (the corrected information can be found at
http://publib.boulder.ibm.com/infocenter/wtelecom/v6r2m0/topic/com.ibm.twss.services.doc/termstat_backend_plan_c.html)
In the "JMS queues" section, remove the following sentence:
The Terminal Status queue is required to prevent errors when the PX21_Parlay.ear starts.

Topic title: Planning to install Parlay X Terminal Location over Parlay (the corrected information can be found at
http://publib.boulder.ibm.com/infocenter/wtelecom/v6r2m0/topic/com.ibm.twss.services.doc/termloc_plan_c.html)
In the "JMS queues" section, remove the following sentence:
The Terminal Location queue is required to prevent errors when the PX21_Parlay.ear starts.

Topic title: Planning to install Parlay X SMS over Parlay (the corrected information can be found at
http://publib.boulder.ibm.com/infocenter/wtelecom/v6r2m0/topic/com.ibm.twss.services.doc/sms_parlay_plan_c.html)
In the "JMS queues" section, remove the following sentence:
The SMS queue is required to prevent errors when the PX21_Parlay.ear starts.

Topic Title: Default service policies for Parlay X Terminal Status over Parlay (the corrected information can be found at
http://publib.boulder.ibm.com/infocenter/wtelecom/v6r2m0/topic/com.ibm.twss.services.doc/terminalstatus_policies_r.html)
The following policies do not apply to this Web service and should be removed from the list:
  • service.config.presence.PresenceServerSIPURI
  • service.config.presence.PresenceServerResourceName
  • service.config.ServiceImplementationName
  • service.config.presence.TerminalBusyRpidActivities
  • service.config.presence.PresenceFetchTimeoutInMillis
  • service.config.ims.InterOperatorIdentifier
  • service.config.AdditionalGroupURISchemes


No J2C activation specification for the MM7 Resource Adapter

When installing the MM7Connector.rar (MM7 Resource Adapter), there is no J2C activation specification associated with that adapter. Therefore, when you use the procedure titled "Installing the JCA adapter for SMPP and MM7-based Web service implementations" in the InfoCenter on the product CD, you should skip step 4 when deploying Parlay X Multimedia Messaging over MM7.

(the corrected information can be found at http://publib.boulder.ibm.com/infocenter/wtelecom/v6r2m0/topic/com.ibm.twss.install.doc/jca_adapter_t.html)

Related information

TWSS 6.2 Information Center

Rate this page:

(0 users)Average rating

Document information


More support for:

WebSphere Telecom Web Services Server

Software version:

6.2

Operating system(s):

AIX, Linux Red Hat - iSeries, Linux Red Hat - pSeries, Linux SUSE - iSeries, Linux SUSE - pSeries

Reference #:

1290337

Modified date:

2008-03-11

Translate my page

Machine Translation

Content navigation