For complete information on how to perform these operations, see the eGate Integrator User’s Guide and the eXchange Integrator User’s Guide, as well as the sample scenario provided in Chapter 5, Implementation Scenario.
Before you can use the ebXML Protocol Manager with eXchange, perform the following actions:
Create and set up at least one ebXML B2B host Project
Create and set up other Projects, as needed
Deploy and activate the Project Profiles
The sample scenario provided in Chapter 5, Implementation Scenario assumes you use the sample Projects provided and the default configurations where possible.
Each ebXML Protocol Manager installation requires at least one Environment. The sample scenario provided in Chapter 5, Implementation Scenario assumes you use the sample Environments provided and the default configurations for all servers where possible.
You must also make any changes where needed, for example:
Each of the companies in the sample scenario has an eXchange installation with one Environment.
Your first step is to create the Project’s Environment and its basic setup as follows:
Using Enterprise Designer, create a new Environment.
Create at least one new Logical Host, as follows:
Create the Integration Server for the Logical Host.
Create the SeeBeyond JMS IQ Manager for that Logical Host.
Create a keystore then import at least one key file and certificate file to activate the protocol’s cryptographic features.
Create the following external system instances:
Batch eWay in local file mode
Inbound and outbound File eWays
Oracle (must also be configured; see Setting Up Oracle External System)
Activating a Project DP creates an eXchange service that provides a connection to Enterprise Manager’s Message Tracking feature and the eXchange database.
The B2B host Project contains the following components:
At least one message service used by the B2B host. It contains messaging actions, alternating inbound and outbound.
The B2B host component, which performs the following functions:
Has business protocols that reference the Project’s services.
Defines XDCs for the Project’s messaging attribute definitions (MADs). For transport to and from TPs, these channels reference the standard SeeBeyond-supplied HTTP transport attribute definitions (TADs).
Defines IDCs (optional). These channels use the Java Messaging Service (JMS) to communicate in the Sender direction.
A Connectivity Map with the following components:
Input, an instance of the B2B host, with two outbound connections
Output, an instance of the eXchange database (Oracle), with two inbound connections
Instance of Message Tracking, connecting to the other two components
For more information on the Message Tracking feature, see the eXchange Integrator User’s Guide.
You must activate the B2B host’s DP. This action creates an eXchange service for the B2B host. The creation and activation of this service is necessary for data communication between TPs.
Before you activate a B2B host Project DP, this DP must be pointed to the appropriate Environment, and this Environment must contain a correctly configured Oracle external system instance.
You must set up an Oracle external system instance in a B2B host’s Environment in Enterprise Designer. Perform this operation using the following general steps:
Create an Oracle external system instance for the current Project on the Environment.
Set the instance up, that is, customize it, for your intended uses.
For complete information on how to create a new external system and its instance in Enterprise Designer’s Environment, see the eGate Integrator User’s Guide. Also, see the Oracle eWay Intelligent Adapter User’s Guide.
The procedure in the rest of this section explains how to set up an Oracle external system instance for ebXML Protocol Manager.
Correctly configure the following properties in the eWay’s Properties dialog box:
Other properties are optional.
When all properties have been configured correctly for your site, click OK.
The Project’s Environment now has its Oracle external system instance configured correctly for activation of the B2B host. For details, see the sample scenario explained in Run-time Steps.