Verifying a Sametime Proxy Server installation

Open the IBM® Sametime® browser-based client to verify that the installation of a primary node was successful.

About this task

Follow these steps to verify the installation on a primary node. These instructions do not apply to verifying the installation on a secondary node because it does not have installed applications. To verify installation on a secondary node, verify that the installation completed successfully.

Procedure

Using a browser, log in to the Sametime Proxy Server application with the following URL:
```
http://serverhostname.domain:port/stwebclient/index.jsp
```
Replace serverhostname.domain with your server name and add the port number. For example:
```
http://stproxy1.example.com:9080/stwebclient/index.jsp
```
Tip: To verify the port number being used by the application, log in to the console on the Sametime Proxy Server:
1. Enter the following URL, replacing serverhostname.domain with the fully qualified domain name of the server.
  http://serverhostname.domain:8600/ibm/console
  8600 is the default port when the Proxy Server is installed as a Cell Profile.
  For example:
  http://stproxy1.example.com:8600/ibm/console
2. Enter the WebSphere® Application Server User ID and password that you created when you installed the server.
3. Click Servers > WebSphere Application Servers > STProxyServer > ports > WC_defaulthost to find the port number.
You can also verify the HTTP port number being used by the Sametime Proxy Server by opening the AboutThisProfile.txt file for the Sametime Proxy Application Server Profile and use the setting specified for the HTTP transport port. The default profile name is STPPNProfile1 when you use a deployment plan to install the server.
Verify that you can create or view contacts.
Verify that the new server was successfully federated to its deployment manager.
The deployment manager handles administration tasks for the cell to which the new server is federated. If the server was not successfully federated, you will encounter problems when you attempt to administer it; you will also be unable to create a WebSphere Network Deployment cluster. Avoid these problems by verifying that the federation was successful and completing federation manually if needed.
1. On the new Sametime Proxy Server, navigate to the following directory: install_root/profiles/profile_name/logs
2. Open the addNode.log file and check for confirmation that the new node was successfully added to the cell's deployment manager.
3. If the node was not federated successfully, use the addNode command to complete the federation by running the following command:
  AIX® or Linux™
```
install_root/bin/addNode.sh -profileName profile_name dmgr_host dmgr_SOAP_port 
```
  Windows™
```
install_root\bin\addNode.bat -profileName profile_name dmgr_host dmgr_SOAP_port 
```
  where:
  - dmgr_host is the fully qualified host name of the deployment manager (typically the Sametime System Console).
  - dmgr_SOAP_port is the SOAP port of the deployment manager.
    The SOAP port is 8879 by default; you can check the port value by opening the deployment manager's WebSphere Integrated Solutions Console and clicking System Administration > Deployment Manager Communications > Ports.
Check the server's status in the WebSphere Integrated Solutions Console by completing the following steps:
- Cell deployment:
1. On the new server, log in to the WebSphere Integrated Solutions Console as the WebSphere administrator:
  - If you installed the server as a primary node, use the following URL:
    http://host_name.domain:8700/ibm/console
    where host_name.domain is the fully qualified host name of the server, and 8700 is the default port.
  - If you installed the server as a cell, use the following URL:
    http://serverhostname.domain:8800/ibm/console
    where host_name.domain is the fully qualified host name of the server, and 8800 is the default port.
2. In the navigation tree, click Servers > Server types > WebSphere application servers.
3. Find the new server in the list and verify that the status column shows that the server is running.
- Federated deployment:
1. On the server hosting the Sametime System Console, log in to the WebSphere Integrated Solutions Console as the WebSphere administrator:
  
  https://host_name.domain:port/ibm/console
  
  where host_name.domain is the fully qualified host name of the server, and 8701 is the default port. For example:
  
  https://sametime.example.com:8701/ibm/console
2. In the navigation tree, click Servers > Server types > WebSphere application servers.
3. Find the new server in the list and verify that the status column shows that the server is running.