Task 3: planning users and security, Guidelines for assigning security settings – HP Integrity NonStop H-Series User Manual
Page 44

Task 3: Planning Users and Security
Setting security for different users (planners, database administrators, and operators) determines
what tasks they have permission to perform:
•
Planners have permission to plan, build, and apply software configurations. For more
information, see
•
Operators have permission to initiate tasks on an assigned target system, usually as directed
by a planner. For more information, see
•
Database administrators have permission to:
—
Maintain the software database
—
Manage security of the installation files and files on target systems
—
Establish user access permissions for target systems
—
Often installs or updates the configuration of DSM/SCM on all systems
For more information, see
“Database Administrator Tasks” (page 46)
Training Site Personnel
If DSM/SCM users at your site have not previously used the HP NonStop SQL/MP or HP NonStop
Transaction Management Facility (TMF) products, they will need training in those areas. For
information about courses that HP offers, contact your HP representative.
Guidelines for Assigning Security Settings
The number of people assuming the roles of planner, operator, and database administrator depends
on the particular site. At least one planner is required. At a smaller site, you can configure a single
user ID as the planner, database administrator, and operator. For a larger site, especially one
with several remote target systems, you might need one planner, one database administrator, and
a separate operator for each target system. Consider assigning a backup to fill these roles if the
regular personnel are unavailable.
summarizes the guidelines for assigning these roles as best suits your work
environment.
Table 3-1 Suggested Assignments for Different Work Environments
Role assignments
Work environment
1 planner/operator/database administrator
Single system
1 planner
Multiple networkconnected development and production
systems with a single host system
1 database administrator
1 operator for development systems, 1 operator for
production systems
Same as for a multiple system site with a single host, or:
Multiple networkconnected development and production
systems with multiple host systems
1 planner for each host system
1 database administrator for each host system
1 operator for development systems under each host system
1 operator for production systems under each host system
1 planner
Multiple systems that are not network connected with a
single host system
1 database administrator
1 operator for each site with systems that are not network
connected
or
1 operator for each system that is not network connected
* The suggestions in this table do not include backups for each role, which you should assign as needed.
44
Planning and Preparing the NonStop Software Management Environment