I deliver the packages to Agents using NOS and they can access the packages from the shared library from the Scalability Servers but I can see that the package is compressed on the Scalability Server at every distribution.

Document ID : KB000025661
Last Modified Date : 14/02/2018
Show Technical Document Details

Description

I deliver the packages to Agents using NOS and they can access the packages from the shared library from the Scalability Servers but I can see that the package is compressed on the Scalability Server at every distribution. How can we avoid the creation of the zip file in order to improve the performance?

Solution

You can configure the Scalability Servers so the zip files will be created only if they are needed.

It can happen when an Agent can not access the share so it uses the internal file transfer and need the zip file for download.

There are two configuration policy parameters to be set under DSM > software delivery > shared:

  • NOS: NOS-less agents attached = No

    Setting is used by Domain Manager and Scalability Server, defines support for NOS-less Agents connected to the Server. If set to Yes it forces the creation of the compressed package needed by nos-less targets. If set to No the Server attempts to determine the need of this file. Used in conjunction with NOSLessOnTheFly.

  • NOS: NOS-less on the fly = True

    Setting is used by Domain Manager and Scalability Server, defines support for NOS-less Agents connected to the Server. If this value is set to False NO compressed files will be created at all. If set to True you can optimize the cpu and disk usage as the compressed file will be created only if needed.

In the default configuration, "NOS-less agents attached" is set to Yes and " NOS-less on the fly" set to True so in this case just changing "NOS-less agents attached" to No will avoid the creation of the zip file when delivering the package and will only be created if needed.