| Oracle® Calendar Administrator's Guide Release 2 (9.0.4) Part Number B10892-02 |
|
|
View PDF |
| Oracle® Calendar Administrator's Guide Release 2 (9.0.4) Part Number B10892-02 |
|
|
View PDF |
This chapter describes the different tasks involved in managing users within a calendar server node. Whether user information is stored internally or in an LDAP directory, the administrative procedures required are similar.
Administrators of installations using LDAP directories must be familiar with user creation and management on their directory server, or should refer to the appropriate on-line help. In an external directory context, users are generally added to calendar server nodes from the directory server, but it is also possible to migrate existing information from a calendar node to a directory server.
The following topics are dealt with in this chapter:
Each person who plans to use calendar services must have a profile on the calendar server. Once a user's profile has been created and added to a node, that person can then use any calendar client to connect to the server and manage his/her personal agenda.
Before you can give a calendar account to users, they must already exist in the directory server. Adding calendar services implies using the existing directory data to create calendar profiles on the calendar server node.
Creating calendar accounts for existing directory users can be done through the Calendar Administrator. Sign in to the node on which you want to create the account, click Users in the main screen, and click Provision Calendar Service to User on the Users page. The Directory Users page will appear where you can list users in the directory who do not have a calendar account. Search for the user or users to whom you wish to provision calendar services. You can click Go to list all users or select a filter and enter a value in the Search edit box to limit the search. When the user is listed, click the "Provision Calendar Service" icon in the Actions column for that user. To provision services for more than one user at a time, select them in the Select column and then click the Provision Calendar Service to User button at the upper right of the list.
Adding calendar users from an existing directory server using the utilities is a two-step process. The first step is to identify all directory server users who are not calendar users. The unidssearch utility will search the directory server DNs and return all entries without the attribute ctCalXItemId. These users can then be added to a calendar server node using the uniuser utility. For full information on use and syntax, see Appendix E, "Utilities" in the Oracle Calendar Reference Manual.
Use unidssearch to search the directory server. For full information on use and syntax, see Appendix E, "Utilities" in the Oracle Calendar Reference Manual.
% unidssearch -c 10 A DID=cn=Lan Nguyen, ou=Research, o=Acme, c=US A DID=cn=James Alexander, ou=Research, o=Acme, c=US A DID=cn=Chris Robbins, ou=Research, o=Acme, c=US A DID=cn=Thomas Addison, ou=Administration, o=Acme, c=US A DID=cn=Claire Roslyn, ou=Administration, o=Acme, c=US A DID=cn=Denis Tremblay, ou=Administration, o=Acme, c=US A DID=cn=Maija Laine, ou=Finance, o=Acme, c=US A DID=cn=Elizabeth McKinley, ou=Finance, o=Acme, c=US A DID=cn=Walter Chen, ou=Finance, o=Acme, c=US A DID=cn=Oliver Maxwell, ou=Finance, o=Acme, c=US
Use uniuser -add -user. For full information on use and syntax, see Appendix E, "Utilities" in the Oracle Calendar Reference Manual.
% uniuser -user -add "DID=cn=James Alexander, ou=Research, o=Acme, c=US" -n 134 Enter SysOp password: uniuser: added: "cn=James Alexander, ou=Research, o=Acme, c=US"
unidssearch to a file named userslist.
% unidssearch -c 5 > userslist
uniuser documentation in Appendix E, "Utilities" in the Oracle Calendar Reference Manual.
A DID=cn=Chris Robbins, ou=Research, o=Acme, c=US/G=Chris A DID=cn=Thomas Addison, ou=Administration, o=Acme, c=US/G=Thomas A DID=cn=Claire Roslyn, ou=Administration, o=Acme, c=US/G=Claire A DID=cn=Denis Tremblay, ou=Administration, o=Acme, c=US/G=Denis A DID=cn=Maija Laine, ou=Finance, o=Acme, c=US/G=Maija
% uniuser -ex userslist -n 134 Enter SysOp password: uniuser: added "cn=Chris Robbins, ou=Research, o=Acme, c=US/G=Chris". uniuser: added "cn=Thomas Addison, ou=Administration, o=Acme, c=US/G=Thomas". uniuser: added "cn=Claire Roslyn, ou=Administration, o=Acme, c=US/G=Claire". uniuser: added "cn=Denis Tremblay, ou=Administration, o=Acme, c=US/G=Denis". uniuser: added "cn=Maija Laine, ou=Finance, o=Acme, c=US/G=Maija".
In a standalone installation of the calendar server, where no LDAP directory server is used, user profiles are added to the internal calendar directory. A user password must be supplied.
Use the Calendar Administrator to add users to a node. Click the Calendar Management tab and then on Users. To add a new user click Create Calendar Account on the far right. Enter the user information and click Apply.
Use the uniuser utility with the -add and -user options to add users to the calendar server's internal directory. For full information on use and syntax, see Appendix E, "Utilities" in the Oracle Calendar Reference Manual.
uniuser -user -add "S=Addison/G=Thomas/PSW=test1/I=W/O=acme" -n 786 -p syspsw uniuser: added "Addison,Thomas,W"
Instead of adding users from the directory server to the calendar server, the administrator may wish to take one or more existing calendar databases and export the user and resource data in an LDIF format that is then used to populate the directory server.
Contact Oracle support for assistance and utilities to handle the migration of all calendar users to the directory server.
Administrators can modify user attributes using the uniuser utility or using the Calendar Administrator. Attributes include user information such as the user name, e-mail address, telephone number, and other personal information. It also includes access rights (designate, viewing rights, etc.), administrative rights (manage holidays, users, server, etc.) and alert attributes (notifications).
A user's calendar account can be disabled. When an account is disabled, the owner cannot sign-in and does not have access to his agenda. The calendar data of disabled accounts is not deleted and will be accessible again once the user account is re-enabled.
Use the Calendar Administrator to view and modify a user's calendar attributes. To modify an existing user, click the Calendar Management tab and then on Users. Search for the user you want to modify using the search box. Click Go to list all users or select a filter and enter a value in the Search edit box to limit the search then click Go. Find the user in the list and click the pencil icon in the Actions column. To modify attributes that are not calendar-specific, use your Oracle Internet Directory administration tools or third-party directory servers.
You may view and modify a user's calendar attributes using the uniuser utility with the -mod option or -s option. To modify attributes that are not calendar-specific, use your Oracle Internet Directory administration tools.
To disable a calendar account, use uniuser with the -mod option. Example:
% uniuser -mod -user "S=Smith/G=John" -m "ENABLE=FALSE" -n 23
To grant access rights from one user to another use the uniaccessrights utility. See Granting access rights later in this chapter. To change a user password, the unipasswd utility can be used. User passwords can also be modified using the Oracle Internet Directory administration tools.
For full information on the use and syntax of uniuser and uniaccessrights, see Appendix E, "Utilities" in the Oracle Calendar Reference Manual.
When a user is deleted from a node, the user's directory entry and records are removed from the local node. This means that all data owned by the user, including any meetings or groups, will be deleted. The user will no longer appear in others' agendas, nor will any meetings and other calendar entries owned by this user remain. Any remote directory listings and remote copies of calendar data owned by the user will also be removed.
To preserve meetings or other calendar entries owned by the user, you should transfer ownership of these meetings to another user before the deletion.
Use the Calendar Administrator to transfer calendar data from one user to another and then to delete the user from the server. Click the Calendar Management tab and then on Users. Search for the user you want to delete using the search box. Click Go to list all users, or select a filter and enter a value in the Search edit box to limit the search then click Go.
To transfer data from this user to another, first click the pencil icon in the Actions column for this user. Click Transfer Calendar at the bottom of the menu on the left. In the "Recipient for Calendar" page, click Go to list all users, or select a filter and enter a value in the Search edit box to limit the search then click Go. Find the target user, and click on the Transfer icon in the Actions column for that user. From the "Calendar Data to Transfer" page, select the types of calendar entries you want to transfer and click Apply.
Once the data has been transferred you can proceed with the deletion. Click the Users tab on the top left. To find the user to delete, use the Search filter and edit box. To delete one user or more, select the users by clicking on the corresponding checkbox in the Select column and then click Delete at the top right.
Remove one or more users from the calendar server node using the uniuser -del -user (single deletion) or uniuser -ex (multiple deletions) commands. For full information on use and syntax, see Appendix E, "Utilities" in the Oracle Calendar Reference Manual.
If the user is the owner of calendar entries (meetings, day events, etc) that you do not wish to delete, you might transfer these entries to another user before deleting the user. Use uniuser with the -transfer option to transfer ownership of selected entries in the user's agenda to another user.
For example, if a manager who controlled group scheduling leaves the company, you might transfer all non-personal entries from his agenda to the person replacing him. Use the -event, -task, -group and -folder options of uniuser to define which type of calendar data to transfer.
To preserve a copy of the user's complete agenda in a file prior to deletion from the node, use the unicpoutu utility. Use the unicpinu utility to copy this information back into a calendar server node.
Due to a variety of potential circumstances -- organizational changes, employee relocation, or the need to redistribute node capacity -- you may need to move one or more users from one node to another.
Use the unimvuser utility. It is advisable to run unimvuser during off-peak hours for the calendar server. Always use the most recent version of unimvuser in your node network. For full information on use and syntax, including a number of crucial warnings and considerations, see Appendix E, "Utilities" in the Oracle Calendar Reference Manual.
To set client display preferences, administrative rights, default viewing privileges or other parameters for a group of users, define a default user profile before adding users to the node. This default user profile may also be applied to existing users.
$ORACLE_HOME/ocal/misc/user.ini file. Edit this file using a text editor supplied with your operating system.$ORACLE_HOME/ocal/misc/user.ini file.uniuser utility, or the Calendar Administrator).[GEN] in the $ORACLE_HOME/ocal/misc/user.ini file. Multiple profiles can be created from this template and appended to the file under different section heading names. These profiles can then be specified during user creation or modification using the uniuser utility with the -s option. For full information on use and syntax, see Appendix E, "Utilities" in the Oracle Calendar Reference Manual.The e-mail addresses allow users to notify each other of created, modified or deleted calendar entries and are used for sending e-mail reminders.
When you add users with uniuser, you may specify their e-mail addresses by using the EMAIL key/value pair. For example:
% uniuser -add "S=Kafka/G=Franz/EMAIL=fkafka@mail.org" -n 23 Enter SysOp password: uniuser: added "Kafka, Franz"
For full information on the use and syntax of uniuser, see Appendix E, "Utilities" in the Oracle Calendar Reference Manual.
An administrator can grant a user the right to access the agenda of another user, resource, or event calendar. These rights include event viewing rights, task viewing rights, scheduling rights and designate rights. A designate is a user assigned the right to modify the agenda of another user or resource. Granting scheduling rights to a user means giving him the right to invite you.
You can set access rights using the Calendar Administrator or the uniaccessrights utility.
Use the Calendar Administrator to grant access rights from one user (grantor) to another (grantee). Click the Calendar Management tab and then on Users at the top left. Search for the user who will be the grantor. Click Go to list all users, or select a filter and enter a value in the Search edit box to limit the search then click Go. Find the user in the list and click the pencil icon in the Actions column to open the profile for this calendar user. Click Access Rights on the left.
In the Access Rights page, any user to whom you already have granted rights can be displayed. Click Go to list them all. To grant rights to a user for the first time, click Grant Rights on the right. Search for the user who will be the grantee and click the Grant Rights icon in the Actions column to change the rights granted to this user. In the "Access Rights to Calendar" page, change the rights and click Apply.
Use the uniaccessrights utility with the -mod option to grant access rights from one user to another or from one user to many users. For example:
% uniaccessrights -mod -grantee "S=OBrian" -grantor "S=Martin/G=Don" -host gravel -p sysop1 -eventview "PERSONAL=ALL" -taskview "all=true"
For full information on the use and syntax of uniaccessrights, see Appendix E, "Utilities" in the Oracle Calendar Reference Manual.
Calendar users can share their agenda with other users through the Oracle Calendar Web client. Calendar sharing is determined using the Global Read Access attribute.
Users with the Global Read Access attribute turned ON can share their agendas with any other Internet user by mailing them a URL defined by the Web client. The default value for Global Read Access is OFF.
Set the Global Read Access attribute using the Calendar Administrator or the uniuser utility. For more information on this feature, see your Web client documentation and on-line help.
