Job Management Partner 1/Software Distribution Administrator's Guide Volume 1
![[Contents]](FIGURE/CONTENT.GIF)
![[Glossary]](FIGURE/GLOSS.GIF)
![[Index]](FIGURE/INDEX.GIF)
![[Back]](FIGURE/FRONT.GIF)
The following points should be noted when you perform packaging:
- The maximum number of cabinets you can create is 1,296. You can register a maximum of 256 packages in each cabinet.
- You can package a maximum of 65,531 files or directories at one time. For details, see the KDSF0123-E message remark # in the subsection 7.2.3 Lists of messages in the manual Administrator's Guide Volume 2.
- Once a package is stored in a cabinet, you cannot rename it or move it to another cabinet.
- The maximum package size is 2 gigabytes. You must package files so that this limit is not exceeded.
- You can only package files that were last updated or accessed in the period from 1970 to 2037. You cannot package files from before or after this period.
- Packaging may fail if a file or directory subject to packaging is being used by another application.
- You cannot package files from multiple directories in the same package.
- When you package another company's software that is compressed, you must first create a directory and copy the software into it, and then specify that directory for packaging.
- When you package user data that is stored on multiple floppy disks, first copy the data onto the hard disk, and then specify the appropriate directory or file for packaging.
- When you package software that requires floppy disks to be read in a certain order, such as another company's software, you must be sure to insert them in the correct order. Inserting floppy disks in the wrong order will result in an installation error after distribution.
- Do not create any non-recorder file in the recorder file storage directory that is specified during packaging.
- A user-created installation script is not checked for syntax errors during packaging. If there is a syntax error, remote installation will fail.
- If another company's software requires entry of a CD key during installation, you can enter it in the Serial number field on the Setup Information page.
- To avoid the difficulty of managing cabinets when there is the same cabinet name for different cabinet IDs, always specify the cabinet name paired with the cabinet ID. In the same cabinet, be sure to provide the package name paired with the package ID.
- You must note the following points when you create a package for UNIX clients:
- Specify the destination directory using no more than 64 characters (including the drive name and colon (:)).
If the specified directory consists of more than 64 characters, the distributed package is installed immediately under the base directory.
- Specify 64 characters or less for the installation directory on which a package is remotely installed in a Unix client computer. Otherwise, since the Unix client determines that nothing is specified for the package installation directory, it will be remotely installed under the root directory.
Installation directory length |
64 characters or less |
65 characters or more |
Remote installation destination |
Specified directory |
Root directory |
- Specify either nothing or four digits for the generation number. If you use fewer than four digits to specify the generation number, distribution of the registered package will fail due to a generation number error.
- The name of a file or directory to be packaged cannot contain spaces, a character string enclosed in parentheses or brackets (such as ( ), [ ], or { }), or any of the following special characters:
$ ! * ? ; & " ' ` ^ \ | < >
- When you create a package (register a resource) using the UNIX version of Packager via relay system of the Windows version, you cannot create (register) it. In this case, the -h option (host-name) in the resource registration command has no effect, and it is created (registered) on the relay system of the Windows version.
- In the Package window, you cannot delete a cabinet or package that was registered using the UNIX version of Packager.
- When you package directly from a Hitachi Integrated CD-ROM, specify in the File window of Packager the root directory of the drive in which the CD-ROM is mounted. Once this is done, the products subject to remote installation will be listed when Packaging is selected from Run. Select and package the products for remote installation from this list. If packaging is executed with a directory other than the root directory of the Hitachi Integrated CD-ROM specified, remote installation will fail.
- Each package is identified with a package ID, version/revision number, and generation number. When you package software on the managing server or the relay manager/system, make sure that you do not specify a package ID, version/revision number, and generation number that are all identical to an existing package.
- When you transfer a package to relay system:
When the relay system contains a software package with ID, version/revision number, and generation number that are all identical to the software package to be transferred, you cannot transfer it to the relay system because it is assumed that the software package has already been stored in the relay system even though the contents of your software package are not the same as the existing one.
- When you remotely install a package on client:
When there is a software package with ID, version/revision number, and generation number that are all identical to the software package to be remotely installed on the client, you cannot remotely install it on the client because it is assumed that the software package has already been installed even though the contents of your software package are not the same as the existing one.
However, you can set JP1/Software Distribution to transfer or remotely install a software package that is identical to an existing one. To do this, during job creation, in the Change Installation Conditions dialog box, select Replace existing package.
All Rights Reserved. Copyright (C) 2009, 2013, Hitachi, Ltd.
Copyright, patent, trademark, and other intellectual property rights related to the "TMEng.dll" file are owned exclusively by Trend Micro Incorporated.