The build script options are important because they provide the
input to the build script generation process. There are six scripts
used by the SCLM build and deploy translators. The values set in the
user build scripts are copied to these locations and perform the actual
build/deploy process. Individual sites can have different scripts
configured for specific build/deploy types. See your SCLM Administrator
for detailed information.
The first option is build script mode, which can be either AST
or native. Switching this option will change the default value of
the build scripts. SCLM Developer Toolkit ships with a native ANT
build process for Java/J2EE support. However, enhancements to the
Java/J2EE build process now additionally provide build support using
Application Server Toolkit (AST). AST allows replicated project workspaces
from the RDz IDE that have been stored in SCLM to be built by SCLM
using headless mode Eclipse on z/OS®.
The scripts include the following:
- Base Java Project Build
Script Name
- Base Java/SQLJ Project Build Script Name
- Base Web Project Build Script Name
- Base EJB Project Build Script Name
- Base EJB/SQLJ Project Build Script Name
- Base EAR Project Build Script Name
- Base Deploy Build Script Name
- Base Secure Copy Script Name
You can specify these additional build script options:
- JACL Script Location and Name
- Specify the JACL script location and name. These details relate
to the script used for a J2EE application to be deployed into a WebSphere® Application Server.
This might be site-dependent because the script can be customized
to suit specific requirements.
- JAR Files location
- Specify the JAR file location. This location is used in the Build
scripts to tell the build processor the z/OS HFS
location that contains the required classpath jars used to build applications.
- WSAdmin Tool Location
- Specify the location of the WSAdmin tool.
- Source Encoding for Build
- Specify the Java source
encoding to determine the Java source
codepage at build time for Java/J2EE projects. Java source might be stored in SCLM as either
ASCII or EBCDIC.