General Meta Objects

There are three groups of general meta objects in the connector that correspond to, and are set by, three properties in the connector configuration file: the configuration meta object, the service registration meta object (this is actually a nested set of objects), and data handler meta object (which is also a nested set).

Configuration Meta Object

The configuration meta object is a BIA_Static_MO. It stores static meta information for processing various message types as Application Specific Information (ASI) values.

Figure 5. BIA_Static_MO in the Business Object Designer

Screenshot

The pertinent attributes of this example object are as follows:

MO Level Attributes Description
Default Describes the default values.
HL7_Message_Create Describes the static meta attribute values for the Create verb associated with HL7_Message objects
HL7_Message Describes the static meta attribute values associated with HL7_Message objects

The types of static meta information for processing message types that are stored as ASI values for each specified message type are as follows:

Application Specific Information for each Message Type Description
mode = Possible values are sync or async. When "sync" the connector in event processing contacts the broker in a synchronous manner. When "async", the contact is asynchronous
collabName = Relevant only in synchronous event processing. Names the collaboration that the connector needs to invoke
client = Clientx Relevant for service call request processing. Names the remote server config stored in the connector configuration attribute Clientx

Service Registration Meta Object

The service registration meta object is a BIA_MO_Service. This is the top level object in a set of objects that describe multiple types of "services" that can be used in processing message types. A "service" is any reusable functionality. Only a Data Handler Service is defined for this release, but others, such as a Database Service for database access, could also be defined.

Figure 6. BIA_MO_Service in the Business Object Designer

Screenshot

The pertinent attributes of the object are as follows:

MO Level Attributes Description
DataHandlerService References a BIA_MO_DataHandlerServiceDetails, which contains further information

The BIA_MO_DataHandlerServiceDetails object provides additional information for for data handler service.

Figure 7. BIA_MO_DataHandlerServiceDetails in the Business Object Designer

Screenshot

The pertinent attributes of the object are as follows:

MO Level Attribute Description
Service Type Contains additional information for specifying the service type. It is not used for connector processing
ServiceName Specifies the Service Name. In the case of the DataHandlerService, this is the mime type of the message to be processed as it designated in the connector configuration file in the DataHandlerMimeType attribute
ServiceInformation References a BIA_MO_DataHandlerService, which contains further information

The BIA_MO_DataHandlerService object provides specific information for invoking the appropriate data handler and its methods.

Figure 8. BIA_MO_DataHandlerService in the Business Object Designer

Screenshot

The pertinent attributes of the object are as follows:

MO Level Attributes Description
hl7 Defines the handling for a specific mime type. The object (the example is a BIA_MO_DataHandlerService_HL7) referenced in this attribute contains specific information used by the data handler. The related child attributes below (indicated by a +) belong to the contained object. They are used if the mime type listed here matches the ServiceName attribute in the BIA_MO_DataHandlerServiceDetails object.
+EventMethodFormat Stores the HL7 DataHandler method to be invoked for event processing
+RequestMethodFormat Stores the HL7 DataHandler method to be invoked for service call request processing
+CharSet Stores the CharSet of the message data coming into the socket
+SupportMultipleMessages Tells the connector whether the data coming in contains single or multiple messages
ncpdp Defines the handling for a second mime type through a reference to another type-specific object (the example here is a BIA_MO_DataHandlerService_NCPDP)

Data Handler Meta Object

The data handler meta object is a BIA_MO_DataHandler_Default. This is the top level object in a hierarchy that stores information used by the designated data handler. This information is distinct from the information stored in the Service Registration object hierarchy.

Figure 9. BIA_MO_DataHandlerDefault in the Business Object Designer

Screenshot

The pertinent attributes of the object are as follows:

MO Level Attributes Description
hl7 Defines the handling for a mime type, as designated in the connector configuration file in the DataHandlerMimeType attribute. The referenced object (in this example, a BIA_MO_DataHandler_HL7) contains type specific information used by the data handler

Copyright IBM Corp. 1997, 2004