Support for stateless Web Service calls
Limitations of Custom Objects in Web Services v1.0
Limitation for Parent Object Insert mapping
Limitation for Many-to-Many relationships
Currently in Oracle Policy Automation Connector for Oracle CRM On Demand, we are only supporting Stateless web service calls via a fixed credential for request authentication. All of the SOAP requests sent to CRM On Demand are using the stateless format which should comply with the following conditions as stated in the Oracle Web Services On Demand guide:
Example of a stateless SOAP message created by the connector for WS1.0
![]()
This SOAP message complies with the first two conditions having the WSSE namespace and the username token containing the credentials specified in the SOAP header.
It is important that the Web Services R16 Compatibility Mode is turned OFF to support stateless calls. If turned ON, all web service calls are treated as stateful regardless if the format is in stateless form. A possible implication of this scenario is the occurrence of this exception.
Error Code: SBL-ODU-01006
Error Message: com.siebel.occam.integration.IntegrationServletException
The reason is that the intention of the Connector is to make stateless calls so it is not responsible for creating and destroying sessions - CRM On Demand will automatically create and destroy it. However, since the Connector is designed to send multiple SOAP requests for a transaction and will support concurrent users, some sessions are not yet destroyed prior to creating a new one which are all automatically handled by CRM On Demand. To prevent this to happen, the user must verify that Web Services R16 Compatibility Mode is cleared in the Company Profile page of the Admin Section.
There are a couple limitations with the usage of Custom Objects in Web Services v1.0:
In essence, Custom Objects (1-3) in Web Services v1.0 are only usable when it is the top-level object. In this case, all fields are present on the schema or WSDL.
Support for Oracle CRM On Demand Web Services API
On the import wizard’s Select and Configure CRM On Demand objects screen, only global is allowed in the Insert entity mapping if the following conditions are true:
If crmodnew<object> is otherwise selected in this scenario, a validation message will be displayed and the user won’t be allowed to proceed to the next screen.
This means that, as of this release, a user won’t be able to simultaneously Save and Insert (using the crmodnew<parent-object> entity) a Parent object instance.
This has been done in order to prevent users from running into Insert or Save problems brought about by mapping both global and crmodnew<parent-object> entities to the parent object. This is a result of the connector becoming confused as to which parent instance should be attached to child object instances during saving or inserting.
Currently in Oracle Policy Automation Connector for Oracle CRM On Demand, we are only supporting One-to-Many relationships between Parent and Child objects. But some object associations have Many-to-Many relationships with each other. When these object associations are used by the Connector, it may produce undesirable results; see the topic Limitation for Many-to-Many relationships.