Preparing WebSphere Application Server before updating to FP1

Before updating to IBM® Sametime® 9.0.1 Feature Pack 1 on a server running IBM WebSphere® Application Server, verify that the standard WebSphere server start and stop scripts function correctly.

About this task

During the update to FP1, the installer starts and stops the node agent and servers using the standard WebSphere scripts. If you made any customizations to your server, these scripts might fail. Ensure that the scripts work properly for the current server by completing the following steps.

Procedure

(Windows™ only) Remove Windows services, because they interfere with the upgrade.
On the server hosting the deployment manager, log in to the WebSphere Integrated Solutions Console as the WebSphere administrator.
Verify that the deployment manager has a valid connection to the server's node agent by stopping and starting the server that you want to update:

When you installed Sametime servers on IBM WebSphere, each server used a deployment type; either Cell, Primary Node (PN), or Secondary Node (SN). A server installed as PN or SN typically uses the Sametime System Console as its deployment manager. A server installed as a Cell deployment includes its own deployment manager (the cell dmgr).
1. In the navigation list, click Servers > WebSphere application servers.
2. In the list of servers, Stop the server that you will upgrade.
3. After the server is completely stopped, Start it again.
Verify that the nodes are synced:
1. In the navigation list, click System Administration > Nodes.
2. In the list of nodes, check the Status column for each node, and make sure that they are all synced.
Move to the server that you want to upgrade and log in as root (AIX®, Linux™) or the administrator (Windows).
Open a command window and change to the server_profile\bin directory.
Run the following server scripts to verify that they function correctly.

The following examples refer to a Sametime Media Manager, which runs on a Linux server. Be sure to substitute the appropriate server name for the server you are working on, and use .bat as the file's extension on Windows (instead of .sh).
1. Stop the application server:
```
sh ./stopServer.sh STMediaServer -username wasadmin -password password
```
2. Stop the node agent:
```
sh ./stopNode.sh STMediaServer -username wasadmin -password password
```
3. Sync the nodes:
```
sh ./syncNode.sh Dmgr_Host_Name 8703 -username wasadmin -password password
```
4. Start the node agent:
```
sh ./startNode.sh
```
5. Start the application server:
```
sh ./startServer.sh STMediaServer
```

What to do next

If there is an issue, such as a server stop or a server start times out, takes too long, or fails, then this issue should be addressed first before attempting the update to Feature Pack 1.