Multiple logic plug-ins that share the same business protocol and are processed in a predefined sequence at run time. Routers and filters can consist, respectively, of multiple router logic plug-ins and multiple filter logic plug-ins, each of which executes as a business message passes through that plug-in point of the c-hub. After one plug-in finishes executing, the next one in the sequence (the "chain") is activated. Each successive plug-in can access the shared message information as the business message passes through the c-hub and can modify or override the changes made by predecessor plug-ins in the chain. Router logic plug-ins form one chain, and filter logic plug-ins form another. The logic plug-ins in the router chain execute first, followed by the plug-ins in the filter chain. Customer-supplied logic plug-ins must be part of a router logic plug-in chain or a filter logic plug-in chain, even when they do not have routing or filtering functionality.
The central component of BEA WebLogic Collaborate, through which trading partners communicate with each other. The c-hub is responsible for routing messages between c-enablers and between non-XOCP clients, and for managing the life cycle of conversations between trading partners. A single recoverable c-hub can host multiple collaboration spaces. The c-hub provides the following services: conversation coordination, security, administration, reliable messaging, persistence and recovery processes, local logging, and XML services.
HTML interface through which the WebLogic Collaborate c-hub system administrator enables, disables, configures, and monitors c-hubs, trading partners, and collaboration spaces. The console is also used to specify business protocols, document definitions, message definitions, subscriptions, and Large Messaging Support; to import XML files from and export them to the repository; and to administer SSL protocol and the HTTP proxy server. The C-Hub Administration Console displays a list of all c-spaces, active conversations, and active trading partners, with identification, message, and state information.
The ability of BEA WebLogic Collaborate and BEA WebLogic Process Integrator to terminate a conversation intelligently and in a controlled manner. For WebLogic Process Integrator clients, conversation is terminated when the conversation initiator workflow reaches a done state, as defined by the conversation termination property (Success or Failure) for the done node. Conversation participant workflows can end their own participation in a conversation, but only conversation initiator workflows can terminate a conversation. For BEA WebLogic Collaborate clients, conversation termination is initiated by the Conversation.terminate() operation, which is performed by the conversation initiator and which results in the receipt of a ConversationHandler.onTerminate() message by each conversation participant.