Configuring the WebSphere Application Servers to start when the nodeagent starts

WebSphere Application Servers

Configuring the WebSphere Application Servers to start when the nodeagent starts


1. Log into the Integrated Solutions Console.
2. Navigate to Servers > Server Types > WebSphere application servers.

3. Click the first server in the list.

4. Under Server Infrastructure, expand Java and Process Management.

5. Click Monitoring Policy.

6. Change the field Node restart state to running.

7. Click OK.

8. Save the changes to the master configuration.

9. Repeat for the remaining WebSphere Application Servers.

p.s.

Configuring the nodeagent to start at boot (Linux)

Perform the following steps to configure the nodeagent to the Startup group when the Linux operating system starts.

1. Log in to the Linux host.
2. Make a note of the WebSphere profiles on the server. These can be found under /opt/IBM/WebSphere/AppServer/profiles
   Note: The path might need to be modified, depending on the AppServer version.
3. Open a terminal window and change to the following directory: /opt/IBM/WebSphere/AppServer/bin
   Note: The path might need to be modified, depending on the AppServer version.
4. Run the following command for each of the profiles. In the following command, the profile name is Docs01:
   ./wasservice.sh -add nodeagent -serverName nodeagent -profilePath “/opt/IBM/WebSphere/AppServer/profiles/Docs01“ -logRoot “/opt/IBM/WebSphere/AppServer/profiles/Docs01/logs/nodeagent” -restart true -startType automatic
5. Restart the server to test if the nodeagent automatically started.
6. Repeat for each Linux-based WebSphere Application Server.

Configuring the nodeagent to start at boot (Windows)

Perform the following steps to configure the nodeagent to the Startup group when the Windows operating system starts.

1. Log in to the Windows host.
2. Make a note of the WebSphere profiles on the server. These can be found under C:\IBM\WebSphere\AppServer
3. Open a command prompt with administrative rights and change to the following directory: C:\IBM\WebSphere\AppServer\bin
4. Run the following command for each of the profiles. In the following command, the profile name is DocsWin01:
   wasservice.exe -add nodeagent -serverName nodeagent -profilePath “C:\IBM\WebSphere\AppServer\profiles\DocsWin01” -logRoot “C:\IBM\WebSphere\AppServer\profiles\DocsWin01\logs\nodeagent” -restart true -startType automatic
5. Restart the server. After the restart, it can take up to 5 minutes for all of the soffice processes to initiate. Refer to the task monitor for these processes.
6. Repeat for each Windows-based WebSphere Application Server.