Configuring the Environment for eLink DIO

# Configuring the Environment for eLink DIO

Before running the eLink DIO, you must configure the eLink Platform torecognize the ELINKDIO server and the eLink DIO configuration file.

Configuring the environment for eLink DIO consists of the following basic tasks:

- Configuring the ELINKDIO Server on eLink Platform

- Configuring eLink DIO

## Configuring the ELINKDIO Server on eLink Platform

Before running the eLink DIO product, you must edit the UBBCONFIG file to recognize the ELINKDIO server that will be used for the data mapping. For UBBCONFIG parameter syntax and definitions, refer to the BEA TUXEDO Reference Manual on the eLink Platform online documentation CDROM.

### Define the ELINKDIO Server on eLink Platform

Define the ELINKDIO server as the server responsible for the data mapping operation. To define this server, add the ELINKDIO information in the *SERVERS section of the UBBCONFIG file. The following parameters are required for defining the ELINKDIO server.

Note: You must specify `ELINKDIO` as the file to execute for the data mapping process. Within this server definition, you must also specify the `-C` option in the CLOPT parameter to pass the `dio.cfg` file.

> Listing 4-1 Syntax for ELINKDIO Server Definition in the UBBCONFIG File

>     *SERVERS

>     ELINKDIO
>     	SRVGRP=groupname
>     	SRVID=n
>     	CLOPT="-A -- -C dio.cfg -WUD -TIO -AE"

For information about the SRVGRP, SRVID, and CLOPT parameter syntax and definitions, refer to the BEA TUXEDO Reference Manual on the eLink Platform online documentation CDROM. The definition of the `-C` option in the CLOPT parameter follows and is required for configuration process.

CLOPT="-A -- -C `configuration_file`"
  specifies the name of the eLink DIO configuration file.

The options specified to the right of the double dashes (`-- -WUD -TIO -AE`) in Listing 4-1 are optional and write trace files and audit logs. These Mercator options may slow performance; however, may assist in troubleshooting. For an explanation of these options, refer to the Execution Command Reference Guide in the Mercator online documentation.

### Sample UBBCONFIG File for Data Mapping

Listing 4-2 is a sample UBBCONFIG file for Windows NT. In this sample, the ELINKDIO server is defined in the *SERVERS section with the required CLOPT -C option specified.

> Listing 4-2 Sample UBBCONFIG File for Data Mapping

>     *RESOURCES

>     IPCKEY		123791
>     DOMAINID		simpapp
>     MASTER		simple

>     *MACHINES

>     DALNT6
>     	LMID		= simple
>     	TUXDIR		= "\tuxedo"
>     	TUXCONFIG		= "\myappdir\tuxconfig"
>     	APPDIR		= "\myappdir"
>     	FIELDTBL		= "sample.fml"
>     	FIELDTBL32		= "sample.fml"
>     	FLDTBLDIR		= "\myappdir"
>     	FLDTBLDIR32		= "\myappdir"
>     	ULOGPFX		= "\myappdir\ULOG"
>     					# LD_LIBRARY_PATH=\mercator
>     					# SHLIB_PATH=\mercator
>     					PATH=\mercator

>     *GROUPS

>     eLINK
>     	LMID=simple		GRPNO=1

>     *SERVERS

>     DEFAULT:
>     	CLOPT="-A"

>     ELINKDIO
>     	SRVGRP=eLINK			SRVID=10
>     	REPLYQ=N
>     	CLOPT="-A -- -C dio.cfg -WUD -TIO -AE"

>     *ROUTING

## Configuring eLink DIO

In addition to the UBBCONFIG file defining the ELINKDIO server, the eLink DIO product must define the configuration parameters for data mapping and data translation. The eLink DIO product requires a configuration file, such as `dio.cfg`, separate from the UBBCONFIG file.

The eLink DIO configuration file requires the following sections:

- SERVER

The SERVER section defines the eLink DIO server for data mapping.

- SERVICE

  The SERVICE sections define the various services the specified server supports.

### Define the eLink DIO SERVER Section

Define the eLink DIO configuration parameters for the data mapping operation. The following parameters are required for defining a server in the eLink DIO configuration file.

> Listing 4-3 Syntax for the *SERVER Section in the eLink DIO Configuration File

>     *SERVER

>     MAP-DIR=map_file_dir
>     MTI-DIR=mti_file_dir
>     NOCACHE=Y
>     SERVICE_LIST=A,B,C,...

*SERVER
  denotes the start of server parameters.

MAP_DIR=`map_file_dir`
  specifies the directory path where the Mercator map files reside. This location can be a directory other than APPDIR.

The default is APPDIR.

MTI_DIR=`mti_file_dir`
  specifies the directory path where the MTI files reside. This location can be a directory other than APPDIR.

The default is APPDIR.

NOCACHE=Y
  specifies whether to disable the MTI and Mercator map caching feature.

Y causes eLink DIO to access the MTI files and Mercator map files from disk each time a service executes. You can load changes to the MTI files or Mercator map files without recycling eLink Platform.

The default behavior is for eLink DIO Server to cache map and MTI files and access them from the cache.

SERVICE_LIST=servicenameA, servicenameB, servicenameC,...
  specifies the list of services that this server will support.

### Define the eLink DIO SERVICE Section

After defining the eLink DIO server in the SERVER section, you must specify the services that the server supports. The following parameters are required for defining a service in the eLink DIO configuration file.

Advertise the service for data mapping by defining it in the SERVICE section of the eLink DIO configuration file.

> Listing 4-4 Syntax for Advertising the Mapping Service

>     *SERVICE=servicename

>     MAP_FILE=mapname
>     [MTI_FILE=mtiname]
>     BUFFER=FML32 | FML32_VAL | STRING | CARRAY
>     FML32_VAL_FLD=fieldname

*SERVICE=`servicename`
  specifies a 1-15 character name of the service for data mapping or transformation process. The eLink DIO product advertises this servicename during server initialization.

MAP_FILE=`mapname.mmc`
  specifies the name of the Mercator map file to use when executing this service. Multiple services can use the same map file. This is a required parameter.

MTI_FILE=`mtiname.mti`
  specifies the name of the MTI file to use when executing this service. Multiple services can use the same MTI file.

Note: This parameter is only required for BUFFER=FML32.

BUFFER=FML32 | FML32_VAL | STRING | CARRAY
  specifies the type of input buffer the eLink DIO service receives when called. Specifying the input buffer type allows eLink DIO to validate the input buffer to ensure the service is invoked correctly.

FML32 specifies that eLink DIO should receive an FML32 input buffer. This buffer type uses MTI processing and requires the MTI_FILE parameter.

STRING specifies that eLink DIO should receive a string input buffer.

CARRAY specifies that eLink DIO should receive a character array buffer as input.

FML32_VAL specifies that eLink DIO should receive an FML32 input buffer that contains one large field with all the data necessary for processing. The FML32_VAL-FLD parameter is required to process this type of buffer.

FML32_VAL_FLD=fieldname
specifies the name of the FML32 field in the input buffer which contains data for processing. This parameter replaces the MERCATOR_FV_IN field used in previous releases of eLink DIO.

Note: This parameter is only required when specifying BUFFER=FML32_VAL.

[Table of Contents] [Prev] [Next]