About the SSL Enabled and Scaled-Out System Upgrade Process
Review the flowchart and roadmap for an overview to upgrade from a multi-node, SSL enabled and scaled-out 12.2.1.4.0 Oracle Business Intelligence or a previous Oracle Analytics Server release deployment.
Task | Required or Optional | Description |
---|---|---|
Learn about the interoperability and compatibility factors that could affect how you upgrade to Oracle Analytics Server. |
Optional |
It is important to understand how two or more Oracle Fusion Middleware products of the same version or different versions work together (interoperate) in a supported Oracle Fusion Middleware configuration. You can learn more about interoperability and compatibility in Oracle® Fusion Middleware Understanding Interoperability and Compatibility. |
If you have not done so already, review the introductory topics in this guide and complete the required pre-upgrade tasks. |
Required |
The pre-upgrade tasks include cloning your production environment, verifying system requirements and certifications, purging unused data, and creating non-SYSDBA user. For a complete list of pre-upgrade tasks, see Pre-Upgrade Requirements. |
Validate whether all the servers in the existing Oracle BI stack are running |
Required |
The following servers must be in the running state on both the nodes:
See Checking the Status of the Servers in the Oracle Analytics Server Instance. |
Download and install the 12.2.1.4.0 Fusion Middleware Infrastructure and Oracle Analytics Server distributions on Node1 and Node2. |
Required |
The Infrastructure distribution combines the WebLogic Server and the Java Required Files (JRF) that are required to set up the foundation to install other Fusion Middleware products. As per the upgrade topology defined in this guide, you must install the Infrastructure in a new Oracle home. The Oracle Analytics Server distribution packs, Oracle Analytics Server and Oracle Analytics Publisher. You must install Oracle Analytics Server in the Oracle home that is created when you installed the 12.2.1.4.0 Infrastructure. To install the product distributions, follow the procedure described in Installing the Product Distributions. |
Run the Readiness Check on Node1. |
Optional |
Run the domain-based pre-upgrade readiness check on Node1 to identify potential issues before you upgrade. See Running a Pre-Upgrade Readiness Check. |
Stop the stack. |
Required |
Before starting the upgrade process, shut down the Administration Server, the Managed Servers, and your existing Oracle BI instance on Node1. However, keep the database (RDBMS) running. |
Disable internal SSL. |
Required | You must disable SSL on the internal communication links before you start the upgrade process. |
Upgrade the existing schemas with the Upgrade Assistant on Node1. |
Required |
The schemas you created during the existing installation are supported in Oracle Analytics Server. Therefore, you don’t need to create the schemas again. You must upgrade all the schemas within your domain using the Upgrade Assistant. For the complete procedure, see Upgrading Product Schemas Using the Upgrade Assistant. |
Backup the mapViewerConfig.xml File. |
Required | The mapViewerConfig.xml file is overwritten by the reconfiguration templates when you run the Reconfiguration Wizard. Therefore, you must back up the mapViewerConfig.xml file before reconfiguring your existing domain. See Backing Up the mapViewerConfig.xml File. |
Reconfigure the existing domain with the Reconfiguration Wizard on Node1. |
Required |
When you run the Reconfiguration Wizard on your existing domain, it prepares your domain for upgrade by selecting and applying the recongifuration templates. It also tests the JDBC data sources and component schemas that are present within your domain. To reconfigure you domain, follow the procedure described in Reconfiguring the Oracle BI Domain with the Reconfiguration Wizard. |
Restore the mapViewerConfig.xml File. |
Required |
You must restore the original file that you backed up before upgrading your domain with the Upgrade Assistant. |
Upgrade the existing domain configurations with the Upgrade Assistant on Node1. |
Required |
After you have reconfigured your existing domain, you must run the Upgrade Assistant to upgrade all configurations used by your domain. You can see all the components within your domain that will be upgraded on the Component List screen when you run the Upgrade Assistant. For the complete procedure, see Upgrading Domain Components Using the Upgrade Assistant. |
Pack the upgraded domain on Node1. |
Required | See Packing the Upgraded Domain on Node1. |
Unpack the domain on Node2. |
Required | See Unpacking the Upgraded Domain on Node2. |
Synchronize connection details to the mid-tier database. |
Required | See Synchronizing Connection Details to the Mid-Tier Database. |
Start the Node Manager on Node2. |
Required | |
Enable the HTTP ports. |
Required | Use the WebLogic Administration console to enable the HTTP ports.
See steps 1 to 6 in Configure HTTPS Ports. |
Start the entire stack. |
Required |
The upgrade process is complete. You can now restart the Administration Server, the Managed Servers, and your Oracle Analytics Server instance. |
Verify that the instance works fine for External SSL. |
Required |
See Disable HTTP. |
Stop the stack. |
Required | |
Enable internal SSL. |
Required | See Enabling Internal SSL. |
Start the stack. |
Required | |
Verify that the instance works fine for internal SSL. |
Required |
Verify that the instance works fine for internal SSL. See Enable Oracle Analytics Server Internal SSL. Stop the stack and start only the Administration server. See Stopping Servers and Processes and Starting Servers and Processes. |
Disable HTTP ports. | Required | Use the WebLogic Administration console to disable HTTP ports. See Disable HTTP Ports. |
Verify your upgrade. |
Required | It is important to compare your existing and the Oracle Analytics Server environments and verify that the data and configuration settings are consistent in the newly upgraded environment. |
Perform the post-upgrade tasks. |
Required | For a list of post-upgrade tasks, see Post-Upgrade Tasks. |
Parent topic: Upgrading Scaled-Out Systems