This chapter describes how to upgrade your existing Oracle Adaptive Access Manager 11g Release 1 (11.1.1.5.0) environment to Oracle Adaptive Access Manager 11g Release 2 (11.1.2).
This chapter contains the following sections:
Backing Up Oracle Adaptive Access Manager 11g Release 1 (11.1.1.5.0)
Upgrading Oracle Adaptive Access Manager 11g Release 2 (11.1.2)
Upgrading MDS Schema and IAU Schema Using Patch Set Assistant
Extending Oracle Adaptive Access Manager 11.1.1.5.0 Component Domains with OPSS Template
Starting the Administration Server and Oracle Adaptive Access Manager Managed Servers
Read the Oracle Fusion Middleware System Requirements and Specifications document to ensure that your environment meets the minimum requirements for the products you are installing or upgrading.
Note:
If you do not follow the exact sequence provided in this task table, your Oracle Adaptive Access Manager upgrade may not be successful.
Table 5-1 lists the steps to upgrade Oracle Adaptive Access Manager.
| Task | For More Information | |
|---|---|---|
|
1 |
Shut down all servers. This includes both Administration Server and Managed Servers. |
See, Shutting Down Administration Server and Managed Servers |
|
2 |
Back up your environment. |
See, Backing Up Oracle Adaptive Access Manager 11g Release 1 (11.1.1.5.0) |
|
3 |
Optional - Upgrade Oracle WebLogic Server 10.3.5 to Oracle WebLogic Server 10.3.6. |
|
|
4 |
Upgrade 11.1.1.5.0 Oracle Home to 11.1.2.0.0. |
See, Upgrading Oracle Adaptive Access Manager 11g Release 2 (11.1.2) |
|
5 |
Upgrade MDS schema and Audit schema using Patch Set Assistant. |
See, Upgrading MDS Schema and IAU Schema Using Patch Set Assistant |
|
6 |
Run Oracle Fusion Middleware Repository Creation Utility (RCU) to create and load OPSS schema for Oracle Identity and Access Management products. |
|
|
7 |
Extend your Oracle Adaptive Access Manager 11.1.1.5.0 domain with the OPSS template. |
See, Extending Oracle Adaptive Access Manager 11.1.1.5.0 Component Domains with OPSS Template |
|
8 |
Upgrade Oracle Platform Security Services. |
|
|
9 |
Run the |
|
|
10 |
Upgrade the Oracle Adaptive Access Manager schemas. |
|
|
11 |
Start the Administration and Managed Servers. |
See, Starting the Administration Server and Oracle Adaptive Access Manager Managed Servers |
|
12 |
Redeploy the applications on Oracle Adaptive Access Manager 11.1.2.0.0 Servers. |
|
|
13 |
Delete the |
See, Deleting Folders |
|
14 |
Restart the servers. |
|
|
15 |
Complete the post-upgrade tasks if required. |
See, Post Upgrade Steps |
|
16 |
Verify the Oracle Adaptive Access Manager upgrade. |
The upgrade process involves changes to the binaries and to the schema. Therefore, before you begin the upgrade process, you must shut down the Administration Server and Managed Servers.
To shut down the Servers, do the following:
Stopping the Administration Server
To stop the Administration Server, do the following:
On UNIX:
Run the following command:
cd <MW_HOME>/user_projects/domains/<domain_name>/bin
./stopWebLogic.sh
On Windows:
Run the following command:
cd <MW_HOME>\user_projects\domains\<domain_name>\bin
stopWebLogic.cmd
To stop the Managed Servers, do the following:
On UNIX:
Move from your present working directory to the <MW_HOME>/user_projects/domains/<domain_name>/bin directory by running the following command on the command line:
cd <MW_HOME>/user_projects/domains/<domain_name>/bin
Run the following command to stop the Servers:
./stopManagedWebLogic.sh <server_name> <admin_url> <user_name> <password>
where
<server_name> is the name of the Managed Server.
<admin_url> is URL of the WebLogic administration console. Specify it in the format http://<host>:<port>/console. Specify only if the WebLogic Administration Server is on a different computer.
<user_name> is the username of the WebLogic Administration Server.
<password> is the password of the WebLogic Administration Server.
On Windows:
Move from your present working directory to the <MW_HOME>\user_projects\domains\<domain_name>\bin directory by running the following command on the command line:
cd <MW_HOME>\user_projects\domains\<domain_name>\bin
Run the following command to stop the Managed Servers:
stopManagedWebLogic.cmd <server_name> <admin_url> <username> <password>
where
<server_name> is the name of the Managed Server.
<admin_url> is URL of the WebLogic administration console. Specify it in the format http://<host>:<port>/console. Specify only if the WebLogic Administration Server is on a different computer.
<username> is the username of the WebLogic Administration Server.
<password> is the password of the WebLogic Administration Server.
For more information, see "Stopping the Stack" in the Oracle Fusion Middleware Installation Guide for Oracle Identity and Access Management.
You must back up your Oracle Adaptive Access Manager 11.1.1.5.0 environment before you upgrade to Oracle Adaptive Access Manager 11.1.2.
After stopping the servers, you must back up the following:
MW_HOME directory, including the Oracle Home directories inside Middleware Home
Domain Home directory
Oracle Adaptive Access Manager schemas
IAU schema, if it is part of any of your Oracle Adaptive Access Manager 11.1.1.5.0 schemas
MDS schemas
Note:
Upgrading Oracle WebLogic Server is not mandatory. However, Oracle recommends that you upgrade Oracle WebLogic Server to 10.3.6.
You can upgrade WebLogic Server 10.3.5 to Oracle WebLogic Server 10.3.6 by using the WebLogic 10.3.6 Upgrade Installer. Complete the following steps:
Download the WebLogic 10.3.6 Upgrade Installer from Oracle Technology Network.
For more information, see "Downloading the Installer From Oracle Technology Network" in the Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server.
Run the Upgrade Installer in graphical mode to upgrade your WebLogic Server.
For more information, see "Running the Upgrade Installer in Graphical Mode" in the Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server.
To upgrade Oracle Adaptive Access Manager, you must use the Oracle Identity and Access Management 11.1.2 Installer. During the procedure, point the Middleware Home to your existing 11.1.1.5.0 Middleware Home. Your Oracle Home is upgraded from 11.1.1.5.0 to 11.1.2.
This section contains the following topics:
Starting the Oracle Identity and Access Management Installer
Installing Oracle Identity and Access Management 11g Release 2 (11.1.2)
For more information on obtaining Oracle Fusion Middleware 11g software, see Oracle Fusion Middleware Download, Installation, and Configuration ReadMe.
This topic explains how to start the Oracle Identity and Access Management 11.1.2 Installer.
Notes:
If you are installing on an IBM AIX operating system, you must run the rootpre.sh script from the Disk1 directory before you start the Installer.
Starting the Installer as the root user is not supported.
Start the Installer by doing the following:
On UNIX:
Move from your present working directory to the directory where you extracted the contents of the Installer to.
Move to the following location:
cd Disk1
Run the following command:
./runInstaller -jreLoc <complete path to the JRE directory>
For example:
./runInstaller -jreLoc <MW_HOME>/jdk160_29/jre
On Windows:
Move from your present working directory to the directory where you extracted the contents of the Installer to.
Move to the following location:
cd Disk1
Run the following command:
setup.exe -jreLoc <complete path to the JRE directory>
For example:
setup.exe -jreLoc <MW_HOME>\jdk160_29\jre
Note:
If you do not specify the -jreLoc option on the command line when using the Oracle JRockit JDK, the following warning message is displayed:
-XX:MaxPermSize=512m is not a valid VM option. Ignoring
This warning message does not affect the installation. You can continue with the installation.
On 64-bit platforms, when you install Oracle WebLogic Server using the generic jar file, the jrockit_1.6.0_29 directory is not created in your Middleware Home. You must enter the absolute path to the JRE folder from where your JDK is located.
Use the Oracle Adaptive Access Manager 11.1.2 Installer to upgrade Oracle Adaptive Access Manager 11.1.1.5.0 to OAAM 11.1.2:
After you start the installer, the Welcome screen appears.
Click Next on the Welcome screen. The Install Software Updates screen appears. Select whether or not you want to search for updates. Click Next.The Prerequisite Checks screen appears. If all prerequisite checks pass inspection, click Next. The Specify Installation Location screen appears.
On the Specify Installation Location screen, point the Middleware Home to your existing 11.1.1.5.0 Middleware Home installed on your system.
In the Oracle Home Directory field, specify the path of the existing Oracle Identity and Access Management Home. This directory is also referred to as <IAM_HOME> in this book.
Click Next. The Installation Summary screen appears.
The Installation Summary screen displays a summary of the choices that you made. Review this summary and decide whether you want to proceed with the installation. If you want to modify any of the configuration settings at this stage, select a topic in the left navigation page and modify your choices. To continue installing Oracle Identity and Access Management, click Install. The Installation Progress screen appears. Click Next.
Note:
If you cancel or abort when the installation is in progress, you must manually delete the <IAM_HOME> directory before you can reinstall the Oracle Identity and Access Management software.
To invoke online help at any stage of the installation process, click Help on the installation wizard screens.
The Installation Complete screen appears. On the Installation Complete screen, click Finish.
This installation process copies the 11.1.2 Oracle Identity and Access Management software binaries to your system.
For more information, see "Installing and Configuring Oracle Identity and Access Management (11.1.2)" in the Oracle Fusion Middleware Installation Guide for Oracle Identity and Access Management.
You must upgrade your MDS schema using Patch Set Assistant. You must also upgrade your Audit (IAU) schema if it is part of your 11.1.1.5.0 schemas.
This section consists of the following topics:
Before running Patch Set Assistant, you should make sure that your database is running and that the schemas are supported. To check this, run the following SQL command:
SELECT OWNER, VERSION, STATUS, UPGRADED FROM SCHEMA_VERSION_REGISTRY;
If the number in the "VERSION" column is 11.1.1.5.0, then the schema is supported for upgrade.
Note:
If you are using an Oracle database, you should recompile database objects before running the Patch Set Assistant by connecting to the database as SYS and running the following from SQL*Plus:
@?/rdbms/admin/utlrp.sql
After running utlrp.sql, and before you upgrade your schema, issue the following query to ensure there are no longer any invalid database objects:
SELECT owner, object_name FROM all_objects WHERE status='INVALID';
Take note of any invalid objects. The existence of invalid database objects may prevent the upgrade from completing successfully.
To start Patch Set Assistant, do the following:
Move from your present working directory to the <MW_HOME>/oracle_common/bin directory by running the following command on the command line:
cd <MW_HOME>/oracle_common/bin
Run the following command:
./psa
Move from your present working directory to the <MW_HOME>\oracle_common\bin directory by running the following command on the command line:
cd <MW_HOME>\oracle_common\bin
Execute the following command:
psa.bat
Note:
Even if you upgrade your schemas from 11.1.1.5.0 to 11.1.2.0.0, you will see the Patch Set Assistant version number as 11.1.1.6.1 on the Welcome screen.
This is not an error. The discrepancy is caused by a difference between how Patch Set Assistant and Identity Access Management releases are tracked internally.
After starting the Patch set Assistant Installer, follow the instructions on the screen to update your schemas.
Follow the instructions in Table 5-2 to update your schemas:
Table 5-2 Patch Set Assistant Screens
| Screen | Description |
|---|---|
|
Welcome |
This page introduces you to Patch Set Assistant. |
|
Select Component |
Select the top-level component you want to upgrade. |
|
Prerequisite |
Verify that you have satisfied the database prerequisites. |
|
Schema |
Specify your database credentials to connect to your database, then select the schema you want to update. Note that this screen appears once for each schema that must be updated as a result of the component you selected on the Select Component screen. |
|
Examine |
This page displays the status of the Patch Set Assistant as it examines each component schema. Verify that your schemas have a "successful" indicator in the Status column. |
|
Upgrade Summary |
Verify that the schemas are the ones you want to upgrade. |
|
Upgrade Progress |
This screen shows the progress of the schema upgrade. |
|
Upgrade Success |
Once the upgrade is successful, you get this screen. |
You can verify the upgrade by checking out log files. The Patch Set Assistant writes log files in the following locations:
On UNIX:
<MW_HOME>/oracle_common/upgrade/logs/psatimestamp.log
On Windows:
<MW_HOME>\oracle_common\upgrade\logs\psatimestamp.log
Some components create a second log file named psatimestamp.out in the same location.
The timestamp reflects the actual date and time that Patch Set Assistant was run.
If any failures occur when running Patch Set Assistant, you can use these log files to help diagnose and correct the problem. Do not delete them. You can alter the contents of the log files by specifying a different -logLevel from the command line.
Some of the operations performed by Patch Set Assistant may take longer to complete than others. If you want to see the progress of these long operations, you can see this information in the log file, or you can use the following query:
SELECT VERSION, STATUS, UPGRADED FROM SCHEMA_VERSION_REGISTRY WHERE OWNER='schema_name';
In the query results, the STATUS field is either UPGRADING or UPGRADED during the schema patching operation, and becomes VALID when the operation is completed.
You must create Oracle Platform Security Services (OPSS) schema because Oracle Adaptive Access Manager upgrade process involves OPSS schema policy store changes. Keys, roles, permissions, and other artifacts used by the applications must migrate to the policy store.
Run Repository Creation utility (RCU) to create the OPSS schema.
For more information, see "Creating Schemas" in the Oracle Fusion Middleware Repository Creation Utility User's Guide.
Note:
In the Select Components screen, expand AS Common Schemas and select Oracle Platform Security Services. The Metadata Services schema is selected automatically. Deselect it and ignore the following message:
Following components require Metadata Services schema: Oracle Platform Security Services.
Oracle Adaptive Access Manager 11.1.2 uses the database to store policies. This requires extending the 11.1.1.5.0 Oracle Adaptive Access Manager domain to include the OPSS data source.
To do so, complete the following steps:
Run the following command to launch the Oracle Fusion Middleware configuration wizard:
On UNIX:
./config.sh
It is located in the <MW_HOME>/<Oracle_IDM1>/common/bin directory.
On Windows:
config.cmd
It is located in the <MW_HOME>\<Oracle_IDM1>\common\bin directory.
On the Welcome screen, select the Extend an existing WebLogic domain option. Click Next.
On the Select a WebLogic Domain Directory screen, browse to the directory that contains the WebLogic domain in which you configured the components. Click Next. The Select Extension Source screen is displayed.
On the Select Extension Source screen, select the Oracle Platform Security Service - 11.1.1.0 [Oracle_IDM1] option. After selecting the domain configuration options, click Next.
The Configure JDBC Data Sources screen is displayed. Configure the opssDS data source, as required. After the test succeeds, the Configure JDBC Component Schema screen is displayed.
On the Configure JDBC Component Schema screen, select the Oracle Platform Security Services schema.
You can set values for Schema Owner, Schema Password, Database and Service, Host Name, and Port. Click Next.
The Test JDBC Component Schema screen is displayed. After the test succeeds, the Select Optional Configuration screen is displayed.
On the Select Optional Configuration screen, you can configure Managed Servers, Clusters, and Machines and Deployments and Services. Do not select anything as you have already configured in your Oracle Identity and Access Management 11.1.1.5.0 environment. Click Next.
On the Configuration Summary screen, review the domain configuration, and click Extend to start extending the domain.
Your existing Oracle Adaptive Access Manager domain is extended to support Oracle Platform Security Services (OPSS).
To upgrade Oracle Platform Security Services (OPSS) schema, do the following:
Move from your present working directory to the <MW_HOME>/oracle_common/common/bin directory by running the following command on the command line:
cd <MW_HOME>/oracle_common/common/bin
Run the following command to launch the WebLogic Scripting Tool (WLST):
./wlst.sh
At the WLST prompt, run the following command:
upgradeOpss(jpsConfig="existing_jps_config_file", jaznData="system_jazn_data_file")
For example:
upgradeOpss(jpsConfig="<MW_HOME>/user_projects/domains/base_domain/config/fmwconfig/jps-config.xml",jaznData="<MW_HOME>/oracle_common/modules/oracle.jps_11.1.1/domain_config/system-jazn-data.xml")
Exit the WLST console using the exit()command.
Move from your present working directory to the <MW_HOME>\oracle_common\common\bin directory by running the following command on the command line:
cd <MW_HOME>\oracle_common\common\bin
Run the following command to launch the WebLogic Scripting Tool (WLST):
wlst.cmd
At the WLST prompt, run the following command:
upgradeOpss(jpsConfig="existing_jps_config_file", jaznData="system_jazn_data_file")
For example:
upgradeOpss(jpsConfig="<MW_HOME>\\user_projects\\domains\\base_domain\\config\\fmwconfig\\jps-config.xml",jaznData="<MW_HOME>\\oracle_common\\modules\\oracle.jps_11.1.1\\domain_config\\system-jazn-data.xml")
Exit the WLST console using the exit() command.
Table 5-3 describes the parameters you need to specify on the command line:
Table 5-3 Parameters for Upgrading OPSS
| Parameter | Description |
|---|---|
|
|
Specify the path to the On UNIX, it is located in the On Windows, it is located in the |
|
|
Specify the path to the system-jazn-data.xml file in your 11.1.2 installation. The following example shows the complete path: On UNIX, it is located in the On Windows, it is located in the |
You must configure the database Security Store as it is the only security store type supported by Oracle Identity and Access Management 11g Release 2 (11.1.2).
For more information on configuring Oracle Platform Security Services, see "Configuring Database Security Store for an Oracle Identity and Access Management Domain" in the Oracle Fusion Middleware Installation Guide for Oracle Identity and Access Management.
To support the latest features and changes that are included in this release, you must upgrade the Oracle Adaptive Access Manager database schema to 11.1.2.0.0. This schema upgrade is done through an offline WLST command.
To upgrade the Oracle Adaptive Access Manager schema, complete the following steps:
Open access_upgrade.properties file in a text editor from the following location:
$<ORACLE_HOME>/common/wlst
Update the values, as listed in Table 5-4:
Move from your present working directory to the <IAM_HOME>/common/bin directory by running the following command on the command line:
cd <IAM_HOME>/common/bin
Run the following command to launch the WebLogic Scripting Tool (WLST):
./wlst.sh
Upgrade the Oracle Adaptive Access Manager 11.1.1.5.0 schemas to 11.1.2 schemas by running the following command:
upgradeAccessSchema(filePath="access_upgrade.properties_Location")
where
filepath is the complete the path to the access_upgrade.properties file in the Oracle Adaptive Access Manager installation.
For example:
upgradeAccessSchema(filePath="<MW_HOME>/<Oracle_IDM1>/common/wlst/access_upgrade.properties")
The OAAM_DB_SYS_PASSWORD is prompted. Enter the SYS password.
Open access_upgrade.properties file in a text editor from the following location:
<ORACLE_HOME>\common\wlst
Update the values, as listed in Table 5-4:
Move from your present working directory to the <IAM_HOME>\common\bin directory by running the following command on the command line:
<IAM_HOME>\common\bin
Run the following command to launch the WebLogic Scripting Tool (WLST):
wlst.cmd
Upgrade the Oracle Adaptive Access Manager 11.1.1.5.0 schemas to 11.1.2 schemas by running the following command:
upgradeAccessSchema(filePath="access_upgrade.properties_Location")
where
filepath is the complete the path to the access_upgrade.properties file in the Oracle Adaptive Access Manager installation.
For example:
upgradeAccessSchema(filePath="<MW_HOME>\\<Oracle_IDM1>\\common\\wlst\\access_upgrade.properties")
The OAAM_DB_SYS_PASSWORD is prompted. Enter the SYS password.
Table 5-4 Parameters for Updating access_upgrade.properties File
| Parameters | Description |
|---|---|
|
|
Specify the 11g Oracle Adaptive Access Manager schema user name. |
|
|
The database URL format is |
|
|
Specify SYS as SYSDBA |
|
|
Specify the path to the Oracle Adaptive Access Manager home. The following example shows the complete path: On UNIX, it is located in the On Windows, it is located in the |
|
|
Specify the path to the domain home. The following example shows the complete path: On UNIX, it is located in the On Windows, it is located in the |
|
|
Set the value as The value |
On UNIX:
OAAM_DB_SCHEMA_USERNAME=EXAMPLE_OAAM OAAM_DB_URL=db.example.com:1521:ex OAAM_DB_SYS_USERNAME=sys as sysdba OAAM_ORACLE_HOME=/<MW_HOME>/<IAM_HOME> OAAM_DOMAIN_HOME=/<MW_HOME>/user_projects/domains/<DOMAIN_NAME> OAAM_DB_10g=false
On Windows:
OAAM_DB_SCHEMA_USERNAME=EXAMPLE_OAAM OAAM_DB_URL=db.example.com:1521:ex OAAM_DB_SYS_USERNAME=sys as sysdba OAAM_ORACLE_HOME=\<MW_HOME>\<IAM_HOME> OAAM_DOMAIN_HOME=\<MW_HOME>\user_projects\domains\<DOMAIN_NAME> OAAM_DB_10g=false
The redeploy command is an online WLST command. Therefore, you must start the Oracle Adaptive Access Manager Administration and Managed Servers before running the redeploy command.
Starting Administration Server
To start the Administration Server, do the following:
On UNIX:
Run the following command:
cd <MW_HOME>/user_projects/domains/<domain_name>/bin
./startWebLogic.sh
On Windows:
Run the following command:
cd <MW_HOME>\user_projects\domains\<domain_name>\bin
startWebLogic.cmd
To start the Managed Servers, do the following:
On UNIX:
Move from your present working directory to the <MW_HOME>/user_projects/domains/<domain_name>/bin directory by running the following command on the command line:
cd <MW_HOME>/user_projects/domains/<domain_name>/bin
Run the following command to start the Servers:
./startManagedWebLogic.sh <managed_server_name> <admin_url> <user_name> <password>
where
<managed_server_name> is the name of the Managed Server
<admin_url> is URL of the WebLogic administration console. Specify it in the format http://<host>:<port>/console. Specify only if the WebLogic Administration Server is on a different computer.
<user_name> is the username of the WebLogic Administration Server.
<password> is the password of the WebLogic Administration Server.
On Windows:
Move from your present working directory to the <MW_HOME>\user_projects\domains\<domain_name>\bin directory by running the following command on the command line:
cd <MW_HOME>\user_projects\domains\<domain_name>\bin\
Run the following command to start the Managed Servers:
startManagedWebLogic.cmd <managed_server_name> <admin_url> <user_name> <password>
where
<managed_server_name> is the name of the Managed Server.
<admin_url> is URL of the administration console. Specify it in the format http://<host>:<port>/console. Specify only if the WebLogic Administration Server is on a different computer.
<user_name> is the username of the WebLogic Administration Server.
<password> is the password of the WebLogic Administration Server.
For more information, see "Starting the Stack" in the Oracle Fusion Middleware Installation Guide for Oracle Identity and Access Management.
You must redeploy changes to the application in the domain after upgrading. Redeploy your 11.1.1.5.0 application on the Oracle Adaptive Access Manager 11.1.2 servers.
To redeploy, complete the following steps:
Move from your present working directory to the <IAM_HOME>/common/bin directory by running the following command on the command line:
cd <IAM_HOME>/common/bin
Run the following command to launch the WebLogic Scripting Tool (WLST):
./wlst.sh
Connect to the Administration Server using the following command:
connect('weblogic-username','weblogic-password','weblogic-url')
At the WLST prompt, run the following WLST command:
redeployApps($<ORACLE_HOME>,adminTarget='<oaam_admin_server1>',serverTarget='<oaam_server_server1>')
Where
<oaam_server_server1> is the Managed Server on which the Oracle Adaptive Access Manager server application is deployed.
Note:
Include offline Target, if Oracle Adaptive Access Manager Offline Server is present in your setup.
Exit the WLST console using the exit() command.
Move from your present working directory to the <IAM_HOME>\common\bin directory by running the following command on the command line:
cd <IAM_HOME>\common\bin
Run the following command:
wlst.cmd
Connect to the Administration Server using the following command:
connect('weblogic-username','weblogic-password','weblogic-url')
At the WLST prompt, run the following WLST command:
redeployApps(<MW_HOME>\\<IAM_HOME>,adminTarget='<oaam_admin_server1>',serverTarget='<oaam_server_server1>')
Where
<oaam_server_server1> is the Managed Server on which the Oracle Adaptive Access Manager server application is deployed.
Note:
Include offlineTarget, if Oracle Adaptive Access Manager Offline Server is present in your setup.
Exit the WLST console using the exit() command.
To deploy Oracle Adaptive Access Manager 11.1.1.5.0 server content and applications in Oracle Adaptive Access Manager 11.1.2, you must delete all content of folders in the following locations:
Deleting tmp:
<MW_Home>/user_projects/domains/domain_home/servers/<OAAM_ADMIN_SERVER_NAME>/tmp
<MW_Home>/user_projects/domains/domain_home/servers/<OAAM_MANAGED_SERVER_NAME>/tmp
<MW_Home>/user_projects/domains/domain_home/servers/<OAAM_OFFLINE_SERVER_NAME>/tmp
Deleting stage:
<MW_Home>/user_projects/domains/domain_home/servers/<OAAM_ADMIN_SERVER_NAME>/stage
<MW_Home>/user_projects/domains/domain_home/servers/<OAAM_MANAGED_SERVER_NAME>/stage
<MW_Home>/user_projects/domains/domain_home/servers/<OAAM_OFFLINE_SERVER_NAME>/stage
Deleting tmp:
<MW_Home>\user_projects\domains\domain_home\servers\<OAAM_ADMIN_SERVER_NAME>\tmp
<MW_Home>\user_projects\domains\domain_home\servers\<OAAM_MANAGED_SERVER_NAME>\tmp
<MW_Home>\user_projects\domains\domain_home\servers\<OAAM_OFFLINE_SERVER_NAME>\tmp
Deleting stage:
<MW_Home>\user_projects\domains\domain_home\servers\<OAAM_ADMIN_SERVER_NAME>\stage
<MW_Home>\user_projects\domains\domain_home\servers\<OAAM_MANAGED_SERVER_NAME>\stage
<MW_Home>\user_projects\domains\domain_home\servers\<OAAM_OFFLINE_SERVER_NAME>\stage
To restart the Administration Server or Managed Servers, you must stop the running Administration Server or Managed Servers first before starting them again.
To stop the servers, see Section 5.2, "Shutting Down Administration Server and Managed Servers".
To start the servers, see Section 5.12, "Starting the Administration Server and Oracle Adaptive Access Manager Managed Servers".
Perform the following additional post-upgrade tasks after upgrading your Oracle Adaptive Access Manager 11.1.1.5.0 environment to Oracle Adaptive Access Manager 11.1.2, if required.
Note:
Perform the following task only if you have integrated Oracle Adaptive Access Manager with Oracle Identity Manager in 11.1.1.5.0.
Upgrade the Self Registration and Self Tracking URLs as follows:
Log in to the Oracle Adaptive Access Manager Administration console:
http://oaam_managed_server_host:oaam_admin_managed_server_port/oaam_admin
You must log in as a user with access to the Properties Editor.
Open the Oracle Adaptive Access Manager Property Editor and upgrade the following:
bharosa.uio.default.signon.links.enum.selfregistration.url: Specify the Self Registration URL.
For example:
http://<OIM Managed Server Host>:<OIM Managed Server Port>/identity/faces/register?&=backUrl=<back URL>
bharosa.uio.default.signon.links.enum.trackregistration.url: Specify the Track Registration URL.
For example:
http://<OIM Managed Server Host>:<OIM Managed Server Port>/identity/faces/trackregistration?&=backUrl=<back URL>
Complete the following steps to upgrade your security policies without erasing your old policies:
Back up all of your old policies.
Export the policies, policies are exported as snapshots.
Import base entities, if you have not done so in the earlier release.
Import patterns.
Import policies.
Note:
If you want to completely move to new content, back up the old content and import the new snapshot.If you want to continue using old policies with the risk involved, no action is required.
Use the following URL in a web browser to verify that Oracle Adaptive Access Manager 11.1.2 is running:
http://oaam.example.com:<oaam_port>/oaam_admin
Assign the investigator role and verify to see the investigator UI.