1 Introduction to Managing Oracle Collaboration Suite 10g Release 1

1.3.2.1 Specifying Access Rights for the LDAP User

When you are creating an Identity Management service (or an LDAP service test) in Grid Control, you are prompted to specify a value for the LDAP User Name property in the Internet Directory Test Properties section of the Create Identity Management Service General page.

If the user name specified for the LDAP User Name property has the access rights for the Collaboration Suite components and target types specified in Table 1-1, then when that user creates an Oracle Collaboration Suite component service (such as a Calendar service or other component service), the appropriate information required to create the component service will be automatically discovered from Oracle Internet Directory and displayed on the pages used to create the component service. If the user does not have the access rights documented in the table, then the user will need to specify the correct information on the pages used to create the component service.

When you are specifying an LDAP user during the creation of an LDAP service test, you should consider whether that user will also be creating an Oracle Collaboration Suite component service at some point in the future and whether it would be beneficial for that user to have the access rights in Table 1-1.

1.3.2.2 Steps for Creating an Identity Management Service

To create an Identity Management service, follow these steps:

1. On the Targets tab in Grid Control, click Services.

2. On the Services page, choose Identity Management Service in the Add box and click Go.

3. On the Create Identity Management Service General page, you:

   • Specify the time zone that you want Grid Control to use when displaying monitoring data for the Identity Management service.

   • Identity the targets related to the Identity Management service that you are creating.

   • Specify the beacons that you would like to monitor the Identity Management service, and specify a key beacon.

   • Specify values for the Internet Directory and Single Sign-On test properties. The beacons use these properties to run the performance and availability tests for the Identity Management service.

     
     

     Note: You will be asked to specify a value for the LDAP User Name property for the Internet Directory test. If the user name specified for the LDAP User Name property has the access rights specified in Table 1-1, "Access Rights for the LDAP User", then when that user creates an Oracle Collaboration Suite component service (such as Calendar), the appropriate information required to create the component service will be automatically discovered from Oracle Internet Directory and displayed on the pages used to create the component service. If the user name specified for the LDAP User Name does not have the access rights specified in Table 1-1, then that user will need to specify the correct information on the pages used to create the component service.

     
     

   • Specify the databases that are critical for the Identity Management service. The databases you specify will be used in root cause analysis for the Identity Management service.

   • Specify the application servers that are critical for the Identity Management service. The application servers you specify will be used in root cause analysis for the Identity Management service.

   Click Help on the Create Identity Management Service General page to learn more about the information to provide on the page.

4. On the Create Identity Management Service Beacons page, the beacons you specified on the General page for monitoring the Internet Directory and Single Sign-On service are displayed. You have the option of making changes to these beacons on this page.

5. On the Create Identity Management Service Database Association page, the databases you specified on the General page are displayed. You have the option of making changes to these databases on this page.

6. On the Create Identity Management Service Names page, you can view and modify the names of the service and system components that will be created for the Identity Management service. These names cannot be modified after the Identity Management Service is created.

7. Click Finish after you have specified the correct values on the Create Identity Management Service pages for the Identity Management service you are creating.

8. Grid Control displays the Identity Management service and subcomponent services on the Services tab. Grid Control also creates the Identity Management system, which appears on the Systems tab.

1.3.3.1 Access Rights for Collaboration Suite Services and Component Services

To create, edit, and delete Oracle Collaboration Suite services, component services, subcomponent services, and aggregate services, you must have the specific Oracle Enterprise Manager access rights documented in Table 1-2.

1.3.3.2 Steps for Creating a Collaboration Suite Service

To create an Oracle Collaboration Suite service, follow these steps:

1. On the Targets tab in Grid Control, click Collaboration Suites.

2. On the Collaboration Suites tab, click Add. See "Enabling the Collaboration Suites Tab" if the Collaboration Suites tab does not exist.

3. On the Add Collaboration Suite Service page, you:

   • Specify a service name for the service and a system name for the system associated with the service. You also specify the time zone that you want Grid Control to use when displaying monitoring data for the Collaboration Suite service.

   • Specify the Identity Management service that is associated with this Collaboration Suite service. See "Creating an Identity Management Service" if no Identity Management services exist.

   • In the Components table, click Add for a component service to create the component service as part of the Collaboration Suite service.

   • Specify whether the dashboard for the Collaboration Suite service you are creating will be available to any user who knows the dashboard URL.

4. When you choose a component service to add in the Components table on the Add Collaboration Suite Service page, the General page (and associated pages) used to create that component service are displayed. To create the service, click Continue after specifying the correct information on the pages used to define the component service. Click Help on any page for more information about that page.

5. After you create a component service, Grid Control displays the Add Collaboration Suite Service page again. You can either continue to create component services one at a time by repeating the previous step, or you can finish creating the Collaboration Suite service after you create a component service.

6. Click OK to create the Collaboration Suite service.

7. Grid Control displays the Collaboration Suite service on the Collaboration Suites tab.

Note that the systems and redundancy groups associated with a Collaboration Suite component are created when the component service is created.

1.3.3.3 Installing Oracle Collaboration Suite Metric and Policy Helpsets

In Grid Control, more than 90 metric helpsets for Oracle Collaboration Suite target types plus the Oracle Calendar policies helpset are not installed by default. Therefore, by default, online help is unavailable for the metrics for the Oracle Collaboration Suite target types that are supported in Grid Control and for Oracle Calendar policies.

A script is available that will include the Oracle Collaboration Suite metric helpsets and the Oracle Calendar policies helpset in the Grid Control online help system.

To run the script, follow these steps:

1. Make sure that the ORACLE_HOME variable is set to the directory where the Oracle Management Service for Grid Control is installed.

2. Change your default directory to the bin subdirectory of the Oracle home for the Oracle Management Service. Then stop the Oracle Management Service. For example:

   $ cd $ORACLE_HOME/bin
   $ ./emctl stop oms
   
   

3. Run the ocs_helpset.pl script, which is in the sysman/bin subdirectory of the Oracle home for the Oracle Management Service. This script copies the Oracle Collaboration Suite helpsets to the correct directories, so that these helpsets will be included in the Grid Control online help after the Oracle Management Service is restarted:

   $ cd $ORACLE_HOME/sysman/bin
   $ $ORACLE_HOME/perl/bin/perl ocs_helpset.pl
   
   

4. Restart the Oracle Management Service. For example:

   $ cd $ORACLE_HOME/bin
   $ ./emctl start oms
   
   

5. After the Oracle Management Service is started, when the first help topic is requested in Grid Control, it takes longer for that topic to be displayed than when only the default helpsets are included in the online help system. This extra time is due to the additional helpsets that are being loaded. The topic should display in less than 2 minutes. Then, for all subsequent help requests, topics display in 2 seconds or less.

Note that after the Oracle Collaboration Suite metric and policy helpsets are included in the online help system, each time the Oracle Management Service is started, it will take a similar length of time (usually under two minutes) for the first help topic to display. Then for all subsequent help requests, topics display in 2 seconds or less.

1.3.3.4 Steps to Perform Before Creating a Mail Service

Before you create a Mail service, create a Collaboration Suite Database target for each mail store created for Oracle Mail. Create these targets on each mail store that you want to monitor.

To create a Collaboration Suite Database target:

1. In Grid Control, navigate to the Agent home page for the Oracle Management Agent that was installed on the mail store host. Use these steps to navigate to the appropriate Agent home page:

   1. Click Setup at the top of any Grid Control page.

   2. Click Agents in the Overview of Setup page subtab.

   3. In the Agents table on the Agents page, click the link for the Management Agent for the mail store host.

2. In the Monitored Targets section of the Agent home page, select Collaboration Suite Database from the Add drop-down menu, then click Go.

   Grid Control displays the property page for the Collaboration Suite Database target type. Provide the required information, as described in Table 1-3.

3. Click OK to create the target.

1.3.3.5 Steps to Perform Before Creating an Ultra Search Service

Before you create an Ultra Search service, create an Ultra Search target for each Oracle Ultra Search instance.

To create an Oracle Ultra Search target:

1. In Grid Control, navigate to the home page for the Management Agent that was installed on the Oracle Ultra Search Repository Database host. Use these steps to navigate to the appropriate Agent home page:

   1. Click Setup at the top of any Grid Control page.

   2. Click Agents in the Overview of Setup page subtab.

   3. In the Agents table on the Agents page, click the link for the Management Agent for the Ultra Search Repository Database host.

2. In the Monitored Targets section of the page, select Ultra Search from the Add drop-down menu, then click Go.

   Grid Control displays the property page for the selected target type.

3. Provide the required information, as described in Table 1-4.

4. Click OK to create the target.

   
   

   See Also: "Adding Targets to be Monitored and Administered by Enterprise Manager" in the Grid Control online help.

   
   

1.3.3.6 Steps to Perform Before Creating a Mobile Collaboration Service

When the Mobile Collaboration service is created, Web applications associated with the service are also created. To ensure that these Web applications work properly, perform these steps before creating the Mobile Collaboration service:

1. On the Collaboration Suite Welcome page, click Oracle Mobile Preferences and specify the credentials the test uses to query the Mobile Collaboration middle tier.

2. On the Collaboration Suite Mobile Preferences page, create a test user mobile access account using the Mobile Access Account ID, Mobile Access PIN, and Confirm your Mobile Access PIN fields.

3. Click OK.

4. In the Administrator's Tools section of the Collaboration Suite Welcome page, click provisioning console.

5. On the Welcome to Self-Service Console page, click Login and log into the test user account. Click on My Profile.

6. On the View My Profile page, click Edit My Profile.

7. In Additional Personal Details section of the Edit My Profile page, make sure that the value selected in the Language field is English (United States).

8. Click Submit and OK.

9. Go to the following URL (replace <host> and <port> with the name of the host and the port where the Collaboration Suite middle tier is installed):

   http://<host>:<port>/ptg/rm

10. On the Login page, specify the test user mobile access account credentials using the Mobile Access Account ID and Mobile Access PIN that were created earlier. Click Submit.

11. Click Preferences.

12. On the User Preferences page, make sure that Show Images is set to Yes, then click Save and Logout.

1.3.3.7 Specifying the Oracle HTTP Server Port for the Mobile Collaboration Push Mail Service

When the Mobile Collaboration service is being created, the value specified for the Port field in the Push Mail Test Properties section of the Create Mobile Collaboration Service All Test Properties page should be the port for the Oracle HTTP Server for the Mobile Collaboration middle tier.

If the port for the Oracle HTTP Server for the Mobile Collaboration middle tier is not specified during creation of the Mobile Collaboration Service, you can specify the correct Oracle HTTP Server port after the Mobile Collaboration Service is created by following these steps:

1. In Grid Control, navigate to the Collaboration Suites tab.

2. On the Collaboration Suites Services page, select the Oracle Collaboration Suite service that contains the Mobile Collaboration service, then click Configure.

3. In the Components section on the Configure Collaboration Suite Service page, click Configure for the Mobile Collaboration service.

4. On the Configure Mobile Collaboration Service page, click Configure for the Mobile Collaboration Push Mail Service.

5. In the Port field on the Configure Mobile Collaboration Push Mail Service All Test Properties page, specify the port for the Oracle HTTP Server for the Mobile Collaboration middle tier.

6. Click Continue and Finish to update the port number.

1.3.3.8 Steps to Perform Before Creating a Voicemail & Fax Service

Before you can create a Voicemail & Fax component service in Grid Control, you need to create Voicemail & Fax system targets for Oracle Collaboration Suite 10g Release 1 (10.1) for Windows.

Before you install Oracle Voicemail & Fax for Oracle Collaboration Suite 10g Release 1 (10.1) for Windows, be sure that the latest Oracle Management Agent for Windows is installed and properly configured on the Windows machine.

For complete information about installing Oracle Voicemail & Fax for Oracle Collaboration Suite 10g Release 1, see Oracle Collaboration Suite Oracle Voicemail & Fax and Oracle Web Conferencing Conversion Servers Installation and Upgrade Guide for Microsoft Windows for Oracle Collaboration Suite 10g Release 1 at:

http://www.oracle.com/technology/documentation/collab10g.html

After installing Oracle Voicemail & Fax for Oracle Collaboration Suite 10g Release 1 (10.1) for Windows, use Grid Control to centrally administer your Voicemail & Fax installation.

Before you start using Oracle Voicemail & Fax, use Grid Control to set up your sites and groups and configure the PBX-Application Cluster.

For more information about getting started with Grid Control and configuring Oracle Voicemail & Fax for Oracle Collaboration Suite 10g Release 1, see Oracle Voicemail & Fax Administrator's Guide for Oracle Collaboration Suite 10g Release 1 at:

http://www.oracle.com/technology/documentation/collab10g.html

After following the instructions in Oracle Voicemail & Fax Administrator's Guide, you can create a Voicemail & Fax component service in Grid Control by following the steps in Steps for Creating a Collaboration Suite Service.

1.3.3.9 Disabling Auto Versioning for Content Services

To prevent the Content Services Send Web Application service from creating a new test file each time it runs and pushing the previous test file to the Trash folder, you should set the Content Services versioning model to disabled before you create the Content Services service.

To set the Content Services versioning model to disabled, follow these steps:

1. Log into Content Services as the Content Services test user you created for the Content Services service test.

2. In the right hand pane in Content Services, right-click the folder for the test user.

3. Choose Properties and then on the Versioning tab enable Modify Settings and set Versioning Model to Disable Versioning.

1.3.3.10 Specifying the Full Path Name to a Content Services Service Sample File

Before you create the Content Services service in Grid Control, you need to create a Content Services sample file.

During the creation of the Content Services service, the full pathname to the Content Services sample file should be specified in the Server-Side Filename field in the Basic Test Properties section on the Configure Content Services General page.

If the full pathname to the sample file is not specified in the Server-Side Filename field when the Content Services service is created, the full pathname to the sample file can be added after the Content Services service is created by following these steps:

1. In Grid Control, navigate to the Collaboration Suites tab.

2. On the Collaboration Suites Services page, select the Oracle Collaboration Suite service that contains the Content Services service, then click Configure.

3. In the Components section on the Configure Collaboration Suite Service page, click Configure for the Content Services service.

4. On the Configure Content Services Service page, click Configure for the Content Services User Access Service.

5. In the Basic Test Properties section on the Configure Content Services User Access Service General page, specify the full pathname to the sample file in the Server-Side Filename field.