Preparing an Artifact List file
Before the first time that you run the ARA Workflow Job to deploy a specific Java EE application, you must ensure that your SCM script file has all the information necessary to retrieve all the relevant artifact files.
The sample p4script.nsh script obtains the list of artifact files from an Artifact List file, which is referenced within the script as argument $3. The Artifact List file is used solely by the SCM script. If you want to use this mechanism, you must prepare the Artifact List file before running the ARA Workflow Job.
The Artifact List file is a text file that contains a list of the artifact files that you want to copy and deploy, along with basic details about each artifact file. A sample file named plants-file.input is provided with the ARA Project module (as discussed in Contents-of-ARA-Workflow-Job-kit).
To create an Artifact List file
Create a text file that contains the most basic information necessary for copying the Java EE application files from the SCM system — the name of the file in the SCM system and the source path.
Within this text file, include a header line with the names of data columns, separated by semicolons. Under the header line, include one line for each Java EE application file. End this file with a hard carriage return (that is, press Enter one last time).
Include the following data columns in this text file:
File property | Column name and description |
|---|---|
Name of file | file name |
Source path in the SCM system | The exact number and names of columns depend on the type of SCM system. |
The following example presents typical lines from a list of artifact files:
file name;depot path;workspace path
helloWorld.ear;//bl/was/apps;/c/p4client/bl/was/apps
plants.war;//bl/wl/apps;/c/p4client/bl/wl/apps