Deploying a batch file within a Software Delivery Package
search cancel

Deploying a batch file within a Software Delivery Package


Article ID: 71704


Updated On:


CA Client Automation - IT Client Manager CA Client Automation CA Client Automation - Patch Manager CA Client Automation - Software Delivery


To troubleshooting Software Delivery Deployment issues sometimes transferring a usual large package may not be feasible. In such cases, deploying a small batch file (2KB) could help troubleshoot the problem quickly.

This document outlines the procedure to create a small batch file package for testing purpose.


Client Automation - All versions


1. Create a simple batch file (named runbat.bat in this example) using 'Notepad' with the following lines as an example.

echo start runbat
date /t
time /t
echo end runbat


2. In the DSM Explorer navigate to Software->Software Package Library. Right-click and select New->Software Package.

3. Give the package a desired name. In this example 'runbat 1.0'. Click OK.

4. The package is now available in the Software Package Library. Expand the package, drag and drop the batch file to the Source section of the package.

5. Expand the package 'Source' and locate the batch file. Drag and drop the batch file to the 'Procedures' section of the package.

6. You can further customize the procedure by right-clicking the procedure and selecting 'Properties'.

7. Add the '>$rf' parameter so that the job output can be captured and displayed in the DSM Explorer. Click OK.

8. Right-click and chose 'Seal' to seal the package to be able to deploy it.


9. Deploy the package to the desired machine to test and troubleshoot deployment issues. If the job is successful, the output will be displayed in the Job properties under the 'Job Output' tab.




Additional Information