JD Edwards EnterpriseOne Business Services Integration Process

Published business services transfer information between JD Edwards EnterpriseOne and other Oracle or third-party systems. Internal business services (web service operations) process that information within EnterpriseOne. Because these systems may be using different programming languages or running on different platforms, data must be formatted during transfer so that it can be read and processed by each system.

The user of a third-party system, also known as the consumer, initiates a business services integration by entering data into an input interface. An input interface is based on JD Edwards EnterpriseOne data structure, and is used to hold the information associated with the user's request. For example, the consumer might specify that they want to inquire on a particular sales order in the JD Edwards EnterpriseOne system. Therefore, they can enter the sales order number in the input interface and specify that they want to inquire on that order.

The published business service reads the consumer's request to determine the action that the system takes, and calls the appropriate business service. In this example the SalesOrderManager published business service calls the GetSalesOrder business service. Additionally, the published business service formats the data in the input interface so that it can be read and processed by the JD Edwards EnterpriseOne system.

The business service passes the data into the EnterpriseOne system and tells the system what actions to perform. After the EnterpriseOne system processes or retrieves the specified information, it sends the results back to the business service. The business service receives the processed data from the EnterpriseOne system and passes it back to the published business service. The published business service then formats the data so that it can be read by the third-party system and passes it back to the consumer using the response interface.