| Oracle® Fusion Middleware Upgrade Guide for Oracle Portal, Forms, Reports, and Discoverer 11g Release 1 (11.1.1) Part Number E10130-04 |
|
|
View PDF |
| Oracle® Fusion Middleware Upgrade Guide for Oracle Portal, Forms, Reports, and Discoverer 11g Release 1 (11.1.1) Part Number E10130-04 |
|
|
View PDF |
The following sections introduce some key concepts of the Oracle Portal, Forms, Reports, and Discoverer environment for Oracle Application Server 10g Release 2 (10.1.2) users:
Components of the Oracle Portal, Forms, Reports, and Discoverer Suite
Basic Architecture of the Oracle Portal, Forms, Reports, and Discoverer Suite
Considerations When Deciding Upon an Oracle Portal, Forms, Reports, and Discoverer Topology
Oracle Application Server 10g Release 2 (10.1.2) provided users with updated versions of the following components:
Oracle Portal
Oracle Business Intelligence Discoverer
Oracle Forms Services
Oracle Reports
Oracle HTTP Server (including mod_plsql)
Oracle Web Cache
Oracle Net Services, which includes the tnsnames.ora, sqlnet.ora, and ldap.ora configuration files
Oracle Fusion Middleware 11g provides updates to all these components. In Oracle Fusion Middleware, they are packaged as the Oracle Portal, Forms, Reports, and Discoverer software suite.
In Oracle Application Server 10g Release 2 (10.1.2), the Oracle Identity Management components, such as Oracle Internet Directory, Oracle Directory Integration Platform, Oracle Single Sign-On, and Oracle Delegated Administration Services were packaged with the Oracle Portal, Forms, Reports, and Discoverer components.
In Oracle Fusion Middleware 11g, your Oracle Identity Management components are packaged and installed separately, but they still provide the same resources and services.
The basic architecture of the Oracle Portal, Forms, Reports, and Discoverer components is the same as Oracle Application Server 10g, with one major difference. Instead of being based on Oracle Containers for Java EE (OC4J), the Oracle Fusion Middleware middle-tiers are based on Oracle WebLogic Server.
Figure 2-1 illustrates a basic Oracle Portal, Forms, Reports, and Discoverer topology in Oracle Application Server 10g Release 2 (10.1.2) and Oracle Fusion Middleware 11g. Notice how the system components are deployed to dedicated managed servers in the Oracle WebLogic Server domain.
In a more complex environment, you can also extend the domain to other hosts, so some of the Oracle Portal, Forms, Reports, and Discoverer components can be deployed on managed servers on remote hosts.
Figure 2-1 Comparing the Oracle Portal, Forms, Reports, and Discoverer Topology in 10g Release 2 (10.1.2) and Oracle Fusion Middleware 11g
The following sections describe the general guidelines for configuring a new Oracle Fusion Middleware 11g topology in preparation for upgrade, as well as considerations for other alternative topologies:
General Guideline for Configuring Your Oracle Fusion Middleware Topology
Understanding the Impact on Upgrade When Configuring an Alternative Topology
In general, Oracle recommends that you upgrade your Oracle Application Server 10g environment to a similarly configured environment.
In other words, if your Oracle Application Server 10g environment consisted of a single Oracle home that contained all the Oracle Portal, Forms, Reports, and Discoverer components, then it is assumed you will be upgrading to an Oracle Fusion Middleware domain that is configured in a similar manner: one Oracle home and one Oracle instance containing all the components.
If you follow this general guideline, you can use the Oracle Fusion Middleware Upgrade Assistant and the procedures documented in this guide to upgrade the components.
Oracle Fusion Middleware 11g provides a flexible architecture that does not prevent you from installing and configuring the Oracle Portal, Forms, Reports, and Discoverer components in separate Oracle instances.
You can, for example, install Oracle Portal and Oracle Forms Services and later extend the Oracle WebLogic Server domain to support Oracle Reports and Oracle BI Discoverer. The resulting topology will include two Oracle instances: one that contains Oracle Portal and Oracle Forms Services and one that contains Oracle Reports and Oracle BI Discoverer.
If you decide upon such an approach, note the following important restrictions and considerations:
Each time you extend a domain to include additional Oracle Portal, Forms, Reports, and Discoverer components, you create a new Oracle instance.
Depending upon the components you choose to configure in each Oracle instance, the configuration tool will create new Web tier components (Oracle HTTP Server and Oracle Web Cache instances) for the components that require them. For example, if you extend a domain to include Oracle Portal, then new Oracle HTTP Server and Oracle Web Cache instances are configured automatically to support Oracle Portal.
If you configure multiple Web tier components in a single domain, then you must decide whether to maintain:
Multiple Web tier components (for example, where each Oracle HTTP Server instance uses a different listening port and routes requests to specific components)
OR
A single set of Web tier components (for example, a single Oracle HTTP Server that routes requests to all the configured components in the domain).
Depending upon your decision, you might have to disable one set of Web tier components or reconfigure one Oracle HTTP Server instance to route requests to the other Oracle instance.
For more information about configuring Oracle HTTP Server to route requests to an Oracle WebLogic Server instance, see "Configuring the mod_wl_ohs Module" in the Oracle Fusion Middleware Administrator's Guide for Oracle HTTP Server.
If your Oracle Fusion Middleware domain contains multiple Oracle instances, then you must run the Upgrade Assistant at least twice (once for each 11g Oracle instance), and you must use care when selecting your upgrade options.
In particular, if you select the Use source Oracle home ports in destination option, note that you can run the Upgrade Assistant with this option selected only once for each host. Otherwise, you will likely encounter port conflicts, since no more than one component can listen on a single same listening port on a single host.
For more information, see Section 3.6.2.2, "Important Notes When Using the Source Oracle Home Ports in the Destination Oracle Instance"
Oracle Access Manager is a component of Oracle Fusion Middleware that you can use in place of Oracle Single Sign-On 10g to implement centralized authentication, policy-based authorizations, delegated administration, and so on.
Before or after you upgrade to Oracle Portal, Forms, Reports, and Discoverer 11g, you can also upgrade your Oracle Identity Management components, which can include upgrading Oracle Single Sign-On 10g to Oracle Access Manager 11g.
For more information about upgrading to Oracle Access Manager for your single-sign on solution, see "Upgrading Your Oracle Single Sign-On Environment" in the Oracle Fusion Middleware Upgrade Guide for Oracle Identity Management.
Specifically, when you are about to perform the upgrade, refer to the following Oracle Single Sign-On upgrade scenario in the Oracle Fusion Middleware Upgrade Guide for Oracle Identity Management:
For information about using Oracle Portal with Oracle Access Manager, see "Relationship Between Oracle Portal and Oracle Access Manager" in the Oracle Fusion Middleware Administrator's Guide for Oracle Portal.
|
 Copyright © 2009, 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
