Follow these steps to save the updated WebSphere® Application Server configuration
after you have uninstalled Presence Server.
About this task
Complete these steps after you have uninstalled the
Presence Server application and removed the
Trust Association Interceptor definitions
from the
WebSphere Application Server administrative
console.
- Open the WebSphere Application Server administrative
console on the deployment manager.
- Save the updated configuration:
- In the navigation panel, click .
- Select Synchronize changes with Nodes.
- Click Save.
- Stop the deployment manager and node agents using the administrative
console or by running the following commands:
- Stop the deployment manager. Run
the following command:
was_profile_root/bin/stopManager.sh -username user_name -password password
was_profile_root/bin/stopManager.sh -username user_name -password password
Where:
- The was_profile_root path
contains the name of the deployment manager profile (for example,
Dmgr01).
- user_name represents your WebSphere Application Server administrator
user ID.
- password represents the password associated
with your user_name.
- Stop each node agent. Run
the following command:
was_profile_root/bin/stopNode.sh -username user_name -password password
was_profile_root/bin/stopNode.sh -username user_name -password password
Where:
- The was_profile_root path
contains the name of a federated node profile (for example, Custom01).
- user_name represents your WebSphere Application Server administrator
user ID.
- password represents the password associated
with your user_name.
- Optionally, restart the deployment manager and node agents:
- Start the deployment manager. Run
the following command:
was_profile_root/bin/startManager.sh
was_profile_root/bin/startManager.sh
Where:
- The was_profile_root path
contains the name of the deployment manager profile (for example,
Dmgr01).
- Start each node agent. Run
the following command:
was_profile_root/bin/startNode.sh
was_profile_root/bin/startNode.sh
Where:
- The was_profile_root path
contains the name of a federated node profile (for example, Custom01).