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:
The start operation starts the Application Server and automatically deploys it, if it has not been deployed.
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.
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.
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.
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.
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.
In the Remove Application Server dialog box, specify options for managing the Application Server deployment directory and the database registration.
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.
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.
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.
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.
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.
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.