You can create a patching workflow to patch a domain, one or more clusters, or one or more servers. The patching workflow can be for rolling out a new Java version, rolling out a new patched Oracle Home, rolling out one or more updated applications, or any combination of these. You can also create a patching workflow to roll back to a previous Oracle Home.
Prior to creating a workflow, ensure that you are familiar with all restrictions and have properly prepared for the workflow. See Preparing for Zero Downtime Patching for more information.
To create a patching workflow:
If you selected the Servers page, select the servers to include in the workflow.
The displayed fields and options depend on the type of rollout or rollback you are performing.
C:\jdks\jdk1.8.0_40 (Windows) or
Oracle recommends that you not select this option unless you are absolutely sure that the session state is practically identical. This may cause the rollout to take longer due to the wait for session completion. Note that WebLogic Server serialization/deserialization differs slightly from Java serialization/deserialization. Therefore, additional fields on classes may result in a session being incompatible with servers on the new version, requiring that they be served by a server on the existing version. For example, a User class that adds a field such as Information will cause that session to be incompatible between versions.
The workflow will be added to the Workflow Progress table.