About Application Server deployments and profiles

This topic provides an overview of Application Server deployment and the different types of Application Servers:

Application Server deployments

A deployment is a directory of services that an Application Server runs. The table describes each deployment and the effect of configuration changes on it.

Deployment Name	Description
_template	The "master" from which other Application Server deployments are created. This deployment: Is created during BMC Server Automation installation. Contains default ("out of the box") settings and initial configuration settings made with the Post-Install Configuration wizard. Changes to this deployment affect all new Application Servers created. Configuration changes you make using `blasadmin -a` affect this deployment.
default	The deployment for a single Application Server or the initial Application Server when there are multiple Application Servers on the same host. This deployment is created when a single or initial Application Server is first started. The startup process copies the _template deployment to create the default deployment. The following configuration changes affect the default deployment: Changes you make using the Application Server Administration console from the BMC Server Automation menu or using `blasadmin` without the `-a` option or `-s` option. See Starting blasadmin to Configure the Default Application Server. Changes you make using the Application Server Configuration Wizard or the `blappconf` command without the `-s` option. See Changing settings using the Application Server Configuration wizard.
<AppServerName>	The deployment for each Application Server created on the same host (in addition to the default Application Server). When there are multiple Application Servers configured on the same host, each Application Server profile determines the number and type of services in its deployment. The following configuration changes affect the deployment: Changes you make using `blasadmin -s <appServerName>` or `blasadmin -a`. See Starting the Application Server Administration console. Changes you make using `blappconf -s <appServerName>` For more information, see Changing settings using the Application Server Configuration wizard.
_spawner	The deployment for the process spawner. See Configuring the process spawner. The _spawner deployment is not affected by the `blasadmin -a` option, which is used to configure all Application Servers on a host. For this deployment, you must use the `blasadmin -s` option, which applies configuration to a specific instance.
_pxe	The deployment for the PXE server. See Configuring the PXE Server. The _pxe deployment is not affected by the `blasadmin -a` option, which is used to configure all Application Servers on a host. For this deployment, you must use the `blasadmin -s` option, which applies configuration to a specific instance.
_launcher	The deployment for the Application Server Launcher. See Understanding the Application Server. The _launcher deployment is not affected by the `blasadmin -a` option, which is used to configure all Application Servers on a host. For this deployment, you must use the `blasadmin -s` option, which applies configuration to a specific instance.
_util	The deployment for blcontent. The blcontent script creates samples of BMC Server Automation system content; BMC Server Automation provides the script as part of the Application Server installation. When you run the blcontent script, it creates sample prepackaged content and loads it into the database that BMC Server Automation system is currently accessing. For more information about running the script, see Loading prepackaged content. Note: You can delete this deployment after running the blcontent script.
_postmig	The deployment for the post-migration utility (postmigration.sh or postmigration.exe). For more information about the utility, see Performing post-migration updates.
_old	The deployment directory used during upgrades.
_install	The deployment directory used during Application Server installation.

Application Server profiles

A profile is a definition of an Application Server identity: its name, type, and attributes. Each Application Server has a different profile. An Application Server profile is essentially a prepackaged set of configuration options for an Application Server. BMC Server Automation uses the profile to create and update an Application Server deployment (the services that the Application Server runs).

An Application Server profile can include attributes of one or more Application Server types. You specify the Application Server types when you create the Application Server. The attributes required for each type are predefined in the profile for the type.

Application Server types

The Application Server Type defines the work that an Application Server performs and services that it runs.
The following table lists Application Server types.

Application Server Type	Functional Description
Configuration	Manages all requests from the BMC Server Automation Console and the BLCLI. While a Configuration server can create jobs and start the execution of jobs, only a Job server can run the work items needed to process a job.
Job	Executes work items required to process a job. A Job server responds to local connection requests from the BMC Server Automation Console or the BLCLI, provided that one or more of the connection ports (for example, AppSvcPort) is open. A Job server never responds to remote connection requests, regardless of settings for the connection ports.
NSH_Proxy	Manages traffic between Network Shell clients and remote servers. An NSH_Proxy server cannot service requests from the BMC Server Automation Console or the BLCLI.
All	Equivalent to (Configuration, Job, NSH_Proxy) An Application Server with its type set to All performs the functions of all Application Server types.

About Application Server deployments and profiles

Application Server deployments

Application Server profiles

Application Server types

Comments