This subsection describes how to create a new Embedded RDB database.

You must specify for the path to the database area a directory that actually exists. You can use alphanumeric characters, the space, and the following symbols:

: . \ # @( )

1. In the Welcome dialog box, select Create new database, and then click the Next button.
   The Authentication Information of Database dialog box appears.
   
2. In the Authentication Information of Database dialog box, specify the password and then click the Next button.
   The Cluster System Environment Settings dialog box appears.
   

   Figure 7-5 Cluster System Environment Settings dialog box

   

   If you are using JP1/Software Distribution Manager in a cluster system environment, select the Used in cluster system environment check box. For details about the settings for using JP1/Software Distribution Manager in a cluster environment, see 11.1 Constructing a JP1/Software Distribution Cluster System.
   This section describes the procedure for creating a database that is to be used by JP1/Software Distribution Manager in a normal network environment.
   
3. Click the Next button.
   The Operation Scale Setting dialog box appears.
   

   Figure 7-6 Operation Scale Setting dialog box

   

   Select a scale of operations appropriate to the environment in which JP1/Software Distribution Manager is used. The default settings for database area sizes are set in accordance with the selected scale of operations. Note that the sizes of database areas can be changed in the dialog box that follows.
   It is recommended that you select Large scale unless otherwise necessary. If you monitor the operation status of clients, it is important that you select Large scale. For guidelines for the number of data items that are expected based on the scale of operations, see (2) Guidelines for the amount of data based on the scale of operations.
   
4. Click the Next button.
   The Database Management Settings dialog box appears.
   

   Figure 7-7 Database Management Settings dialog box

   

   Management database area

   Specifies the directory path where the database and work table area for JP1/Software Distribution Manager are to be stored, as 1 to 46 characters.

   If JP1/Software Distribution Manager is to be used in a cluster system environment, specify the path to the shared disk that stores files in the management database area other than work table area (data that needs to be inherited in the event of failover).

   The size of the management database area is fixed at 4,270 megabytes. To specify a size for work table space, use the Size field in Operation table area.

   Operation table area

   Specifies the size of the operation table area in the range from 50 to1,048,575 megabytes.

   The default size for the operation table area depends on the scale of operations selected in the Operation Scale Setting dialog box. The following table lists the default sizes:

   Selected scale of operation	Default size for operation table area (megabytes)
   Large scale	22,852
   Middle scale	6,855
   Small scale	1,142

   Note that the Path field is enabled when the database is used in a cluster system environment. Specify the path to the local disk that stores files in the work table area (data that need not be inherited in the event of failover), as 1 to 46 characters.

   Automatically increase the size

   Selecting this check box specifies that when the amount of work table area needed exceeds the value entered in the Size field, the size of the work table area is to be increased automatically.

   You should select this check box if the size of the work table area may exceed the specified value because of the type of operations to be performed. The default is that this check box is selected.

   The work table area can be expanded to a maximum of 1,048,575 megabytes (assuming there is sufficient space available on the disk).

   In a cluster system environment, the Automatically increase the size check box setting should be the same in both the executing system and the standby system.

5. Specify necessary information in the Database Management Settings dialog box and then click the Next button.
   The Detailed Settings of Database dialog box appears.
   

   Figure 7-8 Detailed Settings of Database dialog box

   

   In this dialog box, you can specify the paths and sizes of the database area files.
   Specify the path to a database area file as 1 to 104 characters. Note that if the OS being used is a 64-bit version of Windows Server 2012, Windows Server 2008 or Windows Server 2003 (x64), a path under the %Systemroot%\system32 directory can be specified.
   The default database area file sizes depend on the scale of operations selected in the Operation Scale Setting dialog box. The following table lists the default, minimum, and maximum sizes depending on the selected scale of operations.
   

   Table 7-1 Default, minimum, and maximum database area file sizes depending on the scale of operations

   Database area file	Default size (megabytes)			Minimum size (megabytes)	Maximum size (megabytes)
   	Large	Medium	Small
   Resident table file	5,060	1,455	241	50	1,048,575
   Index file	22,870	404	67	50	1,048,575
   Job-related binary object file	13,420	4,232	951	250	1,048,575
   Asset information-related binary object file	131	131	131	100	1,048,575
   Software operation monitoring log file	43,454	50	50	50	1,048,575
   Security update management file	3,200	3,200	3,200	130	1,048,575
   Temporary table file	17,438	1,795	865	680	1,048,575

   For details about how to determine the size of each database area file, see 5.4 Estimating disk space requirements for the database in the Description and Planning Guide.
   If the Operation Log List window is not used with the software operation monitoring facility, it is advisable to specify a small size because the software operation monitoring log file is not used. For example, specify a value of 50 megabytes (minimum value).
   
6. Specify necessary information in the Detailed Settings of Database dialog box and then click the Next button.
   The Execute Database Creation dialog box appears.
   

   Figure 7-9 Execute Database Creation dialog box

   

7. Click the Create button.
   The database is created.
   

The following table provides guidelines for the number of data items that can be expected for each scale of operations, as selected in the Operation Scale Setting dialog box. The default values for the database area files that are set in the database manager are determined from the number of data items shown below.

Table 7-2 Number of data items expected for each scale of operations (database area)

No.	Item	Expected number of data items
		Large	Medium	Small
1	Number of cabinets	5	5	5
2	Number of remote collection-related jobs	2	2	2
3	Average number of clients per job	10,000	3,000	500
4	Number of remote installation-related jobs	20	20	20
5	Average number of packages per job	1	1	1
6	Number of jobs that are not related to remote installation	8	8	8
7	Number of remote installation-related ID group jobs that are managed by relay managing the ID	20	20	20
8	Average number of clients per ID group	5,000	1,500	250
9	Number of ID group jobs that are not related to remote installation	8	8	8
10	Number of ID groups	10	10	10
11	Average number of managing relays per ID group	10	3	0
12	Average number of clients registered per ID group	5,000	1,500	250
13	Number of clients	10,000	3,000	500
14	Average number of files that are acquired by software inventory search	100	100	100
15	Average number of system information items that are acquired	100	100	100
16	Number of job definitions	55	55	55
17	Number of folders	5	5	5
18	Number of remote collection-related job definitions	3	3	3
19	Number of remote installation-related job definitions	20	20	20
20	Number of Get software information from client jobs defined	4	4	4
21	Number of Transfer user inventory schema to client jobs defined	1	1	1
22	Number of jobs	55	55	55
23	Number of ID group jobs managed by relay managing the ID	250	75	0
24	Total number of ID groups specified by ID group jobs	25	25	25
25	Number of items in software search list	200	200	200
26	Number of hosts in the system configuration when OpenView Linkage is used	0	0	0
27	Number of host groups	100	30	5
28	Number of packages	40	40	40
29	Number of jobs executed by scheduling	5	5	5
30	Number of jobs that are not related to remote installation	8	8	8
31	Number of user inventory items	20	20	20
32	Average number of software information items that are to be acquired	200	200	200
33	Number of all-lower-clients jobs	1	1	1
34	Total number of relay managers specified in all-lower-clients jobs	3	0	0
35	Number of hosts subject to acquisition of registry information	10,000	3,000	500
36	Number of registry items to be acquired	10	10	10
37	Number of created registry collection items	10	10	10
38	Number of hosts in the system configuration	10,000	3,000	500
39	Number of files to be managed in the software inventory dictionary	100	100	100
40	Number of files subject to license management	10	10	10
41	Number of files whose deletion is to be managed in the software inventory dictionary	10	10	10
42	Number of clients that are to acquire Microsoft Office products	10,000	3,000	500
43	Number of Microsoft Office products to be managed	5	5	5
44	Number of clients that are to acquire anti-virus products	10,000	3,000	500
45	Number of anti-virus products to be managed	5	5	5
46	Number of destination automatic maintenance policies	2	2	2
47	Number of ID group automatic maintenance policies	2	2	2
48	Number of system configuration information deletion logs	100	30	5
49	Number of non-Software Distribution hosts	100	30	5
50	Number of host search conditions that are set	5	5	5
51	Number of communities specified in the host search settings	5	5	5
52	Number of hosts found by host search	10,000	3,000	500
53	Number of Report message jobs defined	10	10	10
54	Number of software operation monitoring policies	1	0	0
55	Number of programs to be monitored	10	0	0
56	Number of programs whose operation time is to be acquired	10	0	0
57	Number of permission information items for software operation monitoring	10	0	0
58	Number of startup suppression information items in the software operation monitoring result	10	0	0
59	Number of Set the software monitoring policy jobs	2	0	0
60	Number of filtering conditions set by operation monitoring policy	10	0	0
61	Number of clients subject to software operation monitoring	10,000	0	0
62	Amount of operation information that is to be acquired per day per client	1,500	0	0
63	Number of days operation information is to be retained	5	0	0
64	Number of patch information items	789	789	789
65	Number of patches that have been downloaded	100	100	100
66	Number of installation scripts	10	10	10
67	Number of clients belonging to host groups	10,000	3,000	500
68	Number of clients belonging to ID groups	10,000	3,000	500
69	Number of clients with startup suppress history	10,000	3,000	500
70	Maximum number of operating information items (suppress and operation histories) per client	500,000	0	0