Design Phase: Using Enterprise Designer

Within Enterprise Designer, theB2B Host Designer is used to create B2B Hosts. Each B2B Host is a logical collection of business and enveloping attribute definitions, messaging and packaging attribute definitions, and transport attribute definitions.

Attribute definitions supply metadata for a transaction profile — in other words, the types of parameters to be supplied for exchanging messages with trading partners.

After the B2B Host is set up, a connectivity map is created to connect it to both an LDAP external and an Oracle external. Building a deployment using this connectivity map and an environment creates an eXchange Service object in the same environment that contains the LDAP and Oracle externals and a B2B Configuration object. Entries related to the host attributes are updated in the LDAP database. (In future releases, the eXchange Service corresponding to the B2B Host is configurable with keystores, trust stores, and certificates for authentication and non-repudiation. ) Other connectivity maps are created, built, and deployed to connect the ePM GUI application with the LDAP external and the Message Tracker application with the Oracle external.

After the eXchange Service is created, it is used in connectivity maps (both user-created and also pre-supplied) to expose services such as batching/unbatching, dialogs with the trading partner, error-handling, and so forth. When a deployment profile is built and deployed that references the connectivity maps located in the eXchange⇒;Deployment project folder, the selector/handler BPs are exposed to ePM and made available for run time.