Avoid transfer the package to the Scalability Server for each SD deployment
Article ID: 26459
Updated On:
Products
Issue/Introduction
When a SD deployment is made, each time the Domain Manager will transfer the package first to the Scalability Server that manages the target Agent(s) and then the deployment will be made from there.
Is it possible to avoid this transfer every time a new SD deployment is made for that same package?
Environment
CA Client Automation - All Versions
Resolution
The packages can be stored on the Library of Scalability Servers the first time a package is distributed to an Agent connected to that Scalability Server, so the next deliveries will not need to transfer the package again to that Scalability Server.
This can be achieved setting the Job Option "Store Packages in the Scalability Server's Staging Library" when setting up a delivery, when a new Job Container is created:
- Use the "Software packages to deploy with custom settings" to open the Setup Jobs window.
- Select the Jobs tab.
- On the Job Options tab select "Store Packages in the Scalability Server's Staging Library".
- In order to set this parameter permanent for future deployments click on "Set as Default" so this option will be active for further deployments.
Additional Information
There is an option in DSM Explorer under Control Panel > Configuration > Software Job Management > Job Handling :
Fail implicit deliveries to Scalability Servers
Jobs via Scalability Servers will implicitly deliver software from the Manager if not present in the Scalability Server's Staging Library.
To maintain a better control of the deliveries in the network, you can turn off implicit deliveries.
If turned off, jobs will fail if the required software is not present in the Staging Library.
***If you try to send a Software Delivery job for a package is not Staged, you will get the following error
Application is not allowed: Item is not available at Scalability Server <Scalability name> [SDM223615] ***
Feedback
