Job Management Partner 1/Software Distribution Client Description and User's Guide

[Contents][Glossary][Index][Back][Next]

4.4.2 ID group definition (client services)

To define an ID group:

  1. Divide distribution-destination systems into groups and assign an ID group to each group.
  2. Define the ID groups in the ID group definition file.
  3. Register the ID group definition file in relay systems.
Organization of this subsection
(1) Grouping distribution-destination systems
(2) Creating the ID group definition file
(3) ID group definition file registration
(4) Changing the ID group definition

(1) Grouping distribution-destination systems

Group distribution-destination systems according to tasks and types and set an ID group for each group. You can define multiple different ID groups for each machine. You can also define the same ID group to multiple different groups.

The following two types of groups are available for distribution-destination systems:

One-layer group
This group consists of the desired relay systems and/or distribution-destination systems in the same layer. You can define this group even if there is only one applicable machine.

Two-layer group
This group consists of a relay system and the relay systems or distribution-destination systems connected to the relay system in the first layer.

Figure 4-4 shows the types of groups for distribution-destination systems.

Figure 4-4 Types of groups for distribution-destination systems

[Figure]

(2) Creating the ID group definition file

To create an ID group from the distribution-destination system in the ID group definition file, define the ID group to which the local system belongs, and register the file to the desired relay system. This file cannot be used when defining to an ID group registered from the managing server.

(a) File name of the ID group definition file

When the distribution-destination system registers the ID group definition file to an upper-level relay system, the group consists of one layer if the registration destination relay system does not register to that ID group. The group consists of two layers if the registration destination relay system registers to that ID group.

Use the file names shown in Table 4-4 to create the ID group definition file.

Table 4-4 File names for ID group definition file creation

ID group definition registration method Type File name
When registering to another relay system Other than HP-UX /NETMRDS/rdsprm/DMWIDUPM
HP-UX /etc/opt/NETMDMW/rdsprm/DMWIDUPM
When registering to the local relay system# Other than HP-UX /NETMRDS/rdsprm/DMWIDLCM
HP-UX /etc/opt/NETMDMW/rdsprm/DMWIDLCM

#
In a relay system directly connected to the managing server, this file is always used because registration to the upper-level relay system is not possible.

If the ID group definition file shown in Table 4-4 has already been created when JP1/Software Distribution Client is started, the ID group is registered according to the contents of the file. Therefore, if an ID group definition file has been created at installation, the set contents will be valid until recreated. When the ID group is correctly registered, the extension of the ID group definition file is labeled .bak. If registration fails, it will be labeled .err.

(b) Creation format of the ID group definition file

Use a full screen editor to create the ID group definition file. The following shows the format of the ID group definition file.

[LOCAL-ID]
*ID-group-1
:
*ID-group-n

[LOCAL-ID]
Specifies the start of the ID group definition. Enter from the first column, and enclose in brackets [ ]. After [LOCAL-ID], do not specify blanks or tabs.

*ID-group ~ <alphanumerics>((1-8 characters))
Enter * in the first column, and after the *, specify the ID group that the local UNIX machine belongs to. You cannot enter anything between * and the ID group. Do not specify blank spaces or tabs after the ID group.
You can specify multiple ID groups.

Create ID group definition files according to the rules below.

(c) Example of creating the ID group definition file

An example of creating the ID group definition file is as follows:

Example of a one-layer group
Figure 4-5 shows an example of creating the ID group definition file (/NETMRDS/rdsprm/DMWIDUPM) in each distribution-destination system for a one-layer group.

Figure 4-5 Example of creating the ID group definition file (one-layer group)

[Figure]

Example of a two-layer group
Figure 4-6 shows an example of creating the ID group definition file in relay system WS111 for a two-layer group.

Figure 4-6 Example of creating the ID group definition file (two-layer group)

[Figure]

(3) ID group definition file registration

There are two ways to register the ID group definition file to the relay system.

If the ID group definition file cannot be registered due to a transmission error, or other problems, the ID group definition file is stored as is. Correct the cause of the error, and then try again.

If registration cannot be performed due to a syntax error of the ID group definition file, the file name is changed to a name with the extension .err. Correct the definition of the ID group definition file, and then execute again.

You can reference the contents of the registered file by executing the following command.

(4) Changing the ID group definition

(a) For an ID group registered by the distribution-destination

To change the definition of an ID group, recreate the ID group definition file.

The name of the ID group definition file registered to the relay system is changed to a file name ending with .bak. Add or delete the ID group based on this file, and re-execute the process indicated in (2) and (3) in this section.

When the ID group definition file is re-registered, .bak is added to the end of the file name, and the existing ID group definition file becomes invalid. Therefore, when re-creating the file, enter all the ID groups to be defined, as well as the ID group to be added.

Even if the definition change fails due to system errors or for other problems, the ID group definition file name will change to the .bak extension. # is added to the beginning of the ID groups that are not changed.

To delete all ID group definitions where the local system belongs to, execute the rdsiddefine -dl command. If the ID group definition registered by the managing server is deleted, the host name of the deleted client is automatically reported to the managing server. When the definition of an ID group registered from a client is changed, however, the change is not reported to the managing server.

(b) ID groups registered by the managing server

An ID group registered by the managing server can be changed by a relay system and a client workstation. To change an ID group, use the rdsiddefine -s command. To add a definition, execute the rdsiddefine -s command with the -d option (ID-group-name) and -k option (password) specified.

If the definition is successfully added, it will be reflected automatically to the next file. If the definition fails, it will not be added.

For systems other than HP-UX
/NETMRDS/rdsprm/DMWIDUPM.bak
/NETMRDS/rdsprm/DMWIDLCM.bak

For HP-UX
/etc/opt/NETMDMW/rdsprm/DMWIDUPM.bak
/etc/opt/NETMDMW/rdsprm/DMWIDLCM.bak

To delete a definition, delete the ID group and register the ID group definition file.

When an ID group is modified, its content is reported to the managing server. Note that the content is reported only when the managing server is the Windows version of JP1/Software Distribution Manager.

If clients are already defined in an ID group for which overwrite registration is being requested by the managing server, the ID group is first overwritten and then automatically reported to the managing server by JP1/Software Distribution Client.

When modifying the definitions of an ID group registered from the managing server, you may need the password. When the definitions of an ID group registered from a client are modified, the modification is not reported.

[Contents][Back][Next]

[Trademarks]

All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.