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

With the exception of the Hello Partner sample, which verifies the successful use of the XOCP messaging protocol, the samples demonstrate B2B integration solutions to plausible business problems. The following samples are described in this document:

• Hello Partner Sample—Demonstrates the basic handshake necessary for communication. The Hello Partner sample uses XOCP, the default messaging protocol for B2B integration.

• 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 Lightweight 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 lightweight 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

• 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.

 

---

Preparing to Run the Samples

Before you can run the B2B samples, you must install WebLogic Integration and configure the samples. If you have not already done so, complete the following steps:

1. Install WebLogic Integration.

   For instructions, see Installing BEA WebLogic Integration. When prompted to choose an install set, select WebLogic Integration Full Installation With Samples (the default selection).

   The WebLogic Integration installer prompts you to specify the databases to configure for the samples and production domains. The samples database information is used when you configure the samples.

2. Configure and start the server in the 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 WebLogic Database Configuration Wizard can be used to update your samples domain to a new database. If you would like to update the samples domain to use a new database, complete the following steps:

1. Use the WebLogic Integration Database Configuration Wizard to switch to the new database.

   For instructions, see the "Using the Database Configuration 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 Domains

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. This domain, which is fully configured after installation, but is not yet populated, resides in the WLI_HOME/config/samples directory. The Samples domain uses the database chosen during installation, or when the WebLogic Integration Database Configuration Wizard was last run as described in Switching the Default Database.

For additional information about using the preconfigured 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.