| Oracle® Collaboration Suite Upgrade Guide 10g Release 1 (10.1.2.2) for Microsoft Windows Part Number B31282-03 |
|
|
View PDF |
| Oracle® Collaboration Suite Upgrade Guide 10g Release 1 (10.1.2.2) for Microsoft Windows Part Number B31282-03 |
|
|
View PDF |
This chapter guides the reader through the steps for upgrading Oracle Collaboration Suite's middle tier applications. It includes the following sections:
Understanding the Oracle Collaboration Suite Middle Tier Upgrade Process
Resolving Oracle Collaboration Suite Upgrade Assistant Errors
Completing the Upgrade to Oracle Collaboration Suite Applications
Verifying the Upgrade to Oracle Collaboration Suite 10g Applications
|
Note: Oracle does not currently support the upgrade of Oracle Web Conferencing on Windows. You can, however, configure Oracle Real-Time Collaboration for Oracle Collaboration Suite 10g (10.1.2)—formerly known as Oracle Web Conferencing—in Oracle Enterprise Manager. |
Upgrade the middle tier applications after upgrading the following components:
Oracle Application Server Infrastructure
Oracle Collaboration Suite Information Storage Database
To upgrade a Oracle Collaboration Suite middle tier, use the Oracle Universal Installer to install Oracle Collaboration Suite 10g Applications in a new Oracle home. When the Oracle Universal Installer detects an existing middle tier installation on the same system, it offers you the option to upgrade. When the installation completes, the installer starts the Oracle Collaboration Suite Upgrade Assistant to perform the upgrade. The upgrade assistant copies configuration information from the source Oracle home to the destination Oracle home.
The general rules for upgrade are:
Oracle Universal Installer installs all the applications in Oracle Collaboration Suite 10g Applications in the destination Oracle home. The Oracle Collaboration Suite Upgrade Assistant configures all middle tier applications configured in the source Oracle home. If an application was not configured in the source Oracle home, then it is not configured in the destination Oracle home. You can configure additional applications after the upgrade is complete.
Select the option to upgrade at the time you install Oracle Collaboration Suite Applications. Oracle does not support installing a new Oracle Collaboration Suite Applications and running the Oracle Collaboration Suite Upgrade Assistant after the installation completes.
Some component names have changed in 10g Release 1 (10.1.2). This chapter uses the Release 1 (9.0.3.1) and Release 2 (9.0.4.2) component names to refer to the component in the source Oracle home. The 10g Release 1 (10.1.2) name refers to the upgraded component in the destination Oracle home. Table 6-1 summarizes the component names changes.
Table 6-1 Component Name Changes
| 9.0.x Component Name | 10g Release 1 (10.1.2) Component Names |
|---|---|
|
Oracle Collaboration Suite 10g Applications (Applications tier) |
|
|
Oracle Collaboration Suite 10g Mail |
|
|
Oracle Collaboration Suite 10g Content Services |
|
|
Oracle Collaboration Suite 10g Search |
|
|
Oracle Wireless and Voice |
Oracle Collaboration Suite 10g Mobile Collaboration |
The following applications have prerequisite steps to be performed prior to starting the upgrade process:
Perform the steps described in these sections if required and proceed to Section 6.3 for additional required steps.
The steps in this section are optional.
Before the upgrade, user address books are stored in a local Oracle Calendar database. By default, after the upgrade, these address books are migrated to a Common Address Book in Oracle Internet Directory so that they can be shared with Oracle Collaboration Suite 10g WebMail and Oracle Collaboration Suite 10g Web Access Client. The migration, or synchronization, occurs at intervals specified by the [CWS]cabsynctime parameter in DESTINATION_ORACLE_HOME/ocal/misc/unison.ini.
If you are concerned about the load on Oracle Internet Directory because of the size and number of the user's address books or system performance issues, you can disable the synchronization before starting the upgrade. If you disable the synchronization, then the Oracle Calendar clients address books remain independent of the other address books. However, you can enable synchronization any time after the upgrade is complete.
To disable Common Address Book synchronization, in the SOURCE_ORACLE_HOME/ocal/misc/unison.ini file, locate the [ENG] section and add the following line:
cab_enable = FALSE
This value is copied to the unison.ini file in the destination Oracle home so that the Oracle Calendar server does not perform synchronization with the Common Address Book. See Section 6.6.6.2 for information about enabling synchronization after the upgrade.
This section discusses your two options for migrating Oracle Ultra Search data.
To ensure a successful Content Services upgrade, please refer to Metalink note 338875.1 for important upgrade verification steps.
As part of the DBMS upgrade process a new $ORACLE_HOME will be created; however, the upgrade process will not migrate BFILES from the original $ORACLE_HOME. BFILES related to a specific Oracle Files instance must be manually migrated to the new Oracle Content Services DBMS $ORACLE_HOME. This requires copying the entire BFILES directory hierarchy from the old $ORACLE_HOME to the new $ORACLE_HOME. To determine BFILE location, go to the Oracle Content Services home page in Oracle Enterprise Manager. In the Administration section, click on Storage Management to navigate to the Storage Management page. The default BFILE path is./ifsbfiles/schema name, relative to the database $ORACLE_HOME on the database machine.
To migrate the Oracle Ultra Search index and configuration data, perform the steps in Chapter 9. before proceeding Otherwise, you can still migrate the Oracle Ultra Search configuration data from the Oracle9iAS Metadata Repository to the Oracle Collaboration Suite Database as part of the Oracle Collaboration Suite middle tier upgrade.
To prepare for the migrating the configuration data, create a user in the upgraded database to own each migrated Oracle Ultra Search instance. The new user must be granted the WKUSER role which gives it general administrative privileges on the Ultra Search instance. See Section 7.3.3 for instructions.
The Oracle Collaboration Suite Upgrade Assistant performs the migration during the upgrade process. It prompts you for the user names and passwords that you create in this section.
To upgrade Oracle9iAS Wireless configured on multiple middle tiers which use the same Oracle9iAS Metadata Repository:
Shut down all the middle tiers configured with Oracle9iAS Wireless that use the Oracle9iAS Metadata Repository. See Section 7.3.2 for instructions.
Back up the WIRELESS schema in the Oracle9iAS Metadata Repository.
This step is recommended because when you install the OracleAS Wireless middle tier (in the next step), the Wireless Configuration Assistant upgrades the WIRELESS schema in the Oracle9iAS Metadata Repository to Oracle Application Server 10g (9.0.4).
During the Oracle9iAS Metadata Repository upgrade, the Oracle Application Server Metadata Repository Upgrade Assistant (MRUA) will upgrade the 10g (9.0.4) WIRELESS schema to Oracle Application Server 10g Release 2 (10.1.2).
You can back up the WIRELESS schema by using the Export database utility.
exp system/password@service_name file=iasw902.dmp owner=WIRELESS
where:
password is the password of the SYSTEM account.
service_name is the local net service name that points to the Oracle9iAS Metadata Repository such as asdb.
This command creates a database export file called iasw902.dmp with the contents of the WIRELESS schema.
Upgrade the first middle tier to upgrade the Oracle9iAS Wireless schema in the Oracle9iAS Metadata Repository.
Start the upgraded middle tier and the remaining middle tiers. To upgrade the remaining middle tiers, shut down only the middle tier being upgraded.
If you install additional OracleAS Wireless middle tiers against the same Oracle9iAS Metadata Repository, the configuration assistant detects that the WIRELESS schema is already upgraded and does not upgrade it again.
The name of the log file directories have changed for Oracle Voicemail & Fax 10.1.2. If you are upgrading from Oracle Voicemail & Fax 10.1.1 to 10.1.2, these new directories will get added to the existing %ORACLE_HOME%\um\log directory, therefore, doubling the number of directories containing log files. To avoid confusion between which files are 10.1.1 log files and which are 10.1.2 log files, Oracle recommends that you create a %ORACLE_HOME%\um\log\10.1.1_logs directory. Then move the following 10.1.1. directories into this directory:
%ORACLE_HOME%\um\log\TransferProces
%ORACLE_HOME%\um\log\FaxInProcess
%ORACLE_HOME%\um\log\IVRProcess
%ORACLE_HOME%\um\log\MsgDeliveryMonProcess
%ORACLE_HOME%\um\log\MsgRecoveryProcess
%ORACLE_HOME%\um\log\MWIProcess
%ORACLE_HOME%\um\log\RecordingProcess
%ORACLE_HOME%\um\log\RetrievalProcess
%ORACLE_HOME%\um\log\RoutingProcess
%ORACLE_HOME%\um\log\SMDIMonProcess
%ORACLE_HOME%\um\log\TelephonyMonitorProcess
To prepare for the middle tier upgrade:
Back up the Oracle Collaboration Suite 10g Database.
Verify that you have sufficient Oracle Internet Directory credentials to upgrade Oracle Email, Oracle Files, Oracle Calendar, Oracle9iAS Wireless and Oracle Ultra Search.
Verify that Oracle Internet Directory is running. See Section 7.1.3 for instructions.
Verify that the Oracle Collaboration Suite Database is running. See Section 7.2.1 for instructions.
Log on to the system on which the Oracle Collaboration Suite middle tier is installed as the same operating system user that performed the installation.
Set or unset any environment variables according to Section 2.7, "Environment Variables," in Oracle Collaboration Suite Installation Guide for Microsoft Windows.
You are now ready to perform the upgrade.
To upgrade a Oracle Collaboration Suite middle tier, you first install Oracle Collaboration Suite Applications 10g Release 1 (10.1.2) in a new Oracle home using the Oracle Universal Installer. If the Oracle Universal Installer detects another middle tier installation, then it offers you the option to upgrade to 10g (10.1.2). It then runs the Oracle Collaboration Suite Upgrade Assistant to perform the upgrade once the installation completes.
The following sections describe the installation and upgrade procedures:
Verify that you have performed the prerequisite steps described in Section 6.2 and Section 6.3 before continuing.
Mount the installation DVD and start the Oracle Universal Installer.
|
Note: Refer to Chapter 3, "Starting the Oracle Collaboration Suite Installation Guide," of Oracle Collaboration Suite Installation Guide for Microsoft Windows. |
Run the installer and refer to Table 6-2 for information on the options you should select on each screen.
The installer automatically starts the Oracle Collaboration Suite Upgrade Assistant if you are upgrading Oracle Email, Oracle Files, Oracle Web Conferencing or Oracle Ultra Search. See Section 6.4.2 for more information.
After the End of Installation screen appears, exit the Oracle Universal Installer.
Table 6-2 Summary of the Oracle Universal Installer Screens During the Oracle Collaboration Suite Applications Upgrade
| Screen | Description and Recommended Options to Select |
|---|---|
|
Welcome |
Welcomes you to Oracle Universal Installer and the Oracle Application Collaboration Suite 10.1.1 installation procedure. Select Advanced Installation. |
|
Specify File Locations |
Enter a name and path for the new Oracle home. This new Oracle home is the destination Oracle home for the upgraded Oracle Collaboration Suite Applications. |
|
Select Oracle Collaboration Suite Applications 10.1.1. |
|
|
Prerequisite Checks |
This screen displays the results of checking that the system meets the minimum requirements for installing and configuring the product. If the screen displays any warnings or failure, manually correct the problem and click Retry. Depending on the problem, you may need to exit the Oracle Universal Installer, fix the problem and start Oracle Universal Installer again. If you need to modify the kernel parameters on Solaris, for example, you may need to exit, change the parameters, and restart the system. |
|
Oracle Enterprise Manager Warning |
This dialog appears when Oracle Enterprise Manager is still running. If you have not already done so, shut it down. |
|
Language Selection |
If multiple languages are used in the Collaboration Suite Database you are upgrading, select those languages. If you are not sure which languages were installed, but want languages other than English, click the double arrow button (>>) to select all languages. |
|
This screen appears when Oracle Universal Installer detects an existing Oracle Collaboration Suite middle tier installation. Select Upgrade Selected Oracle Collaboration Suite, and then select the Oracle home of the installation you want to upgrade from the list. You may only select one installation at a time. |
|
|
Stop All opmn Controlled Processes |
Shut down all processes on the middle tier of the source Oracle home. For details, see Section 7.3.2, "Shutting Down a Middle Tier Instance". |
|
Enter the user name and password to connect to the Oracle Internet Directory at the host name and port where the database is registered. You must either be the Oracle Internet Directory super user or a Single Sign-On user with appropriate install privileges. The default Oracle Internet Directory super user name is |
|
|
Oracle Collaborative Portlets Configuration Assistant Warning |
If this warning appears, then click OK and continue with the upgrade. When the upgrade completes, follow the instructions in Section 6.4.2.3. |
|
The screen lists Oracle Calendar server and Oracle Search, if these applications are configured in the Oracle home being upgraded. From the table, select the name of the database that each application will use. |
|
|
Create Instance Name |
In the Instance Name field, enter a unique name for the upgraded Oracle Collaboration Suite Applications instance. In the |
|
The Oracle Universal Installer starts the upgrade assistants for the applications configured in the middle tier. See Section 6.4.2 for more information. |
|
|
Summary |
Use this screen to confirm the choices you've made. Click Install to begin installing the new 10g Release 1 (10.1.2) Oracle home. |
If the Oracle Collaboration Suite Applications installation has a component configured, that component is upgraded automatically. Oracle Web Conferencing, Oracle Ultra Search and Oracle Email require information from the user in order to perform the upgrade.
If you did not perform the Oracle Ultra Search index and configuration data migration before the Oracle Collaboration Suite information storage database upgrade, you can still migrate the configuration data to the upgraded Oracle Ultra Search application by selecting the appropriate options in the upgrade assistant. Table 6-3 summarizes these options.
Table 6-3 Summary of the Oracle Collaboration Suite Upgrade Assistant Screens for Oracle Ultra Search
| Screen | Description and Recommended Options to Select |
|---|---|
|
Select Yes to migrate the configuration data to the new Ultra Search application. From the table, select each instance of Ultra Search that you want to migrate. Enter the name of the schema user and password that you created manually in the Oracle Collaboration Suite database with the role of Select No if you have already performed the index and configuration data migration. Oracle recommends not migrating Ultra Search Configuration Data. |
|
|
Select Yes to use the existing index in the Oracle9iAS Metadata Repository database until a new index is created when the crawling schedule is executed. If you select this option, the upgraded Oracle Ultra Search application will point to the existing index and you can use it to perform searches right away. The Instance Names list displays the instances in the Oracle9iAS Metadata Repository database. Select the instance used by the Oracle Ultra Search application and enter its schema password. |
The reason to continue using the existing index is that, after the upgrade, users may experience some down time when performing a Web search using the Oracle Collaboration Suite 10g Search application. You can avoid down time by selecting Yes in the Ultra Search Indexing screen to use the existing index until the new index is ready. When the new index is ready, modify the oc4j-ra.xml configuration file to point Oracle Collaboration Suite 10g Search to the new index. See Section 6.6.5 for more information.
The Oracle Email Upgrade Assistant gives you the option to migrate contacts data as part of the upgrade process. You can also perform the migration manually after the upgrade of all middle tiers configured with Oracle Email.
Table 6-4 Summary of the Oracle Collaboration Suite Upgrade Assistant Screens for Oracle Email
| Screen | Description and Recommended Options to Select |
|---|---|
|
Contacts Upgrade |
Review the information in Section 6.4.2.2.1 and select Yes or No. |
The behavior of the Oracle Collaboration Suite Upgrade Assistant depends on the total number of e-mail entries in Oracle Internet Directory. If the number of entries is less than 10,000, then the Oracle Email Upgrade Assistant displays the following message:
The Contacts can be migrated to Oracle Collaboration Suite 10g during this upgrade install. Do you want to perform address book migration?
If the number of entries in Contacts is greater than 10,000, the Oracle Email Upgrade Assistant displays the following message where X is the current number of entries in Contacts:
The Contacts can be migrated to the Oracle Collaboration Suite 10g version during this upgrade install. Currently there are over X contact entries, migration could be time consuming. Do you want to perform contacts migration at this time?
If the number of entries is more than 10,000, Oracle recommends that you perform the address book migration after the upgrade. From the Contacts Upgrade screen, select No and see Section 6.6.4.2 for instructions on performing the migration.
If you choose to migrate the contacts data during the upgrade, the Upgrade Assistant also checks the entry limit and search size limit parameters set for the Oracle Internet Directory server. Depending on these limits and the current number of address book entries, the Upgrade Assistant may prompt you for a orcladmin credential because these limits do not apply to the orcladmin user.
If the Oracle Universal Installer displays a warning to manually run the Oracle Collaborative Portlets after the install, then run the Oracle Collaborative Portlets Configuration Assistant after you have completed the Oracle9iAS Metadata Repository as described in Section 8.8.
The Oracle Universal Installer displays a window to determine the Oracle Content Services domain you want to upgrade.
Table 6-5 Summary of the Oracle Collaboration Suite Upgrade Assistant Screens for Oracle Content Services
| Screen | Description and Recommended Options to Select |
|---|---|
|
This window enables you to specify the Oracle Content Services domain that you want to upgrade. From the Instance Name field, select the Oracle Content Services domain that you want to upgrade. For the selected Oracle Content Services domain, specify the password for the database user SYS and for the Oracle Content Services schema password. |
|
|
Workflow Schema |
If a workflow has been integrated with Content Services, then specify the workflow schema name. The workflow schema can be left empty. |
If errors occur at either stage of the upgrade process, you must correct the conditions that caused them before you try the upgrade again. The following sections provide some guidance in resolving upgrade errors:
Under certain conditions, the Oracle Collaboration Suite Upgrade Assistant cannot perform an upgrade. Among these are that the starting configuration is unsupported, processes are running in the Oracle homes, the Infrastructure services are unavailable, or there is insufficient memory for a large-scale OC4J application upgrade.
This section identifies each condition and its cause(s), and explains how to resolve it.
If the source Oracle home does not appear as expected in the list on the Oracle Homes, suspect one of these conditions: wrong installation type, Oracle homes are on different computers, or the Oracle home is not identified in the inventory of Oracle products. The solution for each of these is detailed below.
Wrong Installation Type The source Oracle home does not appear if the installation type of the source middle tier is not compatible with the installation type of the destination middle tier instance. If this is the case, make sure you have selected the Oracle Collaboration Suite Applications option from the Select A Product to Install screen.
Oracle Homes on Different Computers Another case in which the source middle tier does not appear as a selection is that the source middle tier instance is installed on a different computer from the destination middle tier instance. If this is the case, you must install the destination middle tier instance on the same computer as the source instance to be upgraded.
Oracle Home Not Identified in the Oracle Inventory The Oracle Collaboration Suite Upgrade Assistant locates Oracle Collaboration Suite Oracle homes on your system by analyzing the contents of the Oracle inventory.
Every time you install an Oracle software product on a host computer, Oracle Universal Installer saves information about the software installation on your hard disk. The directories and files that contain this software configuration information are referred to as the Oracle Universal Installer inventory.In some cases, a particular installation may not appear in the inventory. It could be that the inventory directory was deleted or damaged, or it could be that multiple inventories are installed on the computer.
|
See Also: Oracle Universal Installer Concepts for information about the Oracle Universal Installer inventory.Oracle Universal Installer Concepts is available as part of the Oracle Database 10g (10.1.0.2) documentation library available on OTN: http://www.oracle.com/technology/documentation/database10g.html |
If the upgrade fails during the OPMN, OC4J or Oracle HTTP Server upgrade, it is probably because OPMN is still running in one or both instances (source and destination). You must stop OPMN before starting the Oracle Collaboration Suite Upgrade Assistant.
See Section 7.3.2 for instructions on shutting down processes in a source middle tier Oracle home.
|
See Also: "Stopping an Application Tier" in Chapter 2 of Oracle Collaboration Suite Administrator's Guide. |
If the upgrade fails during the examination phase, it is probably because the Infrastructure is unavailable. The Oracle Collaboration Suite Upgrade Assistant needs the Infrastructure services for certain operations, so the Infrastructure must be started before you start the Oracle Collaboration Suite Upgrade Assistant.
|
See Also: "Starting the Infrastructure Tier" in Chapter 2 of Oracle Collaboration Suite Administrator's Guide. |
You can use the Oracle Collaboration Suite Upgrade Assistant log file to determine the cause of examination and upgrade failures.
The Oracle Collaboration Suite Upgrade Assistant log file is located at:
DESTINATION_ORACLE_HOME\upgrade\log\ocsua.log
|
Note: The Oracle Collaboration Suite Upgrade Assistant appends logging data to the existing log file. |
To determine the cause of an examination failure:
Note the name of the failed component in the Oracle Collaboration Suite Upgrade Assistant dialog or command-line output.
Open the following Oracle Collaboration Suite Upgrade Assistant log file:
DESTINATION_ORACLE_HOME\upgrade\log\ocsua.log
Search for the message Starting to examine component_name.
Refer to Appendix D for information about specific error messages in the Upgrade log files.
To determine the cause of an upgrade failure:
Note the name of the failed component in the Oracle Collaboration Suite Upgrade Assistant dialog or command-line output.
Open the Upgrade log file:
DESTINATION_ORACLE_HOME\upgrade\log\ocsua.log
Search for the message Starting to upgrade component_name.
Refer to Appendix D for information about specific error messages in the Upgrade log files.
If the upgrade fails for any Oracle Collaboration Suite application, you can run the Oracle Collaboration Suite Upgrade Assistant again.
To resolve upgrade errors:
Look in the log file specified in the Oracle Collaboration Suite Upgrade Assistant screen for any errors that occurred.
Fix the problems listed in the log file.
Restart the Upgrade Assistant by selecting the application and clicking Retry.
If these steps do not resolve the error, see Appendix D.
This section explains how to perform the tasks that may be necessary to make the newly upgraded 10g Release 1 (10.1.2) instance functional after the Oracle Collaboration Suite Upgrade Assistant has finished executing.
When the upgrade completes, the following applications have additional tasks to perform to complete the upgrade:
After you upgrade a middle tier to Oracle Collaboration Suite 10g Release 1 (10.1.2), the upgraded instance is configured by Oracle Collaboration Suite Upgrade Assistant to use the same ports that were used by the source instance. For this reason, after the upgrade, you cannot start both the source and destination middle tier instances at the same time; otherwise, port conflicts will occur.
Further, note that the portlist.ini file does not reflect the upgraded port settings; instead, it lists the port values assigned by the installer when the destination instance was initially installed. The portlist.ini file can be found in the following location in the destination Oracle home:
DESTINATION_ORACLE_HOME\install\portlist.ini
To illustrate how ports are initially assigned to the new 10g Release 1 (10.1.2) Oracle home and then modified by the Oracle Collaboration Suite Upgrade Assistant, Table 6-6 lists examples of pre- and post-upgrade values for Oracle HTTP Server, Oracle Enterprise Manager 10g Application Server Control Console, and Oracle Application Server Web Cache.
Another way to review the current port settings for the upgraded middle tier is to use the Ports page in the Application Server Control Console for Collaboration Suite. The Ports page lists all the ports that were in use by the Release 1 (9.0.3.1) or Release 2 (9.0.4.2) instance.
To display the Application Server Control Console, enter the following URL in your browser:
http://ocs_host_name:ocs_control_port_number
If you do not know the Application Server Control Console port, you can locate the port number by checking the StandaloneConsoleURL entry in the following configuration file in the upgraded 10g Release 1 (10.1.2) Applications tier Oracle home:
DESTINATION_ORACLE_HOME\sysman\emd\targets.xml
|
See Also: "Changing Applications Tier Ports" in Chapter 14 of Oracle Collaboration Suite Administrator's Guide. |
Table 6-6 Sample Port Values Before and After Upgrade
| Component | Port in Source Oracle Home | Port Value in Destination Oracle Home Assigned by Installer and Recorded in portlist.ini File | Post-Upgrade Port Value |
|---|---|---|---|
|
Port: 7777 Listen: 7778 |
Port: 7783 Listen: 7784 |
Port: 7777 Listen: 7778 |
|
|
Oracle Enterprise Manager 10g Application Server Control Console |
1810 |
1812 |
1156 |
|
Oracle Application Server Web Cache |
Administration: 4000 Invalidation: 4001 Statistics: 4002 |
Administration: 4003 Invalidation: 4004 Statistics: 4005 |
Administration: 4000 Invalidation: 4001 Statistics: 4002 |
After you upgrade a middle tier, use the following passwords in the destination Oracle home:
To log in to the Application Server Control Console, use the ias_admin password you defined during the installation of the destination Oracle home.
To log in to the OracleAS Web Cache Manager, use the OracleAS Web Cache Administrator password you used in the OracleAS Web Cache source Oracle home.
|
Note: The upgrade process does not change the passwords for the Oracle Collaboration Suite Applications schemas.You may want to change them after completing the upgrade. In previous releases, there was no enforcement of rules for creating secure passwords. Oracle Collaboration Suite 10g Release 1 (10.1.2) does enforce rules. If your passwords do not conform to these rules, Oracle recommends that you change them so they are more secure.For more information, see the following documentation: |
The following sections describe tasks for completing the upgrade of Oracle HTTP Server:
If you enabled SSL in the source Oracle home, verify that the component is still configured for secure communications after you have used the Oracle Collaboration Suite Upgrade Assistant.
To verify the proper configuration of your secure Oracle HTTP Server, use the following procedure to check the required values in the opmn.xml and httpd.conf configuration files. Unless both of these files are configured as described in this procedure, you could encounter problems with your SSL configuration:
Use a text editor to open the following OPMN configuration file:
DESTINATION_ORACLE_HOME\opmn\conf\opmn.xml
Locate the following ias-component entry in the opmn.xml file:
<ias-component id="HTTP_Server">
<process-type id="HTTP_Server" module-id="OHS"> <module-data> <category id="start-parameters"> <data id="start-mode" value="ssl-enabled"/> </category> </module-data>
Within the start-parameters category tag, be sure the start-mode parameter is set to ssl-enabled.
This ensures that OPMN starts Oracle HTTP Server in SSL mode.
Use a text editor to open the following Oracle HTTP Server configuration file:
DESTINATION_ORACLE_HOME\Apache\Apache\conf\httpd.conf
Locate the following entry in the httpd.conf file:
<IfDefine SSL>
LoadModule ossl_module libexec/mod_ossl.so
</IfDefine>
In particular, be sure that the LoadModule ossl_module command is surrounded by the <IfDefine SSL> tag. This ensures that Oracle HTTP Server will be started in SSL mode if and only if OPMN directs it to start in SSL mode. Without the surrounding <IfDefine SSL> tag, Oracle HTTP Server starts in SSL mode regardless of whether OPMN has been configured to do so.
In 10g Release 1 (10.1.2), the SSL configuration is controlled by OPMN so it is important that the settings in both the opmn.xml file and httpd.conf file be consistent.
The Oracle Collaboration Suite Upgrade Assistant upgrades the standard settings for the Oracle HTTP Server. If you have configuration files or documents that are in non-standard locations or referenced in non-standard ways, you must upgrade these manually. These, and other specific cases for manual upgrade, are detailed below.
If mod_osso was configured: If mod_osso was configured, then after the upgrade, the osso.conf file continues to use the source Oracle home partner entry in the OracleAS Single Sign-On server. The 10g Release 1 (10.1.2) partner entry in the OracleAS Single Sign-On server is not being used, and will cause a broken link (invalid URL) when the application logs out. You should remove the 10g Release 1 (10.1.2) partner entry. In addition, if the name of the entry in use is obsolete (in that it refers in some way to the source Oracle home), you may wish to rename it.
If there are configuration files in non-default locations: If httpd.conf, mod_oc4j.conf, mod_osso.conf and moddav.conf files are not in the default location, you must upgrade them manually by applying the customizations in the files in the source Oracle home to the files in the destination Oracle home.
If there are custom files and directories referenced by Oracle HTTP Server configuration files: Because the Oracle Collaboration Suite Upgrade Assistant only upgrades specific items, there may be files or directories referred to by directives such as Alias, mod_rewrite, and log directives, such as ErrorLog, that are not present after the upgrade. Ensure that all such items are upgraded manually and exist in the locations expected by the directives. If these files or directives are missing after the upgrade, the Oracle HTTP Server may not start. You can identify errors by starting the Oracle HTTP Server individually after the upgrade, and examining the following file for errors associated with these items:
DESTINATION_ORACLE_HOME\Apache\Apache\logs\error_log
If there are Dynamic Monitoring Service (DMS) configuration elements in the httpd.conf and mod_oc4j.conf files: You must relocate these configuration elements into the dms.conf file.
If Oracle Application Server Web Cache is the first listener: If OracleAS Web Cache is configured as the first listener, ensure that the Oracle HTTP Server directives listed in Table 6-7 have the same values as the corresponding OracleAS Web Cache elements. In particular, note that the Oracle HTTP Server Port directive specifies the port number of a front-end load balancer or reverse proxy. Thus, if OracleAS Web Cache is used, then the Oracle HTTP Server Port directive should have the value of the port on which OracleAS Web Cache is listening.
If you have static documents in the default DocumentRoot directory that you want to upgrade: The Oracle Collaboration Suite Upgrade Assistant locates static document files and directories for upgrade in the location specified in the DocumentRoot directive. The DocumentRoot directive defines the location for static documents and related directories. The base server has a document root location, and each virtual host has one. The Oracle Collaboration Suite Upgrade Assistant copies files under these directories to the destination Oracle home. The default DocumentRoot directory contains demonstration programs and release notes placed there by the installer, so the Oracle Collaboration Suite Upgrade Assistant does not upgrade this directory. You must upgrade this directory manually:
SOURCE_ORACLE_HOME\Apache\Apache\htdocs
To complete the upgrade to Oracle Collaboration Suite 10g Mail, perform the following steps:
To run the e-mail Listener from the upgraded Oracle home:
Navigate to the DESTINATION_ORACLE_HOME directory and execute the following command:
lsnrctl start listener_es
Migrating contacts data involves exporting the address book to LDAP Data Interchange Format (LDIF) files and loading the data in the LDIF files to the Oracle Internet Directory database.
|
Note: Before you migrate contacts data, you can continue to use the existing address book. Once you complete the contacts migration, do not use the old address book. If you have more than one middle tier configured with Oracle Email using the same address book, perform the contacts migration during or after the upgrade of the last middle tier configured with Oracle Email. |
To migrate e-mail contacts to the Oracle Collaboration Suite common address book, perform the steps in the following sections:
Export contacts data to LDIF files using one of the following methods:
To export contacts for all users, enter the following command:
ORACLE_HOME\oes\bin\migrate_emailaddressbook.pl -manual
where ORACLE_HOME is the destination middle tier Oracle home. Follow the on-screen instructions.
Alternatively, to export address book entries for a list of given users:
Create an input file containing the fully qualified e-mail addresses of the users whose contacts data you want to migrate. For example:
user1@oracle.com user2@oracle.com
Enter the following command:
ORACLE_HOME\oes\bin\migrate_emailaddressbook.pl -manual -users_file filename
where ORACLE_HOME is the destination middle tier Oracle home and filename is the name of the input file created in step a. This script exports the contacts data for each user in the input file.
The script prints additional instructions and information to the screen which are based on the type and amount of contacts data. Read these instructions to determine the number of LDIF files generated, the files names and locations, and the method to use to load the data into Oracle Internet Directory.
These instructions use the name ocsv2emailaddressbook_bulkload.ldif and ocsv2emailaddressbook_ldapmodify.ldif for the LDIF file, but there could be multiple files which use different names.
There are two alternative methods for loading the data into the Oracle Internet Directory database using either the bulkload tool or the ldapmodifymt tool. If the migrate_emailaddressbook.pl script prompts you to run bulkload.sh, then perform step 2. If the script prompts you to run the ldapmodifymt command-line tool, then perform step 3.
|
Note: To run thebulkload tool on the Windows operating system, you need one of the following UNIX emulation utilities:
|
To load the contacts data from the LDIF file into the Oracle Internet Directory database:
From the destination middle tier Oracle home, use the ftp utility to copy the LDIF files (such as ocsv2emailaddressbook_bulkload.ldif or ocsv2emailaddressbook_ldapmodify.ldif) to the system where Oracle Internet Directory is running.
Perform either step 2 or step 3, depending on the instructions provided by the migration script.
Use the bulkload tool by performing the following steps:
Shut down Oracle Internet Directory. See Section 7.1.2 for instructions.
Check the input from the LDIF file schema and inconsistency violations and generate the input files by running bulkload.sh with the following options:
ORACLE_HOME/ldap/bin/bulkload.sh -connect oid_connect_string -check -generate path_to_ldif/ocsv2emailaddressbook_bulkload.ldif
where ORACLE_HOME is the destination Infrastructure Oracle home, oid_connect_string is the connect string for the database used by Oracle Internet Directory and path_to_ldif is the absolute path of the LDIF file.
To load the data into the database, run the bulkload.sh command a second time using the -load option:
ORACLE_HOME/ldap/bin/bulkload.sh -connect oid_connect_string -load path_to_ldif/ocsv2emailaddressbook_bulkload.ldif
where ORACLE_HOME is the destination Infrastructure Oracle home, oid_connect_string is the connect string for the Infrastructure database and path_to_ldif is the absolute path of the LDIF file.
Restart Oracle Internet Directory. See Section 7.1.1 for instructions.
Alternatively, use the ldapmodifymt tool to modify entries concurrently. From the destination Infrastructure Oracle home, enter the following command:
ORACLE_HOME\bin\ldapmodifymt -T no_of_threads -h host -p port -D userdn -w password -f path_to_ldif\ocsv2emailaddressbook_ldapmodify.ldif
where:
ORACLE_HOME is the Infrastructure destination Oracle home.
no_of_threads is the number of threads for concurrently processing entries. The value depends on the number of entries. In general, five to ten should be sufficient.
host is the name of the host where Oracle Internet Directory is running.
port is the port where Oracle Internet Directory is running.
userdn is the DN of the Oracle Internet Directory administrator user.
password is the password of the Oracle Internet Directory administrator user.
path_to_ldif is the absolute path to the LDIF file.
Verify the migration by checking the output of the tools for any error messages. You can also log into Oracle Collaboration Suite 10g WebMail as an existing user and check the address book to make sure the contacts have been migrated.
Optionally, after you complete and verify the migration, delete the old email address book entries by entering the following command:
ORACLE_HOME\oes\bin\migrate_emailaddressbook.pl -delete
where ORACLE_HOME is the destination middle tier Oracle home.
|
See Also: Oracle Internet Directory Administrator's Guide 10g Release 2 (10.1.2) for more information about theldapmodifymt and bulkload tools. |
If you chose to continue using the existing Oracle Ultra Search index, a new index will be rebuilt when the crawling schedule is executed. Use the Oracle Ultra Search Administrative Console to check when the crawl is complete then configure Oracle Collaboration Suite 10g Search to use the new index.
To configure Oracle Collaboration Suite 10g Search to use the new index:
Modify the file ORACLE_HOME/j2ee/OC4J_OCSClient/connectors/UltraSearch/UltraSearch/META-INF/oc4j-ra.xml where ORACLE_HOME is the 10g Release 1 (10.1.2) Applications tier Oracle home by setting the value of all variables to the empty string. For example:
variable1="" variable2=""
Remove the cached file ORACLE_HOME/j2ee/OC4J_OCSClient/application-deployments/default/UltraSearch/oc4j-ra.xml from the 10g Release 1 (10.1.2) Applications tier Oracle home.
Restart the OC4J_OCSClient instance by entering the following commands from the Applications tier Oracle home:
$ORACLE_HOME\opmn\bin\opmnctl stopproc process-type=OC4J_OCSClient $ORACLE_HOME\opmn\bin\opmnctl startproc process-type=OC4J_OCSClient
For more information, see the Oracle Ultra Search User's Guide.
These steps are required if you migrated Oracle Ultra Search data using the manual migration scripts. If you want to point your Web search to an instance other than the default WK_INST instance, you should also follow this procedure. Oracle recommends not migrating the configuration data.
After the Applications tier upgrade, perform the following steps:
In Oracle Internet Directory Service Registry, set the WK_INST instance as the default instance by changing its orclstatus to 'default' and changing the orclstatus of the other entries to the empty string.
Update the oc4j-ra.xml file of the Oracle Ultra Search searchlet to point to the manually migrated instance. In the $ORACLE_HOME/j2ee/OC4J_OCSClient/connectors/UltraSearch/UltraSearch/META-INF/o c4j-ra.xml file, modify the following lines:
<config-property name="virtualServiceDn" value="<INSTANCE_DN>"/> <config-property name="connectionURL" value="<JDBC_CONN>"/> <config-property name="userName" value="<USERNAME>"/> <config-property name="password" value="<PASSWORD>"/> <config-property name="instanceName" value="<INST_NAME"/>
Where:
INSTANCE_DN is the Oracle Ultra Search instance's dn string in Oracle Internet Directory
JDBC_CONN is the JDBC connection string to the Oracle Ultra Search instance
USERNAME is Oracle Ultra Search instance schema name
PASSWORD is Oracle Ultra Search instance schema password
INSTANCE_NAME is the Oracle Ultra Search instance name
For example:
<config-property name="virtualServiceDn" value="cn=store:ocs_inst, cn=VirtualServices,cn=UltraSearch,cn=Services,cn=OracleContext>"/> <config-property name="connectionURL" value="<jdbc:oracle:thin:@stana08:1521:store>"/> <config-property name="userName" value="<ocs_us>"/> <config-property name="password" value="<ocs_us>"/> <config-property name="instanceName" value=="ocs_inst"/>
Delete the cached version of the file in $ORACLE_HOME/j2ee/OC4J_OCSClient/application-deployments/default/UltraSearch/oc4j-ra.xml.
Restart the OC4J_OCSClient instance.
When you choose to use the existing index, you can perform searches right away using Oracle Collaboration Suite Search. However, you cannot perform searches right away using the Query application at http://host:port/ultrasearch/query/search.jsp. This is because this application points to the new system and searches will not return correct results until the crawling is completed.
To verify that the crawling is complete:
Access the administrator page at
http://host:port/ultrasearch/admin
Select the instance and click the Schedules tab.
Check every schedule to see if the crawling has completed.
The steps in the following sections are optional:
Perform the steps in this section if all of the following conditions are true:
Oracle Calendar Release 2 (9.0.4.1) or Release 2 (9.0.4.2) server was integrated with Oracle Web Conferencing before the upgrade and Oracle Calendar server and Oracle Web Conferencing are configured in different middle tiers.
Oracle Web Conferencing middle tiers accessed by the upgraded Oracle Calendar server have not been upgraded and remain at Release 2 (9.0.4.2).
If these conditions are true, then to keep the integration between Oracle Calendar 10g Release 1 (10.1.2) server and Oracle Web Conferencing Release 2 (9.0.4.2) working, then modify the [CONFERENCING] parameters in Oracle Calendar's unison.ini file so that they use the Release 2 (9.0.4.2) authentication information to communicate with Oracle Web Conferencing Release 2 (9.0.4.2).
|
Note: Oracle Calendar clients are not able to create new Web conferences until Oracle Web Conferencing is upgraded to Oracle Real-Time Collaboration 10g Release 1 (10.1.2). At that time, restarting Oracle Calendar server enables integration between Oracle Calendar and Oracle Real-Time Collaboration. Alternatively, you can perform the steps in this section, if you do not plan to upgrade Oracle Web Conferencing immediately and want to continue to provide this functionality to users.Oracle Calendar clients are not able to create new Web conferences using Oracle Web Conferencing Release 2 (9.0.4.2). Configuring Oracle Real-Time Collaboration 10g Release 1 (10.1.2) in Oracle Enterprise Manager enables integration between Oracle Calendar and Oracle Real-Time Collaboration. Alternatively, you can perform the steps in this section, if you want to continue to provide this functionality to users on Oracle Web Conferencing Release 2 (9.0.4.2). |
To restore the Release 2 (9.0.4.2) value for siteauthkey:
Back up the initialization file DESTINATION_ORACLE_HOME/ocal/misc/unison.ini where DESTINATION_ORACLE_HOME is the 10g Release 1 (10.1.2) Oracle home.
Set the autodiscovery values to FALSE in the [CONFERENCING] section in unison.ini:
siteauthkey_auto=FALSE enable_auto=FALSE siteid_auto=FALSE url_auto=FALSE actinghostenable_auto=FALSE allowconfuntil_auto=FALSE
From the SOURCE_ORACLE_HOME/ocal/misc/unison.ini file, copy all the values in the [CONFERENCING] section to the same section in DESTINATION_ORACLE_HOME/ocal/misc/unison.ini. For example:
In the DESTINATION_ORACLE_HOME/ocal/misc/unison.ini, change the value of the walletfile parameter to point to the default_wallet directory in the destination Oracle home:
walletfile = file:DESTINATION_ORACLE_HOME/ocal/etc/default_wallet
Copy all the files that are in the ocal/etc/default_wallet directory in the source Oracle home into the same directory in the destination Oracle home.
Restart Oracle Calendar server by entering the following commands where ORACLE_HOME is the 10g Release 1 (10.1.2) Oracle home configured with Oracle Calendar:
$ORACLE_HOME\opmn\bin\opmnctl restartproc ias-component=CalendarServer
Restart Oracle Calendar application system by entering the following commands where ORACLE_HOME is the 10g Release 1 (10.1.2) Oracle home configured with Oracle Calendar:
$ORACLE_HOME\ocas\bin\ocasctl -stopall $ORACLE_HOME\ocas\bin\ocasctl -start $ORACLE_HOME\ocas\bin\ocasctl -start -t ochecklet
Later, when you have upgraded the middle tier configured with Oracle Web Conferencing to 10g Release 1 (10.1.2), restore the [CONFERENCING] settings from the backup copy of the unison.ini file in the 10g Release 1 (10.1.2) Oracle home or set the values listed in step 2 to TRUE. Restart Oracle Calendar using the command in step 6.
If you disabled synchronization of Oracle Calendar address books with the Common Address Book in Oracle Internet Directory as described in Section 6.2.1, you can enable it using one of the following methods.
To perform an incremental synchronization:
In the DESTINATION_ORACLE_HOME/ocal/misc/unison.ini file, locate the [ENG] section and change the value of cab_enable:
cab_enable=TRUE
Restart the Oracle Calendar 10g Release 1 (10.1.2) server by entering the following command:
$ORACLE_HOME\opmn\bin\opmnctl restartproc ias-component=CalendarServer
Alternatively, to perform the synchronization immediately, from the DESTINATION_ORACLE_HOME/ocal/misc/unison.ini directory, enter the following command:
unidssync -absync
|
Note: If you see an increase in CPU usage after the upgrade, it may be due to the Common Address Book synchronization. Check the value of the[CWS]cabsynctime parameter in unison.ini to see if the increase in CPU usage occurs at the times specified by this parameter.
If you find the incremental process is too slow, you can modify the value of the See "About the Common Address Book" in Chapter 5 of Oracle Calendar Administrator's Guide. |
If you customized the user interface of your Oracle Calendar application system, you need to migrate any custom elements listed in ORACLE_HOME/ocas/conf/ocwc.conf such as images, help documents, banners, style sheets and coloring definition to the new Oracle home. However, due to changes in the Oracle Calendar user interface in Oracle Collaboration Suite 10g Release 1 (10.1.2), reusing these elements in the upgraded Oracle Calendar application may not have the same layout as in the previous version.
The following sections describe procedures to consider when upgrading the middle tiers that are part of an OracleAS Web Cache Cluster. Please note that OracleAS Web Cache must be de-clustered before the upgrade, otherwise the upgrade of OracleAS Web Cache will fail:
Using Multiple Versions of OracleAS Web Cache within an OracleAS Web Cache Cluster
Synchronizing the Upgraded OracleAS Web Cache Cluster Configuration
When upgrading an OracleAS Web Cache cluster, you can upgrade one cache cluster member at a time. The caches will continue to function, but because the other cluster members have a different version of the configuration, the caches will not forward requests to cache cluster members operating with a different version.
For example, if you upgrade Cache_A to the current version, but have not yet upgraded Cache_B and Cache_C, Cache_A will not forward requests to the cache cluster members Cache_B and Cache_C.
In this situation, the Operations page in Web Cache Manager indicates that the Operation Needed is Incompatible software version.
After you upgrade each cache cluster member to 10g Release 1 (10.1.2), you must perform the following additional steps to synchronize the configuration for the members of the cluster:
If the caches have not been started, for each upgraded cache, start OracleAS Web Cache and OracleAS Web Cache Manager. On the command line, enter:
opmnctl startproc ias-component=WebCache
This command starts the OracleAS Web Cache cache server process and admin server process.
In a browser, enter the URL for the OracleAS Web Cache Manager for one of the upgraded caches, and, when prompted, enter the username and password for the ias_admin or administrator user.
Note that after you upgrade an OracleAS Web Cache instance, you log into the OracleAS Web Cache Manager using the Administrator password defined when you installed and configured OracleAS Web Cache source Oracle home.
In the navigator frame, select Administration -> Operations.
The Operations page appears.
In the Operations page, click Retrieve Configuration.
Web Cache retrieves the cache-specific configuration information from the remote cache cluster members. Then, Web Cache Manager indicates that the Operation Needed is Propagate Configuration.
To propagate the configuration to all cache cluster members, select All caches and an Interval of Immediate. Then, click Propagate.
Restart the caches by selecting All caches and an Interval. Then, click Restart. (Note that you can perform this operation as you upgrade each cache, or you can perform this operation after all of the cache cluster members have been upgraded.)
A Release 1 (9.0.3.1) or Release 2 (9.0.4.2) cache cannot accept invalidation messages from a 10g Release 1 (10.1.2) cache. In a configuration that uses a OracleAS Web Cache cluster with a mixture of Release 1 (9.0.3.1) or Release 2 (9.0.4.2) and 10g Release 1 (10.1.2) cluster members, you must configure the Load Balancer to send invalidation messages only to the Release 1 (9.0.3.1) or Release 2 (9.0.4.2) members.
When upgrading a cache cluster from Release 2 (9.0.2) to 10g Release 1 (10.1.2), remove cluster members one at a time from the invalidation pool for the Load Balancer prior and upgrade them. Once all the cluster members are upgraded, add them back to the invalidation pool. As an example, assume a configuration with a Load Balancer in front of a cache cluster that is comprised of four members, webche1-host, webche2-host, webche3-host, and webche4-host, all running Release 2 (9.0.4.2). To upgrade this cache cluster:
In the Load Balancer configuration, remove webche1-host from the pool that is responsible for invalidation.
Upgrade webche1-host from Release 2 (9.0.4.2) to 10g Release 1 (10.1.2).
In the Load Balancer configuration, remove webche2-host from the pool that is responsible for invalidation.
Upgrade webche2-host from Release 2 (9.0.4.2) to 10g Release 1 (10.1.2).
In the Load Balancer configuration, remove webche3-host from the pool that is responsible for invalidation.
Upgrade webche3-host from Release 2 (9.0.4.2) to 10g Release 1 (10.1.2).
Upgrade webche4-host from Release 2 (9.0.4.2) to 10g Release 1 (10.1.2). As this is the last cache member in the Load Balancer configuration, it is not necessary to remove it from the invalidation pool.
In the Load Balancer configuration, add webche1-host, webche2-host, and webche3-host back into the pool that is responsible for invalidation.
This section explains how to perform the manual procedures required to complete the Portal upgrade after the Oracle Collaboration Suite Upgrade Assistant has finished processing. It discusses the following topics:
In cases where a Portal instance accessed through the middle-tier is not using the same Oracle Internet Directory that the middle-tier is registered with, some additional steps need to be carried out after upgrade of the middle tier. These steps validate that the Oracle Internet Directory details stored in the OracleAS Portal Dependency Settings File are correct. When you perform an upgrade, not all of the values are available to the upgrade tool and are simply set to a default value.
To verify the Oracle Internet Directory properties:
Open the following file in a text editor:
DESTINATION_ORACLE_HOME\portal\conf\iasconfig.xml
Review the contents of the file for entries that apply to OracleAS Portal.
In particular, note each occurrence of the PortalInstance element within the file. Example 6-1 shows the contents of a typical iasconfig.xml file.
For each PortalInstance element that refers to an Oracle Internet Directory other than the one with which the middle tier is registered, do the following:
Set the LDAPSSLPort property in the OIDDependency element to the SSL port for the Oracle Internet Directory.
Verify that the AdminDN property of the corresponding OIDComponent element is set to the Administration DN of the Oracle Internet Directory.
Verify that the AdminPassword property of the corresponding OIDComponent element is correctly set to the password of the Oracle Internet Directory.
Save your changes and close the iasconfig.xml file.
Encrypt all manually entered password properties using the following command:
DESTINATION_ORACLE_HOME\portal\conf\ptlconfig -encrypt
Refer to the Oracle Application Server Portal Configuration Guide for more information about the iasconfig.xml and the ptlconfig tool.
Example 6-1 Sample Contents of the OracleAS Portal iasconfig.xml File
<IASInstance Name="midtier.abc.company.com" Host="abc.company.com">
<WebCacheComponent AdminPort="4000" ListenPort="80"
InvalidationPort="4001" InvalidationUsername="invalidator"
InvalidationPassword="@BdS/zVGJHrElbOMohqLzurxsPR1au77peA=="
SSLEnabled="false"/>
<EMComponent ConsoleHTTPPort="1811" SSLEnabled="false"/>
</IASInstance>
<IASInstance Name="infra.xyz.company.com" Host="xyz.company.com">
<OIDComponent AdminPassword="welcome1"
AdminDN="cn=orcladmin" SSLEnabled="false" LDAPPort="389"/>
</IASInstance>
<PortalInstance DADLocation="/pls/portal30" SchemaUsername="portal30"
SchemaPassword="welcome1"
connectString="dbserver.company.com:1521:orcl">
<WebCacheDependency ContainerType="IASInstance"
Name="midtier.abc.company.com"/>
<OIDDependency ContainerType="IASInstance" LDAPSSLPort="4339"
Name="infra.xyz.company.com"/>
<EMDependency ContainerType="IASInstance"
Name="midtier.abc.company.com"/>
</PortalInstance>
Any new deployment property files added in the source Oracle home will be copied to the destination Oracle home. However, any property file that is modified from its original installation time values will not be copied. Any changes in those files must be manually applied to the destination Oracle home.
The location of the property file will vary among web providers, and can be located using the service identifier of the web provider. The service identifier identifies a provider within an application. The deployment property files are named according to the following convention:
SOURCE_ORACLE_HOME\j2ee\OC4J_Portal\applications\application_name\ web_application_name\WEB-INF\deployment\service_identifier.properties
For example, the deployment properties for the JPDK sample web provider, whose identifier is sample, reside in:
SOURCE_ORACLE_HOME\j2ee\OC4J_Portal\applications\jpdk\jpdk\WEB-INF\ deployment\sample.properties
To migrate modified deployment properties from the source to the destination Oracle home:
Identify all customized property files (files in which new properties were added or whose default property values were changed) in the source Oracle home.
Copy the customized properties from these property files in the source Oracle home to the corresponding files in the destination Oracle home.
Oracle Voicemail & Fax supports rolling middle tier upgrades. Release 2 (9.0.4.2) middle tiers configured with Oracle Voicemail & Fax are compatible with 10g Release 1 (10.1.2) Applications tiers in the same environment.
|
Note: Oracle recommends that you schedule the upgrade of your middle tiers in stages rather than perform them all at the same time. |
|
Note: Check MetaLink for the latest patches for Oracle Voicemail & Fax 10g Release 1. |
To upgrade Oracle Voicemail & Fax, perform the steps in the following sections:
Section 6.6.9.1, "Preparing to Upgrade Oracle Voicemail & Fax"
Section 6.6.9.2, "Installing Oracle Voicemail & Fax 10g Release 1 (10.1.2)"
Section 6.6.9.3, "Verifying the Installation of Oracle Voicemail & Fax"
Section 6.6.9.6, "Restoring the Oracle Internet Directory Credentials in the Mail Store"
Section 6.6.9.7, "Mapping Attributes from Release 2 (9.0.4.2) to 10g Release 1 (10.1.2)"
Section 6.6.9.8, "Performing Additional Configuration Steps"
Before you upgrade Oracle Voicemail & Fax, perform the following tasks:
Upgrade the Oracle9iAS Infrastructure and the Oracle Collaboration Suite Information Storage Databases used by Oracle Voicemail & Fax according to the instructions in Oracle Collaboration Suite Upgrade Guide.
When you upgrade these components:
Oracle Internet Directory schemas are upgraded with the 10g Release 1 (10.1.2) Oracle Voicemail & Fax attributes and several new Oracle Internet Directory objects are added.
Oracle Voicemail & Fax schemas in the Oracle Collaboration Suite Information Storage Database are upgraded.
Upgrade middle tiers configured with Oracle Mail to Oracle Collaboration Suite according to the instructions in Oracle Collaboration Suite Upgrade Guide.
If you are already using Oracle Enterprise Manager 10g Management Service, then upgrade it from 10.1.0.3 to 10.1.0.4.
Otherwise, install Oracle Enterprise Manager 10g (10.1.0.4) Management Service in your environment. Oracle Enterprise Manager 10g is required because you need it to manage Oracle Voicemail & Fax.
See Oracle Enterprise Manager Grid Control Installation and Basic Configuration.
To install Oracle Voicemail & Fax 10g Release 1 (10.1.2) in a new Oracle home:
Back up the Oracle home on the middle tier configured with Oracle Voicemail & Fax. You should already have backed up the Oracle9iAS Infrastructure before upgrading it. You will use the process entries in the Release 2 (9.0.4.2) Oracle Internet Directory later to reconfigure the 10g Release 1 (10.1.2) Oracle Internet Directory objects.
From Services, stop and disable all services starting with UM as well as the rmid and rmiregistry services in the middle tier Oracle home configured with Oracle Voicemail & Fax.
Back up the sc_vsto.cfg file. Make a copy of the file and name it sc_vsto.cfg.bak. A new sc_vsto.cfg file is re-created when you restart the system.
The sc_vsto.cfg file is located in the CT server container directory. By default, it is installed in C:\Documents and Settings\All Users\Application Data\Dialogic\CT Media\Containers. If it is not in the default location, check the value of HKEY_LOCAL_MACHINE\\Software\\Dialogic\\CT Media\\2.0\\Server\\Environment\\LocalContainerPath in the Windows registry.
If Oracle Management Agent is already installed on the system, stop its processes and install the 10.1.0.4 patch for Oracle Management Agent.
Otherwise, install Oracle Management Agent 10.1.0.4 in its own Oracle home on the system running Oracle Voicemail & Fax.
Restart the system where Oracle Voicemail & Fax is installed.
Ensure that the NetMerge Converged Communications Server or CT Media Server is set to level 5 (calls enabled).
Ensure that Oracle Management Agent is up and running.
Follow the instructions in Section 3, "Installing Oracle Real-Time Collaboration and Oracle Voicemail & Fax" of the Oracle Voicemail & Fax and Oracle Web Conferencing Conversion Servers Installation and Upgrade Guide and install Oracle Voicemail & Fax 10g Release 1 (10.1.2) in a new Oracle home.
Reboot the Oracle Voicemail & Fax Applications tier so that the updated NetMerge settings take effect.
If this is the first middle tier configured with Oracle Voicemail & Fax that you are upgrading, then upgrade your site and user data by following the procedure in Section 6.6.9.5.
If this is the last middle tier configured with Oracle Voicemail & Fax that you are upgrading, restore the Oracle Internet Directory credentials in the mail store by following the procedure in Section 6.6.9.6.
Installing Additional Oracle Voicemail & Fax Middle Tiers
To upgrade additional Oracle Voicemail & Fax middle tiers, repeat the steps in Section 6.6.9.2 on the systems running those middle tiers. During the installation process, you can choose to create a new PBX-Application cluster. Or you can choose to use an existing PBX-Application Cluster if this Oracle Voicemail & Fax system will communicate with the same PBX as a previously installed Oracle Voicemail & Fax 10.1.2 Applications tier.
To reuse an existing PBX-Application Cluster, select the same PBX-Application Cluster that you created during the installation of the first Oracle Voicemail & Fax instance.
When the installation completes, verify that you can access the Oracle Voicemail & Fax custom Oracle Enterprise Manager Grid Control pages.
Log in to Grid Control and select the Oracle Voicemail & Fax Group target whose name matches the one you entered during the interview phase of the install. If this is your first time accessing this target, then you will be prompted for Oracle Internet Directory login credentials to view these pages. Enter the Oracle Internet Directory user name and password. Leave the Save as Preferred Credential box selected. The Oracle Internet Directory user name can be cn=orcladmin, the Oracle Internet Directory superuser.
After installing Oracle Voicemail & Fax 10g Release 1 (10.1.2) in a new Oracle home, configure the PBX-Application Cluster that you created during the installation process.
For more information on configuring a PBX-Application Cluster, see "Configuring the PBX-Application Cluster" in Chapter 2 and "Configuring PBX-Application Clusters" in Chapter 3 of Oracle Voicemail & Fax Administrator's Guide.
The term site is a new concept in Oracle Voicemail & Fax 10g Release 1 (10.1.2). A site is an extension of a Release 2 (9.0.4.2) group with a physical location assigned to it. It differs from a Release 2 (9.0.4.2) group because users belonging to the site must be assigned phone numbers that belong to that site. In Release 2 (9.0.4.2), there was no such restriction, and groups were not tied to a physical location or to phone numbers belonging to a physical location. Therefore, in Release 2 (9.0.4.2), you could have users with Chicago phone numbers and users with San Francisco phone numbers belonging to the same group. In 10g Release 1, the Chicago users would be in a separate group from the San Francisco users.
When upgrading from Release 2 (9.0.4.2) to 10g Release 1 (10.1.2), you must convert some Release 2 (9.0.4.2) groups to sites, and move all 9.0.4.2 users, based on their phone numbers, under the correct sites. Oracle Voicemail & Fax provides a tool, upgradeOVFGroupsAndUsers.bat, to accomplish this task. You can run this tool from any upgraded Oracle Voicemail & Fax Applications tier, but you cannot use Oracle Voicemail & Fax 10g Release 1 (10.1.2) until the upgrade tool has been run, and the users have been moved to the new sites and groups. You first create a site input file and then run the upgrade script, providing the input file as a parameter.
Creating a Site Input File
The site input file contains information about the 9.0.4.2 groups that should be updated to sites and any additional information about these sites.
The format of this file is shown in the following example:
SiteName=hq.us.oracle.com ExtensionLength=5 LocalNumDigits=10 PBXName=HQ Nortel PBXConnectionType=SMDI PhoneNumberSets=1650506????:1650607????:1650633????
In the preceding format:
SiteName is the name of the Release 2 (9.0.4.2) group to be converted to a site.
The value must be non-null and non-empty and correspond to a group that exists in Oracle Internet Directory.
ExtensionLength is the length of all extensions at this site. This value allows users to identify their phone numbers using a shortened version of the full phone number.
The value must be non-null, non-empty and non-negative.
LocalNumDigits is the number of digits in a local phone number for this site. This value is used by the system when announcing a caller's phone number. A shortened version of the phone number is used instead of specifying the whole international phone number.
The value must be non-negative. If not provided, the default value is 0.
PBXName is the name of the PBX-Application Cluster to which users at this site belong.
The value must be non-null and non-empty.
PBXConnectionType is the integration type for this PBX-Application Cluster.
The value should be either SMDI or CTMedia. Any other values cause the script to display a warning, though the script will still run. The value must be non-null and non-empty. You can change these values later using the Enterprise Manager Grid Control console.
PhoneNumberSets restricts the phone numbers that users belonging to this site and PBX-Application Cluster may have.
The value must be non-null and non-empty. The pattern may include digits, question marks (?), a hyphen (-), or an asterisk (*).
The asterisk (*) represents one or more digits and can only appear once at the end of the pattern, if at all. Hyphens (-) are used to prefix a phone number pattern to differentiate multiple PBXes connecting to the same server using a VoIP gateway. The question mark (?) represents a single digit and can appear anywhere in the pattern.
Repeat this information in the same file for all groups you want upgraded. Ensure that no group specified in the SiteName field is the parent of any other group in the file.
The upgrade tool performs validation checks according to the criteria specified for each field. If any validation check fails, the tool does not run.
Running the Group and User Upgrade Tool
To run the upgrade tool, enter the following commands in sequence from the 10g Release 1 (10.1.2) Oracle home:
%ORACLE_HOME%\um\scripts\upgrade\upgradeOVFGroups %ORACLE_HOME%
um\scripts\upgrade\upgradeOVFGroupsAndUsers.bat oracle_home site_input_file SiteChange UpgradeUsers QueryParent
In the first of the preceding commands:
oracle_home is the Oracle home configured with Oracle Voicemail & Fax 10g Release 1 (10.1.2) Oracle home.
site_input_file is the name of the file created in Creating a Site Input File. This file can be in any directory as long as you specify the full path and file name.
SiteChange is a boolean argument that indicates whether the groups in the input file should actually be converted to sites. If this argument is true, then the following actions take place for each group in the site input file:
The group specified by SiteName is converted to a site, if it is not already a site, and the ExtensionLength and LocalNumDigits are set for this site.
A PBX-Application Cluster is created in Oracle Internet Directory, if it does not yet exist, with the specified PBXName. The Oracle Internet Directory object is created under the container cn=PBXes,cn=UMContainer,cn=Products,cn=OracleContext.
A PhoneNumberDescription object is created in Oracle Internet Directory under the container cn=Phone Numbers,cn=UMContainer,cn=Products,cn=OracleContext.
|
Note: Rerunning this tool with this argument set totrue should not result in an error unless the name of the PBX-Application Cluster is changed. |
UpgradeUsers is a boolean argument that should be set to true if you want all users under the groups specified in the site input file to be upgraded from Release 2 (9.0.4.2) to 10g Release 1 (10.1.2).
For example, if the site input file contains one group, hq.us.oracle.com, then setting this argument to true instructs the tool to match each user under hq.us.oracle.com with the correct site based on his or her phone number. User objects under hq.us.oracle.com that have a phone number belonging to the hq.us.oracle.com site will remain in the same place in Oracle Internet Directory. User objects under hq.us.oracle.com that have a phone number that does not belong to hq.us.oracle.com will be moved under other sites in Oracle Internet Directory.
QueryParent is a boolean argument similar to the UpgradeUsers flag. This flag is only relevant if the UpgradeUsers flag is also true. If this flag is set to true then the tool, in addition to upgrading users under the groups in the input file, will upgrade users belonging to the parents of those groups.
For instance, suppose the site input file contains one group, hq.us.oracle.com. If this flag is set to true, and the UpgradeUsers flag is also set to true, then the tool will look for users directly under the groups us.oracle.com, oracle.com, and com. It will then try to move each of these users to the right site.
For example, if the 10g Release 1 (10.1.2) Oracle home is c:\product\10.1.2\ocs_1, then the commands are:
cd c:\product\10.1.2\ocs_1 um\scripts\upgrade\upgradeOVFGroupsAndUsers.bat c:\product\10.1.2\ocs_1 siteinput.txt true true true
The tool logs messages to the file ORACLE_HOME\um\log\Verification\log.xml.
In addition, the tool produces error logs for users who cannot be moved to the correct site. There are two types of error logs, one for users under a site who cannot be matched to the correct site, and one for users who are matched to the correct site but cannot be moved to that site.
These logs files are located in the ORACLE_HOME\um\scripts directory and have an .error extension. For example, suppose you run the tool and see the following error log files:
hq.us.oracle.com.error
This file contains users under hq.us.oracle.com who cannot be matched to any existing site in the system. It could also include users for which there was an unexpected Oracle Internet Directory or configuration error.
oracle.com-hq.us.oracle.com.error
This file contains users who should have been moved from oracle.com to hq.us.oracle.com; however, an unexpected error occurred while moving these users.
|
Note: For each of the users in the.error files, you should check the ORACLE_HOME\um\log\Verification\log.xml for more detailed information. |
You can rerun the tool after fixing any issues found in the error logs.
When you install Oracle Voicemail & Fax, by default, oracle.com is assigned as the default domain name for the root group. You will need to change the default domain name of the root group to the domain name for your company.
To change the default domain name:
From Enterprise Manager Grid Control, navigate to the Voicemail & Fax home page and click the Administration tab.
Click the Go To Task icon of the Manage Groups and Sites task.
In the Manage Groups and Sites page, click the root group.
On the Edit Group or Site page, change the Default Domain Name from oracle.com to the domain name for your company.
Click OK.
|
Note: If you have more than one domain, you will need to set the Default Domain Name property for each domain. Set this property fro the group at the highest level hierarchy that includes all users in that domain. |
Perform the steps in this section after the last Oracle Voicemail & Fax middle tier is upgraded.
After the mail store was upgraded, you changed the Oracle Internet Directory access user name and password created by the 10g Release 1 (10.1.2) upgrade. After the last middle tier has been upgraded, reset the password for the 10g Release 1 (10.1.2) user name in Oracle Internet Directory using the Oracle Directory Manager tool. Then, restore the Oracle Internet Directory credentials in the mail store.
To reset the password in Oracle Internet Directory:
Ensure that Oracle Internet Directory is running.
Start Oracle Directory Manager by entering the following command from the Oracle Collaboration Suite 10g Infrastructure Oracle home:
bin/oidadmin
When prompted, enter the user name, password, and name of the server and port where Oracle Internet Directory is running. By default, the user name is cn=orcladmin and the port is 389.
Click Login. The Oracle Directory Manager appears.
In the navigator pane on the left side, locate the Entry Management tree item and click the plus (+) sign next to it to view its subcomponents. Repeat this step for the cn=OracleContext, cn=Products, cn=EMailServerContainer, cn=um_system and cn=MailStores tree items.
Locate and expand the entry of the upgraded Oracle Collaboration Suite 10g Database hosting the mail store by its global database name. The entry has the form "cn=db_global_name".
Select the cn=emailisinstance entry. In the userpassword attribute field, enter a new password.
Click Apply.
Exit Oracle Directory Manager by selecting File, Exit.
To restore the Oracle Internet Directory credentials in the mail store:
Log into the upgraded mail store (now a Oracle Collaboration Suite 10g Database) as the es_mail user.
At the SQL*Plus prompt, enter the following command:
begin
UMAdminInfo.set_info ('cn=emailisinstance, cn=infostore_db_global_name,
cn=MailStores, cn=um_system, cn=EMailServerContainer, cn=Products,
cn=OracleContext', 'password', 'ldaphost', ldapport);
end;
In the preceding command:
infostore_db_global_name is the global database name of the upgraded Oracle Collaboration Suite 10g Database.
password is the password you created in Step 6.
ldaphost is the name of the host where Oracle Internet Directory is running.
ldapport is the port where the upgraded Oracle Internet Directory is running.
The following message appears:
PL/SQL Procedure successfully completed.
When you upgrade Oracle Voicemail & Fax, you must manually reconfigure the attributes in the 10g Release 1 (10.1.2) installation. Many of the attributes have been combined, or moved, or both to different objects.
Refer to Oracle Voicemail & Fax Administrator's Guide to understand how attributes can be set at a higher level to be inherited by child processes.
This section summarizes the names and locations of attributes in Oracle Voicemail & Fax Release 2 (9.0.4.2), and how they can be accessed in 10g Release 1 (10.1.2) using Oracle Enterprise Manager 10g Grid Control.
This section includes the following tables:
To find the Oracle Voicemail & Fax Release 2 (9.0.4.2) attribute in 10g Release 1 (10.1.2):
Use Enterprise Manager Grid Control to navigate to the page specified in the Page Name column.
Some properties can be set at more than one level in the Oracle Voicemail & Fax hierarchy. In these instances, two or more pages are listed where the parameter can be edited. The pages are listed, in order, from the higher to lower levels in the hierarchy.
In some instances, the parameter is found on the page specified in the Page Name column. However, in most instances, parameters are organized into categories on the page. Look for the 10g Release 1 (10.1.2) parameter under the category specified in the Parameter Category column.
If a 10g Release 1 (10.1.2) property can be edited at more than one level in the hierarchy, in most instances, the category under which you find the parameter will be the same.
For example, in Table 6-8, the Container_ORCL_WriteChunkSize parameter can be set at the Voicemail & Fax level on the Configure Global Process Settings page or at the Voicemail & Fax Application Level on the Voicemail & Fax Administration page. On either page, the parameter is found under the Database Buffers category.
Table 6-8 summarizes the mappings of mail store parameters.
Table 6-8 Mail Store Parameters
| Name | Release 2 (9.0.4.2) | 10g Release 1 (10.1.2) Oracle Enterprise Manager Grid Control | |
|---|---|---|---|
| Page Name | Parameter Category | ||
|
|
sc_vsto.cfg |
|
Database Buffers |
|
|
sc_vsto.cfg |
|
Database Buffers |
|
|
sc_vsto.cfg |
|
Not applicable |
|
|
sc_vsto.cfg |
|
Not applicable |
|
|
sc_vsto.cfg |
|
Not applicable |
|
|
sc_vsto.cfg |
Set Application Password |
Not applicable |
|
|
sc_vsto.cfg |
Does not need to be edited |
Not applicable |
|
|
sc_vsto.cfg |
Does not need to be edited |
Not applicable |
|
|
sc_vsto.cfg |
Does not need to be edited |
Not applicable |
|
|
multiple Oracle Internet Directory process objects |
|
Not applicable |
|
|
Recovery Oracle Internet Directory object |
No longer required. |
Not applicable |
Table 6-9 summarizes the mappings of PBX integration parameters from Release 2 (9.0.4.2) to 10g Release 1 (10.1.2).
Table 6-9 PBX Integration Parameters
| Name | Release 2 (9.0.4.2) | 10g Release 1 (10.1.2) Oracle Enterprise Manager Grid Control | |
|---|---|---|---|
| Page Name | Parameter Category | ||
|
|
multiple Oracle Internet Directory process objects |
PBX-Application Cluster Administration |
PBX Integration |
|
|
multiple Oracle Internet Directory process objects |
PBX-Application Cluster Administration |
PBX Integration |
|
|
multiple Oracle Internet Directory process objects |
PBX-Application Cluster Administration |
PBX Integration |
|
|
multiple Oracle Internet Directory process objects |
PBX-Application Cluster Administration |
PBX Integration |
Table 6-10 summarizes the mappings of general Oracle Internet Directory process parameters from Release 2 (9.0.4.2) to 10g Release 1 (10.1.2).
Table 6-10 General Oracle Internet Directory Process Parameters
| Name | Release 2 (9.0.4.2) | 10g Release 1 (10.1.2) Oracle Enterprise Manager Grid Control | |
|---|---|---|---|
| Page Name | Parameter Category | ||
|
|
multiple Oracle Internet Directory process objects |
|
Log |
|
|
multiple Oracle Internet Directory process objects |
|
Log |
|
|
multiple Oracle Internet Directory process objects |
|
Log |
|
|
multiple Oracle Internet Directory process objects |
Voicemail & Fax Application Administration |
Log |
|
|
multiple Oracle Internet Directory process objects |
Configure Global Process Settings |
Internet Directory |
|
|
multiple Oracle Internet Directory process objects |
|
Internet Directory |
|
|
multiple Oracle Internet Directory process objects |
|
Internet Directory |
|
|
multiple Oracle Internet Directory process objects |
|
Telephony Server |
|
|
multiple Oracle Internet Directory process objects |
Service Administration Page corresponding to Oracle Internet Directory object |
Telephony Server |
|
|
multiple Oracle Internet Directory process objects |
Service Administration Page corresponding to Oracle Internet Directory object |
Telephony Server |
|
|
multiple Oracle Internet Directory process objects |
|
Telephony Server |
|
|
multiple Oracle Internet Directory process objects |
Voicemail & Fax Application Administration |
Telephony Server |
|
|
multiple Oracle Internet Directory process objects |
Service Administration Page corresponding to Oracle Internet Directory object |
Telephony Server |
|
|
multiple Oracle Internet Directory process objects |
|
Internet Directory |
|
|
multiple Oracle Internet Directory process objects |
|
Internet Directory |
|
|
multiple Oracle Internet Directory process objects |
|
Internet Directory |
|
|
multiple Oracle Internet Directory process objects |
|
Internet Directory |
|
|
multiple Oracle Internet Directory process objects |
|
Internet Directory |
|
|
multiple Oracle Internet Directory process objects |
|
Internet Directory |
Table 6-11 summarizes the mappings of attendant process parameters from Release 2 (9.0.4.2) to 10g Release 1 (10.1.2).
Table 6-11 Attendant Process Parameters
| Name | Release 2 (9.0.4.2) | 10g Release 1 (10.1.2) Oracle Enterprise Manager Grid Control |
|---|---|---|
|
|
Attendant Oracle Internet Directory object |
On the Manage Groups and Sites page, choose the Root group. |
Table 6-12 summarizes the mappings of routing process parameters from Release 2 (9.0.4.2) to 10g Release 1 (10.1.2).
Table 6-12 Routing Process Parameters
| Name | Release 2 (9.0.4.2) | 10g Release 1 (10.1.2) Oracle Enterprise Manager Grid Control | |
|---|---|---|---|
| Page Name | Parameter Category | ||
|
|
Routing Oracle Internet Directory object |
PBX-Application Cluster Administration |
Interactive Voice Response (IVR) |
|
|
Routing Oracle Internet Directory object |
Routing Service Administration |
General |
Table 6-13 summarizes the mappings of recovery process parameters from Release 2 (9.0.4.2) to 10g Release 1 (10.1.2).
Table 6-13 Recovery Process Parameters
| Name | Release 2 (9.0.4.2) | 10g Release 1 (10.1.2) Oracle Enterprise Manager Grid Control | |
|---|---|---|---|
| Page Name | Parameter Category | ||
|
|
Recovery Oracle Internet Directory object |
Voicemail & Fax Application Administration |
Recovery Process |
|
|
Recovery Oracle Internet Directory object |
|
Recovery Process |
Table 6-14 summarizes the mappings of MWI process parameters from Release 2 (9.0.4.2) to 10g Release 1 (10.1.2).
Table 6-14 MWI Process Parameters
| Name | Release 2 (9.0.4.2) | 10g Release 1 (10.1.2) Oracle Enterprise Manager Grid Control | |
|---|---|---|---|
| Page Name | Parameter Category | ||
|
|
MWI Oracle Internet Directory object |
PBX-Application Cluster Administration |
MWI Phone Number Conversion |
|
|
MWI Oracle Internet Directory object |
PBX-Application Cluster Administration Page |
Phone Numbers |
|
|
MWI Oracle Internet Directory object |
PBX-Application Cluster Administration Page |
MWI Phone Number Conversion |
Table 6-15 summarizes the mappings of retrieval process parameters from Release 2 (9.0.4.2) to 10g Release 1 (10.1.2).
Table 6-15 Retrieval Process Parameters
| Name | Release 2 (9.0.4.2) | 10g Release 1 (10.1.2) Oracle Enterprise Manager Grid Control | |
|---|---|---|---|
| Page Name | Parameter Category | ||
|
|
Retrieval Oracle Internet Directory object |
Manage Groups and Sites |
Password Length |
|
|
Retrieval Oracle Internet Directory object |
Manage Groups and Sites |
Password Length |
Table 6-16 summarizes the mappings of recording process parameters from Release 2 (9.0.4.2) to 10g Release 1 (10.1.2).
Table 6-16 Recording Process Parameters
| Name | Release 2 (9.0.4.2) | 10g Release 1 (10.1.2) Oracle Enterprise Manager Grid Control | |
|---|---|---|---|
| Page Name | Parameter Category | ||
|
|
Recording Oracle Internet Directory object |
|
Recording Process |
|
|
Recording Oracle Internet Directory object |
PBX-Application Cluster Administration |
Recording Process |
Table 6-17 summarizes the mappings of SMDI process parameters from Release 2 (9.0.4.2) to 10g Release 1 (10.1.2).
Table 6-17 SMDI Process Parameters
| Name | Release 2 (9.0.4.2) | 10g Release 1 (10.1.2) Oracle Enterprise Manager Grid Control | |
|---|---|---|---|
| Page Name | Parameter Category | ||
|
|
smdi.properties |
SMDI Monitor Service Administration |
SMDI |
|
|
smdi.properties |
SMDI Monitor Service Administration |
SMDI |
|
|
smdi.properties |
SMDI Monitor Service Administration |
SMDI |
|
|
smdi.properties |
SMDI Monitor Service Administration |
SMDI |
|
|
smdi.properties |
SMDI Monitor Service Administration |
SMDI |
|
|
smdi.properties |
SMDI Monitor Service Administration |
SMDI |
|
|
smdi.properties |
SMDI Monitor Service Administration |
SMDI |
|
|
smdi.properties |
SMDI Monitor Service Administration |
SMDI |
|
|
smdi.properties |
SMDI Monitor Service Administration |
SMDI |
Table 6-18 summarizes the mappings of group and user process parameters from Release 2 (9.0.4.2) to 10g Release 1 (10.1.2).
Table 6-18 Group and User Parameters
| Name | Release 2 (9.0.4.2) | 10g Release 1 (10.1.2) Oracle Enterprise Manager Grid Control | |
|---|---|---|---|
| Page Name | Parameter Category | ||
|
|
Group and User Oracle Internet Directory objects |
Manage Groups and Sites |
General |
|
Manage Voicemail Account |
Not Applicable |
||
|
|
Group and User Oracle Internet Directory objects |
Manage Groups and Sites |
General |
|
Manage Voicemail Accounts |
Not applicable |
||
|
|
Group and User Oracle Internet Directory objects |
Manage Groups and Sites |
Feature Access |
|
Manage Voicemail Accounts |
Not applicable |
||
|
|
Group and User Oracle Internet Directory objects |
Manage Groups and Sites |
Feature Access |
|
Manage Voicemail Accounts |
|||
|
|
Group Oracle Internet Directory object |
Manage Groups and Sites |
General |
|
|
Group Oracle Internet Directory object |
Manage Groups and Sites |
Site |
|
|
|
Manage Voicemail Accounts |
Not Applicable |
Table 6-19 summarizes the mappings of other parameters from Release 2 (9.0.4.2) to 10g Release 1 (10.1.2).
Table 6-19 Other Parameters
| Name | Release 2 (9.0.4.2) | 10g Release 1 (10.1.2) Oracle Enterprise Manager Grid Control | |
|---|---|---|---|
| Page Name | Parameter Category | ||
|
|
Recording, Retrieval Oracle Internet Directory objects |
Manage Groups and Sites |
Greeting |
|
|
Recording, Retrieval Oracle Internet Directory objects |
Manage Groups and Sites |
Message |
|
|
multiple Oracle Internet Directory process objects |
Manage Groups and Sites |
General |
|
|
Recording Oracle Internet Directory object |
No longer needed |
Not applicable |
|
|
multiple Oracle Internet Directory process objects |
Manage Groups and Sites |
Look under the Site category for the Mailbox Extension Length parameter |
|
|
multiple Oracle Internet Directory process objects |
Manage Groups and Sites |
Look under the Site category for the Length of Local Phone Number parameter |
|
|
Fax, Recording, Retrieval Oracle Internet Directory objects |
|
Telephone Number Translation Rules (for mailbox numbers) |
|
Telephone Number Translation Rules (for numbers passed to Oracle Voice Mail & Fax through PBX) |
||
|
|
multiple Oracle Internet Directory process objects |
PBX-Application Cluster Adminstration |
Telephone Number Translation Rules |
|
|
multiple Oracle Internet Directory process objects |
PBX-Application Cluster Adminstration |
Telephone Number Translation Rules |
|
|
multiple Oracle Internet Directory process objects |
Manage Groups and Sites |
Message |
|
|
multiple Oracle Internet Directory process objects |
Manage Groups and Sites |
Message |
|
|
multiple Oracle Internet Directory process objects |
Manage Groups and Sites |
Greeting |
|
|
multiple Oracle Internet Directory process objects |
Manage Groups and Sites |
Greeting |
|
|
Recording Oracle Internet Directory process object |
Manage Groups and Sites |
Directory Lookup |
|
|
|
Manage Groups and Sites |
Directory Lookup |
Refer to Chapters 2 and 3 of Oracle Voicemail & Fax Administrator's Guide for information on the additional configuration steps required.
Reconfiguring Customized Menu Settings
The Release 2 (9.0.4.2) menu is not compatible with the 10g Release 1 (10.1.2) menu. Therefore, if you customized the Release 2 (9.0.4.2) menu and you are upgrading to 10g Release 1 (10.1.2), then you will need to edit the 10g Release 1 (10.1.2) menus.xml file with the changes that were made to the Release 2 (9.0.4.2) menus.xml file. In both releases, this file is located in the ORACLE_HOME\um\xml directory.
For more information, see "Customizing Oracle Voicemail & Fax Menus" in Chapter 7 of the Oracle Voicemail & Fax Administrator's Guide.
The following sections provide information on upgrading the Oracle Application Server Wireless Middle Tier from Release 2 (9.0.2) or 10g (9.0.4) to 10g (10.1.2):
Section 6.6.10.1, "Using the Oracle Application Server Wireless Notification Service Upgrade Script"
Operating OracleAS Wireless Release 2 (9.0.2), 10g (9.0.4), and 10g (10.1.2) Middle Tiers Together
|
See Also: Oracle Application Server Wireless Developer's Guide for information on any unfamiliar concepts introduced here, and for information on configuration and development of OracleAS Wireless applications |
|
Note: New OracleAS Wireless features added for the 10g (10.1.2) release will not be available until you upgrade the OracleAS Metadata Repository to 10g (10.1.2). For more information, see Chapter 8, "Upgrading the Oracle9iAS Metadata Repository". |
This section explains how to upgrade notifications created by the OracleAS Wireless Release 2 (9.0.2) Notification Engine in the OracleAS Wireless System Manager. The architecture and functionality of the Notification Engine are not described here.
This procedure is not necessary if you are upgrading from 10g (9.0.4).
You can upgrade notifications from Release 2 (9.0.2) to 10g Release 1 (10.1.2.2) with the migrateNotifications.bat script. To execute the script:
Navigate to DESTINATION_ORACLE_HOME\wireless\bin.
Set the ORACLE_HOME environment variable to the 10g Release 1 (10.1.2.2) Oracle home.
Issue one of the commands below:
migrateNotifications.bat -name deprecated master alert name(s) -owner owner user name
migrateNotifications.bat -oid deprecated master alert oid -owner owner user name
The script does the following:
Creates a new master alert service named old master alert name_New. (This process involves converting the message template to a valid mobile xml, if necessary.)
Creates the folder \master\notifications, if it does not exist.
Creates the master service old master alert name_MS.
Creates a mapping for the new master alert and the new master service based on the message template for the old master alert.
Creates the folder \Users Home\username\notifications, if it does not exist.
Discovers all associated 9.0.2.x AlertService objects and converts them to link objects. (The top-level authorization is flattened to link level authorization during this process.)
Transforms all subscriptions for alert services converted.
The following command upgrades all 9.0.2.x master alert services whose name starts with StockAlert (e.g., StockAlertNews, StockAlertWarning, etc.). All new objects will be owned by the orcladmin user.
migrateNotifications.bat -name StockAlert% -owner orcladmin
The following command upgrades the 9.0.2.x master alert service with the name StockAlert, and assigns all new objects to the systemadmin user.
migrateNotifications.bat -name StockAlert -owner systemadmin
The following command upgrades the 9.0.2.x master alert service with the object ID 1973, and assigns all new objects to the systemadmin user.
migrateNotifications.bat -oid 1973 -owner systemadmin
To complete the upgrade of Oracle Application Server Wireless, perform the steps in this section after the Oracle Universal Installer and Oracle Collaboration Suite Upgrade Assistants complete. During the upgrade, a unique constraint is added to Oracle Internet Directory. The unique constraint is set on the orclWirelessAccountNumber attribute of the orclUserV2 object class which enables wireless voice authentication. Restarting Oracle Internet Directory enables the changes made by the upgrade to take affect.
To restart Oracle Internet Directory:
On the system running Oracle Internet Directory, set the ORACLE_HOME environment variable to the upgraded Infrastructure Oracle home.
Restart the Oracle Internet Directory server and the OC4J instance:
$ORACLE_HOME\opmn\bin\opmnctl restartproc ias-component=OID $ORACLE_HOME\opmn\bin\opmnctl restartproc ias-component=OC4J
You can operate an environment with Oracle9iAS Wireless Release 2 (9.0.2) and OracleAS Wireless 10g (10.1.2) middle tiers using the same Infrastructure services. However, this configuration is subject to some restrictions, as described below.
J2ME download and XHTML/XForms based applications should not be used in a mixed environment. These features are new in OracleAS Wireless 10g (10.1.2), and would cause errors when attempting to access them from any of the Oracle9iAS Wireless Release 2 (9.0.2) middle tiers. If you wish to use these features, then it is necessary to upgrade all middle tiers to OracleAS Wireless 10g (10.1.2).
The Notification Engine cannot be used in a mixed environment. Instead, you should use the Alert Engine.
Service access point (service-level address) should be created through an OracleAS Wireless 10g (10.1.2) middle tier, in order for them to be visible to both the OracleAS Wireless 10g (10.1.2) middle tiers and Oracle9iAS Wireless Release 2 (9.0.2) middle tiers.
OracleAS Wireless 10g (10.1.2) supports user name case sensitivity. However, this requires that you upgrade the Oracle Internet Directory to Oracle Application Server 10g (10.1.2).
If you change (add, delete, or update) a 10g (10.1.2) ASK Access point, the changes you make will not be reflected in the Release 2 (9.0.2) Enterprise Manager Web site until the Release 2 (9.0.2) Enterprise Manager Web site and the OC4J_Wireless OC4J instance is restarted.
Specifically, a driver account (for example, an e-mail account for an e-mail driver) that is removed from an instance and subsequently added to another instance that is a different release version (for example, from Release 2 (9.0.2) to 10g (10.1.2)) may cause messages to be lost. Restarting the OC4J_Wireless OC4J instance resolves this problem.
The Notification Engine introduced in OracleAS Wireless 10g (10.1.2) replaces the Alert Engine, which was part of Oracle9iAS Wireless Release 2 (9.0.2). Although the Alert Engine is still available in OracleAS Wireless 10g (10.1.2), Oracle Corporation recommends that after all middle tiers have been upgraded to OracleAS Wireless 10g (10.1.2), you switch to the Notification Engine, as the Alert Engine may not be available in future versions of OracleAS Wireless.
Upgrade scripts are available to help you with this task. See the Oracle Application Server Wireless Developer's Guide for details. The Oracle9iAS Wireless Release 2 (9.0.2) Alert APIs have been deprecated, and you must upgrade your applications to use the OracleAS Wireless 10g (10.1.2) APIs instead.
In a mixed mode environment, Oracle9iAS Wireless Release 2 (9.0.2) and OracleAS Wireless 10g (10.1.2) may have transport drivers configured to receive incoming messages. The two sets of entry points, Oracle9iAS Wireless Release 2 (9.0.2) and OracleAS Wireless 10g (10.1.2), should not be exposed to a device at the same time. A user issuing a request to the Release 2 (9.0.2) instance should not subsequently send another request, within an 3 hour period, to the entry point defined in the transport driver of the OracleAS Wireless 10g (10.1.2) instance. The same user may not receive any response for requests addressed to the latter entry point, if it is violated.
Since the driver configuration is different in Release 2 (9.0.2) and 10g (10.1.2), when a Oracle9iAS Wireless Release 2 (9.0.2) instance is upgraded to OracleAS Wireless 10g (10.1.2), the transport drivers must be managed such that requests are processed as expected.
In 10g (10.1.2), a site level driver can be enabled or disabled. By default, it is enabled. If a driver is disabled, it is not recognized by the routing algorithm, and therefore is not used by the messaging system. However, in Release 2 (9.0.2), all site level drivers are recognized by the routing algorithm.
If a Release 2 (9.0.2) instance has two middle tiers, after one of the middle tiers and the Infrastructure are upgraded to 10g (10.1.2), the upgraded middle tier may enable or disable a site level driver. However, middle tiers that are not yet upgraded recognize all drivers as enabled. For this reason, it is prudent to remove, rather than disable, a driver in this type of environment.
InRelease 2 (9.0.2), the transport mechanism can route a message to only one driver, and it does not matter whether there is an instance configured for it. This means that a message will not be delivered if it is indeed routed to a driver that has no instance configured. For this reason, the best practice is to remove all drivers that do not have an instance configured in any Release 2 (9.0.2) environment, including a Release 2 (9.0.2) and 10g (10.1.2) mixed environment.
If you have configured OracleAS Portal and you want to keep it working after the upgrade, follow these steps to reconfigure OracleAS Portal for OracleAS Single Sign-On:
Set the ORACLE_HOME environment variable to the destination middle tier Oracle home.
Change directory to the following location in the destination middle tier Oracle home:
DESTINATION_ORACLE_HOME\portal\conf
Run the following command:
ptlconfig -dad portal_DAD -sso
In this command, portal_DAD is the DAD of the OracleAS Portal repository that you just upgraded.
|
See Also: Oracle Application Server Portal Configuration Guide for more information about theptlconfig tool |
Portal instances access web providers via a URL. The process of specifying this URL is referred to as provider registration. If the destination Oracle home will be accessed using a hostname and/or port number different from that of the source Oracle home, or the web providers have been deployed to a different URL path, then you need to update the URLs used to access the upgraded web providers. Web providers can be referenced by multiple portal instances; all of these must be updated.
Follow these steps to update the web provider URL:
Log on to OracleAS Portal as an administrator.
Click the Navigator link.
The Portal Navigator page appears.
Click the Providers tab.
Click Registered Providers.
A sorted list of registered providers appears.
Locate the provider to update, using the Next and Previous links if necessary.
Click the Edit Registration link for the provider to update.
The Edit Provider page appears.
Click the Connection tab.
Update the URL to reflect the new location of the provider.
Click OK or Apply to save the changes.
The Event/Parameter Passing Samples Provider definition has changed since Release 2 (9.0.2). Consequently, if you are upgrading a Release 2 (9.0.2) middle tier, the provider must be refreshed in the OracleAS Portal repository.
Repeat these steps for each Release 2 (9.0.2) OracleAS Portal instance that references this provider.
Follow these steps to update the web provider URL:
Log on to OracleAS Portal as an administrator.
Click the Navigator link.
The Portal Navigator page appears.
Click the Providers tab.
Click Registered Providers.
A sorted list of registered providers appears.
Locate the JPDK V2 Sample Event Web Provider, using the Next and Previous links, if necessary.
Click the Refresh link for the JPDK V2 Sample Event Web Provider.
This section provides steps the user can perform to verify that each component in Oracle Collaboration Suite 10g Applications has been upgraded and is working properly.
|
Note: In 10g Release 1 (10.1.2), the name of Oracle Collaboration Suite middle tier is changed to Oracle Collaboration Suite 10g Applications. |
Verifying the Upgrade of Oracle9iAS Portal and Oracle Collaborative Portlets
Verifying the Upgrade of Oracle Collaboration Suite 10g Mail (Oracle Email)
The Oracle Collaboration Suite Upgrade Assistant creates a ocsua.log log file. Some applications write to this log file during the upgrade and others create their own log file as summarized in Table 6-20. Check these log files for any errors once the upgrade completes.
Table 6-20 Upgrade Log Files
| Component | Log File and Path from Destination Oracle Home |
|---|---|
|
Oracle Collaboration Suite Upgrade Assistant |
|
|
Oracle Calendar |
upgrade\log\ocsua.log |
|
Oracle Collaborative Portlets |
|
|
Oracle Mail |
|
|
OracleAS Portal |
portal\logs\ptlconfig.log |
|
Oracle Ultra Search |
upgrade\log\ocsua.log |
|
Oracle Collaboration Suite 10g Mobile Collaboration |
upgrade\log\ocsua.log |
To verify that the upgrade to Oracle Enterprise Manager 10g was successful:
In a browser, access Oracle Enterprise Manager 10g Application Server Control for Collaboration Suite in the destination middle tier Oracle home by entering its URL:
http://hostname:port/
where:
hostname is the name of the system running the upgraded Applications tier
port is the port number used to access Oracle Enterprise Manager in the Release 1 (9.0.3.1) or Release 2 (9.0.4.2) Oracle Collaboration Suite middle tier. The port number is changed from the port number used before the upgrade. The default port is 1156.
For example:
http://midtierhost.mycompany.com:1156/
Oracle Enterprise Manager 10g prompts you to log in to the Application Server Control Console for Collaboration Suite.
Enter the ias_admin credentials that you used when upgrading the destination Oracle home.
Oracle Enterprise Manager 10g displays the Farm page in your browser window. A link for the Application tier instance appears in the Standalone Instances section of the page.
Click the name of the Application tier instance in the Standalone Instances section.
The System Components page appears.
Verify that the components are running.
Verify that the configuration information for the components in use is reflected in the 10g Release 1 (10.1.2) Oracle home.
From the Application Server Control Console for Collaboration Suite, stop and start all Applications by stopping and starting all OC4J instances.
This section provides steps to verify that the upgrade was successful. You should verify Portal and Oracle Collaborative Portlets only if the Portal schema in the Metadata Repository is 9.0.2.6 or later. If the Portal schema is an older version than 9.0.2.6, postpone the verification after MRUA. To verify that the upgrade was successful:
In a browser, access OracleAS Portal in the destination middle tier Oracle home by entering the following URL:
http://hostname:port/pls/portal
where:
hostname is the name of the system running the upgraded Applications tier
port is the port number used to access the Oracle9iAS Portal in the Release 1 (9.0.3.1) or Release 2 (9.0.4.2) Oracle Collaboration Suite middle tier. The same port number is used for Oracle Collaboration Suite 10g Applications.
For example:
http://midtierhost.mycompany.com:7777/pls/portal
Enter the orclguest user name and password when prompted. The new Oracle Collaboration Suite portal page with portlets for all the Oracle Collaboration Suite 10g Applications appears.
Verify that you can access all the applications through the portal.
The Oracle Collaboration Suite portal page displays portlets for all Oracle Collaboration Suite 10g Applications. Applications which have not been configured may display a "Service temporarily unavailable due to maintenance" error message. You can remove these portlets from the portal page.
To remove a portlet:
Log in to the Oracle Collaboration Suite portal page as an administrator.
Click Edit in the top right hand side. The portal now appears in edit mode.
Locate the portlet that you want to delete and click its Actions icon (next to the pencil icon). The Select Action page appears.
Click Delete then click Yes to confirm.
Return to the portal page and verify that the application no longer appears.
In Oracle Collaboration Suite 10g Release 1 (10.1.2), the name Oracle Email has been changed to Oracle Collaboration Suite 10g Mail.
To verify the upgrade of Oracle Email to Oracle Collaboration Suite 10g Mail, make sure you can access both the administrator and user URLs.
To verify the upgrade of the Oracle Collaboration Suite 10g Mail:
In a browser, access Oracle Mail in the destination Applications tier Oracle home by entering the following URL:
http://hostname:port/um/
where:
hostname is the name of the system running the upgraded Applications tier
port is the port number used to access the Oracle HTTP Server in the existing Oracle Collaboration Suite middle tier. The same port number is used for Oracle Collaboration Suite 10g Applications.
For example:
http://midtierhost.mycompany.com:7777/um/
Enter the name of an administrative user and password when prompted. The new Oracle Mail page appears.
|
Note: There is no default administrative user provisioned for Oracle Mail in 10g Release 1 (10.1.2).The umadmin user created during the installation of previous releases does not exist in the upgraded Oracle Mail. The orcladmin user is not provisioned as an administrator. Log in as another existing user with administrator privileges or create a new user using the Provisioning Console at http://host:port/oiddas/ and provision the user as a domain administrator for Oracle Mail. |
Select each tab and verify that all of them work.
To verify the upgrade of the Oracle Mail user URL:
In a browser, access Oracle Mail in the destination middle tier Oracle home by entering the following URL:
http://hostname:port/um/
where:
hostname is the name of the system running the upgraded Applications tier
port is the port number used to access the Oracle HTTP Server in the existing Oracle Collaboration Suite middle tier. The same port number is used for Oracle Collaboration Suite 10g Applications.
For example:
http://midtierhost.mycompany.com:7777/um/
Enter the orclguest user name and password when prompted. The new Oracle Mail page appears.
Send an e-mail from the orclguest user to user B. Verify that user B receives the e-mail.
To verify the upgrade of Oracle Calendar, verify both the Oracle Calendar administrator and Oracle Calendar Web client.
To verify the upgrade of the Oracle Calendar administrator:
In a browser, access the Oracle Calendar administrator in the destination Applications tier Oracle home by entering the following URL:
http://hostname:port/ocad-bin/ocad.cgi?object=nodeadm
where:
hostname is the name of the system running the upgraded Applications tier
port is the port number used to access the Oracle HTTP Server in the existing Oracle Collaboration Suite middle tier. The same port number is used for Oracle Collaboration Suite 10g Release 1 (10.1.2).
For example:
http://midtierhost.mycompany.com:7777/ocad-bin/ocad.cgi?object=nodeadm
If you are not logged into Oracle Collaboration Suite, then the Oracle Collaboration Suite login page appears. Enter the user name and password of a user with administrative privileges when prompted. The Oracle Calendar login page appears.
Follow the instructions on the screen to log in as the SYSOP user. The Oracle Calendar administrator page appears.
Use the tabs in the Calendar Management section to verify that existing users, resources and event calendars are listed correctly with the same attribute information as before the upgrade.
To verify the upgrade of the Oracle Calendar Web client:
In a browser, access the Oracle Calendar Web client in the destination middle tier Oracle home by entering the following URL:
http://hostname:port/ocas-bin/ocas.fcgi?sub=web
where:
hostname is the name of the system running the upgraded Applications tier
port is the port number used to access the Oracle HTTP Server in the Release 1 (9.0.3.1) or Release 2 (9.0.4.2) Oracle Collaboration Suite middle tier. The same port number is used for Oracle Collaboration Suite 10g Release 1 (10.1.2).
For example:
http://midtierhost.mycompany.com:7777/ocas-bin/ocas.fcgi?sub=web
Enter the orclguest user name and password when prompted. The new Oracle Calendar Web client appears.
Schedule a meeting and create a daily note. Verify that both items appear in the Oracle Calendar Web client.
To verify that the upgrade was successful:
Access the Oracle Enterprise Manager console as described in Section 6.7.2.
Select the link for the applications instance. The Application Server Control Console for Collaboration Suite page for the Application tier appears.
In the System Components table, make sure that there is a Wireless entry and that its status is Up.
Click Wireless to view the Wireless instance page. The standalone processes in Table 6-21 should be running.
Back in the System Components table, make sure that there is a Mobile Collaboration entry and that its status is Up.
Click Mobile Collaboration. The Mobile Collaboration page appears.
In Oracle Collaboration Suite 10g Applications, the name Oracle Wireless and Voice has been changed to Oracle Collaboration Suite 10g Mobile Collaboration.
To verify the upgrade to Oracle Collaboration Suite 10g Mobile Collaboration:
In a browser, access the Oracle Collaboration Suite 10g Mobile Collaboration Web client in the destination middle tier Oracle home by entering the following URL:
http://hostname:port/ocsmobile/welcome.uix
where:
hostname is the name of the system running the upgraded Applications tier
port is the port number used to access the Oracle HTTP Server in the Release 1 (9.0.3.1) or Release 2 (9.0.4.2) Oracle Collaboration Suite middle tier. The same port number is used for Oracle Collaboration Suite 10g Release 1 (10.1.2).
For example:
http://midtierhost.mycompany.com:7777/ocsmobile/welcome.uix
In a browser, access the OracleAS Wireless and Voice Tool in the destination application tier Oracle home by entering the following URL:
http://hostname:port/webtool/login.uix
where:
hostname is the name of the system running the upgraded Applications tier
port is the port number used to access the Oracle HTTP Server in the Release 1 (9.0.3.1) or Release 2 (9.0.4.2) Oracle Collaboration Suite middle tier. The same port number is used for Oracle Collaboration Suite 10g Release 1 (10.1.2).
For example:
http://midtierhost.mycompany.com:7777/webtool/login.uix
Enter the user name and password of a user with administrative privileges. Verify that the users, roles and groups are the same as in the application in the source Oracle home.
In a browser, access the OracleAS Wireless server in the destination middle tier Oracle home by entering the following URL:
http://hostname:port/ptg/rm
where:
hostname is the name of the system running the upgraded Applications tier
port is the port number used to access the Oracle HTTP Server in the Release 1 (9.0.3.1) or Release 2 (9.0.4.2) Oracle Collaboration Suite middle tier. The same port number is used for Oracle Collaboration Suite 10g Release 1 (10.1.2).
For example:
http://midtierhost.mycompany.com:7777/ptg/rm
Enter the name and password of an existing user with administrative privileges. From the OracleAS Wireless page, click the links for Mail, Contacts, Calendar and so forth and verify that you can access each page.
After the Oracle Collaboration Suite middle tier upgrade, Wireless must be configured from Oracle Enterprise Manager if it was not configured in the base environment. Oracle Enterprise Manager does not prompt you for the port number to use for wireless, and creates instance urls that might not use the same port as the wireless URL (http://server:port/ptg/rm). When this happens, one of wireless processes, the notification server, will fail to start. For this reason, you must use Oracle Enterprise Manager to change the instance URLs to use the same port as the wireless URL, and start the notification server.
In Oracle Collaboration Suite 10g Applications, the name Federated Search has been changed to Oracle Collaboration Suite 10g Search.
To verify the upgrade of Federated Search to Oracle Collaboration Suite 10g Search:
In a browser, access the Oracle Collaboration Suite 10g Search in the Applications tier Oracle home by entering the following URL:
http://hostname:port/search
where:
hostname is the name of the system running the upgraded Applications tier
port is the port number used to access the Oracle HTTP Server in the existing Oracle Collaboration Suite middle tier. The same port number is used for Oracle Collaboration Suite 10g Release 1 (10.1.2).
For example:
http://midtierhost.mycompany.com:7777/search
Enter the orclguest user name and password when prompted. The new Oracle Collaboration Suite Search page appears.
Perform a search on a word that appears in an e-mail and in a file that is stored in Oracle Content Services (formerly named Oracle Files). Verify that the search finds all occurrences of the word in both applications.
To verify that the upgrade of Oracle Ultra Search was successful, access the administrator page from a browser:
http://hostname:port/ultrasearch/admin/control/login.jsp
hostname is the name of the system running the upgraded Applications tier
port is the port number used to access the Oracle HTTP Server in the existing Oracle Collaboration Suite middle tier. The same port number is used for Oracle Collaboration Suite 10g Release 1 (10.1.2).
where:
For example:
http://midtierhost.mycompany.com:7777/ultrasearch/admin/control/login.jsp
Enter the name and password of a user with administrator privileges.
If you performed the index and configuration data migration, verify that all sources and schedules are migrated correctly. All configuration data should remain the same as before the upgrade.
Verify that all sources and schedules are migrated correctly. All configuration data should remain the same as before the upgrade. Manually start all schedules to build a new index. When the crawling completes, perform a search from the query page.
|
See Also: Oracle Ultra Search Administrator's Guide |
After you have verified that the upgraded Oracle Collaboration Suite Applications is working, you can uninstall the old Oracle Collaboration Suite middle tiers and delete their Oracle home directories.
After you have verified that the upgraded Oracle Collaboration Suite Oracle Homes are working, you can uninstall the old Oracle Collaboration Suite middle tiers and delete their Oracle home directories. If for any reason you elect to keep the old Oracle Collaboration Suite middle tiers, you MUST set their services startup type to "disabled".
The upgrade process leaves the source Oracle home unchanged. Depending on the type of installation you have, and your future needs, you may elect to remove the source Oracle home, or to retain it for specific reasons.
|
Note: If you retain the source Oracle home, you cannot operate it simultaneously with the destination Oracle home, because certain components have the same port values after upgraded. See Section 6.6.1, "About Port Values and the portlist.ini File After Upgrade". |
The following sections provide more information about decommissioning an upgraded source Oracle home:
If there are application files or log files in the source Oracle home that are being referenced or used by the destination Oracle home, you should move them to another location before you decommission the source Oracle home, and, in the destination Oracle home, change any references to the files to the new location.
If you continue to operate a Release 1 (9.0.3.1) or Release 2 (9.0.4.2) Portal repository, you should not decommission the source Oracle home if there is a possibility that you might later want to load additional languages into the Release 1 (9.0.3.1) or Release 2 (9.0.4.2) Portal repository. The utilities for loading languages in Oracle Collaboration Suite 10g Release 1 (10.1.2) are not compatible with OracleAS Portal in Release 1 (9.0.3.1) or Release 2 (9.0.4.2).
Refer to Section 4.7.3 for information about deinstalling a source Oracle home.
