BEA Logo BEA eLink Data Integration Option 1.3

  Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy

  e-docs.beasys.com   |  Search   |  PDF Files   |  Contact  

 BEA eLink Data Integration Option Home |  Prev |  Next |  Table of Contents |


Data Mapping Worksheet

Data Mapping Worksheet

This worksheet will assist you in setting up your data mapping environment properly.

Step 1: Install Products

The following products must be installed and operational during the execution of a data mapping service request. Install these products in the following order.

  1. BEA eLink Platform 1.1

    Directory location: ______________________________________________

  2. TSI Mercator Open Edition Client 1.4.2

    Note: Use the SERIAL number from the eLink DIO license key when prompted for a Serial number during the Mercator Open Edition Client installation.

    Directory location: ______________________________________________

  3. TSI Mercator Open Edition Client 1.4.2 Service Pack 8

    Directory location: ______________________________________________

  4. BEA eLink Data Integration Option 1.3

    Directory location: ______________________________________________

Step 2: Set eLink Platform Environment Variables

Set the following environment variables:

The following environment variables are platform-specific. Be sure to set the appropriate one for you execution environment.

Step 3: Put Mercator in the System Path

Before developing your data maps on Windows NT, you must put the Mercator Open Edition Client in your system path. Select Program>Settings>Control Panel>System Properties to access properties page. Select the Environment tab and enter the path for Mercator Open Edition Client under User Variables. The default installation directory is C:\mercator.

Step 4: Transfer Source Files to Windows NT

  1. Transfer the FML Field Definition files and non-FML source files to the development environment on the Windows NT system. Use the following table to track the location and names of these files.

  2. Create the FML Group Format file to use with the FML Field Definition file in the development environment on the Windows NT system.

Use the following table to track the location and names of these files.

FML Field Definition Files FML Group Format Files non-FML Source Files

Step 5: UBBCONFIG File Definitions

The following configurations must be modified for data mapping service requests to process correctly.

  1. Define a GROUP for data mapping. Use the following table to plan for the group information that needs to be specified.

    GROUP Parameters Arguments

    groupname

    groupname =

    LMID=logical-machine-ID

    logical-machine-ID =

    GRPNO=n

    n =

  2. Define the ELINKDIO server in the TUXEDO UBBCONFIG file.

    Define the ELINKDIO server in the SERVERS section of the UBBCONFIG file. The ELINKDIO server is responsible for the data mapping operation. Use the following table to plan for the server information that needs to be specified.

    SERVERS Parameters Arguments

    server identifier

    ELINKDIO

    SRVGRP=groupname

    groupname =

    SRVID=ID

    ID =

    CLOPT="-A -- -C dio.cfg"

    dio.cfg =

Step 6: Create an FML Type Tree File

For information about how to create an FML type tree file, refer to "Create an FML Type Tree File Using the eLink DIO FML Importer" on page 5-6.

Step 7: Create a non-FML Type Tree File

For information about how to create a non-FML type tree file, refer to "Create a non-FML Type Tree File Using Importers" on page 5-9.

Step 8: Create a Mercator Map File

For information about how to create a Mercator map file, refer to "Create a Mercator Map File" on page 5-12.

Step 9: Port Map Files for Execution on UNIX Platforms

If your execution platform is HP-UX, AIX, or SUN Solaris, you must port the Mercator map files to these platforms. To port the map, access the Mercator Map Editor and select Map>Port and then select the platform from a list. When the port is complete, the files will be renamed with a platform-specific extension, such as *.hp.

Note: After transferring these ported files to the execution environment you must rename these files with the *.mmc extension again. The execution environment will not recognize the ported files with the extensions such as *.hp.

Step 10: Renaming Meta-Type Information File (Optional)

You must have a copy of the Meta-Type Information (sample.mti) file saved as the Mercator map name (FML2COB.mti and COB2FML.mti).

To obtain this file, copy the FML Meta-Type Information (.mti) file and rename it using the file name of both map files. For example, the FML type tree file is sample.mti and the Mercator map file is FML2COB.mmc. Copy sample.mti and rename it FML2COB.mti. The other map file is COB2FML.mmc. Then copy the sample.mti file and rename it to the COB2FML.mti.

Step 11: Transfer Files

For information about transferring files, refer to "Transfer Files to the Execution Environment" on page 5-15.

Step 12: Start eLink Platform and Remote Applications

For information about how to start eLink Platform and other remote application products, refer to the specific product online documentation.

Step 13: Issue a Service Request for Data Mapping

For information about setting up service requests, refer to the eLink Platform online documentation.


 [Table of Contents] [Prev] [Next]