response_bim_services_info XML parameters example

The following example describes a successful response:

<?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_bim_services_info xmlns:ctmem="http://www.bmc.com/ctmem/schema918">

            <ctmem:status>OK</ctmem:status>

            <ctmem:services>

                <ctmem:service>

                    <ctmem:odate>12:26:07 01/12/2014</ctmem:odate>

                    <ctmem:service_name>Bim Service</ctmem:service_name>

                    <ctmem:status>Service completed</ctmem:status>

                    <ctmem:due_time>12:29:07 01/12/2014</ctmem:due_time>

                    <ctmem:min_end_time>12:26:07 01/12/2014</ctmem:min_end_time>

                    <ctmem:description/>

                    <ctmem:num_jobs>3</ctmem:num_jobs>

                    <ctmem:complete_percentage>100</ctmem:complete_percentage>

                    <ctmem:jobs_completed>3</ctmem:jobs_completed>

                    <ctmem:jobs_without_stats>2</ctmem:jobs_without_stats>

                    <ctmem:time_zone> GMT +2</ctmem:time_zone>

                    <ctmem:data_center>palace620</ctmem:data_center>

                    <ctmem:priority>5</ctmem:priority>

                    <ctmem:min_slack_time>0</ctmem:min_slack_time>

                    <ctmem:status_color>Service in process or completed</ctmem:status_color>

                </ctmem:service>

                <ctmem:service>

                    <ctmem:odate>12:22:00 01/12/2014</ctmem:odate>

                    <ctmem:service_name>Bim Service</ctmem:service_name>

                    <ctmem:status>Service is late</ctmem:status>

                    <ctmem:due_time>12:25:00 01/12/2014</ctmem:due_time>

                    <ctmem:min_end_time>13:52:08 01/12/2014</ctmem:min_end_time>

                    <ctmem:description>Job "Service4" should have started by

                        12:25:00 GMT+02:00 and will not start on time. The reason

                        is: Job is held.</ctmem:description>

                    <ctmem:num_jobs>3</ctmem:num_jobs>

                    <ctmem:complete_percentage>33</ctmem:complete_percentage>

                    <ctmem:jobs_completed>1</ctmem:jobs_completed>

                    <ctmem:jobs_without_stats>2</ctmem:jobs_without_stats>

                    <ctmem:time_zone> GMT +2</ctmem:time_zone>

                    <ctmem:data_center>palace620</ctmem:data_center>

                    <ctmem:priority>5</ctmem:priority>

                    <ctmem:min_slack_time>0</ctmem:min_slack_time>

                    <ctmem:status_color>Service delay or will not complete</ctmem:status_color>

                </ctmem:service>

            </ctmem:services>

        </ctmem:response_bim_services_info>

    </SOAP-ENV:Body>

</SOAP-ENV:Envelope

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">

<SOAP-ENV:Body>

<SOAP-ENV:Fault>

<faultcode> … </faultcode>

<faultstring>…. </faultstring>

<detail>

. . . FAULT_RESPONSE_OF_THE_REQUEST . . .

</detail>

</SOAP-ENV:Fault>

</SOAP-ENV:Body>

</SOAP-ENV:Envelope>

The fault parameters for all requests are described in Fault Response.