Configuring fixed workflows
Introduction described the
two fixed inbound workflow steps that you can configure--one for
unpackaging a protocol and one for parsing the protocol. For outbound
workflows, there is one step, for protocol packaging.
If you
are going to use a user-defined handler to configure a workflow
step, upload the handler, as described in Uploading
handlers.
To configure a fixed workflow, perform the following steps:
- Click Hub Admin > Hub Configuration > Fixed Workflow.
- Click either Inbound or Outbound.
- Click the View Details icon next to the
name of the step you want to configure.
The step, along with a list of handlers already configured for
that step, is listed. See Inbound
workflows and Outbound
workflow for a list of default handlers.
- Click the Edit icon to edit the list of
handlers.
- Perform one or more of the following tasks for each step you
want to modify.
- Add a handler by selecting the handler from the Available List and
clicking Add. (A handler appears in the Available List if
you uploaded a user-defined handler or if you previously removed
a handler from the Configured List.) The handler
is moved to the Configured List.
- Remove a handler by selecting the handler from the Configured List and clicking Remove.
The handler is moved to the Available List.
- Rearrange the order in which the handlers are called by selecting
the handler and clicking Move Up or Move Down.
Handlers are called in the order in which they are listed in
the Configured List. The first available handler
that can process the request is the one that handles the request.
If you anticipate receiving a large number of documents of a certain
type (for example, ROD documents), you can move the handler associated
with that type of document (in this example, com.ibm.bcg.edi.business.process.RODScannerHandler)
to the top of the list.
- Click Save.
Inbound
workflows
This section lists the handlers configured for the inbound
workflows.
Protocol unpackaging handlers
By default, the Protocol Unpackaging step has the following
handlers configured:
- com.ibm.bcg.ediint.ASUnpackagingHandler
- com.ibm.bcg.server.pkg.NullUnpackagingHandler
- com.ibm.bcg.server.pkg.MIMEMultipartUnpackagingHandler
- com.ibm.bcg.eai.EAIUnpackagingHandler
Protocol processing handlers
By default, the Protocol Processing step has the following
handlers configured:
- com.ibm.bcg.server.RNOChannelParseHandler
- com.ibm.bcg.server.RNSignalChannelParseHandler
- com.ibm.bcg.server.RNSCChannelParseHandler
- com.ibm.bcg.server.BinaryChannelParseHandler
- com.ibm.bcg.cxml.cXMLChannelParseHandler
- com.ibm.bcg.soap.SOAPChannelParseHandler
- com.ibm.bcg.server.XMLRouterBizProcessHandler
- com.ibm.bcg.edi.EDIRouterBizProcessHandler
- com.ibm.bcg.edi.business.process.RODScannerHandler
- com.ibm.bcg.edi.business.process.NetworkAckHandler
Outbound
workflow
By default, the Protocol Packaging
step has the following handlers configured:
- com.ibm.bcg.server.pkg.NullPackagingHandler
- com.ibm.bcg.ediint.ASPackagingHandler
- com.ibm.bcg.edi.server.EDITransactionHandler
- com.ibm.bcg.rosettanet.pkg.RNOPPackagingHandler
- com.ibm.bcg.server.pkg.RNPassThruPackagingHandler
- com.ibm.bcg.cxml.cXMLPackagingHandler
- com.ibm.bcg.soap.SOAPPackagingHandler
- com.ibm.bcg.eai.EAIPackagingHandler
