Intelligent Management: rules for ODR service policy administrative tasks
Use administrative tasks to configure Session Initiation Protocol (SIP) or HTTP rules for an on demand router service policy.
Command list
We can specify SIP or HTTP protocols in the commands. The following examples use SIP as the protocol:
- addServiceRule
- removeServiceRule
- createServiceRules
- listServiceRules
- changeServiceRuleAction
- changeServiceDefaultRulesAction
- changeServiceRuleExpression
- changeServiceRulePriority
addServiceRule
The addServiceRule command adds a service policy rule.
Required parameters:
- -protocol
- Name of the protocol to associate with a rule. (String, required)
- -priority
- Positive integer value representing the priority of a rule. Zero is the highest priority. (String, required)
- -expression
- Rule expression. The expression must be enclosed in double quotes. (String, required)
- -transactionClass
- Transaction class to associate with a rule. (String, required)
Optional parameters:
- -odrname
- Name of the ODR to which the service policy work class applies. The -odrname parameter is required only if we modify an ODR.
- -nodename
- Name of the node on which the ODR resides. The -nodename parameter is required only if we modify an ODR.
- -clustername
- Name of the cluster to which the rule applies. The -clustername parameter is required only if we modify an ODR cluster.
Batch mode example usage
- Use Jacl:
$AdminTask addServiceRule {-odrname odr -nodename node1 -protocol SIP -priority 0 -expression "request.method = 'getOperation'" -transactionClass Default_TC}- Use Jython string:
AdminTask.addServiceRule('-odrname odr -nodename node1 -protocol SIP -priority 0 -expression "request.method = \'getOperation\'" -transactionClass Default_TC')
Interactive mode example usage
- Use Jacl:
$AdminTask addServiceRule {-interactive}- Use Jython string:
AdminTask.addServiceRule ('[-interactive]')
removeServiceRule
The removeServiceRule command removes a service policy rule.
Required parameters:
- -protocol
- Name of the protocol to associate with a rule. (String, required)
- -expression
- Rule expression. The expression must be enclosed in double quotes. (String, required)
Optional parameters:
- -odrname
- Name of the ODR to which the service policy work class applies. The -odrname parameter is required only if we modify an ODR.
- -nodename
- Name of the node on which the ODR resides. The -nodename parameter is required only if we modify an ODR.
- -clustername
- Name of the cluster to which the rule applies. The -clustername parameter is required only if we modify an ODR cluster.
Batch mode example usage
- Use Jacl:
$AdminTask removeServiceRule {-odrname odr -nodename node1 -protocol SIP -expression "request.method = 'getOperation'"}- Use Jython string:
AdminTask.removeServiceRule('-odrname odr -nodename node1 -protocol SIP -expression "request.method = \'getOperation\'"')
Interactive mode example usage
- Use Jacl:
$AdminTask removeServiceRule {-interactive}- Use Jython string:
AdminTask.removeServiceRule ('[-interactive]')
createServiceRules
The createServiceRules command creates a rule list for the service policy.
Required parameters:
- -protocol
- Name of the protocol to associate with a rule. (String, required)
Optional parameters:
- -odrname
- Name of the ODR to which the service policy work class applies. The -odrname parameter is required only if we modify an ODR.
- -nodename
- Name of the node on which the ODR resides. The -nodename parameter is required only if we modify an ODR.
- -clustername
- Name of the cluster to which the rule applies. The -clustername parameter is required only if we modify an ODR cluster.
Batch mode example usage
- Use Jacl:
$AdminTask createServiceRules {-odrname odr -nodename node1 -protocol SIP}- Use Jython string:
AdminTask.createServiceRules('-odrname odr -nodename node1 -protocol SIP')
Interactive mode example usage
- Use Jacl:
$AdminTask createServiceRules {-interactive}- Use Jython string:
AdminTask.createServiceRules ('[-interactive]')
listServiceRules
The listServiceRules lists service policy rules.
Required parameters:
- -protocol
- Name of the protocol to associate with a rule. (String, required)
Optional parameters:
- -odrname
- Name of the ODR to which the service policy work class applies. The -odrname parameter is required only if we modify an ODR.
- -nodename
- Name of the node on which the ODR resides. The -nodename parameter is required only if we modify an ODR.
- -clustername
- Name of the cluster to which the rule applies. The -clustername parameter is required only if we modify an ODR cluster.
Batch mode example usage
- Use Jacl:
$AdminTask listServiceRules {-odrname odr -nodename node1 -protocol SIP}- Use Jython string:
AdminTask.listServiceRules('-odrname odr -nodename node1 -protocol SIP')
Interactive mode example usage
- Use Jacl:
$AdminTask listServiceRules {-interactive}- Use Jython string:
AdminTask.listServiceRules ('[-interactive]')
changeServiceRuleAction
The changeServiceRuleAction command changes the service policy action for a rule.
Restriction: The use of the changeServiceRuleAction command with HTTP is not supported.
Required parameters:
- -protocol
- Name of the protocol to associate with a rule. (String, required)
- -priority
- Positive integer value representing the priority of a rule. Zero is the highest priority. (String, required)
- -transactionClass
- Transaction class to associate with a rule. (String, required)
Optional parameters:
- -odrname
- Name of the ODR to which the service policy work class applies. The -odrname parameter is required only if we modify an ODR.
- -nodename
- Name of the node on which the ODR resides. The -nodename parameter is required only if we modify an ODR.
- -clustername
- Name of the cluster to which the rule applies. The -clustername parameter is required only if we modify an ODR cluster.
Batch mode example usage
- Use Jacl:
$AdminTask changeServiceRuleAction {-odrname odr -nodename node1 -protocol SIP -priority 0 -transactionClass Default_TC}- Use Jython string:
AdminTask.changeServiceRuleAction('-odrname odr -nodename node1 -protocol SIP -priority 0 -transactionClass Default_TC')
Interactive mode example usage
- Use Jacl:
$AdminTask changeServiceRuleAction {-interactive}- Use Jython string:
AdminTask.changeServiceRuleAction ('[-interactive]')
changeServiceDefaultRulesAction
The changeServiceDefaultRulesAction command changes the default action of a service policy rule.
Restriction: The use of the changeServiceDefaultRulesAction command with HTTP is not supported.
Required parameters:
- -protocol
- Name of the protocol to associate with a rule. (String, required)
- -transactionClass
- Transaction class to associate with a rule. (String, required)
Optional parameters:
- -odrname
- Name of the ODR to which the service policy work class applies. The -odrname parameter is required only if we modify an ODR.
- -nodename
- Name of the node on which the ODR resides. The -nodename parameter is required only if we modify an ODR.
- -clustername
- Name of the cluster to which the rule applies. The -clustername parameter is required only if we modify an ODR cluster.
Batch mode example usage
- Use Jacl:
$AdminTask changeServiceDefaultRulesAction {-odrname odr -nodename node1 -protocol SIP -transactionClass Default_TC}- Use Jython string:
AdminTask.changeServiceDefaultRulesAction('-odrname odr -nodename node1 -protocol SIP -transactionClass Default_TC')
Interactive mode example usage
- Use Jacl:
$AdminTask changeServiceDefaultRulesAction {-interactive}- Use Jython string:
AdminTask.changeServiceDefaultRulesAction ('[-interactive]')
changeServiceRuleExpression
The changeServiceRuleExpression command changes a rule expression of a service policy.
Required parameters:
- -protocol
- Name of the protocol to associate with a rule. (String, required)
- -priority
- Positive integer value representing the priority of a rule. Zero is the highest priority. (String, required)
- -expression
- Rule expression. The expression must be enclosed in double quotes. (String, required)
- -transactionClass
- Transaction class to associate with a rule. (String, required)
Optional parameters:
- -odrname
- Name of the ODR to which the service policy work class applies. The -odrname parameter is required only if we modify an ODR.
- -nodename
- Name of the node on which the ODR resides. The -nodename parameter is required only if we modify an ODR.
- -clustername
- Name of the cluster to which the rule applies. The -clustername parameter is required only if we modify an ODR cluster.
Batch mode example usage
- Use Jacl:
$AdminTask changeServiceRuleExpression {-odrname odr -nodename node1 -protocol SIP -priority 0 -expression "request.method = 'getOperation0'"}- Use Jython string:
AdminTask.changeServiceRuleExpression('-odrname odr -nodename node1 -protocol SIP -priority 0 -expression "request.method = \'getOperation\'"')
Interactive mode example usage
- Use Jacl:
$AdminTask changeServiceRuleExpression {-interactive}- Use Jython string:
AdminTask.changeServiceRuleExpression ('[-interactive]')
changeServiceRulePriority
The changeServiceRulePriority command changes the priority of a service policy rule.
Required parameters:
- -protocol
- Name of the protocol to associate with a rule. (String, required)
- -priority
- Positive integer value representing the priority of a rule. Zero is the highest priority. (String, required)
- -expression
- Rule expression. The expression must be enclosed in double quotes. (String, required)
Optional parameters:
- -odrname
- Name of the ODR to which the service policy work class applies. The -odrname parameter is required only if we modify an ODR.
- -nodename
- Name of the node on which the ODR resides. The -nodename parameter is required only if we modify an ODR.
- -clustername
- Name of the cluster to which the rule applies. The -clustername parameter is required only if we modify an ODR cluster.
Batch mode example usage
- Use Jacl:
$AdminTask changeServiceRulePriority {-odrname odr -nodename node1 -protocol SIP -priority 0 -expression "request.method = 'getOperation0'"}- Use Jython string:
AdminTask.changeServiceRulePriority('-odrname odr -nodename node1 -protocol SIP -priority 0 -expression "request.method = \'getOperation\'"')
Interactive mode example usage
- Use Jacl:
$AdminTask changeServiceRulePriority {-interactive}- Use Jython string:
AdminTask.changeServiceRulePriority ('[-interactive]')
Related:
Overview of request flow prioritization Configure ODRs Create a static cluster of ODRs Intelligent Management: routing and service policies