IBM WebSphere - Start Stop Restart Administrative Agent

by
Jeremy Canfield |
Updated: March 08 2020
| IBM WebSphere articles
You must install WebSphere Application Server and create an administrative agent profile before you can start or stop the Administrative Agent.
These examples are based on a Linux system.
Start an administrative agent.
${WAS_INSTALL_ROOT}/profiles/your_admin_agent_profile/bin/startManager.sh your_admin_agent
. . .
ADMU3000I: Server adminagent open for e-business; process id is 12345
Stop an administrative agent.
${WAS_INSTALL_ROOT}/profiles/your_admin_agent_profile/bin/stopManager.sh your_admin_agent
. . .
ADMU4000I: Server adminagent stop completed.
A crontab job can be created to ensure the administrative agent is started when the system is rebooted.
@reboot bash ${WAS_INSTALL_ROOT}/profiles/your_admin_agent_profile/bin/startManager.sh your_admin_agent
Did you find this article helpful?
If so, consider buying me a coffee over at