Software

The software requirements for enterprise beans are:
  • IBM® Software Developer Kit for z/OS®, Java™ 2 Technology Edition, Version 1.4.2.
    Note: There are two versions of the IBM Software Developer Kit for z/OS, Java 2 Technology Edition Version 1.4, a 31-bit and a 64-bit version. CICS® TS 3.1 supports only the 31-bit version, which must be at the 1.4.2 level.
  • A name server that supports the Java Naming and Directory Interface (JNDI) Version 1.2. (The JNDI API provides directory and naming functions for Java applications. It enables a client to locate an enterprise bean. The JNDI is mapped to an external name server.) You can use either of the following:
    A Lightweight Directory Access Protocol (LDAP) name server,
    such as IBM SecureWay Directory, which is shipped with the IBM SecureWay Security Server, an optional feature of OS/390 and z/OS.

    A distributed version of IBM SecureWay Directory is also available.

    A Corba Object Services (COS) Naming Directory Service
    such as that provided with IBM WebSphere® Application Server Version 6. This provides a transient CosNaming Service implementation. Being transient means that its contents are lost when it is stopped or restarted; as such, it is likely to be used only on a test system.

    Any industry-standard COS Naming Server that supports JNDI Version 1.2 can be used. For example, CICS also supports the COS Naming Server supplied with IBM WebSphere Application Server Advanced Edition for AIX®, Version 3.5 and later.

    WebSphere Application Server Version 5.0, or later
    The required component is the Assembly Toolkit (ATK) for Windows, which is used to deploy enterprise beans. (The Application Assembly Tool (AAT), provided with WebSphere Application Server Version 4 and early copies of WebSphere Application Server Version 5.0, can still be used but is not supported).
    Note: The ATK is included in WebSphere Studio Enterprise Developer Version 5.1, which is shipped with CICS TS 3.1 as a marketing promotion.