Managing multiple Application Servers on the same host


When there are multiple Application Servers configured on the same host, you manage the additional Application Servers through the Infrastructure Management window.

You can perform any of the following management tasks:

To start a specific Application Server

The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

To stop a specific Application Server

The stop operation ends running jobs and stops the Application Server, providing a controlled shutdown. You can select options for managing the running jobs.

Note

You cannot use the stop operation on an Application Server to which a BMC Server Automation Console is connected.

  1. In the BMC Server Automation Console, from the Configuration menu, select Infrastructure Management.
  2. Expand the Application Servers node.
  3. Right-click the Application Server and select Stop.
  4. In the Stop Application Server dialog box, select the method for managing any running jobs:
    • Stop immediately without waiting for running jobs to finish.
    • Stop when all running jobs finish.
    • Stop when all running jobs finish or after specified number of minutes, whichever comes first.
  5. Click OK.

To redeploy a stopped Application Server

The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

To terminate a specific Application Server

The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

To restart a specific Application Server

 

The Restart operation first stops the Application Server and then starts it again. Use this operation to have configuration changes take effect.

Note

You cannot use the Restart operation on an Application Server to which BMC Server Automation Console is connected.

  1. In the BMC Server Automation Console, from the Configuration menu, select Infrastructure Management.
  2. Expand the Application Servers node.
  3. Right-click the Application Server and select Restart.

To remove an Application Server

The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

To add unmanaged deployments

If you have Application Servers which have been removed from the system, but have had their deployments preserved (using the Preserve deployment option), you can add the deployment back into the system without having to restart the launcher.

  1. Right-click an Application Server Launcher node and select Add Unmanaged Deployments.

    Note

    The option is displayed only if unmanaged deployments for this Application Server Launcher exist.

  2. In the Add Unmanaged Deployments dialog box, select one or more unmanaged deployments that you want to add to the Application Server Launcher.
  3. Click OK.

The Application Server Launcher added the deployments you selected as managed Server Profiles, enabling you to manage these deployments as you would any other deployment in the system.

To edit the list of roles with Application Server Launcher access

At BMC Server Automation installation time, only the BLAdmins role is granted authorization to access to the Application Server Launcher. Users with this role can use the Edit Application Server Launcher Roles dialog box to grant or deny authorization to other roles.

  1. In the BMC Server Automation Console, from the Configuration menu, select Infrastructure Management.
  2. Expand the Application Server Launchers node.
  3. Right-click the Application Server Launcher and select Edit Role List.
  4. Under Available Roles, select one or more roles you want to have access to the Application Server Launcher. Then click the right arrow to move the role to the Selected Roles list.
     To remove roles from the selected list, under Selected Roles, select one or more roles. Then click the left arrow.
  5. When you have finished editing the list, click OK.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*