Viewing and editing an Application Server profile

An Application Server profile is a definition of an Application Server identity: its name, type, and attributes (configuration parameters). To view an Application Server profile or change attribute values, use the Edit Application Server Profile dialog box.

To view and edit an Application Server profile

  1. In the BMC Server Automation Console, from the Configuration menu, select Infrastructure Management.
  2. Expand the hierarchy of the Application Servers node.
  3. Right-click the Application Server you want to edit and select Edit. The Edit Application Server Profile dialog box opens.
  4. In the Edit Application Server Profile dialog box, add or change values for attributes.
    The fields in this dialog box are overrides to default values or to previously specified configuration parameters. For a list of the available attributes, see List of profile attributes.
    • To add an attribute to the Application Server profile, or to change a default value, type a value in the blank field.
    • To change an existing value, clear the field and type the value you want.
    • To remove an attribute from the profile, clear the field.
  5. When you are finished editing the profile, click OK.
  6. Click OK on the warning that configuration changes do not take effect until you restart the Application Server.
  7. Start or restart the Application Server to have changes take effect.

List of profile attributes

The following table describes all attributes that a profile can include. Attributes listed depend on the Server Profile Type (Application Server Type).

Attribute

Description

Application Server Name

Name for the Application Server, specified during configuration. You cannot edit this attribute.

Display Name

Name that appears in all user interfaces, rather than the Application Server name. You do not have to specify a name. If you leave this field blank, the Display Name is the same as the Application Server name. If you specify a name, follow these guidelines:

  • Specify a name that is unique on the host. Do not use the same name as the default Application Server.
  • The name can include letters, digits, hyphens (-), and underscores (_).
  • Do not use the following reserved names: default, _install, _launcher, _old, _pxe, _spawner, _template, _util.

Default Deployment

Shows whether the Application Server uses the default deployment.

Server Profile Type

Application Server type, as specified during configuration. The type can be one or more of the following: Configuration, Job, NSH, or All. See Application Server types. You cannot edit this attribute.

ServiceType

Determines if the Application Server is automatically started by the AppServerLauncher.

  • A ServiceType of Manual, which means that the Application Server can only be started using the Infrastructure dialog box.
  • A ServiceType of Automatic means that the Application Server starts automatically by the AppServerLauncher.
    By default, the ServiceType is Automatic.

AppServiceURLs

Application Service URLs distributed in the session credentials issued by the Authentication Service. To include this attribute in the profile, specify one or more comma-separated values. For example: service:appsvc.bladelogic:blsess://localhost:9841, service:appsvc.bladelogic:blsess://10.10.10.10:9841

Typically, you do not need to specify a value for this attribute. However, to run Network Shell Script Jobs that include BLCLI commands, you can direct these commands to run on a particular Application Server. BLCLI commands used for import or export must run on an Application Server with its type set to Configuration or ALL. By default, BLCLI commands run on the Application Server processing the job. If that Application Server is a Job type Application Server, it cannot process BLCLI commands used for import/export.

AppSvcPort

Listening port for the Application Service (the service that accepts client connections). When you create a new Application Server, BMC Server Automation sets this value to the base port plus 41. This convention avoids conflicts when there are multiple Application Servers on the same host. If you set this value to 0, the Application Server does not run an Application Service.

Note: When you create a job server (Application Server Type Job ), it runs a ClientConnectionService. However, that service accepts only connections from the local machine, unless the server is also a configuration server (Application Server Type Job and Configuration ).

AuthSvcPort

Listening port for the Authentication Service (the service that authenticates user identities). When you create a new Application Server, BMC Server Automation sets this value to the base port plus 40. This convention avoids conflicts when there are multiple Application Servers on the same host. If you set this value to 0 (zero), the Application Server does not run an Authentication Service.

Note: When you create a job server (Application Server type Job ), this port defaults to 0, unless the server is also a configuration server (Application Server Type Job and Configuration ). In that case, the default is base port plus 40.

CLRProxyPort

Listening port for Network Shell communication. If you set this value to 0 (zero), the port is disabled.

ConsoleLogfileName

Name of the console log file for the Application Server. The console log file contains all information logged to the Application Server log, plus any information logged to the console. When you create a new Application Server, BMC Server Automation sets the console log file's name to the Application Server name plus "_console". This convention avoids conflicts when there are multiple Application Servers on the same host. If you edit this attribute, specify a name that is unique on the host.

HttpsPortNumber

Port used for secure access.

JMXManagementPort

Port used to access the BMC Server Automation JConsole or JMXCLI. When you create a new Application Server, BMC Server Automation sets this value to the base port plus 38. This convention avoids conflicts when there are multiple Application Servers on the same host.

JVMArgs

Arguments to pass to Java Virtual Machine for this Application Server. Specify any argument that can be specified to the Java command line. If the MaxHeapSize attribute is set and you specify an -Xmx flag for JVMArgs, the value for JVMArgs is used instead of MaxHeapSize. You do not need to specify a value for this attribute. If you specify a value, it is assumed to be valid and is used when the Application Server is started. If the value is not valid, the Application Server does not start.

LogfileName

Name of the log file for the Application Server. When you create a new Application Server, BMC Server Automation sets the log file's name to the Application Server name plus the .log extension. This convention avoids conflicts when there are multiple Application Servers on the same host. If you edit this attribute, specify a name that is unique on the host.

MaxHeapSize

(Optional) The maximum heap size for the Application Server. If you do not specify a value, the Application Server uses the heap size set in the Application Server startup script or service definition. To specify a value, use the standard Java notation. For example: 1 G or 225 M.

 Click here to review recommendations for the Application Server maximum Java heap size (MaxHeapSize).

This section describes recommended Java heap sizes for Application Servers running under different operating systems. These are recommendations only and must be adjusted in light of observed conditions, especially out-of-memory errors.

  • For 32-bit processes, BMC recommends operating system-specific Java heap size values according to the table below. Due to memory constraints, job servers using 32-bit processes should be configured to use no more than 50 work item threads.
  • For 64-bit processes, BMC recommends that the Java heap size be increased as indicated in the table, if there is sufficient physical memory to support this setting.

The following table provides details about the relevant blasadmin setting:

Module

Setting

Description and Recommendation

AppServer

MaxHeapSize

Specifies the maximum heap size for this Application Server.
See operating system-specific recommendations for this value summarized in the table below.

  

Windows:

  • 32-bit: 1024 MB
  • 64-bit: 6-8 GB
  

Linux:

  • 32-bit: 1536 MB
  • 64-bit: 6-8 GB
  

Solaris:

  • 32-bit: 2048
  • 64-bit: Not applicable

MaxJobs

Maximum number of jobs that the Application Server can execute simultaneously. The default is 20.

Note: If you are running batch jobs, the actual number of jobs running might exceed the MaxJobs setting. Number of jobs running is one of the statistics included in Application Server information in the Infrastructure Management window or in the detailed report that you can export from that window, as well as in the Application Server status report when you generate data for Support. The reason for this phenomenon is that only the batch job itself is counted towards the MaxJobs limit, while all jobs — the batch job and all its member jobs — are included in the count of number of jobs running.

 Click here for examples...

Example 1:

  • MaxJobs is set to 20 jobs.
  • Number of jobs running was 15, but then a batch job with 10 member jobs started executing.
  • The new number of jobs running is now 26:
    15 jobs from before + 1 parent batch job + 10 child (member) jobs

Example 2:

  • MaxJobs is set to 20 jobs.
  • Number of jobs running was 0, and then a batch job started executing.
  • In this batch job, the Execute by server option was selected, and the job is targeted against 28 servers. This option is identical to running multiple batch jobs simultaneously, with each batch job configured to have only one target and to execute individual jobs sequentially.
  • The new number of jobs running is now 57:
    1 parent batch job + 28 child batch jobs (1 per target) + 28 child (member) jobs, one under each child batch job


MaxPort

Maximum dynamic port number. By default, this value is set to Base Port + 99*.*

MaxWorkItemThreads

Maximum size of the pool of threads that can be used to process BMC Server Automation Console jobs. Determines how many targets can be processed in parallel. The default is 50.

MinPort

Minimum dynamic port number. When you create a new Application Server, BMC Server Automation sets this value to the Base Port + 50. This convention avoids conflicts when there are multiple Application Servers on the same host.

ProxyServiceURLs

URL of a Network Shell Proxy Service that runs in the Application Server environment. If you leave this field blank, the system uses the default URL. To override the default URL, provide a value with the following format:
service:proxysvc.bladelogic:blsess://
<nshProxyServerHost>:<portNumber>

For example:
service:proxysvc.bladelogic:blsess://host1.bladelogic.com:9842

ProxySvcPort

Listening port for a Network Shell Proxy Service. You must manually define a listening port for the default deployment of an Application Server. Typically, ProxySvcPort is set to 9842 for the default Application Server. When you deploy a new Application Server with its type set to NSH_PROXY or All, the ProxySvcPort is automatically set to the base port plus 42. You can modify this value if necessary. If this value is blank, the Application Server does not run a Network Shell Proxy Service.

RegistryPort

Listening port for traffic between Application Servers that cooperate by distributing jobs to each other. When you create a new Application Server, BMC Server Automation sets this value to the base port plus 36. This convention avoids conflicts when there are multiple Application Servers on the same host.

SSLPort

Listening port for SSL communication. When you create a new Application Server, BMC Server Automation sets this value to the base port plus 31. This convention avoids conflicts when there are multiple Application Servers on the same host.

SocketsBindAddress

The IP address (IPv4 or IPv6) or host name to which the Application Server listens. Use this attribute if the Application Server has more than one network interface and you want the Application Server to listen for connections on only one.

SqlFiles

List of SQL properties files used by the Database Service. If you leave this field blank, the list is:
sql/sqlmap.properties sql/streamable_sqlmap.properties sql/blas-sqlmap.properties sql/reports-sql.properties In most cases, there is no need to change this list. However, you can override the default list by typing a comma-separated list of properties in the field.

TempDirectoryName

Name of the directory that stores the Application Server tmp files. Usually, this name is the same as the Application Server Name and its location is: <installDirectory>/tmp/ temporaryDirectoryName When you create a new Application Server, BMC Server Automation sets the TempDirectoryName to the Application Server Name. This convention avoids conflicts when there are multiple Application Servers on the same host. If you edit this attribute, specify a name that is unique on the host.

Rules for defining unique attributes

Several rules apply when assigning unique values to attributes:

  • Multiple Application Servers can share any port that is set to 0 (zero) if that setting of 0 disables the port.
  • Multiple Application Servers can have the same value for MaxJobs, MaxWorkItemThreads, or SqlFiles, regardless of the value.
  • All other attributes must be unique. Failure to make attributes unique results in conflicts that can cause a start or restart failure in one or more Application Servers. For information about identifying conflicts in Application Server attributes, see Listing conflicting attributes.

Listing conflicting attributes

The Application Server Launcher automatically detects attribute conflicts among the Application Servers that it controls.
When there are Application Servers on the same host, each should have a unique profile. For the most part, attributes for these Application Servers cannot have the same values.

Typically, a conflict occurs because the same port number has been assigned to more than one Application Server. This type of conflict prevents an Application Server from starting or restarting if it has conflicts with one or more currently running Application Servers. When an Application Server profile has a conflicting attributes, its Application Server details shows State = CONFLICT.

You can also use the List Conflicts option to identify attributes on an Application Server that conflict with attributes on other Application Servers.

  1. In the BMC Server Automation Console, from the Configuration menu, select Infrastructure Management.
  2. In the Infrastructure Management window, expand the hierarchy of the Application Servers node.
  3. Right-click an Application Server and select List Conflicts.
    A Warning panel lists the attributes that conflict with those other Application Servers. For each attribute, the panel shows the attribute name and the name of the Application Server that has the same attribute value specified.
  4. Click OK.
Was this page helpful? Yes No Submitting... Thank you

Comments