Rational Developer for System z

Deployment services

SCLM Developer Toolkit provides several deployment features. You can deploy Enterprise archive files (EAR) into any WebSphere® Application Server (WAS). In addition, any component built or controlled by the SCLM Developer Toolkit can be manipulated using a customizable deployment script. Sample scripts are provided that can be used to copy an EAR to a remote host using the secure copy (SCP) and secure FTP (SFTP) commands.

To launch a deployment script, right click on the project and select Team > Deploy Enterprise Application. The following sections provide information about creating and running deployment scripts, deployment customization, and sample deployment scripts.

Run an existing deployment script

If you already have a deployment script that you wish to execute unchanged, select the Run Existing Deployment Script radio button.

You must specify the scripts member name, group and type. Alternatively, you can click the Browse button, and go through the standard Developer Toolkit member search screens to automatically fill in the values.

Once you have selected the appropriate script and filled in its name, group and type, click OK to continue. At this point, Developer Toolkit will contact the host and invoke the selected deployment script.

Create a deployment script

To create a new script, or pass new parameters to an old script, select the Create Deployment Script radio button. An edit field becomes active below the radio button. You can input the XML for your deployment script there.

Browse SCLM
If you want to modify a script that already exists in SCLM, click this button.
Browse Local
If you want to modify or use a script stored on your workstation, click this button. If you have no prepared script, type into the edit field.
Deploy skeleton
This provides you with the basis of a WAS deployment script. You must modify the skeleton with the details of the target WAS server and EAR file.
Remote deploy skeleton
Provides a WAS deployment script that can be used to deploy an EAR to a remote WAS server.
Secure deploy skeleton
This provides you with the basis of either an SCP or SFTP deployment script. To switch from SCP to SFTP, change the SCLM_ANTXML property value from BWBSCOPY to BWBSFTP.
Include SCLM members
This button enables you to copy a member from SCLM onto the z/OS® UNIX System Services File System. After clicking you will be presented with the familiar member filtering and selection screen. Select the member you are interested in here.

An example script for including SCLM members is as follows:

<ANTXML>
<property longname="cipherWAR.ear" shortname="CI000003" group="RELEASE" 
type="J2EEEAR" dest="/u/username/"/>
</ANTXML>

The parameters are as follows:

longname
The SCLM long name of the member to copy.
shortname
The SCLM short name of the member to copy.
group
The first group in which to look for the member to copy. SCLM will continue to search the hierarchy from the group specified.
type
The SCLM type of the member to copy.
dest
The directory location on the z/OS UNIX System Services File System to which the file should be copied. Alternatively, you can use this feature to select which built object (for example, J2EEEAR) you want to deploy via SCP or SFTP. In this case, you set the z/OS UNIX System Services File System location of the included member and the input location of the EAR file name to the same location, as in the following example:
<ANTXML>
<! -- other script properties -->
<! -- Input EAR file -->
<property name="LOCAL_FILE_PATH" value="/u/username/cipherWAR.ear"/>
<!-- Include member -->
<property longname="cipherWAR.ear" shortname="CI000003" group="RELEASE" 
type="J2EEEAR" dest="/u/username/"/>
</ANTXML>

When you are satisfied with the contents of your script, give it a name and language, and click OK. This launches the deployment process. You can invoke this build script later by selecting Run an existing deployment script.

Deployment customization

At the core of deployment there are essentially two scripts. The first type of script, which is also the one you modify, is a properties script. It simply contains a list of parameters for your deployment operation. The second is the action script that contains the steps required to run your deployment operation.

When you initiate a deployment you specify the contents of the properties script, and one of those properties is SCLM_ANTXML that contains the member name of the corresponding action script. Developer Toolkit will take your properties script and overlay it on the action script, before invoking the resultant action script with ant.

WAS deployment is a special case, where the SCLM_ANTXML points to a JACL action script.

The following is a list of the available sample scripts that come with Developer Toolkit.

BWBDEPLA
WAS EAR Deployment
BWBSCOPY
Secure copy deployment. Copies a build object from one host to another using SCP.
BWBSFTP
Secure FTP deployment. Copies a build object from one host to another using SFTP.
BWBRDEPL
Remote WAS EAR deployment

Sample deployment scripts

The following topics provide sample scripts that use a JACL script to deploy on a local WAS on z/OS:

Feedback