unitas99007
Active Member
I've got a Red Hat Linux HTML server thats been acting kind of unstable. I'd like a quick script to systematically shutdown all JDE /Websphere /HTTP services and the management agent, and then another one to start them all up again. Here's what I've got so far.
Keep in mind scripts are stored at /web, and all related items are installed in the following locations:
JDE management agent - /web/JDE_HOME
IBM HTTP Server - /web/HTTPServer
Websphere 6.1 - /web/WebSphere61
This script, "start_services.sh", to start all services:
<font class="small">Code:</font><hr /><pre>
cd /web/JDE_Home/bin
./restartAgent
cd /web/HTTPServer/bin
./apachectl start
cd /web/WebSphere61/AppServer/bin/
./startServer.sh "server1"
</pre><hr />
And this script, "stop_services.sh", to stop all services:
<font class="small">Code:</font><hr /><pre>
cd /web/WebSphere61/AppServer/bin
./stopServer.sh "server1"
cd /web/HTTPServer/bin
apachectl stop
</pre><hr />
This all works great. However, if I start or stop our application server for our HTML that way (ie, startServer.sh "test_j2ee_83"), it cannot be managed by server manager, and give permission denied errors and that sort of thing.
Any ideas on finishing out this script the proper way??
Keep in mind scripts are stored at /web, and all related items are installed in the following locations:
JDE management agent - /web/JDE_HOME
IBM HTTP Server - /web/HTTPServer
Websphere 6.1 - /web/WebSphere61
This script, "start_services.sh", to start all services:
<font class="small">Code:</font><hr /><pre>
cd /web/JDE_Home/bin
./restartAgent
cd /web/HTTPServer/bin
./apachectl start
cd /web/WebSphere61/AppServer/bin/
./startServer.sh "server1"
</pre><hr />
And this script, "stop_services.sh", to stop all services:
<font class="small">Code:</font><hr /><pre>
cd /web/WebSphere61/AppServer/bin
./stopServer.sh "server1"
cd /web/HTTPServer/bin
apachectl stop
</pre><hr />
This all works great. However, if I start or stop our application server for our HTML that way (ie, startServer.sh "test_j2ee_83"), it cannot be managed by server manager, and give permission denied errors and that sort of thing.
Any ideas on finishing out this script the proper way??