Bulk import for Regular Expression Adaptations

Last Updated : Aug 13, 2019 |

Using System Manager, you can import Regular Expression Adaptations in bulk if the Regular Expression Adaptation feature is enabled. Also, if the Regular Expression Adaptation feature is disabled, the list to select routing data on the Export Routing Data page does not display Regular Expression Adaptations.

Example 1

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<adaptationRegexpFullTOList>
    <buildNumber>0</buildNumber>
    <implementationNumber>0</implementationNumber>
    <specificationVersion>0</specificationVersion>
<AdaptationRegexFullTO>
        <notes>regexAdaptation1 notes</notes>
        <name>RegEx</name> <!--mandatory-->
<enabledState>enabled</enabledState>
      <adaptationRegexpRule>
        <notes></notes>
        <conditionName>condition</conditionName>
        <direction>egress</direction>
        <name>outrule1</name>
        <ruleOrder>1</ruleOrder1>
      <adaptationRegexpAction>
        <notes></notes>
        <actionOrder>1</actionOrder>
        <instance>any</instance>
        <matchRegexp>dd&apos;d&quot;d&amp;</matchRegexp>  <!--value - dd'd"d& -->
        <replaceRegexp>e&lt;ee&gt;</replaceRegexp>  <!--value - e<ee>-->
        <source>accept</source>
        <sourceType>header</sourceType>
        <actionType>modify</actionType>
        <sourceType>header</sourceType>
        <actionType>modify</actionType>
      </adaptationRegexpAction>
      <adaptationRegexpVariable>
        <notes></notes>
        <matchRegexp>abc</matchRegexp>
        <name>var3</notes>
        <source>application</source>
        <sourceType>attachment</sourceType>
        <instance>first-match</instance>
      </adaptationRegexpVariable>
      </adaptationRegexpRule>
      <adaptationRegexpRule>
        <notes></notes>
        <direction>egress</direction>
        <name>rule4</name>
        <ruleOrder>2</ruleOrder1>
      </adaptationRegexpRule>
      <adaptationRegexpRule
        <notes>rule1 notes</notes>
        <conditionName>condition</conditionName>
        <direction>ingress</direction> <!--incoming adaptation rule-->
        <name>rule1</name>
        <ruleOrder>1</ruleOrder1>
        <adaptationRegexpAction>
           <notes></notes>
           <actionOrder>1</actionOrder> <!-- action order should start with 1 and then follow order of 2,3 and so on-->
           <instance>first-match</instance>
           <matchRegexp>xyz</matchRegexp>
           <replaceRegexp></replaceRegexp>
           <source>Accept-Resource-Priority</source>
           <sourceType>header</sourceType>
           <actionType>delete</actionType>
        </adaptationRegexpAction>
        <adaptationRegexpAction>
           <notes></notes>
           <actionOrder>2</actionOrder>
           <instance>last-match</instance>
           <matchRegexp>def</matchRegexp>
           <replaceRegexp>pqr</replaceRegexp>
           <source>Accept-Language</source>
           <sourceType>header</sourceType>
           <actionType>modify</actionType>
        </adaptationRegexpAction>
        <adaptationRegexpVariable>
           <notes>var1 notes</notes>
           <instance>first-match</instance>
           <name>var1</name>
           <source>Accept-Contact</source>
           <sourceType>header</sourceType>
        </adaptationRegexpVariable>
        <adaptationRegexpVariable>
           <notes>var2 notes</notes>
           <instance>last-match</instance>
           <name>var2</name>
           <source>Accept-Encoding</source>
           <sourceType>header</sourceType>
        </adaptationRegexpVariable>
      </adaptationRegexpRule>
      <adaptationRegexpRule>
        <notes></notes>
        <direction>ingress</direction>
        <name>rule2</name>
        <ruleOrder>2</ruleOrder1>
      </adaptationRegexpRule>
    </AdaptationRegexpFullTO>
    <AdaptationRegexpFullTO>
        <notes>regexAdapation2 notes</notes>
        <name>regexAdapation2</name>
    </AdaptationRegexpFullTO>
</adaptationRegexpFullTOList>
    <?xml version="1.0" encoding="UTF-8"?><adaptation>