Deploying ECI V2 and ESI V2 to remote systems

Remote ECI V2 and ESI V2 applications are deployed as executable files.

You are licensed to copy the following files to the machine that is running the ECI V2 and ESI V2 application:

ECI V2 and ESI V2 CICS® TG API runtime library:
  • ctgclient.dll (Windows)
  • libctgclient (UNIX and Linux)

You can find a 32-bit version of this file in the <platform>/lib directory of the ctgredist package. This file can also be found in the <install_path>/lib directory of an installed CICS TG.

You can find a 64-bit version of this file in the <platform>/lib64 directory of the ctgredist package. This file can also be found in the <install_path>/lib64 directory of an installed CICS TG.

On AIX®: libctgclient in <platform>/lib supports both 32-bit and 64-bit operation. There is no <platform>/lib64 directory.

At run time the ctgclient must be available on the system path or in the same directory as the ECI V2 and ESI V2 application.

Start of change

ECI V2 and ESI V2 error log

To enable the error logging of system errors, socket errors, and other Gateway connection errors, turn on CTG_TRACE_LEVEL1 trace. For more information see Tracing in ECI V2 and ESI V2 applications. End of change

CICS Transaction Gateway Desktop Edition:

The license does not permit redistributing components. Each system which you install CICS Transaction Gateway Desktop Edition on or any of its components must have a separate license.

Concept Concept

Feedback


Timestamp icon Last updated: Tuesday, 19 November 2013


https://ut-ilnx-r4.hursley.ibm.com/tg_latest/help/topic/com.ibm.cics.tg.doc//ctgunx/dep_eciv2_remote.html