README for the HP Neoview Transporter Streamlined Access Interface API (R2.3)

called nvtransport within the current working directory.

For example, tar -xvf nvt_sai_v.v.v.tar.

6. The nvtransport directory will contain the following directories:

+--------------------------------------------------------------------+

| Directory | Contents |

|------------+-------------------------------------------------------|

| bin | empty |

|------------+-------------------------------------------------------|

| conf | empty |

|------------+-------------------------------------------------------|

| extensions | empty |

|------------+-------------------------------------------------------|

| inc | header files |

|------------+-------------------------------------------------------|

| lib | Transporter API library and driver DLL |

|------------+-------------------------------------------------------|

| log | default location for Transporter logs (under the |

| | native sub-directory) |

|------------+-------------------------------------------------------|

| mesg | message catalog |

|------------+-------------------------------------------------------|

| samples | sample control files, data, application, and MXODSN |

|------------+-------------------------------------------------------|

| utils | empty |

+--------------------------------------------------------------------+

1.1.2.2 Setting Up the Client Environment

1. Set the environment variable NVTHOME

NVTHOME is used as the basis for the APIs to locate the components.

Set NVTHOME to point to the location where the package is installed.

Assuming the software is installed in /usr or /opt, execute the

following from the command line:

export NVTHOME=/usr/nvtransporter

export NVTHOME=/opt/nvtransporter

2. Update the MXODSN file

The MXODSN file should be updated to point to the datasource set up

for loads on the Neoview server. The default datasource is

Admin_Load_DataSource.

Refer to your ETL product instructions for any tool-specific

configuration.

NOTE: The driver expects the MXODSN file to be present in the current

working directory (CWD) of the application.

1.1.2.3 Using the Sample Application