Home » OpenESB » SFDC INTEGRATION WITH ORACLE OTM USING OPENESB

SFDC INTEGRATION WITH ORACLE OTM USING OPENESB

LogiCoy has implemented OTM with SFDC [Sales Force Dot Com] using OpenESB which is currently running in production.

How OTM integration is implemented using OpenESB? 

Types of integration that we at LogiCoy have accomplished by sending data to [inbound to OTM] and from OTM [outbound from OTM] with SFDC using OpenESB is as follows:

  • License Plant [inbound to OTM]
  • SMS [outbound to OTM]

SFDC

License Plant:

Description:

When License plant requests are created in SFDC, a request is made to a Web service exposed by OpenESB.In real time, simultaneously an instance is created and initialized with the variable which is in JSON format. This is converted into XML format[based on customer requirement ] which invokes the external OTM SOAP web service with the request parameter and response from OTM SOAP service is mapped back to TransmissionAck [OTM Ack ] which is again in XML format .

OpenESB, further re-converts the XML format back to JSON and then forwards the response to SFDC.

SFDC_license

SMS:

Description:

When Shipments and planning are created in OTM ,delivery confirmation date along with account details etc will be sent to sales force and sales force will send the SMS about delivery confirmation date to the end customer.

Once OTM request is made to a Web service exposed by OpenESB, an instance is created and initialized with the variable. Once done we get the session ID and invoke external SFDC SOAP web service with the request parameter and response from SFDC SOAP service is mapped back to TransmissionAck.[OTM]

SMS

The above mentioned integrations [License Plant and SMS] use XSLT so as to avoid Selection Failure Exception.

XSLTransformation is used when the input contains empty elements which are being assigned to the target.

Error Handling in OpenESB:

Error handling is an integral part while designing OpenESB applications as OpenESB applications integrate heterogeneous IT systems across the organizational boundaries, vendor and partner IT assets. Focusing on error handling analysis early in the analysis and design phases ensures that appropriate error handling standards/guidelines are put in place for modules in different platforms.

Error reporting BPEL process flow:

FaultHandler

The catch block of BPEL Interpreter’s execute method is the central point where all exceptions are caught and converted to BPEL faults. A BPEL fault needs to have a fault name (name) and data.

Types of Catch Statements used for the above integrations:

SystemException

SelectionFailureException

CatchAll

 

Leave a Reply

Your email address will not be published. Required fields are marked *

*
*