Oracle Calendar Server Administrator's Guide Release 5.5 Part Number B10093-01 |
|
| View PDF |
This chapter describes the various tasks involved in creating and managing organizational resources, event calendars and holidays. Event calendars are similar to user accounts, but represent schedules such as sports matches, concerts, or other events that may be of interest to your user base. The administrative controls and functionality of resource management are also similar to those of user management, although with some important differences in an LDAP context.
The following topics are dealt with in this chapter:
The first step in holiday management is to assign the appropriate administration rights to a user. The SYSOP, by default, does not have holiday management rights.
You can add holidays to a node using the Calendar Administrator as long as any user on the selected node has the right to administer holidays. For full information on the Calendar Administrator, see Appendix F, "The Calendar Administrator".
Use the uniadmrights
utility to assign holiday administration rights. For full information on use and syntax, see the calendar server Reference Manual, Appendix C, "Utilities."
For example:
% uniadmrights -e "S=Sitchin/G=Zechariah" -add -hday -n 165
Once you have assigned holiday administration rights to a user, use a desktop client to sign in as that user, and select Directory | Manage Holidays...
An event calendar is an administrative user account which exists for the purpose of informing your user base about upcoming happenings that may be of interest to them. Essentially, an event calendar is simply a user account that has the PUBLISHEDTYPE
key set to EVENTCALENDAR
. Other users have read-only access to the events you create in your event calendars. Web calendar users, however, may copy events and appointments from the event calendar into their own calendars. Only administrators may create event calendars, and only administrators may modify events in an event calendar.
Use the Calendar Administrator to create event calendars easily. For full information on the Calendar Administrator, see Appendix F, "The Calendar Administrator".
Use the uniuser
utility introduced in Chapter 7, "Users and Groups", to create event calendars. Remember to set the value of the PUBLISHEDTYPE
key to EVENTCALENDAR
to make the user account an event calendar.
For example:
% uniuser -add "S=Season/G=Hockey/PUBLISHEDTYPE=EVENTCALENDAR" -n 156
Set the GLOBALREADACCESS
key to TRUE
if you want any Internet user to have the ability to view this event calendar, just as you would with a user account. For full information on the use and syntax of uniuser
, see the calendar server Reference Manual, Appendix C, "Utilities."
Use the Calendar Administrator to manage, populate and delete event calendars easily. For full information on the Calendar Administrator, see Appendix F, "The Calendar Administrator".
Use the uniuser
utility introduced in Chapter 7, "Users and Groups", to modify and delete event calendars. For full information on the use and syntax of uniuser
, see the calendar server Reference Manual, Appendix C, "Utilities."
To add new events to an event calendar, you may also sign in as that event calendar using your calendar client of choice and add the desired events or appointments. Remember to grant other users the right to view the events you create if you choose this method of managing events in your event calendars. Do this either by setting each event's access level to "Public" when you create it, or by setting the event calendar's default access right profile to allow all users to view "Normal" events.
A resource is an inanimate object, such as a conference room or a piece of equipment, that has its own account on the calendar server. When creating an event in their agenda, users can invite resources in the same way that they invite other users. Resources are managed by local users who act as designates. Resources can either be set up to permit more than one reservation at a time, or on a first come first served basis to prevent double-bookings.
Resources can also be used to create calendars for tracking related enterprise-wide information, such as company holidays or employees' travel schedules. For example, to create a Travel Planner for an organization, add a resource to the node and name it "Travel Planner". Whenever an employee is scheduled to travel, he/she will create an event in his/her personal agenda and invite the resource. The result is a calendar for the resource Travel Planner containing all entries related to employees' travel.
You can add resources to a node using the Calendar Administrator. For full information on the Calendar Administrator, see Appendix F, "The Calendar Administrator".
Use unires -add
to add a single resource. For full information on use and syntax, see the calendar server Reference Manual, Appendix C, "Utilities."
% unires -add "R=conference room/N=4" -n 786 -p <SYSOP password> unires: added "conference room"
unires
documentation in the calendar server Reference Manual, Appendix C, "Utilities."
A R=conference room/N=104/CA=24/S=Alexander/G=James A R=projector/N=2/S=Addison/G=Thomas/PHONE=123-4567
% unires -ex res1 -n 444 Enter SysOp password: unires: added "conference room" unires: added "projector" unires: added "lab"
You may specify a Resource Relative DN for your installation. If you do, all resources will be stored by default in that location in the LDAP tree. Alternatively, you may specify a full DN for resources as you create them.
While users are typically in the directory server before they are added to a calendar server node, resources are added directly to the calendar server and directory server in a single operation.
You can add resources to a calendar server node easily using the Calendar Administrator. For full information on the Calendar Administrator, see Appendix F, "The Calendar Administrator".
Use unires -add
to add a single resource. For full information on use and syntax, see the calendar server Reference Manual, Appendix C, "Utilities." This example specifies a full DN for the new resource.
% unires -add "DID=cn=Room614,o=Acme,c=US" -n 134 Enter SysOp password: unires: added "cn=Room614,o=Acme,c=US"
This example specifies only a resource name, leaving the resource's location in the LDAP directory to be determined by the Resource Relative DN and the calendar server base DN.
% unires -add "R=Room614" -n 134 Enter SysOp password: unires: added "R=Room614"
unires
documentation in the calendar server Reference Manual, Appendix C, "Utilities." This example specifies full DNs for the new resources.
A DID=cn=Room24, o=Acme, c=US A DID=cn=projector3, o=Acme, c=US A DID=cn=lab5, o=Acme, c=US
% unires -ex res1 -n 444 Enter SysOp password: unires: added "cn=Room24, o=Acme, c=US" unires: added "cn=projector3, o=Acme, c=US" unires: added "cn=lab5, o=Acme, c=US"
The resource now exists in the directory server and on the calendar server node.
You can manage resources easily using the Calendar Administrator. For full information on the Calendar Administrator, see Appendix F, "The Calendar Administrator".
View and modify resource attributes using the unires
utility. For full information on use and syntax, see the calendar server Reference Manual, Appendix C, "Utilities."
When a resource is deleted from a node, the resource's records and directory entry are removed from the local node. This means that the resource will no longer appear as invited in user's agendas, nor will it appear in any directory listings. If required, the resource's agenda can be copied out using the unicpoutr
utility, and subsequently copied back in to any calendar server node using the unicpinr
utility. For full information on use and syntax, see the calendar server Reference Manual, Appendix C, "Utilities."
You can delete resources easily using the Calendar Administrator. For full information on the Calendar Administrator, see Appendix F, "The Calendar Administrator".
Remove the resource(s) from the calendar server node using the unires -del
(single deletion) or unires -ex
(multiple deletions) commands. For full information on use and syntax, see the calendar server Reference Manual, Appendix C, "Utilities."
You may wish to define a default resource profile to apply as you add resources to the database. This profile can also be applied to existing resources.
/users/unison/misc/resource.ini
file. Edit this file using a text editor supplied with your operating system./users/unison/misc/resource.ini
file.unires
utility or the Admin GUI).[GEN]
in the /users/unison/misc/resource.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 resource creation or modification using the unires
command. For full information on use and syntax, see the calendar server Reference Manual, Appendix C, "Utilities."unires -ex
command. For full information on use and syntax, see the calendar server Reference Manual, Appendix C, "Utilities."Designate and other access rights are set according to the default resource profile at the time the resource is added to the node. They can also be set later by using a calendar client to log in as the resource and modify its access rights.