Enterprise service processing sequences
An enterprise service message processes through a number of layers to query and update business object data. You can use these processing layers to customize and control processing to satisfy the integration requirements with the external application.
For asynchronous processing, the data can originate from the following exchange methods:
- Interface tables
- HTTP Post of an XML or JSON message
- Starting a web service that is configured to use a JMS queue
- Starting an EJB
- Direct JMS connection
- Data import of a flat file, JSON or XML file
For synchronous processing, the data can originate from the following exchange methods:
- HTTP Post of an XML or JSON message
- Starting a web service that is configured to use a message queue
- Starting an EJB
Enterprise service processing occurs in the following sequence:
- The external system calls the enterprise service.
- Custom processing can occur at several points during the processing of enterprise services. You
can run custom Java™ classes or
automation scripts to manipulate the message data or you can apply an XSL map. Custom
processing occurs in the following order:
- If a preprocessing method is defined in a user exit class, this method is applied first.
- If an external exit class is specified, this processing is applied.
- If a postprocessing method is defined in a user exit class, this method is applied.
- If an XSL map is specified for the enterprise service, the map is applied to convert enterprise service format to object structure format.
- Object structure processing occurs in the following order:
- You can run custom Java classes or automation scripts to manipulate data during object structure processing.
- If processing rules are configured for the object structure, these rules are run next.
- If processing rules result in the multiplication of data for sites or organizations, the object structure message is duplicated for the additional sites or organizations.
- Objects are created and object processing starts.
- Object processing occurs in the following order:
- If a preprocessing method is defined in a user exit class, this method is applied.
- If an external exit class is specified, this processing is applied.
- If a postprocessing method is defined in a user exit class, this method is applied.
- The business objects are processed, and data is saved to the database.
- For synchronous transactions only, for Create, Update, Delete, and Sync operations, the
enterprise service provides a response to the starting application that includes the following
information:
- Indicates whether the message was processed successfully.
- The value of the internal ID column of the main object, regardless of whether the column is part of the primary key of the main object.
- The values of the primary key fields of the main object.
- The values of any alternate key fields for the main object, which is configured for the object or for the object structure.
- For synchronous transactions only, for Query operations, the entire object structure is returned. You can run custom Java classes or automation scripts to manipulate the response data, or you can apply an XSL map. You can manipulate the response data by applying an XSL map.