Configuring the FIX data handler

To configure a FIX data handler for use with the connector, you must do the following:

  1. Make sure that the class name of the FIX data handler is specified in the connector properties and in the data handler meta-object. See "Configuring the connector meta-object" below
  2. Enter the appropriate values for the attributes of the FIX data handler child meta-object. See "Configuring the data handler child meta-object".
Note:
For the FIX data handler to function properly, you must also create or modify business object definitions so that they support the data handler. For more information, see Business objects.

Configuring the connector meta-object

To configure the connector to interact with the FIX data handler, make sure that the connector-specific property DataHandlerClassName has the value com.crossworlds.DataHandlers.fix.FixDataHandler.

You must set the value of this property before running the connector. Doing so enables the connector to access the FIX data handler when converting FIX messages to business objects and vice versa. For further information, see Connector-specific properties.

Configuring the data handler child meta-object

For the FIX data handler, WebSphere software delivers the default meta-object MO_DataHandler_Default_FIX. This meta-object specifies a child attribute of type MO_DataHandler_Fix. Table 18 describes the attributes in the child meta-object, MO_DataHandler_FIX.

Table 18. Delivered Child Meta-object Attributes for the FIX data Handler

Attribute Name Description Delivered Default Value
ClassName
 
Name of the data handler class to load for use with the specified MIME type. The top-level data-handler meta-object has an attribute whose name matches the specified MIME type and whose type is the FIX child meta-object.
com.crossworlds.Data
 Handlers.fix.FixData
 Handler
 
DefaultVerb
 
The verb used when creating business objects.
Create
 
NumberOfEnvelope
 HeaderField
 
The number of pre-pended message envelope headers to parse. This value is in the tag=value[SOH]-delimiter format and must be added to the FIX standard message header.1
0
 
SMH_BO_BASE_NAME
 
Parsed to obtain the FIX message header business object name.FIXnn is pre-pended to this name. For example, a FIX version 4.3 business object for a FIX header is FIX43_Standard_Message_Header
StandardMessageHeader
 
ERROR_BO_BASE_
 NAME
 
Parsed to obtain the error report business object name. FIXnn is pre-pended to this name. For example, a FIX version 4.2 business object name for an error report is FIX42_ErrorReport.
ErrorReport
 
STATIC_LOOKUP_
 TYPES_LIST
 
Comma-delimited list of attributes in this meta-object that point to locally-stored static configuration files. These configuration files must reside on the same machine as the connector. For example, the file FIX43_MESSAGES contains all the message types for FIX version 4.3. For every entry in STATIC_LOOKUP_TYPES_LIST, a separate attribute must appear in this child data handler meta-object.
FIX43_MESSAGES,FIX43_FIELDS
 
BO_NAMES
 
Name of the configuration file used to determine the business object name.
<pathname>columns=4;
 file=bonames.cfg
 
FIXnn_MESSAGES
 
Local configuration file listed in STATIC_LOOKUP_TYPES_LIST and containing all the message types for FIX versions 4.0, 4.1, 4.2, and 4.3.
<pathname>columns=1;
 file=FIX43_MessageTypes.
 cfg
 
FIXnn_FIELDS
 
Local configuration file listed in STATIC_LOOKUP_TYPES_LIST and containing all of the valid tags for FIX versions 4.0, 4.1, 4.2, and 4.3
<pathname>columns=1;
 file=FIX43_Tags.txt
 
  1. For more on the tag=value syntax and SOH delimiter, see FIX Protocol, Ltd., documentation

The Delivered Default Value column in Table 18 lists the default value of the associated meta-object attribute. You must ensure that all attributes in this child meta-object have a default value that is appropriate for your system and your FIX message type. Also, make sure that at least the ClassName and DefaultVerb attributes have default values.

Note:
Use Business Object Designer to assign default values to attributes in this meta-object.

WebSphere recommends adding attributes that correspond to ISO codes or FIX-defined value sets that the data handler uses to validate incoming FIX messages. The names of these attributes must correspond to the data types defined in IBM CrossWorlds application-specific information for attributes discussed in AppSpecificInfo. For your convenience, some of these attributes and their values are shown in Table 19 below.

Table 19. Additional Child Meta-object Attributes for the FIX data Handler

Attribute Name Description Value
Exchange43
 
Attribute pointing to a local configuration file that contains ISO 10383 codes sets that are used to validate the data content.* The attribute must be listed in STATIC_LOOKUP_TYPES_LIST and is for FIX version 4.3.
<pathname>columns=1;
 file=filename
 
Exchange
 
Attribute pointing to a local configuration file that contains FIX-defined value sets that are used to validate the data content. The attribute must be listed in STATIC_LOOKUP_TYPES_LIST and is for FIX versions 4.0, 4.1, and 4.2.
<pathname>columns=1;
 file=filename
 
Currency
 
Attribute pointing to a local configuration file that contains ISO 4217 currency codes.* This attribute must be listed in STATIC_LOOKUP_TYPES_LIST.
<pathname>columns=1;
 file=filename
 
Country
 
Attribute pointing to a local configuration file that contains ISO 3166 country code data.* This attribute must be listed in STATIC_LOOKUP_TYPES_LIST.
<pathname>columns=1;
 file=filename
 
ISO9362
 
Attribute pointing to a local configuration file that contains ISO 9362 bank identifier code data.* This attribute must be listed in STATIC_LOOKUP_TYPES_LIST.
<pathname>columns=1;
 file=filename
 
CFICode43
 
Attribute pointing to a local configuration file that contains ISO 10962 financial instrument classification data.* This attribute must be listed in STATIC_LOOKUP_TYPES_LIST and is for FIX version 4.3.
<pathname>columns=1;
 file=filename
 
CFICode
 
Attribute pointing to a local configuration file that contains financial instrument classification data. The attribute must be listed in STATIC_LOOKUP_TYPES_LIST and is for FIX versions 4.0, 4.1, and 4.2.
<pathname>columns=1;
 file=filename
 
ISO6166
 
Attribute pointing to a local configuration file that contains ISO 6166 international securities identification data.* This attribute must be listed in STATIC_LOOKUP_TYPES_LIST.
<pathname>columns=1;
 file=filename
 

*To obtain these codes, you must contact the ISO at www.ISO.ch; you must then build a file containing these codes and add the attribute name to the comma-delimited list that defines STATIC_LOOKUP_TYPES_LIST, the child attribute in the data handler meta-object.

To add attributes to :

  1. Download the ISO file that the attribute will point to and use its contents to build a local configuration file.
  2. Use Business Object Designer to add attributes and assign values in the data handler child meta-object, MO_DataHandler_FIX. The values are the names of the files that contain the ISO codes, etc., from step 1. The child attribute names must be as shown in Table 19, but you can choose any name for the file containing the information that the attribute points to. You must specify an absolute pathname as well as the name of the file. For example, the attribute Currency might point to a file C:\dependencies\Currency.cfg
  3. Add the attribute name that points to the local configuration file to the STATIC_LOOKUP_TYPES_LIST, the comma-delimited child attribute in the data handler meta-object (See Table 18).
Note:
The FIX data handler checks the attributes defined in MO_DataHandler_FIX even when building outgoing FIX messages.

Copyright IBM Corp. 1997, 2003