The Blog of Nenad

Oracle Collaboration Suite 10g (10.1.2.2.0) on RedHat Linux AS 3.0
==================================================================

NOTE: Oracle Collaboration Suite Infrastructure and Applications Installation on a Single Computer
NOTE: For Oracle Collaboration Suite Infrastructure and Applications installation on a single computer, 2 GB or more is recommended.

1. Disk Space: recommended total of 19GB, /tmp 250MB
Check disk space with
# df -kH

2. Swap Space: min 1.5GB
Check swap space with
# grep SwapTotal /proc/meminfo

3. Check that Red Hat Enterprise Linux AS/ES 3.0 is installed:
# cat /etc/issue
3a. The minimum supported kernel versions are: kernel-2.6.9-11.EL, kernel-smp-2.6.9-11.EL, kernel-hugemem-2.6.9-11.EL
Check for kernel version with
# rpm -qa | grep kernel

4. Check that the following software packages, or later versions, are installed:

glibc-2.3.2-95.30
glibc-common-2.3.2-95.30
binutils-2.14.90.0.4-35
compat-glibc-7.x-2.2.4.32.6
compat-libstdc++-7.3-2.96.128
compat-libstdc++-devel-7.3-2.96.128
gcc-3.2.3-47
gcc-c++-3.2.3-47
libstdc++-3.2.3-47
libstdc++-devel-3.2.3-47
openmotif21-2.1.30-8
pdksh-5.2.14-21
setarch-1.3-1
make-3.79.1-17
gnome-libs-1.4.1.2.90-34.2
sysstat-5.0.5-5.rhel3 (*CD 3)
compat-db-4.0.14-5.1

Check packages with
# rpm -q glibc \
glibc-common \
binutils \
compat-glibc \
compat-libstdc++ \
compat-libstdc++-devel \
gcc \
gcc-c++ \
libstdc++ \
libstdc++-devel \
openmotif21 \
pdksh \
setarch \
make \
gnome-libs \
sysstat \
compat-db

5. Kernel
kernel.shmall = 3279547
kernel.shmmax = 2147483648
kernel.shmmni = 4096
# semaphores: semmsl, semmns, semopm, semmni
kernel.sem = 256 32000 100 142
fs.file-max = 327679
net.ipv4.ip_local_port_range = 10000 65000
kernel.msgmni = 2878
kernel.msgmax = 8192
kernel.msgmnb = 65535

By specifying the values in the /etc/sysctl.conf file, you ensure that they persist when you restart the system.

# /sbin/sysctl -p

6. Add the following lines to /etc/security/limits.conf file:

* soft nproc 4096
* hard nproc 16384
* soft nofile 4096
* hard nofile 65536

7. Add the following line to the /etc/pam.d/login file, if it does not already exist:

session required /lib/security/pam_limits.so

8. Depending on the default shell of the oracle user, make the following changes to the default shell startup file:

For the Bourne, Bash, or Korn shell, add the following lines to the /etc/profile file:

if [ $USER = "oracle" ]; then
if [ $SHELL = "/bin/ksh" ]; then
ulimit -p 16384
ulimit -n 65536
else
ulimit -u 16384 -n 65536
fi
fi


For the C or tcsh shell, add the following lines to the /etc/csh.login file:

if ( $USER == "oracle" ) then
limit maxproc 16384
limit descriptors 65536
endif

9. Check port 1521
# netstat -an | grep 1521

10. Hosts: The /etc/hosts file should use the following format:
ip_address fully_qualified_hostname short_hostname

Example:
123.456.789.99 ocs.mydomain.com ocs

10. Create directories
# mkdir -p /u01/app/product/10.1.2/apps
# mkdir -p /u01/app/product/10.1.2/infra
# chown -R oracle.oinstall /u01

11. Install OCS Infrastructure

12. Install OCS Applications

Patchset 10.1.2.2.0
-------------------

1. Patch 4892455 - Apps tier
Stop Calendar Server
# $ORACLE_HOME/opmn/bin/opmnctl stopproc ias-component=CalendarServer
# . oraenv
# opatch apply
# $ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=CalendarServer

2. Patch 4898766 - Apps Tier
# . oraenv
# $ORACLE_HOME/ocas/bin/ocasctl -stopall
# opatch apply
# $ORACLE_HOME/ocas/bin/ocasctl -startall

3. Patch 5007932 - Infra tier
Check infrastructure DB Version with 'select * from v$version;'
# . oraenv
# opatch apply

Stop App tier components
# $ORACLE_HOME/opmn/bin/opmnctl stopproc ias-component=email
# $ORACLE_HOME/opmn/bin/opmnctl stopproc process-type=OC4J_Mail
# $ORACLE_HOME/opmn/bin/opmnctl stopproc process-type=OC4J_OCSClient

Load es_patch_10.1.2.2.sql package as the es_mail database user. (infra)
# cd $ORACLE_HOME/oes/install/sql
# sqlplus es_mail/manager1
# SQL> @es_patch_10.1.2.2.sql

Load esserver.jar and esmesg.jar into the es_mail schema:
# $ORACLE_HOME/bin/loadjava -f -v -r -user "es_mail/manager1" $ORACLE_HOME/jlib/esserver.jar
#$ORACLE_HOME/bin/loadjava -f -v -r -user "es_mail/manager1" $ORACLE_HOME/jlib/esmesg.jar

Recompile all invalid objects as the sys database user. Execute the following commands in the Oracle Collaboration Suite Database (Oracle Mail Database) Oracle_Home:

# cd $ORACLE_HOME/rdbms/admin
# $ORACLE_HOME/bin/sqlplus sys/@ as sysdba
# SQL> @utlrp.sql

Do not start Apps tier components

4. Patch 4949529 - Apps tier
# . oraenv
# opatch apply

Use the Mail Administration page to modify an IMAP property:
Log in to the Oracle Enterprise Manager Collaboration Suite Control console of the Oracle Mail Applications tier. For example: http://appstiername.com:1810
Log in as ias_admin
On the Farm page, click the Applications tier Oracle Application Server instance name. For example: inst1.appstiername.com
On the Oracle Collaboration Suite Control Home page, click Mail Application in the System Components table.
Click IMAP Server on the Service Targets table.
Click Default Settings.
Modify the Public Folder Cache Refresh Interval (min) value, setting it to 1440.
Click Apply. A confirming message appears.
Click Mail Application.
Select the IMAP Server radio button.
Click Stop.
Click Start.


When patching the FIRST Applications tier, upload oes10122patchsetupgrade.ldif into the Infrastructure Oracle Internet Directory. To do this, run the following command under $ORACLE_HOME:
$ORACLE_HOME/bin/ldapmodify -c -v -a -D"cn=orcladmin" -w -h -p -f $ORACLE_HOME/oes/bin/oes10122patchsetupgrade.ldif

Restart all protocol servers and OPMN instances:
# $ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=email
# $ORACLE_HOME/opmn/bin/opmnctl startproc process-type=OC4J_Mail
# $ORACLE_HOME/opmn/bin/opmnctl startproc process-type=OC4J_OCSClient

Restart the Applications tier Oracle Enterprise Manager:
# $ORACLE_HOME/bin/emctl stop iasconsole
# $ORACLE_HOME/bin/emctl start iasconsole

5. Patch 4957487 - Apps tier
# . oraenv
# opatch apply

Stop OPMN using the following command:
# $ORACLE_HOME/opmn/bin/opmnctl stopall

Start OPMN using the following command:
# $ORACLE_HOME/opmn/bin/opmnctl startall

6. Patch 4924473 - Apps tier
# . oraenv
Oracle recommends that the OC4J_OCSClient instance be shut down before applying this patch. This can be done using OPMN; for example:
# $ORACLE_HOME/opmn/bin/opmnctl stopproc gid=OC4J_OCSClient
This patch also stops some other Application tier components during patching process (Portal, Web Cache, HTTP server). After patching is done, stopped components are started again.

Apply patch
# opatch apply -pre oid_su oid_pwd -opatch_pre_end -post oid_su oid_pwd -opatch_post_end
oid_su is the Oracle Internet Directory superuser (such as cn=orcladmin)

7. Patch 4924895 - Apps tier
# . oraenv
# opatch apply

8. Patch 4930030 - Apps tier
# . oraenv

Create an entry in your $MIDTIER_ORACLE_HOME/network/admin/tnsnames.ora that defines the connection details to the Oracle Collaboration Suite mailstore database for the internal Discussions administrator user owning Discussions folders (its username is discussions_ where is the Oracle Mailstore database SID). The mailstore is the database where the ES_MAIL schema used by Discussions stores data. A sample tnsnames.ora entry is shown below. Refer to Oracle Documentation Net Service Reference for more details on the tnsnames.ora syntax.

OCSMAILSTORE = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP) (HOST = myhost.mycompany.com) (PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = dbsid.mycompany.com) ) )

Collect the following pieces of information prior to applying the patch. You will need this information to successfully apply the patch:
- The net service name (as defined in the tnsnames.ora file, "OCSMAILSTORE" in the preceding example) that defines the connection to the mailstore database. This is referred to as .
- The password for the "sys" user in the mailstore database. This password is referred to as .
- Oracle Internet Directory (OID) hostname, referred as , OID port referred as , OID administrator username referred as , and finally OID administrator password referred as .

Verify that the Oracle Collaboration Suite Infrastructure and Oracle Collaboration Suite mailstore database are running. Make sure that the OC4J process where the Discussions application is deployed (by default OC4J_OCSClient) is running on the Applications tier. You may leave other middle tier processes (such as OPMN, Webcache and Oracle Collaboration Suite Control (Enterprise Manager)) running.

Apply patch
# opatch apply -pre -dbconn -dbpwd -opatch_pre_end -post -oidhost -oidport -oidusr -oidpwd

9. Patch 4912230 - Apps tier
# . oraenv

Verify that the Oracle Collaboration Suite Infrastructure and Workspaces Database are up and running. Make sure that the OC4J process where the Workspaces application is deployed (by default OC4J_OCSClient) is running on the Applications tier. You may leave other middle tier processes (such as OPMN, Webcache and Oracle Collaboration Suite Control (Enterprise Manager)) running.

Apply patch (see previous patch notes for details)
# opatch apply -pre –dbconn -dbpwd -opatch_pre_end -post –oidhost -oidport -oidusr -oidpwd

10. Patch 4928124 - Apps tier
Stop the Oracle Content Services processes running on all Applications Tiers, as follows:
- Using a browser, access the following URL:
http://Applications_tier_host_name:port
For example, http://myserver.mycompany.com:1156.
- Enter the authentication information for the ias_admin user.
- Click your Applications Tier instance. The page refreshes to display all the Oracle Collaboration Suite components.
- Click the Content component or the component that corresponds to the Oracle Content Services instance.
- In the page corresponding to Oracle Content Services, click Stop Domain. (Node)
- Click OK on the confirmation page.

Ensure that the infrastructure and database instances are running

Type the following at the UNIX prompt to verify that these UNIX commands are available in the path and have no aliases attached to them. If there are aliases, the application of the patch may fail.
The expected response will indicate the path to the UNIX command. For example, /usr/bin/cp.
which cp
which rm
which sed
which find
which mkdir
which dirname
which zip
which unzip

# . oraenv
Apply the patch
# opatch apply
(You can track patch progress with # tail -f /u01/app/product/10.1.2/apps/content/log/Patch.log)

11. Patch 4947127
# . oraenv

Portal Schema Password
The portal schema password is required in the upgrade process. You can look up the Portal schema password using the following procedure:
- Start Oracle Directory Manager:
# $ORACLE_HOME/bin/oidadmin &
- Enter the name of the Infrastructure host running the Oracle Internet Directory instance used by Oracle Collaboration Suite Portlets.
- Log in using the orcladmin account.
- Navigate the following links:
Entry Management|cn=OracleContext|Products|IAS|IAS Infrastructure Databases|orclReferenceName=|OrclResourceName=PORTAL
The Portal schema password is the value of the orclpasswordattribute property. Make a note of the password, for use during the patch process.

Stop the OC4J Portal process
# $ORACLE_HOME/opmn/bin/opmnctl stopproc process-type=OC4J_Portal

Apply patch
# opatch apply

Execute script
# $ORACLE_HOME/ocsprovs/bin/ocsprovs_installer.sh -mode packages -p portal -ps -c infra.dbhost.com:1521:sid -ouser -opass -ipass

for example
# $ORACLE_HOME/ocsprovs/bin/ocsprovs_installer.sh -mode packages -p portal -ps Xj0H00wr -c ocs.parallel.co.yu:1521:orcl -ouser cn=orcladmin -opass manager1 -ipass manager1

Start the OC4J Portal process
# $ORACLE_HOME/opmn/bin/opmnctl startproc process-type=OC4J_Portal

==================================================================

Stop everything and backup software installation and database.
Installation:
# tar -cvf fullbck.tar /u01/app/oracle/*
System Files
# tar -cvf sys.tar /etc/ora* /usr/local/bin/*env /usr/local/bin/dbhome

==================================================================

SETUP OF WORKFLOW MAILER
------------------------

To configure the Oracle Workflow notification mailer:

1. Create an e-mail account for the notification mailer administrator (for example, wfadmin). The workflow account you create should only be used by the notification mailer system. Concurrent connections to this account are not allowed.
2. Create three folders for this e-mail account: one to use as an inbox, one to store processed messages, and one to store discarded messages. The default values for these folders in the notification mailer configuration wizard are INBOX, PROCESS, and DISCARD.
3. Ensure that all Oracle Workflow and e-mail server processes are running.
4. Access the Oracle Collaboration Suite Control on the computer where Oracle Workflow is running and go to the Collaboration Suite Home page.
5. In the System Components table, click Oracle Workflow.
6. On the Workflow Home page, click Service Components in the Related Links: Configuration section.
7. In the Service Components table, select Workflow Notification Mailer and click Edit.
8. Ensure that Automatic is selected for Startup Mode and click Next.
9. Click Next on the following page.
10. In the Inbound EMail Account section, provide the following information:
* Server Name: Enter the fully-qualified host name for the incoming e-mail server.
* Username: Enter the e-mail address you created for the workflow notification mailer administrator.
* Password: Enter the password for the workflow notification mailer administrator e-mail address.
* Inbox Folder: If the folder you created to use as an inbox has a name different from the default, provide the name of the inbox folder. The name for this folder is case-insensitive.
11. In the Outbound EMail Account section, in the Server Name field, provide the fully-qualified host name for the outgoing e-mail server.
12. In the EMail Processing section, provide the names of the Processed Folder and Discard Folder. The names for these folders are case-sensitive.
13. Click Next.
14. In the Send section, provide the following information:
* Reply-to Address: Enter the e-mail address you created for the workflow notification mailer administrator.
* HTML Agent: Enter the base URL that identifies the HTML Web agent that handles HTML notification responses, in the format: http://applications_tier_host:oracle_http_server_port/pls/wf
15. Click Next on all the remaining pages, then click Finish on the Review page.
16. Return to the Collaboration Suite Home page, select Service_Component_Container, and click Restart.

==================================================================

ENABLING CUSTOM WORKFLOW
------------------------
Enabling BPEL Workflow Creation in Oracle Content Services. To enable BPEL workflow creation in Oracle Content Services:

1. Connect to the Oracle Collaboration Suite Control and go to the Content Services Home page.
2. In the Administration section, click Domain Properties.
3. Click IFS.DOMAIN.WORKFLOW.BPEL.CreationEnabled. You may need to move to the next page to find this property, or you can use the Search field.
4. Set the Value to true.
5. Click OK.
6. Return to the Content Services Home page and click Restart Domain.

==================================================================

BACKUP
------

1. Prepare the Oracle Collaboration Suite Database for backup
* enable ARCHIVELOG mode
- Set the ORACLE_HOME and ORACLE_SID environment variables
- Shutdown the database.

# sqlplus " / as sysdba"
SQL> shutdown immediate

- Start up the database in mount mode.
SQL> startup mount

- Enable ARCHIVELOG mode.
SQL> alter database archivelog;

* Enabling the flashback database feature for the Oracle Collaboration Suite Database
- Run the following query to check if the flashback_recovery_area is set up:
SQL> show parameters db_recovery

- Check that the database is only mounted.
SQL> select open_mode from v$database;

- Specify the destination directory for your archives by including the initialization parameter LOG_ARCHIVE_DEST_n in the initialization file. Set the log_archive_dest_1 parameter. The flash_recovery_area directory can be found under your $ORACLE_HOME location. Check that the location exists before entering the command.
SQL> alter system set log_archive_dest_1= "LOCATION=/u01/app/oracle/flash_recovery_area/ORCL/archivelog" scope=spfile;

- Turn on flashback database with the following SQL command:
SQL> alter database flashback on;

* Enabling block change tracking
- Run the following query to check if the db_create_file_dest parameter is set:
SQL> show parameters db_create_file

- Use the following command to enable block change tracking.
SQL> alter database enable block change tracking;

- Shutdown the database.
SQL> shutdown immediate;

- Start up the database and exit SQL*Plus.
SQL> startup
SQL> exit

2. Backup applications tier
- Execute the ocs_bkp_restore.sh script to configure the Oracle Collaboration Suite Recovery Manager to back up Oracle Collaboration Suite Applications.

# cd $ORACLE_HOME/backup_restore
# ./ocs_bkp_restore.sh -m configure

This script requires the following input:
Configure the backup environment file (yes/no) : yes >
Confirm that you want to configure the backup environment file. Click [Enter].

Enter ORACLE_HOME : /u01/app/oracle/product/10.1.2/ocs_1/apps >
Confirm the ORACLE_HOME path. Click [Enter].

Enter the config backup path :
Enter the path to your backup directory, where you want to store the configuration files (this example uses /u02/backup/apps/config).

Enter the database backup path :
Enter the path to your backup directory, where you want to store the database files (this example uses /u02/backup/apps/db).

Enter the log path :
Enter the path to your backup directory, where you want to store the log files (this example uses /u02/backup/apps/logs).

Enter the ORACLE_SID : orcl >
Confirm the ORACLE_SID setting. Click [Enter].

Enable Email notification (yes/no): yes >
Confirm that you want Email notification. Click [Enter] or type No, if you do not want Email notification.

Enter the SMTP host : >
Provide the name of the SMTP host. Enter the host name (this example uses a single-box installation).

Enter the SMTP port : 25 >
Confirm the SMTP port. Click [Enter].

Enter the from address : > @
Enter the to addresses(comma seperated) : > @

Enter the Email address from where you want to send notifications regarding backup and recovery and who should receive these notifications.

NOTE: You need to perform this step only once and not for each backup that you will take.

* After finished configuration
Back up the Applications instance using the backup_instance_cold mode. Press the [Enter] key when prompted by the question: Do you wish to continue?

./ocs_bkp_restore.sh -m backup_instance_cold

NOTE: repeat this in 'infra' tier