Getting Started

The business-to-business (B2B) integration samples are provided to help you understand how B2B integration functionality works in WebLogic Integration. In addition, successful installation and setup of the Hello Partner sample provides verification that you have successfully installed WebLogic Integration and configured it properly.

This section includes the following topics:

• Overview of Samples

• Preparing to Run the Samples

 

---

Overview of Samples

This section introduces the seven samples described in this document: Hello Partner, Channel Master, RosettaNet 2.0 Security, Trading Partner Zeroweight Client, Messaging API, and ebXML.

Note: Four of the samples are based on features that are deprecated as of this release, however. The Hello Partner, Channel Master, and Trading Partner Zeroweight Client samples are all based on the XOCP protocol, which is deprecated as of this release. The Messaging API sample is based on the Messaging API, which is also deprecated now. For information about the features that are replacing XOCP and the Messaging API, see BEA WebLogic Integration Release Notes.

With the exception of the Hello Partner and the ebXML samples, which verifies the successful use of the XOCP and ebXML messaging protocols, respectively, the samples demonstrate B2B integration solutions to plausible business problems.

The following descriptions provide a high-level view of each sample:

• Hello Partner Sample—Demonstrates the basic handshake necessary for communication. The Hello Partner sample uses the XOCP business protocol.

• Channel Master Sample—Demonstrates how a large trading partner uses WebLogic Integration to automate its supply chain. The sample shows both point-to-point and multicast (broadcast) communications using the XOCP business protocol between WebLogic Integration trading partners.

• RosettaNet 2.0 Security Sample—Demonstrates how WebLogic Integration can be used to implement RosettaNet 2.0 PIP 3A2 and PIP 0A1 using workflows. This sample uses the WebLogic Integration security features required for RosettaNet 2.0 support: two-way SSL authentication, digital signatures, data encryption, and nonrepudiation.

• Trading Partner Zeroweight Client Sample—Illustrates a request-reply scenario in which two trading partners without a B2B integration installation use the B2B integration mailbox interface. Two types of zeroweight client communication are simulated for this demonstration:

  • Browser-based client—Uses XML and JMS to prepare, deliver, and collect information

  • File-sharing client—Uses a third-party file-sharing server to exchange messages

Note: The Trading Partner Zeroweight Client sample is based on the XOCP protocol, which is deprecated in this release of WebLogic Integration. For information about the feature that is replacing XOCP, see BEA WebLogic Integration Release Notes.

• Messaging API Sample—Shows how the WebLogic Integration Messaging API can be used. Specifically, it demonstrates the use of two message-delivery mechanisms available with the Messaging API and the logic plug-in feature of WebLogic Integration B2B integration.

• ebXML Sample—Demonstrates how WebLogic Integration can be used to implement an ebXML business transaction between two trading partners, each of which deploys WebLogic Integration. Specifically, it shows the design and use of two workflows, one for each trading partner. The workflows choreograph the exchange of ebXML-based business messages between the trading partners.

 

---

Preparing to Run the Samples

Before you can run the B2B samples, you must install two components of WebLogic Platform, WebLogic Server and WebLogic Integration, along with the sample applications for both. You must also configure the samples. If you have not already performed these tasks, complete the following steps:

1. Install BEA WebLogic Platform.

   For instructions, see Installing BEA WebLogic Platform in the BEA WebLogic Platform document set, available at the following URL:

   http://download.oracle.com/docs/cd/E13196_01/platform/docs70/install/index.html

   During installation, you have a choice of two procedures:

   • Typical Installation—If you select this option, the installer automatically installs the WebLogic Server, WebLogic Integration, WebLogic Portal, and WebLogic Workshop components, along with the sample applications.

   • Custom Installation—If you select this option, the Choose Components window is displayed. At a minimum, you must select the following components:

     WebLogic Server (specifying Server and Server Examples)

     WebLogic Integration (specifying Integration Server and Samples)

   By default, the preconfigured sample domain is configured to use the PointBase database.

2. Configure and start the server in the preconfigured samples domain.

   For instructions, see "Configuring and Starting the Samples Domain" in Getting Started in Starting, Stopping, and Customizing BEA WebLogic Integration.

When you execute the RunSamples command as described in "Configuring and Starting the Samples Domain," the following actions are performed:

• The samples database is created.

• The sample repository data is bulk loaded into the database.

• WebLogic Server is started and the workflows are imported. A browser is started and the samples launcher page is displayed.

Note: To display the samples launcher page on a UNIX system, your PATH environment variable must include the directory in which the Netscape executable (netscape) resides. For additional Web browser configuration requirements, see "Web Browser Configuration Requirements" in WebLogic Integration Administration and Design Tools in Starting, Stopping, and Customizing BEA WebLogic Integration.

Once you have configured the samples and started the server in the samples domain, any additional steps required to configure a particular sample are provided in the documentation for that sample. Instructions are provided for both Windows and UNIX systems.

Switching the Default Database

You can use any supported database with the samples domain. The BEA WebLogic Integration Database Wizard can be used to update your samples domain to a new database after installation. If you would like to change the database used by the samples domain, complete the following steps:

1. Use the Database Wizard to switch to the new database.

   For instructions, see the "Using the Database Wizard" and "Specifying a New Database for a Domain" topics in Customizing WebLogic Integration in Starting, Stopping, and Customizing BEA WebLogic Integration.

2. Execute the RunSamples command to configure the new database, start the samples domain, and display the samples launcher in your Web browser.

   For instructions, see "Configuring and Starting the Samples Domain" in Getting Started in Starting, Stopping, and Customizing BEA WebLogic Integration.

WebLogic Integration Sample Domain

As described in Getting Started in Starting, Stopping, and Customizing BEA WebLogic Integration, a domain is a set of interrelated WebLogic Server resources defined in a single configuration file. A special WebLogic Server domain is set up to run all WebLogic Integration samples that require only one server. During installation, this samples domain is fully configured, but not populated. It resides in the BEA_HOME/weblogic700/samples/integration/config/samples directory, where BEA_HOME is the top-level BEA directory, for example, on Windows, c:\bea.

The Samples domain uses the PointBase database by default. The default database can be changed using the Database Wizard as described in Switching the Default Database.

For additional information about using domains installed with WebLogic Integration, see Getting Started in Starting, Stopping, and Customizing BEA WebLogic Integration.

Browser Proxy Settings

If your browser is unable to connect to the URL for the samples launcher, it may be using a proxy server that prevents you from connecting to your local WebLogic Server. If this condition exists, the following error message is displayed:

The requested URL could not be retrieved

To bypass the proxy server, change the browser proxy settings so that the browser does not use the proxy server to access the servlet. The procedure for making this change is browser-dependent:

• For Internet Explorer, choose Tools—>Internet Options—>Connections—>LAN Settings—> The Local Area Network (LAN) Settings Dialog box is displayed. Select the following option: Bypass proxy server for local addresses.

• For Netscape, choose Edit—>Preferences—>Advanced—>Proxies—>View. In the Exceptions text field, specify your localhost:listening_port. (The value of listening_port should be the listening port number specified in the config.xml file.) The default is 7001.