I have HCL Connections 6.5 installed on Linux - RHEL 7.8. I want to create a service in Linux that will restart all of WebSphere when we reboot our server.
I want the deployment manager, nodeagent, Connections server, IHS service and db2services to restart.
Using this approach I've set up Dmgr and nodeagents to start automatically and for the application servers I used the Monitoring policy settings in IBM Solutions Console
Hi Anatoly, Thanks for the response. Yes, I have done this for node agent and DMGR, it works.
Setup the monitoring policy setting, the application server will start automatically when nodeagent is in running state.
However, will the Application server stop automatically when we reboot the Linux OS without stopping Application server? Will monitoring policy setting do the job...
Hi Anatoly, Thanks for your response. Yes, nodeagent will start the app servers when Linux OS booting up but what about stopping WAS server automatically? will this monitoring policy help to stop the WAS server when shutdown the Linux OS.
Hello Martin, Can you please me to the auto startup script for DB2 as well. And where did you mentioned in the WAS script that it should start after DB2 gets started?
the dependency is configured in the websphere.service description.
The 2 file are placed in the directory /etc/systemd/system and then added as service to the multi-user.target.wants directory. I don't know the correct command now.
You need to adapt the service descriptions to your needs. e.g. run as root.
Hello Martin, I have installed WAS and Connections using root user, not created any non-root user.
I need your help that how to stop using root user and how to pass the password while stop the script. Please refer the below output. Thanks.
[root@connections startup]# ls startAllNodes.sh startAllServer.sh startInfrastructure.sh stopAllNodes.sh stopAllServer.sh stopInfrastructure.sh
[root@connections startup]# ./stopInfrastructure.sh ERROR: Script must not be executed as root.
[root@connections startup]# ./stopAllServer.sh Profile: /local/connections/IBM/WebSphere/AppServer/profiles/Dmgr01 Profile: /local/connections/IBM/WebSphere/AppServer/profiles/AppSrv01 Process with PID is running. Need to stop Stop Server /local/connections/IBM/WebSphere/AppServer/profiles/AppSrv01 - ICCluster_server1 ADMU0116I: Tool information is being logged in file /local/connections/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/ICCluster_server1/stopServer.log ADMU0128I: Starting tool with the AppSrv01 profile ADMU3100I: Reading configuration for server: ICCluster_server1 Realm/Cell Name: <default> Username:
Regarding the startInfrastructure.sh and stopInfrastrucuture.sh scripts. Remove this 4 lines from the script which prevent the start as root:
if [ "$EUID" == "0" ]; then echo "ERROR: Script must not be executed as root." exit 1 fi
!!! All scripts contain the installation path of the WAS Server. You may need to adapt this path. !!!
Regarding the stop - missing password.
The username and password is configured in the soap.client.props found in <WASProfile>/properties/ direcotry of all profiles. The configured attributes are
If you don't have configured wasadmin username and password in soap.client.properties, you have to append them to each row:
-stopArgs "-username wasadmin -password *******"
Then you can start/stop the services using these commands directly:
service IC01_DM_was.init start
service IC02_NA_was.init start
service IC03_ICCluster_was.init start
service IC04_IBMViewer_was.init start
service IC05_IBMDocsProxy_was.init start
service IC06_IBMDocs_was.init start
service IC07_IBMConversion_was.init start
service IC08_IHS.init start
service IC01_DM_was.init restart
service IC02_NA_was.init restart
service IC03_ICCluster_was.init restart
service IC04_IBMViewer_was.init restart
service IC05_IBMDocsProxy_was.init restart
service IC06_IBMDocs_was.init restart
service IC07_IBMConversion_was.init restart
service IC08_IHS.init restart
service IC08_IHS.init stop
service IC07_IBMConversion_was.init stop
service IC06_IBMDocs_was.init stop
service IC05_IBMDocsProxy_was.init stop
service IC04_IBMViewer_was.init stop
service IC03_ICCluster_was.init stop
service IC02_NA_was.init stop
service IC01_DM_was.init stop
In this script, where did you mentioned that server have to start after nodeagent started. I am talking about the dependency service, meaning that nodeagent should get started before the server start.
I'm not sure, but I think that init.d calls this scripts in the same runlevel in alphabetical order - that's why I named them this way. At least, it seams to work for us. ;-)