About Package Global Settings
Before creating install packages, you need to decide where the packages should be located and how they will be made available. The Packages > Package Global Settings context contains settings that affect how the install packages are generated and distributed.
| Property | Description |
|---|---|
|
Package Build Location |
This is where the Install files will be built. If the Uniprint Website is installed, this value will contain the location of the Uniprint directory on the web site. When the Uniprint Web site is installed, the Package Build Location property is set to the full path of the Uniprint directory e.g. \\SERVER\C\Inetpub\wwwroot\Uniprint\. Since the C drive of a web server is unlikely to be shared for security reasons, it is best to make the Uniprint directory into a network share with appropriate permissions, then change the Package Build Location to this share name, e.g. \\SERVER\UniprintWebSiteShare\. |
|
Package Download and Update Location |
This specifies the URL of the website or network location that users will be able to download Install Package from, and where updates will be retrieved from. If the Uniprint Website is installed, this value will contain the URL of the Uniprint directory on the web site. If the web site uses a different port than the default (80), this must be included in the URL, e.g. http://server:81/Uniprint/. Packages and modules can be made available for download from a network share, rather than a web server. In this case, the URL should start with file://, rather than http://. If your site uses SSL, the URL should start with https://. |
|
Shared Directory |
This specifies the shared network location of all the user supplied source files (e.g. EULA files and Custom Modules) that are used to create install packages. This is to ensure that packages can always be created, regardless of where the Pharos Administrator is installed. The default location is Pharos\bin\shared on the Principal Server. If you change the location of the shared directory, you must copy any existing files from the old location to the new location manually. |
|
Update Frequency (days) |
This value determines how often installed components should check to see if updated components are available. Components check for updates whenever they are used, provided that the amount of time specified here has passed since they were last used. For example, if the Update Frequency is set to one day, and a user prints five times in a day, the components will only check for updates once that day. However, if the user goes more than one day without printing, the components will not check for updates until the next time the user prints. |