How CRM On Demand Connector interacts with Web Services

The Oracle Policy Automation Connector for Oracle CRM On Demand interacts with the Web Services v1.0 and v2.0 API by dynamically building the necessary SOAP requests, sending them to a CRM On Demand endpoint and then parsing the SOAP response based on the operation performed.

The Connector is built to produce multiple SOAP requests if deemed necessary, based on its appropriate operation. Generally speaking, there would be separate SOAP requests for different operations.

The following are the guidelines that describe how the Connector determines which kind of SOAP request it will create:

 

By default, the CRM On Demand Connector sends stateless web service calls - that is, the user login credentials are embedded in the SOAP request via the UsernameToken header.

 

The following is a sample Account QueryPage SOAP request generated by the connector for pre-seeding interview data:

 

 

The following is a sample SOAP response after executing the above request:

 

 

Note:

By setting the level value to Debug in the log4j.xml configuration file, the generated SOAP requests and received SOAP responses will be logged by the Connector; this gives the user the opportunity to see the cause for a web service call failure.