Configuring EDI Integration

BEA WebLogic EDI Integration must be completely configured before it can be used. Because EDI Integration depends on BEA EDI Connect for WebLogic Integration to operate properly, make sure you configure Power.Enterprise! correctly so that you can communicate with your trading partners.

 

---

General Configuration

This section discusses the general configuration information that you should perform before attempting to configure a specific document exchange with a trading partner.

Configure Trading Partners

Before configuring individual transactions, you should configure all trading partners, including your own company, using Power.Manager!. For more information about configuring trading partners, see the following topics:

• Configuring Trading Partners

• Chapter 4, "Partners," in the Power.Manager! User Reference Manual

Configure VAN/Trading Partner Connectivity

You should also configure your trading partner connectivity before attempting to configure individual document exchanges. See the following topics:

• Connections and VAN Connectivity

• Chapter 3, "Connections," in the Power.Manager! User Reference Manual

Although you may not want to set up connectivity to your production trading partners at this time, you may want to configure them with file connectors for development and testing purposes.

 

---

Configuring EDI Integration to Receive an EDI Document

This section describes how to configure EDI Integration so that the BEA WebLogic Adapter for Power.Enterprise! 3.1 can receive an EDI document and send it to the WebLogic Integration process engine as an XML document.

Pre-Planning

• Determine the EDI standard, version, and document type of the document you will receive. For example, you might select an X12 850 document v4010, which is an X12-standard, 850-type document, version 4010.

• Define the XML format that you will use internally. This XML format should contain a complete data map of the fields in the EDI document that you will use.

• Create a DTD and an XSD for the XML document. You must create both because Power.Enterprise! and WebLogic Integration do not use the same data file format for this step. WebLogic Integration requires an XSD (if you supply one at all), while Power.Enterprise! requires a DTD. You should note that Power.Enterprise! does not provide any export utility to export a DTD or XSD from a map definition once the DTD or XSD has been imported. You will be responsible for creating both the DTD and XSD files.

Within Power.Enterprise!

1. Create a map between the XML document and the EDI document. Import the DTD into Power.Map! to load the XML document standard. The appropriate EDI document should already exist in the Power.Server! repository. If the EDI document is not present, contact BEA Customer Support. For more information about how to do this, see the following topics:

   • Mapping XML and EDI Data

   • Chapter 3, "Maps" in the Power.Map! User Reference Manual

2. Define an inbound connection. This connection should use your trading partner's connection protocol, which you should have defined already. For more information, see Connections and VAN Connectivity.

3. Define an RMI target connection. This connection is used to communicate with the WebLogic Integration process engine.

4. Define an exchange profile, using the procedure discussed in Configuring Exchange Profiles. This exchange profile should connect the inbound connection from your trading partner to the RMI target connection.

Within BEA WebLogic Integration

1. Create an application view, using the procedure in Configuring the BEA WebLogic Adapter for Power.Enterprise!.

2. Create an event for the application view you just created, using the procedure in Configuring Events. Be sure to set the following parameters:

   • Event Name: A descriptive name for the event, such as ReceivePurchaseOrder

   • Event Description: Text that provides details about the event

   • RMI Service Name: Should match RMI service name defined in the Power.Enterprise! RMI target connection set up in the Within Power.Enterprise! section

   • XSD: The XML schema of the XML message to be received (optional)

   • XML Root Element: The XML root element of the XML schema (optional)

3. Deploy the application view you have created and defined.

Verify that the Power.Server! instance is running. At this point, the application view should be available to the WebLogic Integration process engine through the application integration plug-in. For more information about the application integration plug-in, see Understanding the Application Integration Plug-In for BPM in Introducing Application Integration.

Note: Always start the Power.Server! before you start WebLogic Integration or WebLogic Server. The WebLogic Integration connectors expect to see the Power.Server! running when they are initialized, and they throw exceptions if Power.Server! is not running when they are initialized.

 

---

Configuring EDI Integration to Send an EDI Document

This section describes how to configure EDI Integration to send an EDI document using an XML document in the WebLogic Integration process engine as the source.

Pre-Planning

1. Determine the EDI standard, version, and document type of the document you will receive. For example, you might select an X12 850 document v4010, which is an X12-standard, 850-type document, version 4010.

2. Define the XML format that you will use internally. This XML format should contain a complete data map of the fields in the EDI document that you will use.

3. Create a DTD and an XSD for the XML document. You must create both because Power.Enterprise! and WebLogic Integration do not use the same data file format for this step. WebLogic Integration requires an XSD (if you supply one at all), while Power.Enterprise! requires a DTD. You should note that Power.Enterprise! does not provide an export utility that can be used to export a DTD or XSD from a map definition once the DTD or XSD has been imported. You are responsible for creating both the DTD and XSD files.

Within Power.Enterprise!

1. Create a map between the XML document and the EDI document. Import the DTD into Power.Map! to load the XML document standard. The appropriate EDI document should already exist in the Power.Server! repository. If the EDI document is not present, contact BEA Customer Support. For more information about how to do this, see the following topics:

   • Mapping XML and EDI Data

   • Chapter 3, "Maps" in the Power.Map! User Reference Manual

2. Define an outbound connection. This connection should use your trading partner's connection protocol, which you should have defined already. For more information, see Connections and VAN Connectivity.

3. Define an RMI source connection. This connection is used to communicate with the WebLogic Integration process engine.

4. Define an exchange profile, using the procedure discussed in Configuring Exchange Profiles. The exchange profile should connect the RMI source connection to your trading partner's outbound connection.

Within BEA WebLogic Integration

1. Create an application view, using the procedure in Configuring the BEA WebLogic Adapter for Power.Enterprise! in this document.

2. Create a service for the application view you just created, using the procedure in Configuring Services in this document. Be sure to set up the following parameters:

   • Service Name: A descriptive name for the service, such as SendPurchaseOrder

   • Service Description: Text that provides details about the service

   • Connection Name: Should match the RMI service name defined in the Power.Enterprise! RMI target connection set up in the Within Power.Enterprise! section.

   • XSD: The XML schema of the XML message to be sent (optional)

   • XML Root Element: The XML root element of the XML schema (optional)

• Deploy the application view you have created and defined.

Verify that the Power.Server! instance is running. At this point, the application view should be available to the WebLogic Integration process engine through the application integration plug-in. For more information about the application integration plug-in, see Understanding the Application Integration Plug-In for BPM in Introducing Application Integration.