2.3 Planning the domain content structure and management policy (system administrator)

JP1/DH - Server users must be assigned to JP1/DH - Server groups. Therefore, the system administrator first prepares groups to manage JP1/DH - Server users.

Procedure

Prepare information about the users who use JP1/DH - Server to deliver data.

This example assumes that the following users use JP1/DH - Server to deliver data.

Location	Department	User	User ID	Email address
Tokyo	-	Kobayashi Manabu^#	`kobayashi`	`akaadmin@XXX.co.jp`
Tokyo	Design	Suzuki Tomoko	`suzuki`	`suzuki@XXX.co.jp`
Tokyo	Design	Sato Daisuke	`sato`	`sato@XXX.co.jp`
Tokyo	Design	Tanaka Kenta	`tanaka`	`tanaka@XXX.co.jp`
Overseas	Manufacturing	Watanabe Makoto	`watanabe`	`watanabe@XXX.co.jp`
Overseas	Manufacturing	Mia Wilson	`wilson`	`wilson@XXX.co.jp`
Overseas	Manufacturing	Li Jing	`li`	`li@XXX.co.jp`

Legend -: Does not belong to a department defined in JP1/DH - Server.

#:: In addition to a user with Administrator authority, the system administrator must prepare a user and user ID with the authority of a representative user. In the example above, the user Kobayashi Manabu with the user ID kobayashi is created for this purpose.

Create email accounts so that the users whose information was prepared in step 1 can send and receive email.

Create accounts for these users on the mail server specified in the digikatsuwide.xml file. After the at mark (@) in the email address, specify a domain name that can be used in your environment. In this document, XXX.co.jp is used as an example domain name.
Design the layout on JP1/DH - Server for the users whose information was prepared in step 1.

In JP1/DH - Server, data is delivered between users under the same group called a domain. This example assumes the following group configuration:

In this example, the group Hitachi G is a domain.

As shown in this example, a domain is a group that is created to aggregate subgroups and users.

By defining the Design and Manufacturing groups under the domain Hitachi G, users who belong to these groups and users defined directly under Hitachi G are able to deliver data to each other.

Note that in this scenario, the user Suzuki Tomoko is created directly under Hitachi G domain despite being affiliated with the Design department. This allows her to manage all domain content under the Hitachi G domain.
Select a domain-content manager, and determine the password he or she will use to log in to JP1/DH - Server.

The groups such as Design and Manufacturing under a domain are collectively referred to as domain content.

The system administrator selects the user (domain-content manager) who will manage this domain content.

A domain-content manager is created by assigning the representative user authority to a user in JP1/DH - Server. When doing so, the system administrator also sets the initial password.

In the example above, Kobayashi Manabu (the system administrator) and Suzuki Tomoko are nominated as domain-content managers.

Tip

When there are several domain-content managers, you can set the same character string as their initial password. This allows the system administrator to send the same email to each domain-content manager when notifying them in step 6.
Design the operational policies to apply to all domain content.

Design the operational policies to be applied to the entire groups under the domain, including the groups Design and Manufacturing.
- Password entry rules
- Data delivery policies
Provide domain-content managers with the information they need.

Send an email to domain-content managers that contains the JP1/DH - Server URL, their user IDs and passwords, and information about their responsibilities.

The password contained in this email is the initial password. Ask the domain-content manager to change the password at the first login.

Postrequisites

Enter settings in JP1/DH - Server that implement the domain content structure and management policy that you designed in this procedure.

Related topics

To Page Top