The method you must use to deploy your application depends
on the CICS TG API used by the application.
Configuring remote Client application environments
The files required for compiling and running
applications on a client machine are installed with CICS® Transaction Gateway and must be copied
to the client machine.
Deploying the CICS resource adapter The resource adapter is provided as
a standard module, ready for deployment into a Java Platform, Enterprise
Edition (JEE) application server. The resource adapter can be packaged
in a JEE application along with other components such as Enterprise
JavaBeans, and can be used to create larger, more complex systems.
Deploying ECI V2 and ESI V2 to remote systems
Remote ECI V2 and ESI V2 applications are deployed as executable
files. The API is not supported on z/OS® but connectivity from a remote ECI V2 or
ESI V2 application to CICS TG
for z/OS is supported.
Deploying .NET applications to remote systems
Remote .NET applications are deployed to the Windows runtime environment as an executable
assembly (.exe) or library assembly (.dll), depending on the type
of application.