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.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 the Enterprise Manager.
Note:
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.
For more information, see Starting and Stopping Servers in the Correct Order.
Oracle recommends you to start and stop the servers in a particular order to avoid issues with the deployment.
After the Infrastructure upgrade, start all of the Administration and Managed servers for your environment and make sure that they are functioning as expected.
Note:
Procedures for starting and stopping Oracle Fusion Middleware, including the Administration Server, Managed Servers, and components are provided in Starting and Stopping Oracle Fusion Middleware in Administering Oracle Fusion Middleware.
Start servers in the following order:
Node Managers
Administration Server
Webtier (including the Oracle HTTP Server)
Oracle Web Services Manager (OWSM) Managed Server (if installed)
Service-Oriented Architecture (SOA) Managed Server (if installed)
Oracle Service Bus (OSB) Managed Server (if installed)
Business Activity Monitoring (BAM) Managed Server (if installed)
Stop servers in the following order:
Business Activity Monitoring (BAM) Managed Server (if installed)
Oracle Service Bus (OSB) Managed Server (if installed)
Service-Oriented Architecture (SOA) Managed Server (if installed)
Oracle Web Services Manager (OWSM) Managed Server (if installed)
Webtier (including the Oracle HTTP Server)
Admin Server
Node Managers
For more information on stopping servers, see Starting and Stopping Oracle Fusion Middleware in Administering Oracle Fusion Middleware.
Node Manager is a Java utility that runs as separate process from WebLogic Server and allows you to perform common operations for a Managed Server, regardless of its location with respect to its Administration Server.
Note:
To use a per-host Node Manager configuration, ensure that –Dohs.product.home=<MW_HOME> is set for JAVA_OPTIONS in the appropriate Node Manager script. Run the command NodeManager.cmd|sh if you are not using the Node Manager service. Run the command installNodeMgrSvc.cmd if you are using the Node Manager service.
The Host and Port used should match those used with your Upgraded setup. For more information on how to edit the Host/Port values in the file to install the Node Manager Service with the correct details, see Configuring Java Node Manager in Oracle Fusion Middleware Node Manager Administrator's Guide for Oracle WebLogic Server
The Administration Server provides a central point for managing a WebLogic Server domain. All other WebLogic Server instances in a domain are called Managed Servers. In a domain with only a single WebLogic Server instance, that server functions both as Administration Server and Managed Server.
http://administration_server_host:administration_server_port/console
To verify that the domain-specific-component configurations upgrade was successful, log in to the Administration console and the Fusion Middleware Control and verify that the version numbers for each component is 12.2.1.
To log into the Administration Console, go to: http://administration_server_host:administration_server_port/console
To log into the Fusion Middleware Control, go to: http://administration_server_host:administration_server_port/em
Note:
After upgrade, make sure you run the administration tools from the new 12c Oracle home and not from the previous Oracle home.
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.
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.
For more information, see Re-apply Customizations to Startup Scripts.
Note:
To prevent losing your custom configuration settings in a future upgrade, see Maintaining Your Custom setDomainEnv Settings (Optional).
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 Configuring and Managing Auditing in Fusion Middleware Application Security Guide.
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.
Note:
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_authentication_service_policy, no_authorization_service_policy, or no_messageprotection_service_policy. For more information, see Disabling a Globally Attached Policy in Securing Web Services and Managing Policies with Oracle Web Services Manager.
Note:
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. For more information, see Disabling a Globally Attached Policy in Securing WebLogic Web Services for Oracle WebLogic Server
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
| Task | Description | More Information |
|---|---|---|
|
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. |
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:
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:
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.
ojdeploy command line tool to generate the required deployment descriptors in your deployment archive.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 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.
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.
For more information, see Migrating to Oracle JDeveloper 12.2.1 From a Previous Version in Installing Oracle JDeveloper.
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 Developing Asynchronous Web Services in Developing Oracle Infrastructure Web Services.