Fusion Middleware 12c Upgrade - Standalone server

Oracle Fusion Middleware Upgrade from 11.1.1.7.4 to 12.1.3.0 on standalone server
Kranti Guduru
Table of Contents
 Introduction
 Reference Links
 12c Upgrade Flow Diagram
 Upgrade Overview
 Pre Upgrade
o Prerequisites Check
o Software Installation
 Upgrade
o Creating Database Schemas for
o Upgrading Schemas and Instances Data
o Reconfiguring the 11g Domain
o Upgrading the 11g Domain
 Post Upgrade Task
o WebLogic
o SOA and BPM
o OSB
o BAM
 Annexure A
 Annexure B
 Annexure C
 Known Issues

Kranti Guduru
 Introduction
o This Oracle fusion middleware upgrade technical guide provide us a detailed way to perform
upgrade from 11G to 12C on existing 11G domain and the Oracle Fusion Middleware component
configuration in that domain to SOA Suite and Business Process Management 12c (12.1.3)
o This paper provides step by step instructions to upgrade 11g SOA Suite and Business Process
Management to 12c
o Major steps involved for this migration are listed below
Reference:
SOA and BPM: http://docs.oracle.com/middleware/1213/core/FUPSS/toc.htm
OSB: https://docs.oracle.com/middleware/1213/core/FUPSS/osb.htm#CHDHAHJC
BAM: http://docs.oracle.com/middleware/1213/core/FUPSS/bam.htmsss

Kranti Guduru

Kranti Guduru
 Instructions
Please read this section carefully before performing the pre-upgrade tasks
o When upgrading the SOA Suite 11g environment to 12c (12.1.3) SOA Suite and Business Process
Management, one should understand how pre-upgrade environment will be affected by the
upgrade
Example, schemas and domain directory upgrades are performed "in place" which updates the
existing 11g files during the upgrade. The 12c (12.1.3) Oracle Home binaries are upgraded
"Out of place" as the binaries are installed in a new directory
o Upgrade to 12c (12.1.3) includes the “midtier” and the “schemas”. You cannot perform a
midtier-only or schema-only upgrade
o If your SOA domain includes BAM, then the upgrade is more complex because BAM does not
support “in place” upgrade. The basic idea is to migrate the whole BAM deployment to a
separate domain using export/import, remove BAM from the SOA domain during upgrade, and
upgrade your SOA domain to interop with the bam 11g domain. Later slowly and carefully
migrate to BAM 12c from BAM 11g
o Can only upgrade a domain that is 11.1.1.6 or 11.1.1.7. Migrate to a supported starting point
before upgrade
o Can only upgrade a domain using an oracle Database versions 10.2.0.5+, 11.1.0.7+ and release
11.2.0.2+ are supported by the SOA Suite 12c certification matrix. Migrate to a supported DB
version before upgrade
o If a database schema upgrade was failed due to a sizing error, it’s not recommended to add disk
space and retry the upgrade. The schemas have been left in an inconsistent state and may have
been marked "INVALID". You cannot recover from this error without restoring the original,
Pre-upgrade environment from backups
o In 11g it is possible to run Oracle Service Bus without a database as the SOA schema was not
required. In 12c, however, you must have a supported database configured with the required
SOA schemas before you can run OSB 12c (12.1.3)
o Only JDK 7 is supported
o Can only upgrade a deployment using a 64 bit JVM. Migrate to 64 bit JVM before upgrade
o Can only upgrade a production domain not using XE DB and is not an admin server only domain
o Can only upgrade a domain using LDAP or DB OPSS policy store. Migrate file based policy store
to DB or LDAP based policy store before upgrade

Kranti Guduru
o Can only upgrade a domain based on WebLogic server
o Can only upgrade a domain at this time with products deployed that were released in 12c
o Cannot upgrade a domain at this time created with T2P or pack/unpack before SOA Suite
11.1.1.6
o Cannot upgrade a domain at this time with multiple products in 12c in separate non clustered
managed servers using UMS. Examples are BAM, OSB and SOA. The reason is because after
upgrade UMS configuration is at the domain level or the cluster level, but not at a non-clustered
managed server level
o If your SOA schema tables are partitioned, and you want to upgrade to 12c (12.1.3), upgraded
using the process described in this guide is not possible
o There is no upgrade support for an Oracle BAM-only domain (a domain without SOA)
o Oracle Business Activity Monitoring (BAM) 12c has been completely redesigned for use with
Oracle SOA Suite 12c, so there is no direct upgrade path
o The schemas, binaries, and directory structure used in Oracle BAM 12c are different than those
used with Oracle BAM 11g. Therefore, upgrading from Oracle BAM 11g to BAM 12c cannot be
handled with the standard upgrade procedures. You will need to perform several manual
configuration tasks to complete the upgrade
Prerequisites Check
o Verify that your Oracle FMW products are supported for 12c upgrade
o Verify that your Oracle database is supported for 12c upgrade
o Verify that your JAVA and JVM version s are supported for 12c upgrade
o Before you begin the upgrade process from SOA Suite and BPM 11g to 12c, you must read and
understand how all of the components within your 11g domain will be impacted by the upgrade.
o Understanding Interoperability and Compatibility provides a detailed matrix of which
components can and cannot be upgraded together. For example, if your 11g domain includes
Oracle Service Registry (OSR) or Oracle Enterprise Repository (OER) then you cannot upgrade a
domain
o Oracle strongly recommends that you create a copy of your actual production environment,
upgrade the cloned environment, verify that the upgraded components work as expected, and
then (and only then) upgrade your production environment
o Create a complete backup of your existing environment before you start any pre-upgrade
procedures
o Run 11g Purge scripts before starting the upgrade to reduce downtime during the upgrade
o Re-associate any file-based policy stores to database-based stores

Kranti Guduru
Migrate from file based policy store to DB based policy store
Step 1: Create the OPSS schema by Running RCU
Step 2: Create a data source for the OPSS schema in WebLogic console
Start the Admin and Managed servers “Login to WebLogic console”
Select domain Expand Services and then click on Datasources
Click Create a new Generic Datasources
Name: OPSSDS
JNDI Name: jdbc/OPSSDS
Database Type: Oracle
Click Next
Database Driver Oracle's Driver (Thin) for Instance connections
Click Next
Unselect Supports Global Transactions
Click Next
Database Name:<DB_NAME>
Host Name: <database hostname>
Port: 1521
Database User Name <opss_user_name>
Password <opss_user_password>

Kranti Guduru
Click Next
Click “Test Configuration” to make sure connection is tested
Click Next
Check AdminServer and SOAServer
Click Finish
Step 3: Associate Policy Store to OPSS DS:
Navigate to the drop-down menu for the WebLogic Domain and choose Security –>
Security Provider Configuration
Click “Change Store Type” button, then...

Kranti Guduru
Select the corresponding JNDI name for OPSS schema and provide the Data source properties
Now Click OK.
o If you have a domain that includes BPM and OSB or multiple servers in the same domain, then
these managed servers must be defined in a cluster. Else, we may experience issues while server
startup & post upgrade, especially with messed up configuration files
o Stop all 11g FMW servers and processes before you launch the Upgrade

Kranti Guduru
OSB:
o For OSB only domain, If Oracle Web Services Manager (OWSM) Policy Manager is not already
deployed in your Oracle Service Bus 11g environment, then you must manually deploy it before
you upgrade to 12c
o You must export services and resources into a configuration JAR file before you can upgrade to
Oracle Service Bus 12.1.3. After the upgrade, you will import the JAR file to the new 12c
environment
o After the export, disable the proxy service and continue using business service to product
message. You must delete the user-created services (Those are not necessary) and resources
before the upgrade
BAM:
o If you have a BAM in your 11g domain, and want to upgrade to Oracle BAM 12c, then you must
create a new Oracle BAM 11g domain and copy all objects from existing 11g domain to new 11g
domain using BAM iCommand
o It is also important to understand that the only Oracle BAM 11g objects that can be used in your
BAM 12c domain are data objects (DOs) and enterprise message sources (EMS)
o You will need to manually export these objects to an XML file and then import them into the
BAM 12c domain
o The other Oracle BAM 11g artifacts, such as dashboards for example, will have to be manually
recreated in Oracle BAM 12c domain
o Oracle recommends that you continue to use your Oracle BAM 11g domain after the upgrade to
allow time to create and test all of the necessary artifacts. Therefore, before you begin the SOA
with Oracle BAM upgrade process, it is strongly recommended that you reinstall the Oracle
BAM 11g domain in a separate location so that the source files remain untouched during the
domain reconfiguration
Install 12C Software
o We have 2 ways to install 12C software 1) normal 2) silent method, Let me give you both ways...
o Oracle Infrastructure 12c (12.1.3) (which includes WebLogic Server and JRF), SOA Suite and
Business Process Management 12c (12.1.3) distribution binaries are installed in a new Oracle
home. The upgrade of binaries is considered "out of place" as the 11g binaries cannot be
overwritten
Manual Installation:
1) WebLogic Installation:
12c binaries will be installed in same home with different middleware home from 11g
installation. Example: 11g is installed in the path like /u01/app/fmw, then install 12c binaries in
/u01/app/fmw12c

Kranti Guduru
The whole upgrade is done offline. The first step is to install 12c. You install
FMW_12.1.3.0_INFRASTRUCTURE.jar downloaded from edrlivery.oracle.com -> WebLogic standard
edition -> Fusion middleware infrastructure in a new MWHOME as follows.
We need to configure the 12c home location as below

Kranti Guduru
Then run the .jar file as mentioned below, it will automatically extract the content in the jar file and
startup screen will appear

Kranti Guduru
At welcome screen click next to proceed further. Mention the installation home directory and click next

Kranti Guduru
Choose the installation type as by default “Fusion Middleware Infrastructure” and proceed next
After the prerequisite is verified click next to proceed next

Kranti Guduru
In the security updates option provide the mail and password for better support and click next (optional)

Kranti Guduru
Click NEXT as below slide summarize installation components

Kranti Guduru
Click on Next to proceed further

Kranti Guduru
Click on finish to complete the WebLogic installation

Kranti Guduru
2) SOA/BPM Installation:
Install soa_generic.jar in the same MWHOME as follows

Kranti Guduru
When the above command is executed installer will pop-up

Kranti Guduru
Click on Next to proceed for further installation

Kranti Guduru
Mention the installation home which we have already given in the installation of WebLogic

Kranti Guduru
Note: select SOA suite only for SOA components required

Kranti Guduru
Note: Select BPM for BPM suite
When the prerequisites are done, click on next to proceed for further installation

Kranti Guduru
Click on NEXT

Kranti Guduru
Congrats installation done successfully!!!!
Creating Database Schemas for 12c
After installing 12c components, new schemas required to support 12C database. When you
create the new 12.1.3 schemas, be sure to use a unique schema prefix. This prefix enables you
to differentiate between any schemas previously installed or upgraded in the database, as
opposed to those that you have created specifically for Oracle Fusion Middleware 12c
Specifically, run the 12c (12.1.3) Repository Creation Utility (RCU) to create the following
schemas
 STB
 WLS
 SOA_INFRA, if not created in 11g
 MDS, if not created in 11g

Kranti Guduru
 AUDIT_SERVICES, if not created in 11g
 Run rcu from $ORACLE_HOME/oracle_common/common/bin
Click next in the welcome screen
Select “Create Repository” and choose any one the option as per the DB ownership

Kranti Guduru
Enter the DB details with sys username & password

Kranti Guduru
Click NEXT

Kranti Guduru
Note: Ignore the warning
Select required components such as MDS & SOAINFRA (OSB only domain), STB, IAU_APPEND,
IAU_VIEWER and WLS

Kranti Guduru
Note: STB and WLS are dedicated to 12c. If other schemas were not created for 11g already please use
this console to create them

Kranti Guduru
Enter password for those schemas
Click NEXT

Kranti Guduru
Below screen will pop-up
Click on OK

Kranti Guduru
Click on create for further process
We are one step ahead to complete process

Kranti Guduru
Congrats!! We completed RCU installation successfully
Upgrading Schemas and Instances Data
o The 11g schemas are upgraded to 12c "in place" which means that the Upgrade Assistant
update and overwrites the schemas during the upgrade process. The upgrade of active
and closed instances from 11g to 12c happens automatically as part of the schema
upgrade. The servers must be down during this process
o If 11g domain included with BAM the run below step before upgrading 11g schemas
o Before upgrading the 11g schemas with the Upgrade Assistant, please change the names
of the following Oracle BAM reconfiguration templates if not upgrade will fail. Make sure
that you have exported your 11g Oracle BAM data before completing this step
o The templates can be found in the following 12c directory:
$ORACLE_HOME/soa/common/templates/wls

Kranti Guduru
Template Name
oracle.bam.reconfig_template_12.1.3.jar oracle.bam.reconfig_template_12.1.3.jar.old
oracle.bam.reconfig.template_12.1.3.jar.rename oracle.bam.reconfig_template_12.1.3.jar
Note: Rename the files as given in the above example as it is….
Upgrade Assistant to upgrade Schemas from
11g to 12C at DB level
Before starting the upgrade process:
 Edit upgrade_soainfra_111170_121300_oracle.tsql at location
/opt/fedex/eprs/oracle/middleware12c/soa/common/sql/soainfra/sql/oracle
 At line 4852
Replace
ALTER TABLE AUDIT_TRAIL DROP CONSTRAINT AT_PK
by
ALTER TABLE AUDIT_TRAIL DROP CONSTRAINT AT_PK DROP INDEX;
 At line 6929
Replace
ALTER TABLE TEST_INSTANCE DROP CONSTRAINT TEST_INSTANCE_PK;
by
ALTER TABLE TEST_INSTANCE DROP CONSTRAINT TEST_INSTANCE_PK DROP INDEX;
Go to the below location and run upgrade assistant
/u01/Oracle/Middleware12c/Oracle_Home/oracle_common/upgrade/bin./ua

Kranti Guduru
Welcome Screen
At welcome screen click on Next to proceed for further installation

Kranti Guduru
Initially we need to upgrade the schemas to 12C
Note: Ensure that application servers are down and DB is up before upgrading the schemas

Kranti Guduru
Choose the checkboxes as mentioned in the screenshot and click on Next to proceed further

Kranti Guduru
Ensure that prerequisites are met and click the checkboxes for further upgrade steps

Kranti Guduru
Choose the 11g domain directory and click next
Provide sys user DB credentials with schema password and hit next

Kranti Guduru

Kranti Guduru
Note: BAM schema upgrade not required

Kranti Guduru
The above screenshot shows the examine process of the schema after it gets successful click on next to
continue

Kranti Guduru
Save response file to install in silent mode, and hit next to proceed

Kranti Guduru
The schemas which you have chosen will now upgraded to 12C, 12.1.3.0

Kranti Guduru
Finally close the screen. And check your schemas are upgraded or not by the below screen

Kranti Guduru
Login in to the root user named as sys and run the query
Select * from schema_version_registry;
The schema version is now pointed to 12.1.3.0
Reconfiguring the 11g Domain
The existing SOA domain is upgraded "in place". During the upgrade you will identify the
location of the 11g SOA domain and the 11g domain will be reconfigured to point to the new
SOA 12c (12.1.3) home directory
Reconfiguring the 11g Domain
Go to the /u01/Oracle/Middleware12c/Oracle_Home/oracle_common/common/bin above location
and run the

Kranti Guduru
./reconfig.sh
Choose the 11g domain directory and click NEXT
Note: Ensure that your servers are down

Kranti Guduru
Let the process complete 100% as below screen print

Kranti Guduru
Click NEXT. The above wizard will check the domain you have entered is a valid domain directory or not

Kranti Guduru
In default it will fetch your JAVA home path, or we can manually click the other JDK location and provide
the path. Click on Next to continue

Kranti Guduru
The above screen will fetch the Datasources which you have created click NEXT to continue

Kranti Guduru
Choose the top first checkbox and click the test selected connections button, ensure that it tested
successfully then click NEXT

Kranti Guduru
Edit your service name, hostname, port, schema owner and password and click on Get RCU
configuration, the result is OK. Click Next to proceed

Kranti Guduru
Check the schema owner name password, hostname and service are correct. If it is not correct click on
that particular checkbox and edit in the above table. Click on Next
Note: Check the schema owner names properly
Choose the top first checkbox and click the test selected connections button, ensure that it tested
successfully and click NEXT

Kranti Guduru
Click NEXT

Kranti Guduru
Provide Node manager credentials and Click NEXT

Kranti Guduru
Click next, we can choose the checkbox and can configure here or after admin console is up we can
create

Kranti Guduru
Click on Reconfig to reconfigure your 11g domain. Note: This Reconfiguration will reconfigure only our
11g domain. We can’t find our domain folder in 12C home path

Kranti Guduru
Note: We have got domain reconfiguration failed on the above screen because we renamed the soa-
infra to soa-infra-wls.
Default: soa-infra
Modified: soa-infra-wls
Reverted to soa-infra:
Modify the name in the config.xml which is present in
/u01/Oracle/Middleware11g/user_projects/domains/coe94_domain/config
Reverted the soa-infra-wls to soa-infra(Name which is default)
Upgrading the 11g Domain
After the reconfiguration of the 11g SOA domain, the Upgrade Assistant is used again to
upgrade any remaining domain component configurations that require an upgrade in the new
SOA 12c (12.1.3) home directory

Kranti Guduru
Upgrading Domain Configurations to 12C
Go to the below location and run upgrade assistant
/u01/Oracle/Middleware12c/Oracle_Home/oracle_common/upgrade/bin./ua
At welcome screen click NEXT to continue
Note: Ensure that your servers are down before running the upgrade assistant for upgrading WebLogic
components

Kranti Guduru
Choose “WebLogic component configurations” 11g domain directory for upgrade and click NEXT

Kranti Guduru
The above list of components will get upgraded, click NEXT

Kranti Guduru
Ensure that your prerequisites have been met and click NEXT
In this screen you have to provide your LINUX machine credentials and click NEXT
Note: Linux username and password

Kranti Guduru
Then…

Kranti Guduru
Save the response file for silent installation and click on upgrade to proceed further

Kranti Guduru
Save the response file for silent installation.

Kranti Guduru
When your upgrade process succeeds click on Next to proceed further. If you have get any errors kindly
click on the view log button

Kranti Guduru
After the upgrade succeeds close the screen

Kranti Guduru
Click on Finish
Post Upgrade Task
After a successful upgrade, you may need to perform one or more of the following tasks. Review
your own use case scenarios and existing deployment to determine if the following tasks apply
to your environment
Use the below URL’s for acceding admin and other consoles.
WebLogic Admin: http://HOST:PORT/console
Fusion Middleware control: http://HOST:PORT/em
Service Bus: http://HOST:PORT/sbconsole
BAM: http://HOST:PORT/bam/composer
Worklistapp: http://HOST:PORT/integration/worklistapp
WebLogic

Kranti Guduru
Perform the below post-upgrade tasks for WebLogic
 Importing Security Configurations like user and roles etc
SOA and BPM
Perform the below post-upgrade tasks for SOA and BPM.
 Reapply customizations to scripts and configuration files.
 Verify the file permissions
 Start servers
 Verify that closed instances have finished migrating
 Test Services/Applications.
OSB
Perform the below post-upgrade tasks for OSB
Importing Domain Configuration Data
Importing Jar (resource) to 12c (which exported in pre-upgrade task)

Kranti Guduru
Upgrading Your XQuery Resources
Oracle Service Bus supports XQuery 1.0. The older XQuery 2004 is also supported. Any new
XQuery resource created in Service Bus uses the XQuery 1.0 version, by default.
If you have upgraded from a pre-12c Service Bus project, all XQuery resources in the project are
configured to use the XQuery 2004 version and it can be converted to XQ 1.0 as shown below
Understanding 12c Split-Joins
The 11g split-join business service will no longer exist in 12c because in 12c there is a direct way
to invoke a split-join component from a pipeline or a proxy service. The upgrade process will
automatically change all statically configured invoke references to a split-join business service as
follows:
 The flow business service is removed. This means the Timeout property configured for
the Flow business service is also removed.
 If the business service is located in the same project as the proxy service that invokes it,
then the pipeline associated with that proxy service invokes the split-join directly.
 If the business service is located in a different project from the proxy service that invokes
it, then a local proxy service is created to invoke the split-join. The local proxy service is
invoked by the original proxy service

Kranti Guduru
BAM
1. Delete the UMS JMS resources running on the Oracle BAM server or Oracle BAM
cluster.
2. Delete Subdeployment resources targeted to UMS JMS Server targeted to Oracle
BAM.
3. Delete the UMS Email driver for the Oracle BAM server
4. Remove the Oracle BAM Servers and Clusters from the domain.
5. Remove unnecessary Oracle BAM 11g files from the upgraded domain by running
./domainupdater.sh from ORACLE_HOME/soa/bam/bin
6. For Cluster Upgrades Only: Run the pack and unpack command
7. Configure 11g Oracle BAM Adapter to work with SOA 12c domain (If necessary).
8. Delete the existing UMS Email driver from the SOA domain.
9. Extending the SOA Domain with Oracle BAM 12c. Refer Annexure D for more
details.
10. Create the new UMS Email driver for the Oracle BAM server
11. Import the Oracle BAM 11g data objects and EMS data to the BAM 12c server
Manually recreate the 11g BAM dashboards, alerts, and other artifacts for use in the BAM 12c
domain
Congrats we all set with upgradation, go ahead with testing that includes performance testing
fix any defects if noticed. Configure alert monitoring

Kranti Guduru
‘

Fusion Middleware 12c Upgrade - Standalone server

Recommended

Recommended

More Related Content

What's hot

What's hot (19)

Viewers also liked

Viewers also liked (11)

Similar to Fusion Middleware 12c Upgrade - Standalone server

Similar to Fusion Middleware 12c Upgrade - Standalone server (20)

Fusion Middleware 12c Upgrade - Standalone server