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 start operation starts the Application Server and automatically deploys it, if it has not been deployed.

  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 Start.

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. 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

You can select a stopped Application Server and then redeploy it with a different profile type. This action is only available for stopped Application Servers.

  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 Redeploy.
  4. In the Redeploy Application Server dialog box, enter the following:
    • Base port: enter a new base port. base_port is a number that is combined with offset values to determine Authentication and Application Server port numbers. For example, the offset for the authentication port is 40 by default. If the base_port is 9500, the authentication port would be 9540.
    • Application Server Type: select the profile type for this Application Server or All (a combination of all three types). For information about each type, see Application Server types.
    • Preserve Existing Data: Check this box to preserve deployment data from the existing deployment. You cannot enter a new Application Server name. This option automatically migrates any customizations from the existing deployment to the new deployment. In the case where there are options in the customized deployment that do not exist in the new deployment type, those options are ignored.
  5. Click OK to validate the information you entered and execute the action on the Application Server launcher.

To terminate a specific Application Server

The Terminate operation terminates the Application Server process immediately. This selection is useful in cases where Stop does not work, for example, when the Application Server stops responding. You cannot use the Terminate 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 Terminate.

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. 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 Remove operation removes an Application Server from the Application Server Launcher so the Application Server does not automatically restart when the Application Server Launcher starts. This operation can be useful in situations where an Application Server is "missing" and no longer in use, such as when a system has been decommissioned or repurposed.

  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 Remove.

  4. In the Remove Application Server dialog box, specify options for managing the Application Server deployment directory and the database registration.

    Option

    Description

    Preserve deployment

    Removes the Application Server but leaves its deployment directory unchanged. If you create a new Application Server with the same name, it uses this deployment directory.

    Delete deployment

    Removes the Application Server and deletes its deployment directory.

    Preserve server registration

    Removes the Application Server but does not delete the database entry for the Application Server. This selection ensures that the Application Server can still be referenced from routing rules. In addition, the Application Server still appears under the Application Server Launchers node.

    Delete server registration

    Removes the Application Server, deletes its database entry, and removes references to the Application Server from routing rules. In effect, this selection removes the Application Server from the BMC Server Automation environment.

  5. Click OK. The Application Server is removed from the Application Server Launcher.

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*