Business object definitions of FIX messages are based on specifications published by the Financial Information Exchange Protocol Organization. For comprehensive information, see the Financial Information Exchange Protocol (FIX) documentation available at:
http://www.fixprotocol.org/cgi-bin/Welcome.cgi
The mapping of a business object to a FIX message is straightforward. A top-level FIX business object definition represents a single FIX message for a specific FIX version (for example, FIX 4.3). FIX business object naming conventions and attribute characteristics reflect the FIX message structure.
The sections below describe attribute characteristics and naming conventions as well as how business object attributes map to FIX message tags.
The connector is a meta-data-driven connector. In WebSphere business objects, meta-data is data about the application, which is stored in a business object definition and which helps the connector interact with an application. A meta-data-driven connector handles each business object that it supports based on meta-data encoded in the business object definition rather than on instructions hard-coded in the connector.
Business object meta-data includes the structure of a business object, the settings of its attribute properties, and the content of its application-specific text. Because the connector is meta-data-driven, it can handle new or modified business objects without requiring modifications to the connector code. However, the connector's configured data handler makes assumptions about the structure of its business objects, object cardinality, the format of the application-specific text, and the database representation of the business object. Therefore, when you create or modify a business object for FIX protocol, your modifications must conform to the rules the connector is designed to follow, or the connector cannot process new or modified business objects correctly.