To interact with the Application Manager, you will normally use the Parlay Administration Console. However, you can also configure the Application Manager itself to determine how it will manage your Parlay applications.
Before you begin
You must ensure that the
WebSphere® Application Server has started.
About this task
Certain environment variables must be enabled in the deployment descriptor of the Application Manager. Although the variables are set automatically and do not normally need to be changed, you can examine them and change their settings. For example, you might decide to change some settings for performance tuning.
Software that is customized for a particular gateway might require additional environment variables. The environment variables are required at startup, and they might require redeployment of the application.
Note: The components and applications managed by the Application Manager are called managed objects.
To configure the Application Manager, complete these steps.
- Log in to the Integrated Solutions Console:
- Open a browser and navigate to the following
URL: https://host_name:port/ibm/console.
Where:
- host_name is the fully qualified host name
of the server where the application or the network deployment manager
is deployed.
- port is the secured port used to access the
console. The default port is 9043.
Note: The default unsecured port is 9060.
If you use 9060, you must have "http" instead of "https" in the URL.
- Enter an administrator user ID and password. (Omit the password if security is
not enabled.)
- Click Log in.
- In the navigation pane, expand TWSS
Parlay Administration.
- Click Telecom Server to display
the list of deployed telecom applications.
- Click the name of the application you want to configure,
for example Parlay Connector.
- Click Application Manager.
- Select configuration values for the Application Manager as follows:
- Auto-start Enabled
- If true, the Application Manager starts itself automatically when WebSphere Application Server starts. If false, the Start button is the only way to start the Application Manager. The default value is false.
- Cluster initialization sleep time in seconds
- During startup, the number of seconds to wait for the cluster to come up before setting the appropriate Application Manager state. This value is used for synchronizing the startup sequence of the nodes in the cluster. The default value is 10 seconds.
- Parlay Event Queue - max threads
- The number of QueuedObjectEvent threads that need to run. The default value is 8.
- Parlay Event Queue - dispatch mode
- The algorithm mode used by the Application Manager to dispatch events. Select one of the following values:
- *
- Round-robin: events are dispatched across all computers in the cluster.
- 1
- Local: events are dispatched locally.
- i
- Idle: events are dispatched based on workload.
- Optional: Specify values so that the Application Manager can write events using the Fault and Alarm component Web service, as follows:
- EndPoint URI
- The endpoint URI for the Fault and Alarm component Web service, for example http://localhost:9080/TWSS/ServicePlatform/FaultAlarm/services/FaultAlarm
- Username
- The user name for application-level authentication
- Password
- The password for application-level authentication
- Timeout
- The request timeout, in seconds, for invoking the Fault and Alarm component Web service
- Click OK to save your changes.
- Optional: Restart the application for your changes to take effect if you configured either or both of the following values:
- Auto-start enabled
- Cluster initialization sleep time in seconds
What to do next
To configure additional applications, or managed objects, to be managed by the Application Manager, follow the steps in the topic
Specifying Parlay applications to be managed.