This section contains conceptual information and instructions on administering calendar resources.
After your resources are added, you can administer them using Delegated Administrator or csresource.
This section contains the following topics:
This section contains instructions for retrieving resource LDAP information.
You can retrieve resource properties from the LDAP resource entry with one of three tools:
To Retrieve Resource Information Using Delegated Administrator Console
14.6.1.1 To Retrieve Resource Information Using Delegated Administrator Utility
In the Delegated Administrator Console, click the Calendar Resources tab.
Use the Search Results drop-down box to select one of the following options:
Search Calendar Resource by Resource ID
Search Calendar Resource by Calendar Resource Name
Type the value you want to search for.
Click Search.
Use the commadmin resource search command to retrieve LDAP information for a resource.
For example, to search for the resource CF101 in the sesta.com domain, use the following command:
commadmin resource search -D serviceadmin -w serviceadmin -n sesta.com \s -d sesta.com -u CF101
You can retrieve the LDAP entry information for a resource or for all resources using the csresource utility.
Change to the sbin directory.
Use the csresource list command to list one or all resources.
For example, list all the information about all the resources:
./csresource -v list
Or, list all the information about a specific resource, CF101:
./csresource
Change to the sbin directory.
Use the csresource enable command to enable one or more resources.
For example, to enable the ConfRm12 resource:
./csresource -v enable ConfRm12
Change to the sbin directory.
Use the csresource disable command to disable one or more resources. For example, to disable the ConfRm12 resource:
./csresource -v disable ConfRm12
Change to the sbin directory.
Use the csresource delete command to delete one or more resources. For example, to delete the ConfRm12 resource:
./csresource -v delete ConfRm12
This section contains directions for setting up a bitbucket channel for both Messaging Server and Sendmail. The bitbucket channel is a way to discard the email generated for resource calendars. These examples use a resource named Room100 on the sesta.com server. If you don’t set up the bitbucket channel (or equivalent), you will need to periodically delete the email messages sent to the resource calendar.
This section contains the following procedures:
Ensure the bitbucket channel is defined in the imta.cnf file.
To direct messages to the bitbucket channel, create the email address for the resource using the csattribute utility:
csattribute -a mail=Room100@bitbucket.sesta.com add Room100 |