Page Comparison

...

If you want to enable the SOAP request validation using XML validation files then you have to set the parameter SOAP.VALIDATION.IS_ENABLED to Y and specify the path where the validation XML files are located using parameter SOAP.VALIDATION.PATH_TO_XMLS.

Note: The recent versions of this framework support loading XML files from a specific folder in CLASSPATH called SOAP_XML. E.g.: <...>/Tomcat/webapps/your-soap-application/WEB-INF/classes/SOAP_XML.

After you have designed you workflow and specified hookpoint keys, then you might start calling the service and invoking the workflows.

The most basic request structure should include the elements specified in the following table:

Request:

CONTEXT:

And the example SOAP request for this structure would look like:

<?xml version="1.0" encoding="UTF-8"?>
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
  <S:Body>
    <ns2:executeMethod xmlns:ns2="http://soap.CDRator.com/">
      <arg0>
        <hookpointKey>YOUR_HOOKPOINT_KEY</hookpointKey>
        <values xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ns2:complexValueDTO">
          <key>CONTEXT</key>
          <value xsi:type="ns2:stringValueDTO">
            <key>LANGUAGE</key>
            <value>EN</value>
          </value>
          <value xsi:type="ns2:stringValueDTO">
            <key>OPERATOR</key>
            <value>eka</value>
          </value>
        </values>
      </arg0>
    </ns2:executeMethod>
  </S:Body>
</S:Envelope>

If you try to make the call to InvokerServer using this request, the framework should try to start the workflow having the provided hookpoint key.

Note: For every hookpoint key you call, you will have to provide the validation XML file with the same name as the hookpoint key. That means, if you want to invoke the workflow with the hookpoint key 'YOUR_HOOKPOINT_KEY', then there should be a validation XML for this call named <path_to_xml_files>/YOUR_HOOKPOINT_KEY.xml.