Using the Upgrade Validation Checklist
After the upgrade, make sure that you can successfully complete the basic administration tasks, such as verifying whether you are able to start the Node Manager, Administration Server, Webtier, Administration Console, and Enterprise Manager Fusion Middleware Control.
The order in which you start the following servers is important and failure to start (or stop) them in the correct order can cause issues with the deployment.
- Verify that you are able to start the Node Managers.
- Verify that you are able to start the Administration Server and any Managed Servers (if included) from the original Domain Home
bindirectory. Windows operating system users may find it useful to start the servers from a new command prompt (and not the one used to launch the 12c Upgrade Assistant).
Note:OHS does not need a Managed Server for it's own configuration.
- Verify that you are able to start the Webtier (OHS server).
- Verify that you are able to access the Administration console and Enterprise Manager using the following URLs: Administration console:
Verifying the Domain-Specific-Component Configurations Upgrade
To verify that the domain-specific-component configurations upgrade was successful, sign in to the Administration console and the Oracle Enterprise Manager Fusion Middleware Control and verify that the version numbers for each component is 18.104.22.168.0.
To sign in to the Administration Console, go to:
To sign in to Oracle Enterprise Manager
Fusion Middleware Control Console, go to:
After upgrade, make sure you run the administration tools from the new 12c (22.214.171.124.0) Oracle home directory and not from the previous Oracle home directory.
During the upgrade process, some OWSM documents, including policy sets and predefined documents such as policies and assertion templates, may need to be upgraded. If a policy set or a predefined document is upgraded, its version number is incremented by 1.
If you created the FMW user to run the Upgrade Assistant, ensure that you delete the account after verifying your upgrade was successful.
Reapplying Custom Configuration Settings to setDomainEnv
To complete the upgrade of your application environment to 12c it might be necessary to reapply any custom configuration settings to startup scripts, such as
setDomainEnv. During the upgrade, the scripts are overwritten with new 12c versions. You must manually reapply the custom configuration settings you had made in previous releases.
Configuring an Oracle Fusion Middleware 12c Audit Data Store
If you were using a file-based audit store in your 11g deployment, then after the upgrade to Oracle Fusion Middleware 12c, you should enable the loading of audit data to a database-based Audit Data Store.
As a part of the overall upgrade process, you should have created the IAU schema in the database where your other Oracle Fusion Middleware schemas reside. For more information about using the Audit Data Store, see Managing the Audit Store in Securing Applications with Oracle Platform Security Services.
Maintaining the Security Status of Older Java EE Web Service Applications
The introduction of global policy attachment support for Java EE web services and clients in 12c may impact the backwards compatibility of existing Java EE web services and clients (12.1.2 and earlier). If a Java EE web service or client endpoint that depends on the absence of a policy falls within the scope of a global policy attachment, the presence of the globally-attached policy can alter the security behavior of that endpoint.
In Fusion Middleware 12.1.2 and earlier, global policy attachments defined for SOAP Web Service and SOAP Web Service Client subject types were applicable to Oracle Infrastructure web services and clients only, and were ignored by Java EE web services and clients. After upgrading to 12c (12.2.1), the global policy attachments defined for these subject types apply to Java EE web services and clients, as well, and may alter the security behavior of existing Java EE web services and clients.
To maintain backwards compatibility, you can disable the global policy attachments for specific endpoints by attaching an OWSM no behavior policy to the service or client, such as
no_messageprotection_service_policy. See Disabling a Globally Attached Policy in Securing Web Services and Managing Policies with Oracle Web Services Manager.
You can use the WebLogic
Wssp1.5-No-Op.xml no behavior policy. However, since WebLogic security policies can only be attached to web service clients programmatically, it requires code change. See Disabling a Globally Attached Policy in Securing WebLogic Web Services for Oracle WebLogic Server.
Documentation Resources for Managing your Oracle Fusion Middleware 12c Software
This topic provides a list of common administration tasks you likely want to perform after upgrading to Infrastructure 12c and associated documentation resources.
Table 5-1 lists some common administration tasks you will likely want to perform after upgrading to Infrastructure 12c.
Table 5-1 Basic Administration Tasks
Getting familiar with Fusion Middleware administration tools
Get familiar with the various tools available which you can use to manage your environment.
Overview of Oracle Fusion Middleware Administration Tools in Administering Oracle Fusion Middleware.
Starting and stopping products and servers
Learn how to start and stop Oracle Fusion Middleware, including the Administration Server, Managed Servers, and components.
Starting and Stopping Oracle Fusion Middleware in Administering Oracle Fusion Middleware.
Configuring Secure Sockets Layer (SSL)
Learn how to set up secure communications among between Oracle Fusion Middleware components using SSL.
Configuring SSL in Oracle Fusion Middleware in Administering Oracle Fusion Middleware.
Monitoring Oracle Fusion Middleware
Learn how to keep track of the status of Oracle Fusion Middleware components.
Monitoring Oracle Fusion Middleware in Administering Oracle Fusion Middleware.
Understanding Backup and Recovery Procedures
Learn the recommended backup and recovery procedures for Oracle Fusion Middleware.
Introducing Backup and Recovery in Administering Oracle Fusion Middleware.
Using Your 11g Application Deployments in Oracle Fusion Middleware 12c
After you upgrade to Oracle Fusion Middleware 12c, the custom Java and Application Development Framework (ADF) you previously deployed on Oracle Fusion Middleware 11g work as they did in Oracle Fusion Middleware 11g. However, there are some new features and capabilities available in ADF 12c and in JDeveloper 12c.
The following sections provide some additional information about how you can migrate your applications to JDeveloper 12c:
About Oracle Application Development Framework (ADF) 12c
Oracle ADF is an end-to-end Java EE framework that simplifies application development by providing out-of-the-box infrastructure services and a visual and declarative development experience.
Information about Oracle ADF can be found in the following Oracle Fusion Middleware 12c documentation library:
Overview of Oracle ADF in Understanding Oracle Application Development Framework
About Oracle JDeveloper 12c
Oracle JDeveloper is an integrated development environment that simplifies the development of Java-based applications addressing every step of the application lifecycle. JDeveloper offers complete end-to-end development for Oracle's platform and applications.
Installing Oracle JDeveloper 12c
Oracle JDeveloper provides an embedded version of Oracle WebLogic Server that can be used to locally test your applications.
To install Oracle JDeveloper 12c, see Installing the Oracle JDeveloper Software in Installing Oracle JDeveloper.
For more information about using JDeveloper to test your applications, see Deploying and Testing Applications Developed in Oracle JDeveloper in Installing Oracle JDeveloper.
Migrating Applications Using Oracle JDeveloper 12c
After you install Oracle JDeveloper 12c, you can open your custom application projects in Oracle JDeveloper 12c and automatically migrate them to Oracle JDeveloper 12c.
See Migrating Oracle JDeveloper From a Previous Version in Installing Oracle JDeveloper.
About Migrating Asynchronous Web Services with Oracle JDeveloper 12c
If your application contains Application Development Framework Business Components (ADF BC) asynchronous Web Services, ensure that you rebuild it using Oracle JDeveloper or the
ojdeploy command line tool to generate the required deployment descriptors in your deployment archive.
For more information about developing asynchronous Web Services, see Introduction to Developing Asynchronous Web Services in Developing Oracle Infrastructure Web Services.