11 Postinstallation Tasks for Oracle Collaboration Suite

This chapter contains the following sections:

• Section 11.1, "State of Oracle Collaboration Suite Instances After Installation"

• Section 11.2, "Setting Environment Variables"

• Section 11.3, "Passwords for Oracle Collaboration Suite Components"

• Section 11.4, "Modifying Password Settings for Oracle Internet Directory"

• Section 11.5, "NFS Installations"

• Section 11.6, "Enabling SSL"

• Section 11.7, "Performing Component-Specific Tasks"

• Section 11.8, "Configuring the Time-out Value in the sqlnet.ora File"

• Section 11.9, "Backup and Recovery"

• Section 11.10, "What to Do Next?"

11.1 State of Oracle Collaboration Suite Instances After Installation

After installation, the components that you have configured are started up, unless you have configured them to use ports lower than 1024, in which case you have to start them manually.

You can view the Welcome page and the Application Server Control page in a browser window. The URLs for these pages are shown in the last screen of the installer. You can view the contents of the last screen in the file $ORACLE_HOME/install/setupinfo.txt.

You can use scripts or you can use the Oracle Enterprise Manager 10g Application Server Control to start and stop Oracle Collaboration Suite instances. See the Oracle Collaboration Suite Administrator's Guide for details.

11.2 Setting Environment Variables

After the installation is complete, you might need to set the environment variables listed in the following section. These environment variables are required for proper functioning of some Oracle Collaboration Suite commands. Variables that you must set are listed in the following table:

Variable Name	Bourne, Korn, or Derivative Shells	C Shell
ORACLE_HOME	ORACLE_HOME=/u01/oracle/product/ocs; export ORACLE_HOME	setenv ORACLE_HOME /u01/oracle/product/ocs
PATH PATH must include ORACLE_HOME/bin.	PATH=$ORACLE_HOME/bin:$PATH; export PATH	setenv PATH $ORACLE_HOME/bin:$PATH
DISPLAY DISPLAY must point to a running X server. Do not use X emulation on your client computer to start server processes. Run X server instead.	DISPLAY= X server:display_number.screen_number; export DISPLAY For example: DISPLAY= localhost:0.0; export DISPLAY	setenv DISPLAY X server:display_number.screen_number For example: setenv DISPLAY localhost:0.0
LD_LIBRARY_PATH LD_LIBRARY_PATH must include $ORACLE_HOME/lib	LD_LIBRARY_PATH=$ORACLE_HOME/lib; export LD_LIBRARY_PATH	setenv LD_LIBRARY_PATH $ORACLE_HOME/lib
NLS_LANG (optional, for globalization support)	NLS_LANG=language_territory.characterset; export NLS_LANG For example: de_de.WE8ISO8859P15; export NLS_LANG	setenv NLS_LANG language_territory.characterset For example: setenv de_de.WE8ISO8859P15
ORA_NLS ORA_NLS is the location of the globalization support-specific message files.	ORA_NLS=$ORACLE_HOME/ocommon/nls/admin/data; export ORA_NLS	setenv ORA_NLS $ORACLE_HOME/ocommon/nls/admin/data
TNS_ADMIN TNS_ADMIN is the location of the SQL*Net configuration files tnsnames.ora, listener.ora, sqlnet.ora and by default these are located in $ORACLE_HOME/network/admin.	TNS_ADMIN=$ORACLE_HOME/network/admin; export TNS_ADMIN	setenv TNS_ADMIN $ORACLE_HOME/network/admin

Note: You can source the $ORACLE_HOME/bin/oraenv or $ORACLE_HOME/bin/coraenv scripts (depending on their current shell) to set the ORACLE_HOME and ORACLE_SID variables. These scripts will also add $ORACLE_HOME/bin in to the PATH variable.

11.3 Passwords for Oracle Collaboration Suite Components

If you selected the password for all Oracle Collaboration Suite components during the installation, then for security reasons it is recommended that you should change the passwords of the various components to have different values.

See the Oracle Collaboration Suite Administrator's Guide and the component guides in the Oracle Collaboration Suite Documentation Library for details on how to alter the passwords for the components you have installed.

11.4 Modifying Password Settings for Oracle Internet Directory

Beginning with Oracle Internet Directory 10g (9.0.4), the default password expiry time, which is assigned to the pwdmaxage attribute, is set to 60 days.

To change the default value, perform the following steps:

1. Perform this step only if your Oracle Internet Directory account is locked. Unlock the cn=orcladmin superuser account before you can modify password policies. Use the oidpasswd utility to unlock the superuser account as follows:

   oidpasswd connect=ocsdb unlock_su_acct=true
   OID DB user password:
   OID super user account unlocked successfully.
   
   

   This unlocks only the superuser account, cn=orcladmin. Do not confuse this account with the cd=orcladmin account within the default realm cn=orcladmin,cn=users,dc=xxxxx,dc=yyyyy. These are two separate accounts.

2. Start an Oracle Internet Directory 10g (10.1.2) version of Oracle Directory Manager and navigate to Password Policy Management. You will see the cn=PwdPolicyEntry or password_policy_entry,dc=acme,dc=com, which has the PasswordExpiryTime attribute.

   Another entry, pwdmaxage can be found under Entry Management as cn=PwdPolicyEntry, cn=common, cn=products, cn=OracleContext, dc=acme, dc=com or cn=PwdPolicyEntry, cn=common, cn=products, cn=OracleContext.

   Both, the PasswordExpiryTime attribute and the pwdmaxage attribute are the same and if you change one attribute, the subtree for the other attribute will be updated automatically.

   Change the pwdmaxage attribute in each password policy to an appropriate value:

   • 5184000 = 60 days (default)

   • 7776000 = 90 days

   • 10368000 = 120 days

   • 15552000 = 180 days

   • 31536000 = 1 year

3. Start the Oracle Directory Manager and navigate to the realm-specific orcladmin account. Find the userpassword attribute and assign a new value. You should then be able to start any Oracle component that uses Oracle Application Server Single Sign-On and log in as orcladmin.

   Rerun the odisrvreg utility to reset the randomly generated password for Directory Integration and Provisioning:

   odisrvreg -D cn=orcladmin -w welcome1 -p 3060
   Already Registered...Updating DIS password...
   DIS registration successful.
   
   

4. Reregister the connector:

   odisrvreg -p port -D cn=orcladmin -w passwd
   

See Also: Oracle Identity Management Integration Guide

11.5 NFS Installations

If you installed Oracle Collaboration Suite on an NFS disk, then you must edit the LockFile directive in the $ORACLE_HOME/Apache/Apache/conf/httpd.conf file so that it points to a local disk. This file is used by the Oracle HTTP Server component.See the Oracle HTTP Server Administrator's Guide for details.

11.6 Enabling SSL

You may want to enable Secure Sockets Layer (SSL) depending on your security requirements. For detailed information on enabling SSL in Oracle Collaboration Suite, refer to Chapter 7, "Enabling SSL in Oracle Collaboration Suite", of Oracle Collaboration Suite Security Guide.

You will also find detailed information about enabling SSL in a single-computer installation in Chapter 7, "Enabling SSL in Oracle Collaboration Suite", of Oracle Collaboration Suite Security Guide.

11.7 Performing Component-Specific Tasks

After you have successfully installed Oracle Collaboration Suite Applications and if you have installed Oracle Mail as a part of the Applications tier, then perform the following steps:

1. Log in as the oracle user.

2. Obtain the values of uid and groupid using the following command:

   prompt> id
   uid=509(oracle) gid=510(oinstall) groups=510(oinstall),511(dba) 
   
   

3. Switch to the root user.

4. Set the ORACLE_HOME and PATH variables.

5. Start the TNS listener using the following command:

   tnslsnr listener_es -user user_id -group group_id &
   
   

   In the preceding command, user_id and group_id are the IDs of user that owns the installation. Here, assuming the oracle user installed Oracle Collaboration Suite, user_id refers to the value 509 and group_id refers to the value 510, as shown in Step 3.

11.8 Configuring the Time-out Value in the sqlnet.ora File

You must configure the SQLNET.EXPIRE_TIME parameter in the $ORACLE_HOME/network/admin/sqlnet.ora file on the application infrastructure database. For the OracleAS Single Sign-On server, the parameter must be updated on each database host. The parameter should be set to a value less than the TCP timeout setting on the load balancer SSO virtual server.

To configure the time-out value, perform the following steps:

1. Open the file $ORACLE_HOME/network/admin/sqlnet.ora file.

2. Set the SQLNET.EXPIRE_TIME parameter to a value lower than the TCP session time-out value for the load-balancing router and firewall.

3. Restart the listener by issuing the following commands in $ORACLE_HOME/bin:

   lsnrctl stop
   lsnrctl start 
   

11.9 Backup and Recovery

You should also perform a complete Oracle Collaboration Suite environment backup after installing Oracle Collaboration Suite. This enables you to restore a working environment in case something goes wrong. For details on how to perform a complete Oracle Collaboration Suite environment backup, see the Oracle Collaboration Suite Administrator's Guide.

You should also perform a complete Oracle Collaboration Suite environment backup after each successful patch set upgrade and after each successful configuration change.

11.10 What to Do Next?

After installing Oracle Collaboration Suite, you should read the Oracle Collaboration Suite Administrator's Guide. Specifically, you should read the "Getting Started After Installing Oracle Collaboration Suite" chapter.