2 Managing Oracle Collaboration Suite

2.2.2.1 Changing the Status of a Mail Listener on UNIX to Up

To change the status for Mail listeners on the UNIX operating system to Up in Grid Control, follow these steps:

1. Use the Net Merge utility to modify the listener.ora file to create one or more TCP addresses for the same listener without the presentation, that is, add the following to the end of the description list:

   (description=(address=(protocol=tcp)(port=<any_available_port_above_1024>)(host=127.0.0.1)))
   
   

   Note that the port can be any port above 1024 that is available on the system for the listener, such as 1522 or 1526, but it has to be different than the one with presentation. Make sure that the port you choose is not being used by any other listener running on the system, otherwise the tnslsnr command described later in this section will fail.

2. Restart the Mail listener by performing the following steps:

   1. Log in as root.

   2. Check if sendmail is running by using this command:

      ps -ef | grep sendmail
      
      

      If it is running, kill the process.

   3. Execute the following command, where userid is the UNIX account that owns the Oracle software:

      id userid
      
      

   4. After changing your default directory to the $ORACLE_HOME/bin directory, issue the following command, where listener_es is the name of the Mail listener:

      tnslsnr listener_es <uid_value> -group <gid_value>
      
      

      
      

      Note: The Mail listener cannot be started using lsnrctl from a user shell. Since it has to listen on ports below 1024, it has to be started by the superuser on UNIX operating systems. When restarting the Mail listener following the listener.ora change, you should use the same command, with the same command line arguments, as was used to start it up initially.

      
      

3. In Grid Control, navigate to the All Targets page and select the listener_es target that shows a status of Down.

4. Click Configure. On the Monitoring Configuration page, change the Machine name property to 127.0.0.1 and change the Port number property to the port number used in the new TCP address without presentation.

2.2.2.2 Changing the Status of the Mail Listener on Windows to Up

To change the status for Mail listeners on the Windows operating system to Up in Grid Control, follow these steps:

1. In Grid Control, navigate to the All Targets page and select the listener_es target that shows a status of Down.

2. Click Configure. On the Monitoring Configuration page, make sure that the Port number property is set to the port number corresponding to the port number used in the new TCP address without presentation (that is, the port number corresponding to the entry in listener.ora which has HOST=127.0.0.1).

2.2.3.1 Configuration Steps for Content Services Read and Send Web Application Services

For the Content Services Read Web Application and Content Services Send Web Application services to work, the Content Services Web UI must be enabled for the Content Services instance for which you created the Content Services service. Enable the Content Services Web UI to get these Content Services services to work. If you do not want to enable the Content Services Web UI, delete the Read and Send Web Application services. See "Editing and Deleting Collaboration Suite Services and Component Services" for information on deleting services.

2.2.3.2 Configuration Steps for a Content Services FTP Service

When a Content Services service is created, a Content Services FTP service is also created. For the Content Services FTP service to work, the FTP service must be enabled for the Content Services instance for which you created the Content Services service. Enable the FTP service for the Content Services instance to get the Content Services FTP service to work.

If you do not want to enable the FTP service for the Content Services instance, follow these steps, otherwise the status of the parent Oracle Collaboration Suite service will always be Down:

1. On the Collaboration Suites tab, select the Content Services FTP service, then click Configure.

2. On the Monitoring Configuration page, click Availability Definition.

3. On the Availability Definition page:

   1. Choose System in the Define availability based on: field.

   2. Select the At least one key component is up option.

   3. In the System table, enter a check mark in the Key Component column for every component in the table.

   4. Click OK.

For more information on enabling FTP access for a Content Services instance, see Oracle Content Services Administrator's Guide for Oracle Collaboration Suite 10g Release 1 at:

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

2.2.3.3 Configuration Steps for a Content Services Records Management Service

When a Content Services service is created, a Content Services Records Management Web Application service is also created. For the Content Services Records Management Web Application service to work, the Content Services Records Management UI must be enabled for the Content Services instance for which you created the Content Services service. Enable the Records Management UI to get the Content Services Records Management service to work.

If you do not want to enable the Records Management UI for the Content Services instance, follow these steps, otherwise the status of the parent Oracle Collaboration Suite service will always be Down:

1. On the Collaboration Suites tab, select the Content Services Records Management service, then click Configure.

2. On the Monitoring Configuration page, click Availability Definition.

3. On the Availability Definition page:

   1. Choose System in the Define availability based on: field.

   2. Select the At least one key component is up option.

   3. In the System table, enter a check mark in the Key Component column for every component in the table.

   4. Click OK.

2.2.3.4 Deleting Test Files for the Content Services Test User

In the Content Services application, you should regularly delete the test files created bythe Content Services FTP service in the Trash folder for the Content Services test user. Otherwise, the value of the Number of Documents metric (which is collected by Grid Control) will increase over time, because the metric includes all documents for the test user (including those in a user's Trash folder).

2.2.4.1 Updating the Voicemail & Fax Service when the SMDI Status is Changed

When you create a Voicemail & Fax service, you need to enter the SMDI status (enabled or disabled) of the Voicemail & Fax instance on the Create Voicemail & Fax General page. The SMDI status information is used to compute the status of the Voicemail & Fax services.

If the SMDI status of a Voicemail & Fax instance is changed after the Voicemail & Fax service for that instance has been created, then the SMDI status of the Voicemail & Fax service has to be updated to match the SMDI status of the instance.

For example, when the Voicemail & Fax service for a Voicemail & Fax instance was created, the SMDI status of the instance may have been disabled. In this case, the person creating the Voicemail & Fax service would have specified that SMDI was disabled for the service. Later, if SMDI is enabled for the instance, then the SMDI status needs to be changed to enabled on the Edit Voicemail & Fax General page for the Voicemail & Fax service.

2.2.4.2 Process Control for Voicemail & Fax Systems and PBX-Application Clusters

If you attempt to stop, start, restart, or reload an Oracle Voicemail & Fax system or PBX-Application Cluster on a Voicemail & Fax Group Home page or a PBX-Application Cluster Home page, you receive this error message:

The version of the Agent on the host: host-name does not support this operation.
Upgrade to a newer version of the Agent.

Upgrading to a newer version of the Agent will not fix this problem.

The way to work around this is to stop, start, restart, or reload each of the Voicemail & Fax middle tier and Agent-monitored targets individually.