Bookshelf v7.5: Low-Level Teller Connector Workflow Process Flow

This section provides a summary of the algorithms used in the FINS IFX Connector Outgoing and FINS IFX Connector Incoming workflow processes to help you understand how the various components fit together.

NOTE: This description is for a general case that is used most of the time. It does not cover the details of situations like using VBCs or overrides.

Table 36. FINS IFX Connector Outgoing Flow Steps
Step	Description
FINS IFX XML Transaction Manager	Input: DispatcherMapName, IXMLMapPath, isVBC (optional), and VBCFieldMap(optional) argument. Looks up the dispatcher map entry for the message. From the dispatcher map entry, identifies the internal integration object to instantiate. Calls the Siebel Adapter to create an internal integration object instance. Passes in the search specification to constrain the rows returned by the Siebel Adapter to just those that are specified. Adds a property to the internal integration object instance that identifies the DTE map name obtained from the dispatcher map. If a virtual business component is used, transforms the VBCFieldMap into an integration object instance.
FINS IFX XML DTE	Input: Internal integration object instance. Using the internal integration object name and DTE map name, looks up the external integration object name from the DTE map. Instantiates a new external integration object. Passes the internal integration object instance, DTE map name, and external integration object instance to the eAI Data Transformation Engine business service. Returns the external integration object instance after the transformation that contains the message body.
FINS IFX XML Converter	Input: External integration object instance representing the message body and the Envelope integration object name. Creates a new instance of the envelope integration object and populates it with the proper data values such as the IFX session key, user name, password, and other values passed in. Performs any date/time conversion to convert the internal date formats to the external date formats. Generates and adds the UUIDs to the proper places in the external integration object. Returns the external integration object instance that contains the envelope and message body. Date/time values have been converted, UUIDs have been generated, and the session key or user name/password information has been attached.
XML Hierarchy Converter	Input: External integration object instance representing the complete message and envelope. A string for the DOCTYPE declaration. Serializes the integration object instance to a string value. Adds the DOCTYPE declaration in the appropriate place.

Table 37. FINS IFX Connector Incoming Flow
Step	Description
XML Hierarchy Converter	Input: The incoming XML string. Converts the incoming XML string to a generic property set.
FINS IFX XML Dispatcher	Input: The incoming property set, the dispatcher map name, and the envelope integration object name. Creates a property set with various nodes tagged to identify them as header or body nodes. Looks up the dispatcher map to find a key that matches the message name, then decomposes the dispatcher map value into its components and adds those values as properties to the output property set.
FINS IFX XML Converter	Input: The tagged property set from the Dispatcher. Creates an external integration object instance for the incoming property set. The external integration object name is the value extracted from the dispatcher map. Converts the IFX date/time format to internal Siebel format. Creates a new property set that holds all the <Status> aggregates from the incoming message.
Parse Status	Input: The status property set generated from the converter. Scans the status property set and sets the error code, error message, error location, and error severity arguments based on the status information. If the error code is nonzero, it will use the Tools object called Message Category to look up the corresponding translated message for the given error code. The Message Category object in Tools should have an entry called IFX Messages. This will contain a list of error codes and error messages that are displayed to the user. The error message displayed to the user is obtained from this table using the incoming IFX error code.
Translate Error Code	Input: The error code process property. Calls the EAI Value Map Translator to translate the numeric error code to a word like `Success' or `Warning.'
FINS IFX XML DTE	Input: The external integration object from the converter. Calls the FINS IFX XML DTE service to transform the external integration object to an internal integration object. The DTE map name is identified by the value extracted from the dispatcher map. Returns an internal integration object.
FINS IFX XML Transaction Manager	Input: The internal integration object from the DTE. Calls the configured business service from the dispatcher map, usually the Siebel Adapter, to update, insert, or delete data from the Siebel application.