To configure a platform, you must log in as a privileged user.
The table below summarizes the different possibilities:
Table 1-1 Access Permissions
User | Access Level | Configuration Required |
|---|
| root | Full access to whole platform, including HP OpenCall SS7. | none |
| ocadmin | Default privileged user for HP OpenCall SS7. | |
| other user | root can grant privileged
access to HP OpenCall SS7 to other members of the ocadmin group | Add default environment variables to
the user’s profile. Add default environment
variables to the user’s profile. “Authorizing
Access for Other Users”.
Configure the user’s .rhosts file. There are several references in the procedures
to creating or modifying the file ~ocadmin/.rhosts. For other users, the file ~<other_user_name>/.rhosts should be created or modified instead. Other users must
belong to the group ocadmin. |
The package installation creates:
the directory /home/ocadmin
These must not be
removed.
The appropriate environment variables are also added to both ocadmin and root profiles.
The HP OpenCall SS7 files and directories are handled when configuring the
platform. The root user must not create or modify
any files or directories belonging to the HP OpenCall SS7 file system
layout, except when using the supported command line tools.
 |
| |
|
 | NOTE: All files in the HP OpenCall SS7 configuration directories,
and the directories, must be owned by a member
of the group ocadmin. |
|
| |
|
Most platform commands can be used by the ocadmin user,
however, some require root access. Refer to the
Tools Catalog in Appendix A “Tools Catalog”
Authorizing
Access for Other Users |
|
If you want users other than root and ocadmin to
have access to the platform tools or man pages, you must add the
default environment variables to each user’s profile:
PATH=$PATH:/opt/OC/bin
MANPATH=$MANPATH:/opt/OC/share/man |
This is done automatically for the ocadmin and root users.
Any users that you want to access the platform, must be members
of the ocadmin group.
Printable version
