SCLM Developer Toolkit provides Java/J2EE language translators to SCLM to enable full Java/J2EE build capability. SCLM Developer Toolkit not only provides functionality to store Java/J2EE source and objects but through these translators enables SCLM to build and fully control Java/J2EE applications. The Java/J2EE objects supported through these language translators are Java™ classes, Java archive files (JAR) including Enterprise Java Beans (EJB) JAR files, Web archive files (WAR) and Enterprise archive files (EAR).
Deployment functionality enables an EAR file to be deployed into a J2EE container. SCLM Developer Toolkit not only supports EAR deployment on WebSphere® Application Server running on z/OS® but the deploy framework allows the distribution and deployment to non-z/OS platforms. For more information on SCLM Deployment, refer to Deployment services.
The SCLM ARCHDEF is the primary SCLM file for defining the elements of a Java/J2EE project. In regards to Java/J2EE applications the ARCHDEF represents how the J2EE application is structured in the Client project workspace.
The ARCHDEF contains an inventory of all files in the project, using the SCLM host short file name mappings. Additional keywords in the ARCHDEF such as LKED, SINC, OUT1 indicate to SCLM the J2EE nature of this project and source include a Java/J2EE build script to facilitate build processing of this project.
For very simple Java projects the source may be built directly by issuing the build against the Java source in SCLM. Certain Java build properties must be set in the $GLOBAL file which resides in SCLM type J2EEBLD. This includes properties to set the Java build environment on z/OS . In addition, if the Java source requires external classpath dependencies, these external classes or JAR files may be stored in the z/OS Unix file system directory referenced and set by the property CLASSPATH_JARS in $GLOBAL.
A separate ARCHDEF is required for each application component that might make up an enterprise application (EAR); for example, an EAR which contains a WAR which contains an EJB JAR, should have an archdef for the JAR, a high level archdef for the WAR with an INCL of the EJB JAR archdef, and a INCL of the WAR archdef. The high level EAR archdef should also include an INCL of the WAR archdef and an INCL of the JAR archdef. SCLM Developer Toolkit will create the appropriate Archdef and associated build script in SCLM when adding (migrating) a new J2EE project into SCLM. When adding additional parts to SCLM there is an option to add them to the appropriate ARCHDEF.