This chapter summarizes the tasks you might have to perform after upgrading to Oracle Fusion Middleware 12c Infrastructure.
This chapter includes the following sections:
Section 4.2, "Starting and Stopping Servers in the Correct Order"
Section 4.3, "Verifying the Domain Component Configurations Upgrade"
Section 4.5, "Configuring an Oracle Fusion Middleware 12c Audit Data Store"
Section 4.6, "Maintaining the Security Status of Older Java EE Web Service Applications"
Section 4.7, "Documentation Resources for Managing Your Oracle Fusion Middleware 12c Software"
Section 4.8, "Using Your 11g Application Deployments in Oracle Fusion Middleware 12c"
After the upgrade, make sure that you can successfully complete the following basic administration tasks. Detailed information about how to perform each of these steps is documented in the other sections of this chapter.
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 Section 4.2, "Starting and Stopping Servers in the Correct Order".
Verify that the Node Managers can be started.
Verify that the Administration Server and any Managed Servers (if included) from the original 12.1.2 Domain Home bin directory can be started. 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 the Webtier (OHS server) can be started.
Verify that you can access the Administration console and Enterprise Manager using the following URLs:
http://machinename.my_company_com:administration_port
http://machinename.my_company_com:administration_port/em
After the Infrastructure upgrade, you should start all of the Administration and Managed servers for your environment and make sure that they are functioning as expected.
The order in which you START and STOP the servers is important, and failure to start or stop them in the correct order can cause issues with the deployment.
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 Oracle Fusion Middleware Administering Oracle Fusion Middleware.
Node Managers
See Also: Section 4.2.1, "Starting the Node Manager".
Administration Server
See Also: Section 4.2.2, "Starting the Administration Server"
Webtier (including the Oracle HTTP Server)
See Also: Section 4.2.3, "Starting the Webtier (OHS 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)
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 Oracle Fusion Middleware Administering Oracle Fusion Middleware.
To start Node Manager, go to the DOMAIN_HOME/bin directory.
On UNIX operating systems, start the Node Manager as shown below, using nohup and nm.out as an example output file:
nohup ./startNodeManager.sh > nm.out&
On Windows operating systems, run:
startNodeManager.cmd
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
Start the Administration Server by running the following command from the directory DOMAIN_HOME/bin (on UNIX) or DOMAIN_HOME\bin (on Windows):
(UNIX) ./startWebLogic.sh
(Windows) startWebLogic.cmd
To verify that the 11g domain was reconfigured successfully, log in to the Administration console using the following URL, and verify if the version number displayed on the console is 12.1.3:
http://administration_server_host:administration_server_port/console
For information about stopping and starting the Administration Server, see "Starting and Stopping Administration Servers" in the Oracle Fusion Middleware Oracle Fusion Middleware Administering Oracle Fusion Middleware.
After starting the Node Manager and Administration Server, you can start the Oracle HTTP (OHS) server. Navigate to the DOMAIN_HOME/bin directory and execute the following command:
On Unix operating systems:
DOMAIN_HOME/bin/startComponent.sh ohs_name
On Windows operating systems:
DOMAIN_HOME\bin\startComponent.cmd ohs_name
For more information, see "Starting and Stopping System Components" in Oracle Fusion Middleware Administering Oracle Fusion Middleware.
To verify that the domain component configurations upgrade was successful, log in to the Administration console and the Fusion Middleware Control using the following URLs, and verify the upgraded version numbers for each component:
Administration Console URL: http://administration_server_host:administration_server_port/console
Fusion Middleware Control URL: http://administration_server_host:administration_server_port/em
Note:
After upgrade, you must run the administration tools from the new 12.1.3 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 12.1.3 it might be necessary to re-apply any customizations to startup scripts, such as setDomainEnv. During the upgrade, the scripts are overwritten with new 12.1.3 versions. Any customizations you had made in previous releases will need to be reapplied.
For more information, see "Re-apply Customizations to Startup Scripts".
Note:
To prevent losing your customizations in a future upgrade, see Section 2.3, "Maintaining Your Custom setDomainEnv Settings (Optional)".
If you were using a file-based audit store in Oracle Fusion Middleware11g, 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 Data Store" in Securing Applications with Oracle Platform Security Services.
The introduction of global policy attachment support for Java EE web services and clients in 12.1.3 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 will 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 12.1.3, the global policy attachments defined for these subject types will 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 will require a change to your code. For more information, see "Disabling a Globally Attached Policy" in Securing WebLogic Web Services for Oracle WebLogic Server
Table 4-1 lists some common administration tasks you will likely want to perform after upgrading to Infrastructure 12.1.3.
Table 4-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 Oracle Fusion Middleware 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 Oracle Fusion Middleware 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 Oracle Fusion Middleware 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 Oracle Fusion Middleware 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 Oracle Fusion Middleware Administering Oracle Fusion Middleware. |
After you upgrade to Oracle Fusion Middleware 12c, the custom Java and Oracle Application Development Framework (ADF) applications 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 Oracle ADF 12c and in Oracle JDeveloper 12c.
The following sections provide some additional information about how you can migrate your applications to Oracle JDeveloper 12c:
Information about the Oracle ADF can be found in the following Oracle Fusion Middleware 12c documentation resources:
The Oracle Application Development Framework (ADF) Common tasks page in the Oracle Fusion Middleware 12c Documentation Library
This section provides the following information:
To install Oracle JDeveloper 12c, refer to Installing Oracle JDeveloper.
Note that Oracle JDeveloper provides an embedded version of Oracle WebLogic Server that can be used to locally test your applications. For more information, 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 From a Previous Version to Oracle JDeveloper 12.1.3" in Installing Oracle JDeveloper.
If your application contains 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 Oracle Fusion Middleware Developing Oracle Infrastructure Web Services.