[Contents] [Prev] [Next] [Index] [Report an Error]

Configuring RKS Pairs for Associated Application Managers

By default, the JPS has four associated application managers. All parameters that share the same application manager name configure the RKS pair to which events associated with a specific application manager are sent.

Use the following configuration statement to configure the associated application manager:



slot number jps rks-interface am am-name { 
am-id am-id; 
rks-pair-name rks-pair-name; 
trusted; 
}

To configure the associated application manager:

From configuration mode, access the configuration statement that configures the RKS pair for the associated application manager. In this sample procedure, the application manager name called 1 is configured. user@host# edit slot 0 jps rks-interface am 1
Specify the identifier of the application manager. [edit slot 0 jps rks-interface am 1] user@host# set am-id am-id
If no value is specified, the RKS pair configuration is not defined for this application manager. If you must set trusted to true without defining the RKS pair configuration, you must specify a value for am-id and not specify a value for rks-pair-name.
(Optional) Specify the RKS pair that the JPS will send events to when those events are triggered by gate transitions associated with the application manager specified by am-id with the same application manager name (am-name). [edit slot 0 jps rks-interface am 1] user@host# set rks-pair rks-pair-name
If no value is specified, the RKS pair configuration is not defined for this application manager. Use when you must set trusted to true without defining the RKS pair configuration.
(Optional) Specify whether this application manager is a trusted network element to the JPS. [edit slot 0 jps rks-interface am 1] user@host# set trusted

(Optional) Verify your configuration.

[edit slot 0 jps rks-interface am 1] 
user@host# show

[Contents] [Prev] [Next] [Index] [Report an Error]