Configuring the binary host data handler

To configure the binary host data handler for use with a connector, take the following steps:

Each of these steps is described in more detail in the following sections.

Note:
To use the binary host data handler, you must also create or modify business object definitions so that they support the data handler. For more information, see Business object definitions for EDI documents.
Note:
The binary host data handler can only be used with an adapter configured to work with binary processing. The JText adapter is one such adapter.

Configuring the JText connector configuration object

The following attributes need to be set in the MO_JTextConnector_Default file, which is the connnector configuration object.

Table 68. Attributes of the MO_JTextConnector_Default

Attribute name Description
EventDataHandler Sets the DataHandler for Event Processing scenario. Must have the MO_DataHandler_DefaultBinaryHostConfig selected from the drop box containing object types.
OutputDataHandler Sets the DataHandler for Service Call scenario. Must have the MO_DataHandler_DefaultBinaryHostConfig selected from the drop box containing object types.
DataProcessingMode Must always be "binary" for connecting to the binary host data handler. The binary host data handler throws an error if unspecified, or if specified as 'text'.
FTPTransferType Must always be "record". The binary host data handler throws an error if unspecified, or if specified as 'file'.
FTPDataStructure Must always be "record". The default value is "file".

Refer to the Adapter for Jtext User Guide for more information about how to configure these properties of the JText connector.

Configuring the binary host data handler child meta-object

MO_DataHandler_DefaultBinaryHostConfig object is the meta object that defines the properties of the binary host data handler that determine the transformation of binary data.

The EventDataHandler and OutputDataHandler attributes in the MO_JTextConnector_Default must be set to MO_DataHandler_ DefaultBinaryHostConfig to enable the binary host data handler.

After setting these attributes, the child attributes of MO_DataHandler_DefaultBinaryHostConfig have to be set, to customize the behavior of the binary host data handler in the event or request processing scenarios. Table 69 describes the attributes in this child meta-object.

Table 69. Child meta-object attributes for the binary host data handler

Attribute name Description Delivered default value Required
ClassName Name of the data handler class to load for processing the binary data. Note that the complete package structure needs to be specified. com.crossworlds. DataHandlers.binary Yes
BODefinitionName Name of the BO template that the user has created to support the COBOL copybook.
Yes
CxBlank Field used by the data handler to handle blanks. User need not specify anything here. CxBlank No
CxIgnore Field used by the data handler to handle null value. User need not specify anything here. CxIgnore No
DefaultVerb Specifies the default verb used by the data handler for its operations on application specific business objects (ASBOs) Create No
BinaryEncoding Specifies the encoding which the binary host data handler uses to decode data obtained from MVS, or to encode data sent to MVS.
Yes
DummyKey Key field; has a unique value for every instance. 1 Yes

The "Delivered default value" column in Table 32 lists the value in the Default Value property for the corresponding attribute in the delivered business object. You must examine your environment and set the Default Value properties of all the attributes to the appropriate values.

Note:
Use Business Object Designer to modify business object definitions.

For more information about how to configure a data handler, see Configuring data handlers.

Copyright IBM Corp. 1997, 2003