The following implementation scenarios for JD Edwards EnterpriseOne/World exemplify the integration uses to which EXTOL Enterprise Adapter can be applied, when used with the EXTOL Business Integrator (EBI) base product:

EDI⇐⇒JD Edwards EnterpriseOne/World (F47 files): A large customer requires that your company implement Orders, Advance Ship Notices, and Invoices, using X12 EDI. Your IT staff is familiar with the F47 file layouts and processing. To meet the customer’s requirement, you use EEA to:

• Customize the “base” EDI implementations included in the EEA product to suit the requirements stipulated by your customer.
• Test and deploy.

Despite the complexity that attends EDI integration, because this case is directly supported by many features of the EEA product, implementation is significantly faster and easier than using other EDI integration offerings for JD Edwards EnterpriseOne/World.

Spreadsheet to JD Edwards EnterpriseOne (web service / XML): Your organization uses spreadsheets to gather/record information on the shop floor, in the warehouse, and from your business partners. The spreadsheet data is then manually entered into the JD Edwards EnterpriseOne application. You can use EEA to integrate the spreadsheets directly with JD Edwards EnterpriseOne and eliminate manual data entry by taking the following steps, using EBI:

• Generate document schema(s) from examples of the source spreadsheet(s) used by your organization, using the EBI Spreadsheet Schema Wizard.
• Import WSDLs for each of the target documents and services, from EnterpriseOne Business Services (EOBS).
• Create Transformation rules that specify how to create the desired XML documents from the spreadsheet content.
• Configure a File Read adapter for the spreadsheet source files.
• Generate web services consumers to push the required target documents to EOBS provider services.
• Create a business process model to sequence the spreadsheet file read, transformation, and web service-to-EOBS transport steps.

Together with the EXTOL Business Integrator, EEA makes it easy to integrate proprietary spreadsheet and flat file data with JD Edwards EnterpriseOne. This is particularly useful when integrating with legacy applications and external customers, suppliers, and business partners that are incapable of interacting using EDI and other structured B2B integration methods.

Customer Portal to JD Edwards EnterpriseOne (web service / XML): You use a Web-based portal service, and want to integrate your customer portal with JD Edwards EnterpriseOne to check on orders and order status. You can use EEA to implement integration with your external portal by taking the following steps:

• Create XML document schemas that define the order detail and order status documents needed by the web portal.
• Using EBI, generate web services providers for the Orders and Order Status services, and export the WSDLs for use in creating the consumer interfaces in the web portal.
• Create Transformation rules in EBI that specify how to marshal and send the Orders and Order Status requests to EOBS and create the outputs requested by the web portal.
• Model a business process to sequence the execution of the required communications and data transformation steps.

At runtime, when a customer requests order status through the external portal, the request is satisfied by the EBI Web Services provider, which receives the request, interacts with EOBS to retrieve the order and status information from JD Edwards EnterpriseOne, transforms the returned data into appropriate XML documents, and returns the results to the web portal.