The following list describes the B2B host Projects’ components and their functions:
bhAtlanta and bhBerlin are the actual B2B hosts. These hosts have the following components and functions:
ebXML, under Business Protocols (BPs), the only messaging attribute definition (MAD) contained in the Project, for each B2B host.
BPs that reference two message services (both under ebXML): PurchaseService and urn:oasis:names:tc:ebxml-msg:service, for each B2B host.
PurchaseService message service contains the Projects’ messaging actions, inbound and outbound.
There are two external delivery channels (XDCs) for the single ebXML MAD in each B2B Host. These XDCs are named xdcAtlanta_ebXML_via_HTTP and xdcBerlin_ebXML_via_HTTP.
For transport to and from TPs, these XDCs reference the standard SeeBeyond-supplied HTTP transport attribute definitions (TADs).
Only bhAtlanta has internal delivery channels (IDCs). These channels use JMS to communicate in the sender (ToInternal) direction. These IDCs are:
idcAtlanta_ebXML_Send_via_File
idcAtlanta_ebXML_Recv_via_File
The Enterprise Designer canvas cmHostAtlanta is a Connectivity Map. It shows a graphical view of the cmHostAtlanta components.
This Connectivity Map has the following components:
bhAtlanta1: Only input, an instance of bhAtlanta, with two outbound connections.
extOracleOut: Only output, an instance of extOracleOutAtlanta, with two inbound connections.
mtrk: Instance of Message Tracking, connecting to the other two components.
For more information on eXchange’s Message Tracking, see the eXchange Integrator User’s Guide.
The Enterprise Designer canvas cmHostBerlin is also a Connectivity Map (similar to Components of Companies’ B2B Host Projects) and has the following components:
bhBerlin1: Only input, an instance of bhBerlin, with two outbound connections.
extOracleOut: Only output, an instance of extOracleOutBerlin, with two inbound connections.
mtrk: Instance of Message Tracking, connecting to the other two components.