x

The document travels through the channel components as follows:

• Inlet Phase:
  • Listener. Protocol handler that receives input for a channel from a configured source.
  • Decryptor. Applies a decryption algorithm, which must be supplied in a custom module.
  • Preparser. Transforms non-XML to XML. You can choose from several supplied preparsers or use a custom preparser.

    Note: Unless the listener allows a non-XML document, XML is required from here through output validation; otherwise, an XML parser error occurs.

• Route Phase:
  • Input Reviewer. Analyzes the document. This agent is typically used to extract and handle headers.
  • Input Validation Rules. Applies validation using the rules validation engine. Rules are provided when HIPAA, HL7, and SWIFT adapters are installed, or you can write custom rules for input documents.
  • Input Transformation. Applies iWay transformations or XSLT transformations to input documents received by a listener.
  • Process. Executes the business logic of an application. You can choose from several agents provided by iWay that access iWay data adapters and application adapters or you can use custom-written agents that access third-party applications and systems. You can use multiple agents in series or in parallel.
  • Output Transformation. Applies iWay transformations or XSLT transformations to all XML outbound response documents.
  • Output Validation Rules. Applies validation using the rules validation engine. Rules are supplied for HIPAA, HL7, and SWIFT adapters, or they may be custom written for output documents.

    Note: Non-XML is allowed from here on.

  • Output Reviewer. Analyzes the document. This agent usually adds headers.
• Outlet Phase:
  • Preemitter. Transforms XML to non-XML. You can choose from several preemitters that are provided or use a custom preemitter.
  • Encryptor. Applies an encryption algorithm, which must be supplied in a custom module.
  • Emitter. Protocol handler that drives the output of a channel to a configured endpoint.

Note: XML parsing is implied in channel execution and occurs between the inlet and route phases. This step may be disabled on your channel, depending on your needs.

x

iWay Service Manager (iSM) executes business logic based on the message that arrives and the protocol on which it is received. To accomplish a task in iSM, you must apply the appropriate business logic at the appropriate time. The business logic that is applied relates to both the message being processed and the processing stage. The task of iSM is to apply the configured business logic at the appropriate stage of message processing.

Configuration determines the business logic to apply to a message. Using the configuration, you can refer to built-in logic elements, or you can supply your own.

To apply business logic, iWay Service Manager must know:

• How to locate the logic, regardless of whether it is built-in or supplied externally.
• The stage at which it is to be associated with the message.
• The logic elements to apply in each case.

The major stages in the life of a message or document are:

• On arrival, before it is parsed into XML.
• After parsing, before execution of a business function.
• Execution of a business function.
• Before it is emitted to a specific end point on a protocol.

Business logic is associated with each of these stages.

You can define a business logic element from the Registry section in the iWay Service Manager Administration console, or when you add it to a channel or listener. After a business logic element is defined, it can be applied to messages in a specific message flow. Business logic can also execute iWay Designer process flows.

Business logic, in the form of document-content based routing, may be performed by a listener or from within a process flow. For more information, see the iWay Service Manager Programmer’s Guide.