Installing new Sametime Gateway EAR and WAR files for FP1

Finish installing the Sametime® Gateway server by deploying new EAR and WAR files.

Procedure

Stop all of the Sametime Gateway processes on the server:
Note: In a clustered environment, perform this step on the deployment manager.

Be sure to check for the following processes and stop them all:
- Sametime Gateway Server instances
- WebSphere® Node Agent
- WebSphere SIP proxy server instance
- Deployment manager (DMGR) server
If there are any Java™ processes listed in the operating system processes table, forcefully end them now.
Start the Sametime Gateway server and wait to make sure it has started before proceeding.
- Single server:
  Start the server process. For information on starting a Sametime Gateway server, see Starting a single Sametime Gateway server.
  Important: Do not proceed to step 4 until the server has started.
- Clustered deployment:
  Start the Deployment Manager (DMGR) process. For information on starting the deployment manager, see Stopping and starting the deployment manager.
  Important: Do not proceed to step 4 until the deployment manager has started.
Open the folder STGW9.0.1 and edit the setenv file that is appropriate for your platform:
- Linux™: /home/myuser/STGW9.0.1/setenv.sh
- Windows™: C:\STGW9.0.1\setenv.bat
Change the following environment variable values to match your environment if needed:
- WASDIR is the WebSphere application installation location
- GWProfileName is the profile name of the upgraded Sametime Gateway server
- WASUSERDATADIR is the profile location path
- SCHEMANAME is the DB2® schema name used by the Sametime Gateway server
For example:
```
WASDIR=C:\Program Files\IBM\WebSphere\AppServer
WAS_USER_NAME=stgwadmin
WAS_PASSWORD=stgwadmin
```
Save and close the setenv file.
Use the following commands to run the reDeploySTGW batch file:
- Linux:
```
chmod +x ./reDeploySTGW.sh
chmod +x ./setenv.sh
dos2unix ./reDeploySTGW.sh
dos2unix ./setenv.sh
./reDeploySTGW.sh
```
- Windows: reDeploySTGW.bat
The results are written to the reDeploySTGW.log.txt output log.

To validate that the redeployment was successful, make sure the following lines appear in the reDeploySTGW.log.txt output log:

ADMA5013I: Application Sametime Gateway Core installed successfully.
ADMA5013I: Application Sametime Gateway User locator installed successfully.
ADMA5013I: Application Sametime Gateway Event logger installed successfully.
ADMA5013I: Application Sametime Gateway Authorization controller installed successfully.
CWLAA1001I: The Integrated Solutions Console module was deployed successfully.

Important: Make sure that the word "exception" does not appear in the output file.

Restart Sametime Gateway:
- Single server: stop and then restart the server. This task is now complete; proceed to the next task.
- Clustered deployment: stop and then restart the deployment manager, and then continue with step 10.
Start all node agents on the Sametime Gateway (STGW) and WebSphere SIP proxy servers.
Log in to the deployment manager's Integrated Solutions Console and synchronize your changes to all nodes in the cluster:
1. Click System Administration > Nodes.
2. Select all nodes in the cluster, and then click Full Resynchronize.