Control-M 8 Integration

I need some feedback from Control M customers.

Here at xMatters we're in the process of updating our Control-M integration and adding support for Control-M 8.

The integration points have changed quite significantly since our last version was released and I am looking at what properties we should use to populate our messages.

Here is an example of a response from the Control-M API which shows what properties are available for us to use.

<?xml version="1.0" encoding="iso-8859-1"?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">

  <SOAP-ENV:Body>

    <ctmem:response_act_retrieve_jobs xmlns:ctmem="http://www.bmc.com/ctmem/schema800">

      <ctmem:retrieved_nodes_number>1</ctmem:retrieved_nodes_number>

      <ctmem:jobs>

        <ctmem:job>

          <ctmem:job_data>

            <ctmem:control_m>vic-vw-ctrl-m</ctmem:control_m>

            <ctmem:order_id>0000r</ctmem:order_id>

            <ctmem:rba>00000r</ctmem:rba>

            <ctmem:table_rba>000000</ctmem:table_rba>

            <ctmem:application/>

            <ctmem:application_type>OS</ctmem:application_type>

            <ctmem:group/>

            <ctmem:job_name>aarons dir job3</ctmem:job_name>

            <ctmem:mem_name/>

            <ctmem:mem_lib/>

            <ctmem:order_table>aaronfolder2</ctmem:order_table>

            <ctmem:owner>administrator</ctmem:owner>

            <ctmem:description>aarons test job</ctmem:description>

            <ctmem:task_type>Command</ctmem:task_type>

            <ctmem:time_zone/>

            <ctmem:in_BIM_service>0</ctmem:in_BIM_service>

            <ctmem:job_status>Ended OK</ctmem:job_status>

            <ctmem:job_state>Run (9)</ctmem:job_state>

            <ctmem:state_digits>000030010000000</ctmem:state_digits>

            <ctmem:odate>130627</ctmem:odate>

            <ctmem:otime>20130627105642</ctmem:otime>

            <ctmem:next_time>20130627110800</ctmem:next_time>

            <ctmem:rerun_counter>00008</ctmem:rerun_counter>

            <ctmem:average_runtime>000001</ctmem:average_runtime>

            <ctmem:start_time>20130627110716</ctmem:start_time>

            <ctmem:end_time>20130627110716</ctmem:end_time>

            <ctmem:critical>1</ctmem:critical>

            <ctmem:cyclic>1</ctmem:cyclic>

            <ctmem:emergency>False</ctmem:emergency>

            <ctmem:time_from>0938</ctmem:time_from>

            <ctmem:time_until/>

          </ctmem:job_data>

       </ctmem:job>

      </ctmem:jobs>

    </ctmem:response_act_retrieve_jobs>

  </SOAP-ENV:Body>

</SOAP-ENV:Envelope>

I've attached a snippet from the Control-M API guide that explains what these fields are.

We are passing all of these properties to xMatters so all of them are available to use in subscriptions and messages.

However, by default I want to limit the content of the messages so they only contain the essential information needed. Anything else can be added to the message content later of course but I'm taking the less is more approach for setting up the default messages.

Here's what we've got at the moment. We're still a month or so away from completing this so there is plenty of time to make an update if we've missed anything.

All feedback welcome!