Tables 5-10 and 5-11 show the disk space required for JP1/Software Distribution Manager.

Table 5-10 Disk space required for JP1/Software Distribution Manager (central manager)

Facility		Disk space requirements
JP1/Software Distribution server	For Embedded RDB	120 MB + space allocated during database operations The amount of space allocated automatically during database operations depends on the scale selected when the database was created: Small scale: 300 MB Medium scale: 500 MB Large scale: 1,100 MB
	For Microsoft SQL Server or Oracle	12 MB
Remote Installation Manager	For Embedded RDB	24 MB
	For Microsoft SQL Server or Oracle	22 MB
Asset Information Manager Subset	For Embedded RDB	140 MB + space allocated during database operations The amount of space allocated automatically during database operations depends on the size of the database: 100 MB or less: 300 MB 101 to 500 MB: 1 GB 501 MB or more: 1 GB
	For Microsoft SQL Server or Oracle	45MB
AMT Linkage		1 MB
WSUS Linkage		1 MB
OpenView Linkage		9 MB
OpenView Gateway Server		4 MB
Common area of JP1/Software Distribution Manager		36 MB
Packaging by the Packager		1 KB + package size
Package storage		Number of packages (package size after compression + 2 KB) (KB)
Storing operation history		See (3) Disk space required for storing operation log files.
Backing up operation history		Number of clients x (size of compressed operation history that is to be backed up) (MB)
Remote installation		1.0 x number of packages x number of clients + number of packages x 0.3 (KB)

Table 5-11 Disk space required for JP1/Software Distribution Manager (relay manager)

Facility		Disk space requirements
JP1/Software Distribution server	For Embedded RDB	142 MB
	For Microsoft SQL Server or Oracle	34 MB
Remote Installation Manager	For Embedded RDB	24 MB
	For Microsoft SQL Server or Oracle	22MB
AMT Linkage		1 MB
WSUS Linkage		1 MB
OpenView Linkage		9 MB
OpenView Gateway Server		4 MB
Common area of JP1/Software Distribution Manager		43 MB
Packaging by the Packager		1 KB + package size
Package storage		Number of packages (package size after compression + 2 KB) (KB)
Storing operation history		See (3) Disk space required for storing operation log files.
Backing up operation history		Number of clients x (size of compressed operation history that is to be backed up) (MB)
Remote installation		1.0 x number of packages x number of clients + number of packages x 0.3 (KB)
Storage of packages distributed from the central manager		Number of packages (package size after compression + 2 KB) (KB)
Storage of management information about the package distributed from the central manager		Number of clients (number of packages within client x 2 KB) (KB)
Package installation		See (4) Disk space required for package installation below.

Tables 5-12 and 5-13 show the disk space required for JP1/Software Distribution Client.

Table 5-12 Disk space required for JP1/Software Distribution Client (relay system)

Facility	Disk space requirements
Relay system	30 MB
Remote Installation Manager	4 MB
Common area of JP1/Software Distribution SubManager	39 MB
AMT Linkage	1 MB
Storage of packages at relay system	Number of packages (package size after compression + 2 KB) (KB)
Storage of relay system management information	Number of clients (number of packages within client x 2 KB) (KB)
Package distribution	1.0 x number of packages x number of clients + number of packages x 0.3 (KB)
Package installation	See (4) Disk space required for package installation below.

Table 5-13 Disk space required for JP1/Software Distribution Client (client)

Facility		Disk space requirements
Client	Client core	24 MB
	Package Setup Manager	2 MB
	Additional facility	5 MB
	Distribution facility by Visual Test 6.0	2 MB
	Distribution facility by Visual Test 6.5	2 MB
	AMT Linkage	1 MB
Storage of client management information		Number of packages within client x 1.0 (KB)
Packaging information display		Number of packages to be packaged x 1.0 (KB)
Package installation		See (4) Disk space required for package installation below.
Startup Kit Support Tool		4 MB
Help		4 MB
Common area for JP1/Software Distribution Client		11 MB

This subsection explains the formula for calculating the disk space required for storing operation log files. Calculate the required capacity according to the operation log data you plan to collect.

Size of the operation log data for each item for one day

The following gives the formula for calculating the size of each item that can be collected as operation log data in one day.

• Process start = number of events expected per day (a) x 335 = A
• Process stop = number of events expected per day (b) x 335 = B
• Caption change = number of events expected per day (c) x 335 = C
• Active window change = number of events expected per day (d) x 590 = D
• Machine start = number of events expected per day (e) x 15 = E
• Machine stop = number of events expected per day (f) x 15 = F
• Logon = number of events expected per day (g) x 35 = G
• Logoff = number of events expected per day (h) x 35 = H
• File operation = number of events expected per day (i) x 837 = I
• Web access = number of events expected per day (j) x (621) = J
• Print operation = number of events expected per day (k) x 890 = K
• Printing suppression = number of events expected per day (l) x 890 = L
• Print suppression released = number of events expected per day (m) x 147 = M
• Operations to or from external media = number of events expected per day (n) x 150 = N
• USB media connection permission = number of events expected per day (o) x 300 = O
• USB media connection suppression = number of events expected per day (p) x 300 = P
• Device connection = number of events expected per day (q) x 350 = Q
• Device disconnection = number of events expected per day (r) x 350 = R
• Device connection permission = number of events expected per day (s) x 350 = S
• Device connection suppression = number of events expected per day (t) x 350 = T

For any item that will not be collected as an operation log, substitute 0 for the number of events. The units for all items is bytes.

For a - t, substitute the number of events expected per day for the corresponding item. A - T indicate the size of the operation log data for one day for individual items. The number of events expected per day is the number of operation-target events that occur in one day on a client PC. For Web accesses, multiple log entries are collected for any Web page that is divided into frames. Note, therefore, that multiple log entries might be collected even for a single Web access. For Web accesses, choose whether the maximum value (2,484 bytes) or effective log size (621 bytes) will be used for calculating the size of each event.

Additionally, to collect operation logs from a virtual environment, add the following size:

size of operation logs per day x number of logon users

Size of operation log data for a single client and JP1/Software Distribution Manager

Determine the size of the operation log data for a single client as described below based on the size of each item per day. DAY, WEEK, and MONTH indicate the size for 1 day, 1 week, and 1 month, respectively.

• Size of operation log data on a single client = A + B + C + D + E + F + G + H + I + J + K + L + M + N + O + P + Q + R + S + T = DAY
• Size of operation log data on a single client in 1 week (5 days) = DAY x 5 = WEEK
• Size of operation log data on a single client in 1 month (20 days) = DAY x 20 = MONTH

Based on the size of operation log data for a single client as determined using the above formulas, determine the disk space required for JP1/Software Distribution Manager. For example, if X clients are being managed, the following formula is used to calculate the disk space required for 1 month:

• Disk space required for 1 month when X clients are being managed = MONTH x X

The required disk space depends on the type of package to be installed. The value to be used in the calculation formula should be rounded up for each cluster size.

• Hitachi program product or another company's software
  Disk space requirement (bytes) =
  PCn x 944 + (size of installation script + size of AIT or recorder file) + (RPSz) + MAX(PPSz) + (APSz) + PCn x 300
  The sizes of the installation script, AIT file, and recorder file are as follows:
  

  For a Hitachi program product:

  The size of the installation script is 2,700 bytes and the size of the AIT and recorder files is 0.

  For another company's software (when the standard AIT or recorder file is used):

  The maximum total size of the installation script and the AIT or recorder file is 43 kilobytes.

  For another company's software (when a user-created AIT or recorder file is used):

  The maximum total size of the installation script and the AIT or recorder file is the total size of the files created by the user.

• For user data and user programs
  Disk space requirement (bytes) =
  PCn x (944 + 2500) + (RPSz) + MAX(RPSz) + (APSz) + PCn x 300
  
• For user data and user programs with optional facilities specified
  Disk space requirement (bytes) =
  PCn x (944 + 2500) + (RPSz) + MAX(RPSz) + MAX(size of installation destination directory) + (APSz) + PCn x 300
  
• When the background installation mode is used for data and user programs and when normal installation is specified
  Using the background installation mode and specifying normal installation can reduce the disk space required for a client during remote installation.
  Disk space requirement (bytes) =
  PCn x (944 + 2500) + MAX(RPSz) + (APSz) + PCn x 300
  

Legend:

PCn

Number of packages to be installed concurrently

RPSz

Size of the package, which can be obtained from the following formula:

(Number of files to be packaged + number of directories) 80 + size of the program product to be remote-installed on the storage media)

PPSz

Size of the program product to be installed on the storage media

APSz

Size of the program product after installation (if a new version is being distributed, use the difference in size from the previous version)

( )

Sum of the values

MAX( )

Maximum value

The following table shows the disk space required for the Packager.

Table 5-14 Disk space required for the Packager

Facility	Disk space requirements (in megabytes)
Packager	7

The required disk space depends on the type of package. The value to be used in the calculation formula should be rounded up for each cluster size.

• Packing user data or user programs
  Disk space requirement (bytes) = RPSz
  
• Packing compressed user data or user programs
  Disk space requirement (bytes) = RPSz x 2
  
• Packaging of Hitachi program product or another company's software on FD
  Disk space requirement (bytes) = RPSz + RDs
  
• Compressed packaging of Hitachi program product or another company's software on FD
  Disk space requirement (bytes) = RPSz x 2 + RDs
  
• Packaging of Hitachi program product or another company's software on CD-ROM
  Disk space requirement (bytes) = RPSz
  
• Compressed packaging of Hitachi program product or another company's software on CD-ROM
  Disk space requirement (bytes) = RPSz x 2
  

Legend:

RPSz

(Number of files to be packaged + number of directories) x 80 + total size of the files to be packaged

RDs

Data size of the target storage media

The following table shows the disk space required for the Automatic Installation Tool.

Table 5-15 Disk space required for the Automatic Installation Tool

Facility	Disk space requirements (in megabytes)
Automatic Installation Tool	6

For JP1/Software Distribution Manager (central manager), there are no files that depend on the user environment. For details about the database files for JP1/Software Distribution Manager, see 5.4 Estimating disk space requirements for the database.

The following files depend on the user environment of JP1/Software Distribution Manager (relay manager) and JP1/Software Distribution Client.

Files for managing higher systems:

Files for managing higher systems are created in \Master\Db\HOSTSYS in the installation directory of JP1/Software Distribution. One of these files is created for each higher system, and each file uses 400 bytes. A file is created when the higher system is changed or when the local system is accessed by the higher system. When multi-polling is used, a file is required for each of the specified higher systems.

File for managing installed-package information:

The installed-package information management file UPLISTD.BON is created in \Master\Db\ in the installation directory of JP1/Software Distribution. As many information items as there are software programs are added to this file at the following times:

• When software is found by Search software installed by Software Distribution, Search all software, or Search software listed in "Add/Remove Programs" of a Get software information from client job
• When software is installed by a Install package or Send package, allow client to choose job.

Each software item requires one kilobyte of space.

Note that all software packages installed by JP1/Software Distribution that have the same package ID are treated as the same package. Therefore, there is only one software information item for a software program with the same package ID even if multiple different versions are installed.

File for managing file search information:

The file search information management file VIFLIST.BON is created in \Master\Db in the installation directory of JP1/Software Distribution. As many information items are added to this file as there are files found by Search for a file of a Get software information from client job.

Each file uses 300 bytes of disk space.

File for managing Microsoft Office product information:

The Microsoft Office product information management file INFSCTx0.BON (x: internal management number) is created in \Master\Db\ in the installation directory of JP1/Software Distribution. As many information items are added to this file as there are software programs found by Search for Microsoft Office products of a Get software information from client job. Although the size depends on the product, approximately 300 bytes of disk space are required for each software item.

File for managing anti-virus product information:

The anti-virus product information management file INFSCTx1.BON (x: internal management number) is created in \Master\Db\ in the installation directory of JP1/Software Distribution. As many information items are added to this file as there are software programs found by Search for anti-virus products of a Get software information from client job. Although the size depends on the product, approximately 300 bytes of disk space are required for each software item.

For details about the user environment-dependent files for JP1/Remote Control, see the manual Job Management Partner 1/Remote Control Description and Operator's Guide.