Package Factory steps
This class of steps comprises all those concerned with the package factory and the creation and maintenance of the different types of packages and packagers.
Copy Package
This step copies a package from a remote package factory to your local package factory. Be aware that it is imperative that the packager alias for the package type to be copied is already created under section HttpAliases of the HttpProtocolHandler.ini configuration file of the server, for example, PackagerCustom.
Parameter | Description |
|---|---|
Package Type | Select the type of the package that is to be copied from the drop-down list. |
Package Name | The name of the package to be copied. |
Server Port | The corresponding port on the remote device. |
Server Name | Enter the name of the server from which the package is to be copied. You may enter in form of the remote device's IP address, for example, 192.1.125.2 or FD43-0-0-0-8C84-4BAD-D413-DD68.ipv6-literal.net , or as its short or long network name. |
User Name | Enter into this field a valid user login to log on to the remote device. |
User Password | The password corresponding the login specified above. For security reasons the password is only displayed in the form or asterisks (*). |
Publish Package to Master
This step publishes a specific package to the master at a specific time which is managed via the package's schedule. The step must be executed on the respective packager.
Parameter | Description |
|---|---|
Package Type | Select the type of the package to be published to the master from the drop-down list. |
Package Name | Enter into this field the complete name of the package, that is, including the extension, for example, orca.msi . If the package is located in a folder under the packager this folder must also be included in the complete name, that is, database_pkgs/orca.msi . |
Comments
Log in or register to comment.