BEA Logo BEA WLI Release 2.1

  BEA Home  |  Events  |  Solutions  |  Partners  |  Products  |  Services  |  Download  |  Developer Center  |  WebSUPPORT

   http://www.oracle.com/technology/documentation/index.html   |   Site Map   |   Search   |   PDF Files   |   Contact   |   Glossary

 

   WLI Doc Home   |   B2B Topics   |   Using EDI   |   Previous Topic   |   Next Topic   |   Contents   |   View as PDF

Configuring Power.Enterprise!

 

This section describes the installation and configuration of Power.Enterprise! and its associated software:

 

Installing Power.Enterprise!

Power.Enterprise! is delivered in two packages that must be installed separately. In addition, you may want to install Cleo A+ to manage VAN connectivity issues.

If you plan to install both Power.Server! and Power.Client! on the same machine, you must install them in separate directories.

Getting Licenses

Whether you download Power.Enterprise! as part of the WebLogic Integration 2.1 installation or install it from CD media, you will need to obtain your Power.Enterprise! 3.0 evaluation license from the BEA website at the following URL:

http://commerce.bea.com/downloads/weblogic_integration.jsp

A Power.Enterprise! production license is provided when you purchase BEA WebLogic Integration. For more information, please contact your BEA sales representative.

In addition, you may download and install a 30-day trial of Cleo A+, for handling VAN connectivity. To convert your trial license to a production license, contact Cleo Communications.

Access to the Get2Connect.Net VAN is included with the BEA WebLogic Adapter for Power.Enterprise!. To use Get2Connect.Net, contact Peregrine Customer Support through their Web site at http://www.peregrine.com/.

Installing the Power.Server!

To install the Power.Server! software, you must fulfill the prerequisites listed in the previous sections of this document. For general information about installing Power.Server!, see Installing the Power.Enterprise! Software in Installing BEA WebLogic Integration.

Installing the Power.Client!

To install the Power.Client! software (specifically Power.Map! and Power.Manager!), you must fulfill the prerequisites listed under Installing Power.Enterprise!. For general information about installing Power.Map! and Power.Manager!, see Installing the Power.Enterprise! Software in Installing BEA WebLogic Integration.

Connecting to Get2Connect.Net

To use Get2Connect.Net, you must have the Power.Enterprise! software installed. You must also have a valid Product Serial Number (PSN) to register as a Get2Connect.Net trading partner. To get a valid PSN, contact BEA Customer Support.

Installing Cleo A+

If you intend to use Cleo A+ for VAN communications, go to the following URL:

http://www.cleo.com/install/peregrine/install.htm

This Web page provides downloadable installation sets for all platforms supported by Power.Server!, as well as installation and user documentation. The downloadable software includes a trial license. For production licensing, contact Cleo Communications.

Downloading Software Updates

Power.Enterprise! is designed to be updated with downloaded software patches from the BEA Customer Service Web site.

To install software patches for Power.Enterprise!:

  1. From within Power.Manager! click Self Service, then click Software Update.

  2. Click Step 1: Select Software. This launches a Web browser which automatically connects to the BEA Customer Service web page, listing all software update files available for download. Instructions for installation of these updates are also included on this Web page.

Updating EDI Document Descriptions

Power.Enterprise! ships with definitions for many standard EDI documents included. BEA will also make new definition sets available through BEA Customer Service.

To install new standards downloaded from the BEA Customer Service Web site:

  1. From within Power.Manager! click Self Service, then click Standards Update.

  2. Click Step 1: Select Standards. This launches a Web browser which automatically connects to the BEA Customer Service web page, listing all EDI definition files available for download.

  3. Select and download the EDI definition files that you require.

  4. Place the downloaded files into the following directory: 
    Power_Server_install_dir\downloads\metadata\

  5. Stop, then restart the Power.Server on which you have installed the definition file.

  6. Remove the downloaded files from the following directory: 
    Power_Server_install_dir\downloads\metadata\

  7. To access the document descriptions from within Power.Map!, check them out from the server.

Connecting to a Server for the First Time

Before you can log in to Power.Manager! or Power.Map!, you must create a Power.Server! connection. Subsequently, you can use the same procedure to connect to other instances of Power.Server!, allowing you to manage multiple instances of Power.Server! from a single console. All connection data is persistent: once you create a connection, it will be available every time you start Power.Manager!.

To create a connection:

  1. Log in to Power.Manager! or Power.Map by choosing
    Start Menu—>Programs—>Power.It. Select the appropriate application. To create a server connection, Power.Server! must be running on the machine to which you want to connect.

    Figure 4-1 Power.Manager! Server Connection Dialog Box


     

  2. Click Add to add a new Power.Server! connection.

    Figure 4-2 Power.Manager! Server Add Dialog Box


     

  3. Enter the Server Hostname and Server Control Port of the Power.Server!. Click Add. A list of defined instances of Power.Server! is displayed.

  4. Select the Power.Server! to which you want to connect from the list of defined connections. Click Connect. The Power.Manager! Server Connection dialog box is displayed.

    Figure 4-3 Power.Manager! Server Connection Dialog Box


     

 

Configuring Power.Enterprise!

Power.Enterprise! allows you to configure multiple connections to the BEA WebLogic Adapter for Power.Enterprise!. Each connection to the BEA WebLogic Adapter for Power.Enterprise! is defined as a separate RMI connection, either sending data to or receiving data from Power.Enterprise!. All other configuration required by Power.Enterprise! is designed to configure trading partners, maps, external connections, and exchange profiles. When initially configuring Power.Enterprise!, be sure to configure the following entities in the order shown:

 

Configuring Trading Partners

To use EDI Integration with WebLogic Integration, you must enter your trading partner data into both Power.Enterprise! and WebLogic Integration. No mechanism exists to move trading partner data either to or from Power.Enterprise!, so you any trading partner data registered with WebLogic Integration must also be entered into Power.Enterprise!.

You must create a Power.Enterprise! trading partner profile for every trading partner involved in your transactions, including your own company.

To create a new trading partner:

  1. Start Power.Manager!. A list of defined instances of Power.Server! is displayed.

  2. Select the instance of Power.Server! to which you want to connect. (If no Power.Server! connections are defined, see Connecting to a Server for the First Time.)

    Figure 4-4 Power.Manager! Server Connection Dialog Box


     

  3. Click Connect. The Power.Manager! main window is displayed.

    Figure 4-5 Power.Manager!


     

  4. To set up a trading partner's company profile, choose Partners—>Company Profiles. The Company Profile window is displayed.

    Figure 4-6 Company Profile List


     

  5. Click New Company. Enter the required information about your trading partner.

For more information about creating and maintaining trading partners, see Chapter 4 of the Power.Manager! User Reference Manual.

 

Mapping XML and EDI Data

One of the primary goals of Power.Enterprise! is to enable you to manage the translation of messages from a standard data format into a standard EDI message format. To do so, you must create maps between the data format you have selected and the corresponding EDI message. These maps are unidirectional: they operate only in one direction. Thus, if you need to be able to translate data back and forth between a particular XML message format and a specific EDI message format, you must create two maps: one for outbound transformation (XML to EDI) and one for inbound transformation (EDI to XML).

Fortunately, creating such maps is not a difficult task. Power.Map! can understand a variety of standard document definitions, including flat files, database tables, XML, and all the major EDI formats (X12, EDIFACT, and TRADACOMS). As used within Power.Map!, a document definition is an element-by-element description of a document, its structure, and the data carried within it. Thus, you can use standard document definitions to outline your maps, then simply connect the individual data elements between two document definitions using a drag-and-drop interface.

Figure 4-7 Power.Map! Main Window


 

For more information about creating maps, see the Power.Map! User Reference Manual.

You may work on maps without being connected to a Power.Server! instance. If you try to use any repository commands, however, the Server Connection dialog box is displayed, requiring you to connect to a server instance so the repository command can be run. To define a server connection, see Connecting to a Server for the First Time.

At any time, you can save a copy of the map you have created on your local system. Choose File—>Save, then enter a descriptive name for the map file in the dialog box. The map is stored as a jar file.

Before you can use a map in production, you must promote the map to your server. Select the Finish tab, then click Promote at the bottom of the tab to send the map to the server. If you are not already connected to the server, you must establish a connection before you can promote the map.

 

Connections and VAN Connectivity

Connections define how message traffic is delivered, both into and out of the Power.Server!. Before you can use the BEA WebLogic Adapter for Power.Enterprise!, you must configure a minimum of four connections:

Two of these connections, the source and target RMI connections, are used to communicate with BEA WebLogic Integration. These two connections are used by all EDI transactions.

Creating RMI Connections

To set up the source and target RMI connections:

  1. From within Power.Manager!, select Connections. The Connections window is displayed.

    Figure 4-8 Power.Manager! Connections List


     

  2. Create a source RMI connection. To begin, click Add New. The Create New Connection dialog box is displayed.

    Figure 4-9 Create New Connection Dialog Box


     

  3. Set the name to BEASource, the Transport to RMI, and the Direction to Source. Click OK. The Connection Properties dialog box is displayed.

    Figure 4-10 Inbound RMI Properties


     

  4. Set Status to Active and Envelope Recognition BDD to XMLEnvelope. Click OK.

  5. Create an outbound RMI connection. To begin, click Add New. The Create New Connection dialog box is displayed.

  6. Set the name to BEATarget, the Transport to RMI, and the Direction to Target. Click OK. The Connection Properties dialog box is displayed.

    Figure 4-11 Outbound RMI Properties


     

  7. Set Status to Active, Target to localhost, and Service Name to edi. Click OK.

Creating Trading Partner Connections

The other two connections, the inbound and outbound trading partner connections, are specific to each trading partner. Therefore, you must define a unique pair of connections for each trading partner. When you set up each pair, you must select the transport that you and your trading partner will use. We recommend the following transport options:

Other connection options are also available. For details about all options, see Chapter 3 of the Power.Manager! User Reference Manual.

 

Configuring Exchange Profiles

The exchange profile specifies how a trading partner exchanges messages through Power.Server!. Because Power.Server! is an EDI gateway, it is not the final point of receipt for a message. An exchange profile describes how Power.Server! receives a message, transforms it, and sends it to its destination. For example, an exchange profile might define the receipt of an EDI message from a trading partner, its transformation into an XML message, and its delivery to the BEA WebLogic Adapter for Power.Enterprise!.

Exchange profiles cannot be created unless certain prerequisite information has been defined. Specifically, you must have created and promoted to the server your exchange maps, your trading partner profile, and both the source and target connections. (The source and target connections post messages to Power.Server! and receive messages from Power.Server!, respectively.) For example, to create an exchange profile that allows you to send a message to your trading partner, you need the following:

Other information is also required. For details, see Chapter 4 of the Power.Manager! User Reference Manual. For examples of both inbound and outbound exchange profiles, see EDI Sample in this document.

 

back to top previous page next page

 

Copyright © 2001 BEA Systems, Inc. All rights reserved.
Required browser: Netscape 4.0 or higher, or Microsoft Internet Explorer 4.0 or higher.