Benefits of the CCI Connector for CICS TS

  1. The CCI Connector for CICS® TS helps you to build powerful server components that make use of existing CICS programs.
  2. CICS enterprise beans that use the connector:
    • Enable programmers of Java client applications, who typically have little or no knowledge of CICS, to add the power of CICS to their applications.
    • Can be called by Java client applications and servlets running on many platforms. The client code used to call the bean (and through it the CICS server program) is identical on all Java platforms. Thus, for example, the client could be an enterprise bean running on WebSphere, a servlet running on a Web server, or a standalone application on a workstation.
    • If written correctly, should be portable, with little or no modification, between all EJB servers that support the Common Client Interface.
  3. Because the Common Client Interface is a non-proprietary standard, the CCI code that calls the server program should be portable, with little or no modification, to and from most Java-enabled platforms.
  4. Because the CCI Connector for CICS TS runs inside CICS, no network flows are required between the connector and CICS. Thus, the connector's performance is better than that of CCI connectors that use the ECI resource adapter to access CICS programs from outside CICS.
  5. Using the connector from a CICS session bean results in a simple, two-tier deployment model: Client → CICS TS.
  6. Programs written to use the ECI resource adapter can be easily adapted to use the CCI Connector for CICS TS. Thus, client programs that previously accessed CICS server programs from outside CICS can be migrated to run inside CICS.
    Note: If you port a program written to use the ECI resource adapter to use the CCI Connector for CICS TS, you must recompile the program to use the CICS TS-supplied classes in the dfjcci.jar JAR file, rather than the CICS Transaction Gateway classes.
  7. The CCI Connector for CICS TS supports the Java 2 security policy mechanism.