|  | BEA eLink Data Integration Option 1.2 Information Center
HOME | SEARCH | CONTACT | PDF FILES | WHAT'S NEW
| TABLE OF CONTENTS | PREVIOUS TOPIC | NEXT TOPIC

Configuring the Environment for eLink Integrator

# Configuring the Environment for eLink Integrator

Before running the eLink Integrator, you must configure the BEA TUXEDO server and the eLink for Mainframe gateway to run with an alternate data mapping product, such as Mercator.

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

- Configuring the elinkmerc Server to Run with eLink Integrator

- Configuring the eLink for Mainframe Gateway to Run with eLink Data Integration Option

## Configuring the elinkmerc Server to Run with eLink Integrator

Before running the eLink Integrator, you must edit the UBBCONFIG file to recognize the services that will be used for the data mapping. For UBBCONFIG parameter syntax and definitions, refer to the BEA TUXEDO Reference Manual.

### Define the elinkmerc Server

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

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

> Listing 3-1 Syntax for elinkmerc Server Definition in the UBBCONFIG File

>     *SERVERS

>     elinkmerc
>     	SRVGRP=groupname			SRVID=n
>     	CLOPT="-s servicename1:XLATE_SERVICE
>                   -s servicename2:XLATE_SERVICE -- -WUD -TIO -AE
>                   -NOMTI"

For information about the SRVGRP, SRVID, and CLOPT parameter syntax and definitions, refer to the BEA TUXEDO Reference Manual. The definition of the `-s` option in the CLOPT parameter follows and is required for the data mapping process.

CLOPT="-s `servicename`"
  specifies the services to advertise. In this case, the `servicename` is the advertised service to use for the data conversion. It is the name of the Mercator map files, such as `fml2cob.mmc` and `cob2fml.mmc`.

Note: The `servicename` specified in the CLOPT parameter must also be defined in the SERVICE section of the UBBCONFIG file.

`-NOMTI` specifies the FML Default Format which groups FML according to the order of fields defined in the FML Definition File. Specify `-NOMTI` in upper case only. This option must be specified, for example, when using the eLink Mercator Integrator for DIO component with SAP applications and conversions from FML to IDOCs.

If you do not specify `-NOMTI`, then the default is used, which is the FML Field Definition file and the FGF file.

The options specified to the right of the double dashes (`-- -WUD -TIO - AE`) in Listing 3-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.

### Advertise the Services for Data Mapping

Advertise the service for data mapping by defining it in the SERVICES section of the UBBCONFIG file.

> Listing 3-2 Syntax for Advertising the Mapping Service

>     *SERVICES

>     servicename1
>     servicename2

`servicename1`
  specifies a 1-15 character name of the service for data mapping. An example would be `fml2cob` and `cob2fml`.

Note: The name of each of the services must match the map names in the CLOPT parameter in the elinkmerc server definition. For more information about defining services, refer to the BEA TUXEDO documentation about the UBBCONFIG.

### Sample UBBCONFIG File for Data Mapping

Listing 3-3 is a sample UBBCONFIG file for Windows NT. In this sample, the elinkmerc server is defined in the SERVERS section with the required CLOPT -s option specified.

> Listing 3-3 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"

>     elinkmerc
>     	SRVGRP=eLINK			SRVID=10
>     	REPLYQ=N
>     	CLOPT="-sFML2COB:XLATE_SERVICE -sCOB2FML:XLATE_SERVICE -- -WUD -TIO -AE"

>     GWIDOMAIN
>             SRVGRP=eLINK   SRVID=21
>             CLOPT="-A -- -eMERC"

>     *SERVICES

>     FML2COB
>     COB2FML

>     *ROUTING

## Configuring the eLink for Mainframe Gateway to Run with eLink Data Integration Option

To configure the products and components to work together to convert buffers between an FML and COBOL copybook format and transfer the buffers between a UNIX or Windows NT environment and a mainframe environment, you must set up the eLink for Mainframe product. The eLink for Mainframe product will invoke an alternate data mapping product to perform the actual data conversion.

Before running the eLink for Mainframe gateway, you must edit the UBBCONFIG file and the DMCONFIG file to recognize the alternate data mapping product to use for data mapping. For configuration information for the eLink for Mainframe gateway, refer to the eLink for Mainframe online product documentation.

TABLE OF CONTENTS | PREVIOUS TOPIC | NEXT TOPIC