Updating Oracle Identity Navigator 11.1.1.3.0 to 11.1.1.5.0
6.6.1 Upgrading Node 1
To upgrade Node 1 in the cluster, follow the instructions in Section 6.2, Updating Oracle Identity Manager 11.1.1.3.0 to 11.1.1.5.0 .6.6.2 Upgrading Node 2
To upgrade Node 2 in the cluster, follow the instructions below: 1. Back up the Oracle Identity Manager 11.1.1.3.0 domain, and your Oracle Identity Manager and Oracle SOA Suite binaries. 2. Shut down all Managed Servers for Oracle Identity Manager and Oracle SOA Suite that are running in the domain. 3. If your Oracle WebLogic Server, Oracle Identity Management, and Oracle SOA Suite binaries are NOT at a shared location, perform the following steps. Otherwise, skip to Step 4. a. Patch Oracle WebLogic Server as described in Section 6.1.4, Patching Oracle WebLogic Server 10.3.3. to 10.3.5 . b. Update your Oracle SOA Suite software as described in Section 6.1.5, Patching Oracle SOA Suite 11.1.1.3.0 to 11.1.1.5.0 Oracle Identity Manager Users Only . c. Update your Oracle Identity and Access Management software as described in Section 6.1.6, Patching Oracle Identity and Access Management 11.1.1.3.0 to 11.1.1.5.0 . 4. Run the following command to pack your domain on Node 1: On UNIX operating systems: cd MW_HOME oracle_commoncommonbin .pack.sh -domain= OIM_Domain_Home -template= Domain_Configuration_Jar_ Destination -template_name= template_nanme -managed=true On Windows operating systems: cd MW_HOME \oracle_common\common\bin pack.cmd -domain= OIM_Domain_Home -template= Domain_Configuration_Jar_Destination -template_name= template_nanme -managed=true Replace OIM_Domain_Home with the full path to your OIM domain, Domain_ Configuration_Jar_Destination with the full path to the location where you want to create your domain configuration .jar file, and template_name with the name of this domain configuration template. Below is an example on UNIX operating systems: .pack.sh -domain=homeOracleDomains11.1.1.3.0_OIMDomain -template=homeOracleData -template_name=OIM Domain -managed=true On Windows operating systems: pack.cmd -domain=D:\Oracle\Domains\11.1.1.3.0_OIMDomain -template=D:\Oracle\Data -template_name=OIM Domain -managed=true 6-16 Oracle Fusion Middleware Patching Guide 5. Unpack the domain configuration information on Node 2. On UNIX operating systems: cd MW_HOME oracle_commoncommonbin .unpack.sh -domain= OIM_Domain_Home -template= Domain_Configuration_Jar_Location -overwrite_domain=true On Windows operating systems: cd MW_HOME \oracle_common\common\bin pack.cmd -domain= OIM_Domain_Home -template= Domain_Configuration_Jar_Location -overwrite_domain=true Replace OIM_Domain_Home with the full path to your OIM domain on Node 2, and Domain_Configuration_Jar_Location with the full path to the location where you want created your domain configuration .jar file on Node 1. Below is an example on UNIX operating systems: .unpack.sh -domain=homeOracleDomains11.1.1.3.0_OIMDomain -template=homeOracleData -overwrite_domain=true On Windows operating systems: pack.cmd -domain=D:\Oracle\Domains\11.1.1.3.0_OIMDomain -template=D:\Oracle\Data -overwrite_domain=true 6. Go to the OIM_HOME serverbin on UNIX operating systems or OIM_ HOME \server\bin on Windows operating systems directory and edit the dwps1upgrade.properties file so that all properties EXCEPT for oim.ps1.soacomposite.patch are set to false. 7. Start the SOA Managed Server on Node 2. This is required to deploy SOA composites on Node 2. 8. Run the standalone utility as described in Step 9 in Section 6.2.1, Instructions for Updating Oracle Identity Manager . 9. Check to see if any login module .jar files are found in the MW_ HOME wlsserver_10.3serverlibmbeantypes on UNIX operating systems or MW_HOME \wlsserver_10.3\server\lib\mbeantypes on Windows operating systems directory in your Release 11.1.1.3.0 environment. If there are no files, you can skip this step. If there are, copy the following login module files from OIM_ HOME serverloginmodulewls to MW_HOME wlsserver_ 10.3serverlibmbeantypes on UNIX operating systems or from OIM_ HOME \server\loginmodule\wls to MW_HOME \wlsserver_ 10.3\server\lib\mbeantypes on Windows operating systems: ■ OIMAuthenticator.jar ■ oimmbean.jar ■ oimsigmbean.jar ■ oimsignaturembean.jar Note: The domain directory structures must be identical on both nodes.Parts
» Oracle Fusion Middleware Online Documentation Library
» Types of Patches That can be Used with OPatch
» OPatch System Requirements Backup and Recovery Considerations for Patching
» Patching with a Local Middleware Home
» Patching with a Shared Middleware Home
» Patching a Fusion Middleware Product Patching Artifacts Deployed Outside the Oracle Home
» Using the OPatch Property File
» Configuring Node Manager Beginning with OPatch release 11.1.0.8.2, the -auto
» Using the -auto Option with the -domain Option The -auto option should be used
» Sample Output for the apply Command
» Deploying Patched Artifacts to WebLogic Servers
» Listing the Source Oracle Homes
» Listing the Domains Created from the Middleware Home or Oracle Home
» Listing the Applicable Oracle Homes for a Patch
» Listing Patches Applied to an Oracle Home or WebLogic Domain
» Starting or Stopping a Runtime Instance
» Notes About Patching the MDS Repository Setting the Machine Name and Listen Address
» Summary of the Oracle Fusion Middleware Patching Process
» Special Instructions for Patching Oracle WebCenter
» Special Instructions for Patching Oracle Identity and Access Management Release 11.1.1.3.0
» Stop the Servers and Processes
» Back Up Your Middleware Home, Domain Home and Oracle Instances
» Back Up Your Database and Database Schemas
» Back Up Additional Configuration Information
» Patch Oracle WebLogic Server
» Product Installers About the Installers Used for Patching
» Patch Set Installers About the Installers Used for Patching
» Download the Installer Download and Start the Product Installer or Patch Set Installer
» Start the Installer Download and Start the Product Installer or Patch Set Installer
» Patch Set Installer Instructions
» Post-Patching Tasks If Your Starting Point is Release 11.1.1.2.0
» Post-Patching Tasks If Your Starting Point is Release 11.1.1.3.0
» Post-Patching Tasks If Your Starting Point is Release 11.1.1.4.0
» Upgrading System Components Post-Patching Tasks for System Components
» Updating Configuration Properties in Oracle Identity Federation
» Updating Oracle Configuration Manager Windows Only
» Resolving JDBC Errors in Oracle Reports and Oracle Portal
» Updating the Configuration in SSL-Enabled Oracle Portal Instances
» Updating Fusion Middleware Shared Libraries
» Updating Configurations and Stores
» Enabling WS-AtomicTransaction Post-Patching Tasks for Your WebLogic Server Domain
» Removing the tmp Folder for SOA Composer and BPM Workspace
» Updating the soa-infra Application in Warning State
» Run soa-upgrade.py to Update the Policy Store and Deploy a Shared Library
» Updating the Oracle Data Integrator Clients if BAM-ODI Integration is Enabled
» Committing or Reverting Open Edit Sessions in SOA Composer
» Saving and Restoring XEngine Customizations for Oracle B2B
» Updating Oracle IPM in Oracle Enterprise Content Management Suite
» Updating Oracle Application Adapters for Oracle Enterprise Content Management Suite
» Applying Patch 12369706 for Oracle Information Rights Management
» Adding New OWSM Pre-Defined Policies
» Updating an Oracle Service Bus Domain After Applying the Latest Patch Set
» Deleting Oracle WebLogic Server 11g Release 1 10.3.3 You need to create a new
» Updating Oracle Business Intelligence Code Grants
» Updating Oracle Business Intelligence Catalogs
» Update the rtd_ils Resource Type Using WLST Perform the following to add
» Add Permissions to the BIAdministrator Principle Using EM The steps in this
» Finalizing Repository Patching Post-Patching Tasks for Oracle Data Integrator
» Reconfiguring the Java EE Agent
» Reconfiguring the ODI Standalone Agent
» Reconfiguring Oracle Enterprise Manager Properties
» Update Your Schemas with Patch Set Assistant Start the Servers and Processes
» Verify Your Patch Installation
» Which Schemas Need to be Updated with Patch Set Assistant?
» General Information about the Patch Set Assistant
» Starting the Patch Set Assistant
» Command Line Syntax Running the Patch Set Assistant
» Additional Database Connection Information for Oracle Data Integrator
» Sample Commands Verifying the Schema Version Number After Update
» Checking for Invalid Database Objects Loading the Oracle SOA Suite Purge Scripts
» Patch Set Assistant Log Files
» Performing General Oracle Fusion Middleware Pre-Patching Steps
» Saving Your OmniPortlet and WebClipping Customizations
» Purging Old Documents in MDS for WebCenter Spaces
» Upgrading Oracle Universal Content Management 10
» Removing the LD_LIBRARY_PATH Entry from the setDomainEnv Script
» Choosing Your Oracle WebCenter Update Method
» Updating Oracle WebCenter Using WLST Commands
» Configuring Node Manager Updating Oracle WebCenter Using Node Manager and Automated Script
» Verifying Your Node Manager Configuration
» Updating Your Oracle WebCenter Software and Database Schemas
» Example 1: No Optional Parameters Specified If no optional parameters are
» Example 2: Specifying a Properties File and Setting the Value of user.config.file If you
» Example 3: Specifying a Properties File and Administrator Password If you specify a
» Example 4: Specifying a Properties File, Administrator Password, and Node Manager
» Properties That can be Set in the Upgrade Properties File
» Formatting Your Properties File You must make sure you escape values correctly
» Procedure for Migrating Oracle Wiki Pages and Blogs
» Troubleshooting Problems During Wiki Migration
» Restoring Your OmniPortlet and WebClipping Customizations
» Upgrading Oracle WebCenter Custom Portal Managed Servers
» Migrating Content Presenter Custom Templates
» Updating Oracle WebCenter Portal Schemas
» Configuring an Identity Asserter
» Configuring the Credential Store
» Updating Multi Calendar Layouts Extending a Domain to Install Oracle WSM Policy Manager
» Setting the Web Context Root on the UCM Connection
» Configuring Group Space Workflows
» Allowing Group Spaces to Have a Default Template Set
» Updating the Timezone Attribute in WebCenter Spaces
» Updating the Group Spaces Display Mode
» Migrating WebCenter Spaces Custom Library
» Starting Oracle BPM to Login to WebCenter Spaces
» Configuring Web Services Security for Discussions
» Enabling Process Spaces in a Patched Domain
» Extending a WebCenter Domain to Add Oracle WebCenter Analytics Collector
» Upgrading a WebCenter Custom Application to Add Portal Framework Features
» Prerequisites Preparing to Patch
» Before You Begin Preparing to Patch
» Backing Up Oracle Fusion Middleware
» Patching Oracle WebLogic Server 10.3.3. to 10.3.5
» Instructions for Updating Oracle Identity Manager
» Configuring Oracle Identity Manager Design Console
» Setting System Properties for LDAP Sync and Referential Integrity
» Updating Oracle Access Manager 11.1.1.3.0 to 11.1.1.5.0
» Updating Oracle Adaptive Access Manager 11.1.1.3.0 to 11.1.1.5.0
» Updating Oracle Identity Navigator 11.1.1.3.0 to 11.1.1.5.0
Show more