|
|
The Agent Manager & Monitor (AMM) agent provides a complete, self-contained, multi-agent execution environment. It provides a multi-agent platform that can dynamically launch applications in response to a passed token in a startapp request as configured through the schedule table. It can also start STATIC_NOWAIT agents which require no startapp. It can also start STATIC agents which are loaded before receiving the startapp, but still require a startapp to complete initialization. It binds the network objects required for agent execution. It monitors and manages agent instances for normal and abnormal termination and state transition conditions. An agent instance is a single execution of a particular agent. This section describes the configuration of the following:
$PARMLIB/parms/APP/Group.<hostname>
Groups can be defined within DAP to differentiate billing records (using an account code) for different sets of users. It is also used to manage the maximum number of agent instances allowed by any one group. DAP groups are similar in concept to UNIX groups defined in /etc/group; however, there is no linkage between the two.
Step 1 Go to the Server you would like to administer.
Step 2 Login as spmaster
Step 3 Edit $PARMLIB/parms/APP/Group.<hostname>. Each GROUP entry has four parameters:
GROUP GroupName GroupNumber AccountCode MaxGroupInstances
These parameters are required.
| Parameter Name | Description | Valid Values and Defaults |
|---|---|---|
The character name of the group. | 1 - 8 characters. Default not applicable. | |
An arbitrary number assigned to the group. | Any signed 32-bit integer except 0, which is reserved for the UNKNOWN group. Default not applicable. | |
A character string used for billing records. | 1 - 8 characters. Default not applicable. | |
The maximum number of agent instances that are allowed to execute at one time for this group on this AMM host. | Any positive integer. (The effective limit is dictated by the capacity of your computer system to handle load.) This number must not be greater than the MaxInstances attribute of the AMM agent. Default not applicable. |
#------------------------------------------------------------------ |
The schedule table is only used by the AMM. It contains information about how and when applications should be launched (started). This file is read by the AMM at startup. In addition, this file can be dynamically reloaded into the memory of an AMM that is up and operational using the reloadsched command.
When an AMM is first started, it will start all STATIC and STATIC_NOWAIT agents. A STATIC_NOWAIT application does not wait for an external event to start it. It starts when the AMM agent starts. The maximum number of agents started is determined by the MaxInstances. Any changes to the schedule table will not affect a STATIC_NOWAIT application that is operational until the application is killed and restarted or if the AMM agent is stopped and restarted.
The DYNAMIC entries specify dynamic applications. Such applications are started by an external event (startapp) such as triggered by an incoming call or a token passed by MWI_Notify. The maximum number of applications that can potentially be started is determined by the MaxInstances. Any changes to the schedule table will affect a DYNAMIC agent upon the next instance. An instance is simply one process of the application being launched.
Both STATIC_NOWAIT and DYNAMIC applications can either be persistent or not persistent. However, it is unwise for a STATIC_NOWAIT application to be non-persistent. An application that is not persistent will terminate after it has completed its task. For example, a uOne application instance will go away after a call session is completed for either call answer service or subscriber services. On the other hand the FaxPrint application is persistent, it continues to run even when there are no more redirected faxes to act upon.
An AMM agent can be configured to allow STATIC, STATIC_NOWAIT, and DYNAMIC instances, provided you do not use the same application and token for both.
STATIC_NOWAIT application or vice versa. Applications are either designed to be persistent or they are not. The file also allows entries called STATIC and EXTERNAL, but these are not recommended for use with uOne.
You cannot exceed the maximum number of instances indicated by the MaxInstances attribute configured for an AMM agent.
MaxInstances of DYNAMIC instances to allow is:
MaxInstances per AMM agent ($PARMLIB/parms/Attrib.<hostname>) should be set to the number of STATIC_NOWAIT instances + the max. number of DYNAMIC instances above. The default value is 48.
MaxInstances per group ($PARMLIB/parms/APP/Group.<hostname>) should be set to the same value as MaxInstances per AMM agent, unless attempting to limit Communities of Interest (COI) to a maximum portion of instance resources.
Step 1 Go to the Server you would like to administer.
Step 2 Login as spmaster
Step 3 Edit $PARMLIB/parms/APP/Schedule.<hostname>. Each DYNAMIC entry has seven (or eight) parameters. Each STATIC_NOWAIT entry has eight (or nine) parameters.
DYNAMIC entries require:
DYNAMIC GroupNumber StartCMDCount TrapLevel StartTime EndTime StartToken ProgramName ProgramParameters
(where ProgramParameters are optional)
STATIC_NOWAIT entries require:
STATIC_NOWAIT GroupNumber InstanceCount TrapLevel StartTime EndTime StartToken ProgramName ProgramParameters
(where ProgramParameters are optional)
Step 4 Use umcli (see uOne Gateserver Installation and Configuration Manual) to reload the schedule table into the AMM agent's memory. These changes will take effect on the next instance of a dynamic application. It will take effect on the next load of the STATIC_NOWAIT applications.
| Parameter Name | Description | Valid Values and Defaults |
|---|---|---|
The number of the group to associate with the application when it is launched. See | Any number except 0, which is reserved for the | |
For dynamic applications, this is the total number of start commands which this program can be sent. Until implemented, this field should be set to ensure successful operation. Note ForDYNAMIC applications, this field is for future use.
For | For For | |
The number of times an agent will be started. Note This field is used only forSTATIC_NOWAIT types.
| Valid Values: Valid positive integer (>0). Also, can be set to 0 to designate infinite starts. | |
The trap level. 0 means trap notification is off and 1 means traps notification is on (e.g. if trap notification is on, traps will be sent when the instance is started as well as notification that the instance has gone away). Note Traps will always be sent if an application aborts. | Valid Values: 0, 1 | |
For For | 00:00 to 23:59 inclusive. An * indicates the program should always be selected. | |
For For | 00:00 to 23:59 inclusive; must be greater than the start time. An * indicates the program should always be selected. | |
For For | User defined. Any Alphanumeric token. | |
| Note If the application is to be started via an incoming phone call, the token specified here must match the 10-digit (in N. America) RDNIS. For direct calls, the RDNIS equals the DNIS (depending on the value of the TEL DomainLookup attribute) phone number of the incoming call. | |
The pathname to the application program to start from the InstancePath. | User defined. If the name starts with a /, it is a full pathname, otherwise it is relative to | |
If there is more than one parameter, the parameters must be separated by a space. | 0 or more parameters. The maximum number of characters supported is 100 characters. | |
DYNAMIC 100 1 0 * * 8 UM/UM UM.ini DYNAMIC 100 1 1 * * MWI_OnOff MWI_OnOff/MWI_OnOff STATIC_NOWAIT 101 1 1 0 * * SMS SMS_Notify/SMS_Notify STATIC_NOWAIT 100 1 1 1 * * LogRemover LogRemover/LogRemover
|
The following table provides information about the parameters that affect the AMM. Descriptions, default values, and ranges of valid values are listed for each parameter.
Changes to AMM parameters take affect when you start AMM. Therefore, if AMM is running and you make parameter changes, you will need to stop and start AMM.
Administering the $PARMLIB/parms/APP/Attrib.Global
Step 1 Go to the Server you would like to administer.
Step 2 Login as spmaster
Step 3 Edit $PARMLIB/parms/APP/Attrib.<hostname> and use:
MaxInstances n
where n is the value calculated from "Engineering Considerations" .
| Attribute | Description | Valid Values and Defaults |
|---|---|---|
Defines the maximum number of instances which can be running at the same time. | Any positive integer. However, the upper limit is effectively determined by the limitations of your computer system to handle load. Default = 48. |
Posted: Mon Sep 25 19:22:20 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.