IBM BJ0NJML - Service And Asset Management, Integration Manual

Page: 161 / 330

Handlers
Endpoints and Handlers
147
The following example is an IBM WebSphere Application Server provider URL.
corbaloc:iiop: hostname : iiopport
If the handler and the target enterprise bean are running on the same application
server instance, do not specify this property because it defaults to the local server
URL.
USERNAME and
PASSWORD Properties
The user name and password properties correspond to the
java.naming.security.principal (USERNAME) and
java.naming.security.credentials (PASSWORD) properties that are used to create
the InitialContext object.
FLATFILE Handler
The FLATFILE handler converts outbound data from the queue into a flat file and
writes it to a directory that has a configurable location. Flat files contain ASCII
data in the form of rows and columns. Each line of text constitutes one row, and a
separator character separates each column in the row. The FLATFILE handler
encodes outbound flat files in the standard UTF-8 format.
The FLATFILE handler can be used only with publish channels, not invocation
channels. The object structure that you associate with a publish channel must be
marked as flat supported. Resolve all object structure alias conflicts and format
the XML message according to the system schema to write the message to a flat
file.
Flat File Naming Convention
File names require the following format.
externalsystemname_publishchannelname_uniqueidentifier .DAT
T externalsystemname is the identifier of the system (the value of
MAXVARS.MXSYSID).
T publishchannelname is the name of the publish channel.
T uniqueidentifier is a number based on current system time.
The file name EXTSYS1_MXASSETInterface_10971102668641498.dat indicates
that the file was generated by the system to send data to the external system
EXTSYS1. The file name also indicates that the file contains a message that was
published through the MXASSETInterface publish channel.
The first two lines of the file contain header information. The first line has the
following format:
externalsystemname <separator> publish channel name <separator> [action]
<separator> langcode
The second line of the file contains the names of the columns, separated by the
separator character. The column names are the same as the names in the
corresponding interface table.