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.
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.
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.
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:
<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.
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.