BEA eLink Data Integration Option 1.2   Information Center     

        HOME   |   SEARCH   |   CONTACT   |   PDF FILES |   WHAT'S NEW 
 
        TABLE OF CONTENTS   |   PREVIOUS TOPIC   |  
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 TUXEDO 6.4 or 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. BEA eLink Data Integration Option 1.2

    Directory location: ______________________________________________

  4. (Optional) To connect to a mainframe environment, you can use one of the following BEA products:

  5. (Optional) To connect to SAP R/3 applications:

Step 2: Set TUXEDO 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.

    Note: This file is optional and not required when specifying the -NOMTI option in the CLOPT parameter of the server configuration.

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 elinkmerc server in the TUXEDO UBBCONFIG file.

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

    SERVER Parameters Arguments

    server identifier

    elinkmerc

    SRVGRP=groupname

    groupname =

    SRVID=ID

    ID =

    CLOPT="-s servicename1
    servicename2
     -NOMTI"

    servicename1 =
    servicename2 =

  3. Define the gateway server in the TUXEDO UBBCONFIG file.

    Define the gateway server in the SERVER section of the UBBCONFIG file. Use the following table to plan for the server information that needs to be specified.

    SERVER Parameters Arguments

    server identifier

    GWIDOMAIN | GWSNAX

    SRVGRP=groupname

    groupname =

    SRVID=ID

    ID =

    CLOPT="-A -eMERC"

  4. Define the advertised data mapping services in the TUXEDO UBBCONFIG file.

    Define the advertised data mapping services in the SERVICES section of the UBBCONFIG file. Use the following table to plan for the server information that needs to be specified.

    SERVICES Parameters Arguments

    servicename1

    servicename1=

    servicename2

    servicename2 =

Step 6: DMCONFIG File Definitions (Optional)

The following configurations are optional and must be modified for data mapping service requests to process correctly when using the BEA eLink for Mainframe product.

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

    DM_LOCAL_SERVICES Parameters Arguments

    service

    service =

    INBUFTYPE=FML:servicename

    servicename =

    OUTBUFTYPE=FML:servicename

    servicename =

  2. Define a DM_REMOTE_SERVICES for data mapping. Use the following table to plan for the service information that needs to be specified.

    DM_REMOTE_SERVICES Parameters Arguments

    service

    service =

    INBUFTYPE=FML:servicename

    servicename =

    OUTBUFTYPE=FML:servicename

    servicename =

Step 7: 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 FML and View Importer".

Step 8: 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".

Step 9: Create a Mercator Map File

For information about how to create a Mercator map file, refer to "Create a Mercator Map File".

Step 10: 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 11: Renaming Meta-Type Information File (Optional)

Note: This step is optional and not required when specifying the -NOMTI option in the CLOPT parameter of the server configuration.

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 12: Transfer Files

For information about transferring files, refer to "Transfer Files to APPDIR in the Execution Environment".

Step 13: Start BEA TUXEDO and Remote Applications

For information about how to start BEA TUXEDO and BEA eLink for Mainframe products, refer to the specific product online documentation.

Step 14: Issue a Service Request for Data Mapping

For information about setting up service requests, refer to the BEA TUXEDO online documentation.


        TABLE OF CONTENTS   |   PREVIOUS TOPIC