The acquireData() function is called to get data in an NDO tree from the application. An NDO object is constructed and is passed into the adapter plug-in. This plug-in should populate the NDO data tree and return an indication on whether the loop should continue or not. After the NDO has been populated, the data tree is extracted from the NDO and is put to the transport if the data tree is not empty.
If you are using an NDO with the NCF Serializer, the message type is used to look up the metadata in the schema repository. You can set the message type using the msg.type configuration key as detailed in “Configuration Keys”. OPT_MESSAGE_TYPE is more likely to be set dynamically in the adapter or by the NDO name. To keep the schemas cleaner when using the NCF wire format, not all schema information is kept in the wire format. If a message is being retrieved (Deliver mode) from a transport using NCF Serializer, the message must have the OPT_MSG_TYPE option set to the format name matching the schema repository file. When running MQSI or to place the message on the transport accessed by the deliver, the MQS_PROPAGATE option must be set to PROPAGATE in the rules GUI for the putqueue action placing the message on the transport. Otherwise, the message will not have the OPT_MSG_TYPE set.