Managing Log Files in Collaboration Suite

How to handle the log files to free disk space?

Make sure you shut down both the infra-tier & mid-tier instances before proceeding ahead.

I. Infrastructure Tier

a) Clear the Oracle Internet Directory Logs from the following folders

$ORACLE_HOME/ldap/log

$ORACLE_HOME/ldap/odi/log

b) Clear Apache Logs from 

$ORACLE_HOME/Apache/Apache/logs

c) Clear OC4J_SECURITY logs from

$ORACLE_HOME/j2ee/OC4J_SECURITY/application-deployments/APPLICATIONS_FOLDER/OC4J_SECURITY_default_island_1/application.log 

II. Mid-Tier Instance

a) The Apache logs are at the similar location as in Infra Tier

b) The Webcache logs are generated under:

$ORACLE_HOME>/webcache/logs

c) The Mail application log files are generated under:

$ORACLE_HOME/oes/log/um_system/

You can delete all the folders under:

• $ORACLE_HOME/oes/log/um_system/admin/
• $ORACLE_HOME/oes/log/um_system/backup/
• .....
• $ORACLE_HOME/oes/log/um_system/smtp_in/

You must not delete the folders: admin, backup, ..., smtp_in...etc. Only the subfolders of these folders.

d) The Web Access Client (WAC) logs are generated under:

$ORACLE_HOME/ocsclient/log/

e) The OC4J logs are generated under:
$ORACLE_HOME/j2ee/OC4J_Container/application-deployments/APPLICATIONS_FOLDER/OC4J_Container_default_island/application.log

f) The Calendar log files are generated under:

• $ORACLE_HOME/ocal/log for Calendar server
• $ORACLE_HOME/ocas/logs for Calendar application

What is Oracle Collaboration Suite & what are the components that constitute OCS?

Oracle Collaboration Suite is a suite of enterprise-class messaging and collaboration applications. Oracle Collaboration Suite contains the following components:

1.Calendar

Oracle Calendar is the time management component of Oracle Collaboration Suite, combining group and resource scheduling functionality with a variety of access methods to give you up-to-date task management information.
2.Content Services

Oracle Content Services is an enterprise content management system that enable users to collaborate more efficiently.

3.Discussions

Oracle Discussions is a scalable, manageable, and easy-to-use application for managing online discussion forums
4.Mail

Oracle Mail is Oracle Collaboration Suite's open-standards-based solution for enterprise-wide e-mail, voice mail and faxes
5.Mobile Collaboration

Oracle Mobile Collaboration is a collection of applications that enables you to access your e-mail, voice mail, calendar, contacts, tasks, files and corporate directories from any device with wireless or voice access.
6.Real-Time Collaboration

Oracle Real-Time Collaboration is the real-time messaging and conferencing component of Oracle Collaboration Suite. Oracle Real-Time Collaboration lets you participate in chats and Web conferences as well as publish your presence and availability.
7.Search

Oracle Collaboration Suite Search offers gives users of Oracle Collaboration Suite a configurable, all-in-one search solution across the following Oracle Collaboration Suite components: Oracle Mail, Oracle Calendar and Oracle Content Services.
8. Voicemail & Fax

Oracle Voicemail & Fax provides Oracle Collaboration Suite with centralized and secure message storage and retrieval for voice mail and faxes.
9.Workspaces

Oracle Workspaces let you can share documents, hold discussions, administer meetings and manage tasks

How should you map Application Components to Collaboration Suite Middle Tier Components?

I. The OC4J Instances

The more important ones that should usually be running at all times are the following:

1. OC4J_Content: The Content Services application that runs the various file-serving protocol servers.
   
2. OC4J_Mail: The Mail application that runs the various e-mail protocol servers
   
3. OC4J_OCSADMIN: The Ultrasearch application.
   
4. OC4J_OCSCLIENT: The starting point of the user interface to Oracle Collaboration Suite that must be running if any of the web clients are to be used.
   
5. OC4J_Portal: A PL/SQL application that requires several Java modules,including the PPE that renders the pages to be returned to the user, to be running on the middle tier
   

An Oracle Collaboration Suite infrastructure instance will be configured with one OC4J instance that should be running at all times. This is the OC4J_SECURITY instance that runs the OIDDAS application.

Note that there is also a HOME OC4J instance created in both middle tier and infrastructure instances. It should never be necessary to start this.

II. Mapping Application Components to Middle Tier Components

a) The Web Cache and HTTP Server (the Apache web listener) manage the HTTP traffic between browsers and middle tier instances.

b) Portal, consisting of the component that generates pages and the parallel page engine, is necessary to construct the web pages seen by end users.

c) The Calendar server itself consists of a set of processes visible in the Application Server Control window as just one component: the Calendar Server.

To see the individual processes, use the opmnctl utility:

$ opmnctl status ias-component=CalendarServer

d) Content Services is two components: the server component and a web interface component that runs within an OC4J container. These are shown in Application Server Control as the components Content and OC4J_Content.

e) The Mail application also consists of two components: Mail Application and OC4J_Mail. The Mail application is the Mail protocol servers. The OC4J_Mail component provides the Mail web interface.

g) The Real-Time Collaboration components are OC4J_imeeting and Real-Time Collaboration.The imeeting component manages the web interface for web conferencing; the Real-Time Collaboration component is the server process that enables real-time communication between users.

h) The Search component, based on the Ultrasearch web crawling facility that can crawl through database and web content, is accessed through the OC4J_OCSADMIN component.

i) The wireless capability is two components: OC4J_Wireless and Wireless.

j) Workspaces are implemented in PL/SQL and therefore cannot be controlled through OPMN or Application Server Control.

k) The Management component is the Enterprise Manager daemon. Since this is the Application Server Control process it clearly cannot be started or stopped through Application Server Control; you must manage it with the emctl utility.

Oracle Collaboration Suite Fine Tuning

Runtime Configuration
The critical directives & their values in the httpd.conf file of an Oracle Collaboration Suite installation in production are the following:

• 
  KeepAlive on
  
• 
  MaxKeepAliveRequests 100
  
• 
  KeepAliveTimeout 15
  
• 
  MinSpareServers 5
  
• 
  MaxSpareServers 20
  
• 
  StartServers 5
  
• 
  MaxClients 150