Writing Connector Policy › Connector Policy Examples › Example: Writing Connector Policy for the CA Catalyst Connector for SNMP › Integrating with CA Workload Automation through the SNMP Connector › Write Policy Operations › Policy Operations for the Item Event Class › Normalize

Normalize

In the parsing section, the job state property temp_state that you created from a specific trap varbind value represents the activity state of the trap. The activity state for CA Workload Automation traps can be one of the following:

• Unknown
• Complete
• Monitor
• Exec
• Failed
• Premature End
• Inactive
• Overdue
• Suberror
• Agent Down
• Ready
• Abandon Submission

You must map these activity states to the CA SOI activity states using the Normalize operation. Normalize operations transform the syntax of event property values to give values from all sources a uniform nomenclature. For performing these mappings, write the Normalize section as follows:

<Catalog version="1.0" globalextends="GLOBAL!">

<!-- ======Event Class====== --> 
<EventClass name="Item">
<!-- Classify --> 
<Classify>

<Field input="snmp_varbindoids" pattern=".*1\.3\.6\.1\.4\.1\.11203\.9.*$" output="eventtype" outval="ITActivity" />

</Classify>
<Parse>

<Field input="snmp_varbindvals" output="temp_nodetype,temp_nodename,temp_domain,temp_applname,temp_applgen,temp_ jobname,temp_jobequal,temp_state,temp_status" pattern="^(.*?),(.*?),(.*?),(.*?),(.*?),(.*?),(.*?),(.*?),(.*?)$" /> 

</Parse>
</EventClass>
<!--  ======Event Class======   --> 
<EventClass name="ITActivity" extends="Item">
<Normalize>

<Field input="temp_state" type="map" output="activityState">
<mapentry mapin="[Uu][Nn][Kk][Nn][Oo][Ww][Nn]" mapout="Unknown" />
<mapentry mapin="[Cc][Oo][Mm][Pp][Ll][Ee][Tt][Ee]" mapout="Finished" /> 
<mapentry mapin="[Mm][Oo][Nn][Ii][Tt][Oo][Rr]" mapout="Normal" /> 
<mapentry mapin="[Ee][Xx][Ee][Cc]" mapout="Normal-Running" /> 
<!--  Informational  --> 
<mapentry mapin="[Ff][Aa][Ii][Ll][Ee][Dd]" mapout="Trouble" /> 
<mapentry mapin="[Pp][Rr][Ee][Mm][Aa][Tt][Uu][Rr][Ee] [Ee][Nn][Dd]" mapout="Obstructed" /> 
<mapentry mapin="[Ii][Nn][Aa][Cc][Tt][Ii][Vv][Ee]" mapout="Normal-Waiting" /> 
<mapentry mapin="[Oo][Vv][Ee][Rr][Dd][Uu][Ee]" mapout="Obstructed" /> 
<mapentry mapin="[Ss][Uu][Bb][Ee][Rr][Rr][Oo][Rr]" mapout="Finished-Completed" /> 
<mapentry mapin="[Aa][Gg][Ee][Nn][Tt] [Dd][Oo][Ww][Nn]" mapout="Trouble" /> 
<!--  Fatal   --> 
<mapentry mapin="[Rr][Ee][Aa][Dd][Yy]" mapout="Normal" /> 
<mapentry mapin="[Aa][Bb][Aa][Nn][Dd][Oo][Nn] [Ss][Uu][Bb][Mm][Ii][Ss][Ss][Ii][Oo][Nn]" mapout="Finished-Abandoned" /> 
</Field>

</Normalize>
</EventClass>

</Catalog>

This policy maps all potential values of the temp_state property to activity states that CA SOI can understand. For example, Complete maps to Finished, Failed maps to Trouble, Inactive maps to Normal-Waiting, and so on. Now, when you map this property value to the activityState USM property, it can understand and display the supported activity state values.