BEA Logo BEA WebLogic Collaborate Release 1.0.1

  Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy

 

   WebLogic Collaborate Doc Home   |   C-Hub Administration   |   Previous Topic   |   Next Topic   |   Contents   |   Index

Introducing the C-Hub

 

The following sections introduce the c-hub component of the BEA WebLogic Collaborate system:

Before you read this document, it is recommended that you read the BEA WebLogic Collaborate Getting Started document.

 


C-Hubs

The following sections describe c-hubs:

C-Hubs and C-Enablers

An electronic marketplace, or e-market, is an environment through which companies conduct business-to-business e-commerce. E-markets offer a set of services to conduct, manage, and orchestrate conversations between various trading partners.

WebLogic Collaborate offers a flexible, extendable, and scalable solution for implementing e-markets. A WebLogic Collaborate system consists of the following main parts:

The following figure shows an example of the relationships among c-hubs, c-spaces, and c-enablers. Each trading partner uses a c-enabler to join a c-space, which exists in a c-hub. By joining a c-space, the trading partner can participate in conversations with other trading partners.

Figure 1-1 Architecture of a Possible WebLogic Collaborate Configuration

In the figure, c-enabler #3 is colocated with the c-hub, which means that they are deployed on the same BEA WebLogic ServerTM instance. A c-hub runs on a single WebLogic Server instance, and a WebLogic Server instance can host a single c-hub. However, multiple c-enablers can run on a single WebLogic Server instance, as illustrated by c-enablers #1 and #2 in the figure. Instead of running on WebLogic Server, a c-enabler can run on WebLogic Express as illustrated by c-enabler #4.

A c-hub node (the machine on which a c-hub is running) can host one or more c-enablers, as illustrated by c-enabler #3. In the figure, the c-enablers are deployed on various WebLogic Servers or WebLogic Express, but all the c-enablers participate in the same c-space. A non-XOCP client can also participate in a c-space.

A c-hub represents an e-market owner and can host multiple c-spaces. Each trading partner can subscribe to business conversations, which are communicated through a mediated messaging system, and define local workflow and actions to execute upon receipt of business events (messages or documents).

The c-enabler is a 100-percent Java class library that is deployed at each participant node to allow access to c-spaces hosted on a c-hub. The c-enabler is typically downloaded with authorization from the e-market administrator. For a detailed description of c-enablers, see the BEA WebLogic Collaborate C-Enabler Administration Guide.

For a complete explanation of e-markets, collaboration, and other related concepts, see the Overview section in BEA WebLogic Collaborate Getting Started.

C-Hub Services

A c-hub provides the following shared services to c-enablers:

 


Architecture

The following figure shows the c-hub architecture. WebLogic Collaborate runs on WebLogic Server. The c-hub can integrate with any packaged, custom, or mainframe applications running on WebLogic Server.

Figure 1-2 C-Hub Architecture

 


Message Processing

The following figure illustrates how a c-hub processes a message.

Figure 1-3 Message Processing

The following steps describe the preceding figure:

  1. The transport service reads the incoming message and forwards it to the appropriate decoder based on the message protocol, such as XOCP or RosettaNet. The URL on which the transport service receives the message identifies the protocol and the c-space. For information about business protocols, see Configuring Business Protocols.

  2. The decoder processes the protocol-specific headers, identifies the sending trading partner, enlists the sending trading partner in a conversation, prepares a reply to return to the sender, and forwards the message to the scheduling service.

  3. The scheduling service enqueues the message to store it for subsequent retrieval and forwards the message to the router.

  4. The router determines the trading partners to whom the message should be routed and forwards the message to the routing service. You can use logic plug-ins to add recipients to or delete recipients from the list. For information about routing, see Routing and Filtering XOCP Business Messages. For information about logic plug-ins, see Developing Logic Plug-Ins in the BEA WebLogic Collaborate Developer Guide.

  5. The routing service performs the final validation of the message recipients, stores the message for delivery to each validated recipient, and forwards one copy of the message to the filter for each validated recipient.

  6. The filter receives the message for a specific recipient and determines whether or not to send the message to the recipient. You can use logic plug-ins to affect how this decision is made. If the message is going to be sent to the recipient, the filter forwards the message to the scheduling service. For information about filtering, see Routing and Filtering XOCP Business Messages. For information about logic plug-ins, see Developing Logic Plug-Ins in the BEA WebLogic Collaborate Developer Guide.

  7. The scheduling service performs additional internal operations related to quality of service issues and conversation management. The scheduling service forwards the message to the encoder. For information about quality of service, see the BEA WebLogic Collaborate Developer Guide.

  8. The encoder transforms the message as necessary to support the business protocol and forwards the message to the transport service.

  9. The transport service sends the message to the recipient.

 


Configuration and Monitoring

The C-Hub Administration Console enables you to create, configure, and monitor a c-hub. For information about the C-Hub Administration Console, see Using the C-Hub Administration Console, which is Part II in this document.

The Bulk Loader enables you to create and configure a c-hub. For information about the Bulk Loader, see Working with the Bulk Loader.

You can create c-hub management applications that use the c-hub MBeans to monitor c-hub run-time activities. MBeans function as a monitoring API that is based on the Java Management Extensions (JMX) published by Sun Microsystems, Inc. For information about working with the c-hub MBeans, see the BEA WebLogic Collaborate Developer Guide.

 


Repository

The repository is a database that stores configuration information for the c-hub object. The following figure shows the relationships among elements in the repository. Solid lines represent inclusion, which means that if you remove an element, all the inclusion elements are also deleted. For example, if you remove a c-space, then all the collaborators for that c-space are also removed. Dashed lines represent reference, which means that if you remove an element, the elements referenced by the removed element are not removed. For example, if you remove a business protocol, the reference to the business protocol definition is removed, but the business protocol definition remains.

Figure 1-4 Element Relationships

To manage the information in the repository, you can:

The following sections provide overviews of the main elements in the repository:

C-Hubs

C-Spaces

Conversation Definitions and Roles

Document Definitions

Trading Partners and Trading Partner Protocols

Logic Plug-Ins

Business Protocols and Business Protocol Definitions

Message Definitions

 


Responsibilities and Tasks

The following responsibilities are associated with c-hubs:

Working with a c-hub involves the following tasks: