Skip Headers
Oracle® Collaboration Suite Installation Guide
10g Release 1 (10.1.2) for Microsoft Windows

Part Number B25463-03
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

11 Postinstallation Tasks for Oracle Collaboration Suite

This chapter contains the following sections:

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 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.3 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
    

11.4 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.5 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.6 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.7 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.