CICS® Transaction Gateway is installed and runs as a Windows service.
Initially you manually start CICS Transaction Gateway as a Windows service. When you have created a configuration file and tested the configuration settings by running CICS Transaction Gateway, you should then configure the IBM® CICS Transaction Gateway service to start automatically when Windows starts. For more information see Configuring the Windows service. The product does not require a user to be logged on to Windows for it to run.
To view the CICS Transaction Gateway Windows service:
For more information on Windows services, see your Windows documentation.
Messages generated by CICS Transaction Gateway when running as a service are written to the application log and the system log of the Windows event viewer, whenever the service is started or stopped. Details of any startup override parameters are written to the Windows application event log when the service starts.
When starting CICS Transaction Gateway on Windows, any standard output or error text produced is captured in the file jvmdbg.log, located in the <product_data_path> directory. The main use of this file is to capture debug output from the jvm, when the CICS Transaction Gateway is started with debug java startup parameters specified.
CICS Transaction Gateway can also be installed on a remote desktop server. In this situation you can access the product through remote desktop services.