+

Search Tips   |   Advanced Search

Operating Systems: AIX, HP-UX, Linux, Solaris, Windows, z/OS

 

Rules for ODR service policy administrative tasks


You can use administrative tasks to configure Session Initiation Protocol (SIP) or HTTP rules for the on demand router (ODR) service policy. You can specify SIP or HTTP protocols in the commands. The following examples use SIP as the protocol.

Command name: Description: Parameters and return values: Examples:
addServiceRule Use this command to add a service policy rule. Optional parameters:

-odrname
Name of the ODR to apply the service policy work class. Required only if modifying an ODR.
-nodename
Name of the node on which the ODR resides. Required only if modifying an ODR.
-clustername
Name of the cluster to which to apply the rules. Required only if modifying an on demand router cluster.
Required parameters:

-protocol
Name of the protocol to associate with these rules.

-priority
Specifies a positive integer value that represents the priority of the rule. Zero is the highest priority.
-expression
Specifies the rule expression. Place the expression value in double quotes.
-transactionClass
Specifies the transaction class to associate with a rule.

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: 
    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: 
    AdminTask.addServiceRule ('[-interactive]')
changeServiceRuleAction Use this command to change a service policy action for a rule. Note: Not supported for HTTP. Optional parameters:

-odrname
Name of the ODR to apply the service policy work class. Required only if modifying an ODR.
-nodename
Name of the node on which the ODR resides. Required only if you are modifying an ODR.
-clustername
Name of the cluster to apply the rules to. Required only if you are modifying an on demand router cluster.
Required parameters:

-protocol
Name of the protocol to associate with these rules.

-priority
Specifies a positive integer value that represents the priority of the rule. Zero is the highest priority.
-transactionClass
Specifies the transaction class to associate with a rule.

Batch mode example usage:

  • Use Jacl: 
    $AdminTask changeServiceRuleAction {-odrname odr -nodename node1 -protocol SIP -priority 0 -transactionClass Default_TC}

  • Use Jython: 
    AdminTask.changeServiceRuleAction('[-odrname odr] [-nodename node1] [-protocol SIP] [-priority 0] [-transactionClass Default_TC]')

Interactive mode example usage:

  • Use Jacl: 
    $AdminTask changeServiceRuleAction {-interactive}

  • Use Jython: 
    AdminTask.changeServiceRuleAction ('[-interactive]')
changeServiceDefaultRulesAction Use this command to change a rules service policy default action. Note: Not supported for HTTP. Optional parameters:

-odrname
Name of the ODR to apply the service policy work class. Required only if modifying an ODR.
-nodename
Name of the node on which the ODR resides. Required only if you are modifying an ODR.
-clustername
Name of the cluster to apply the rules to. Required only if you are modifying an on demand router cluster.
Required parameters:

-protocol
Name of the protocol to associate with these rules.
-transactionClass
Specifies the transaction class to associate with a rule.

Batch mode example usage:

  • Use Jacl: 
    $AdminTask changeServiceDefaultRulesAction {-odrname odr -nodename node1 -protocol SIP -transactionClass Default_TC}

  • Use Jython: 
    AdminTask.changeServiceDefaultRulesAction('[-odrname odr] [-nodename node1] [-protocol SIP] [-transactionClass Default_TC]')

Interactive mode example usage:

  • Use Jacl: 
    $AdminTask changeServiceDefaultRulesAction {-interactive}

  • Use Jython: 
    AdminTask.changeServiceDefaultRulesAction ('[-interactive]')
changeServiceRuleExpression Use this command to change a service policy rule expression. Optional parameters:

-odrname
Name of the ODR to apply the service policy work class. Required only if modifying an ODR.
-nodename
Name of the node on which the ODR resides. Required only if you are modifying an ODR.
-clustername
Name of the cluster to apply the rules to. Required only if you are modifying an on demand router cluster.
Required parameters:

-protocol
Name of the protocol to associate with these rules.

-priority
Specifies a positive integer value that represents the priority of the rule. Zero is the highest priority.
-expression
Specifies the rule expression. Place the expression value in double quotes.
-transactionClass
Specifies the transaction class to associate with a rule.

Batch mode example usage:

  • Use Jacl: 
    $AdminTask changeServiceRuleExpression {-odrname odr -nodename node1 -protocol SIP -priority 0 -expression "request.method = 'getOperation0'"}

  • Use Jython: 
    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: 
    AdminTask.changeServiceRuleExpression ('[-interactive]')
changeServiceRulePriority Use this command to change a service policy rule priority. Optional parameters

-odrname
Name of the ODR to apply the service policy work class. Required only if modifying an ODR.
-nodename
Name of the node on which the ODR resides. Required only if you are modifying an ODR.
-clustername
Name of the cluster to apply the rules to. Required only if you are modifying an on demand router cluster.
Required parameters:

-protocol
Name of the protocol to associate with these rules.
-priority
Specifies a positive integer value that represents the priority of the rule. Zero is the highest priority.
-expression
Specifies the rule expression. Place the expression value in double quotes.

Batch mode example usage:

  • Use Jacl: 
    $AdminTask changeServiceRulePriority {-odrname odr -nodename node1 -protocol SIP -priority 0 -expression "request.method = 'getOperation0'"}

  • Use Jython: 
    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: 
    AdminTask.changeServiceRulePriority ('[-interactive]')
createServiceRules Use this command to create a service policy rule list. Optional parameters:

-odrname
Name of the ODR to apply the service policy work class. Required only if modifying an ODR.
-nodename
Name of the node on which the ODR resides. Required only if you are modifying an ODR.
-clustername
Name of the cluster to apply the rules to. Required only if you are modifying an on demand router cluster.
Required parameters:

-protocol
Name of the protocol to associate with these rules.

Batch mode example usage:

  • Use Jacl: 
    $AdminTask createServiceRules {-odrname odr -nodename node1 -protocol SIP}

  • Use Jython: 
    AdminTask.createServiceRules('[-odrname odr] [-nodename node1] [-protocol SIP]')

Interactive mode example usage:

  • Use Jacl: 
    $AdminTask createServiceRules {-interactive}

  • Use Jython: 
    AdminTask.createServiceRules ('[-interactive]')
listServiceRules Use this command to list service policy rules. Optional parameters:

-odrname
Name of the ODR to apply the service policy work class. Required only if modifying an ODR.
-nodename
Name of the node on which the ODR resides. Required only if you are modifying an ODR.
-clustername
Name of the cluster to apply the rules to. Required only if you are modifying an on demand router cluster.
Required parameters:

-protocol
Name of the protocol to associate with these rules.

Batch mode example usage:

  • Use Jacl: 
    $AdminTask listServiceRules {-odrname odr -nodename node1 -protocol SIP}

  • Use Jython: 
    AdminTask.listServiceRules('[-odrname odr] [-nodename node1] [-protocol SIP]')

Interactive mode example usage:

  • Use Jacl: 
    $AdminTask listServiceRules {-interactive}

  • Use Jython: 
    AdminTask.listServiceRules ('[-interactive]')
removeServiceRule Use this command to remove a service policy rule. Optional parameters:

-odrname
Name of the ODR to apply the service policy work class. Required only if modifying an ODR.
-nodename
Name of the node on which the ODR resides. Required only if you are modifying an ODR.
-clustername
Name of the cluster to apply the rules to. Required only if you are modifying an on demand router cluster.
Required parameters:

-protocol
Name of the protocol to associate with these rules.
-expression
Specifies the rule expression. Place the expression value in double quotes.

Batch mode example usage:

  • Use Jacl: 
    $AdminTask removeServiceRule {-odrname odr -nodename node1 -protocol SIP -expression "request.method = 'getOperation'"}

  • Use Jython: 
    AdminTask.removeServiceRule('[-odrname odr] [-nodename node1] [-protocol SIP] [-expression "request.method = 'getOperation'"]')

Interactive mode example usage:

  • Use Jacl: 
    $AdminTask removeServiceRule {-interactive}

  • Use Jython: 
    AdminTask.removeServiceRule ('[-interactive]')


 

Related concepts


Overview of request flow prioritization

 

Related tasks


Configure ODRs
Routing and service policies

Related information


SIP rules for ODR routing policy administrative tasks