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
- In the TrueSight Server Automation Console, from the Configuration menu, select Infrastructure Management.
- Expand the hierarchy of the Application Servers node.
- Right-click the Application Server you want to edit and select Edit. The Edit Application Server Profile dialog box opens.
- 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.
- When you are finished editing the profile, click OK.
- Click OK on the warning that configuration changes do not take effect until you restart the Application Server.
- 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 |
|---|---|
| Name for the Application Server, specified during configuration. You cannot edit this attribute. |
| 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
|
| Shows whether the Application Server uses the default deployment.
|
| 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. |
| Determines if the Application Server is automatically started by the AppServerLauncher.
|
| 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: |
| Listening port for the Application Service (the service that accepts client connections). When you create a new Application Server, TrueSight 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. |
| Listening port for the Authentication Service (the service that authenticates user identities). When you create a new Application Server, TrueSight 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. |
| Listening port for Network Shell communication. If you set this value to 0 (zero), the port is disabled. |
| 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, TrueSight 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. |
| Port used for secure access. |
| Port used to access the TrueSight Server Automation JConsole or JMXCLI. When you create a new Application Server, TrueSight 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. |
| 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 |
| Name of the log file for the Application Server. When you create a new Application Server, TrueSight 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. |
| (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. |
| 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. |
| Maximum dynamic port number. By default, this value is set to Base Port + 99*.* |
| Maximum size of the pool of threads that can be used to process TrueSight Server Automation Console jobs. Determines how many targets can be processed in parallel. The default is 50. |
| Minimum dynamic port number. When you create a new Application Server, TrueSight Server Automation sets this value to the Base Port + 50. This convention avoids conflicts when there are multiple Application Servers on the same host. |
| 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: For example: |
| Listening port for a Network Shell Proxy Service. You must manually define a listening port for the default deployment of an Application Server. Typically, |
| Listening port for traffic between Application Servers that cooperate by distributing jobs to each other. When you create a new Application Server, TrueSight 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. |
| Listening port for SSL communication. When you create a new Application Server, TrueSight 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. |
| List of SQL properties files used by the Database Service. If you leave this field blank, the list is: |
| 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, TrueSight 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, orSqlFiles, 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.
- In the TrueSight Server Automation Console, from the Configuration menu, select Infrastructure Management.
- In the Infrastructure Management window, expand the hierarchy of the Application Servers node.
- 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. - Click OK.
Comments