Preparing the SCM script
Before the first time that you run an ARA Workflow Job, you must prepare an NSH script that is responsible for retrieving the Java EE application files from the SCM system, in preparation for deployment. This script performs the following actions:
- Accesses your SCM system.
- Copies the relevant Java EE application files from the SCM system.
- Stores copies of the application files in a location that you specify, where they are ready for deployment.
A sample SCM script file named p4script.nsh is provided by BMC Software for the Perforce SCM system (as discussed in Contents-of-ARA-Workflow-Job-kit). You can use this sample script as a template for the creation of your own script that adheres to your unique organizational standards. To use the sample script, you must first edit the script and configure the values of the parameters within the script.
Arguments for inclusion in the script
The following arguments that you can include in your SCM script are based on data received from the input parameters of the ARA Workflow Job.
Argument | Workflow Job input parameter | Description |
|---|---|---|
$1 | SCM Build ID | The exact revision of the application files. |
$2 | NSH Path to Copy Artifacts to | The path, in NSH format, to where you want to store copies of the application files to enable their deployment. |
$3 | NSH Path to Artifact List File | The path, in NSH format, to the Artifact List File that you created, which lists all the application files that need to be copied and deployed. |
$4 and on | Optional SCM Script Arguments | Any additional optional arguments that you want to include in your SCM script. |
For more information about the input parameters of the ARA Workflow Job, see Creating-an-ARA-Workflow-Job.