This section discusses the following topics:
This topic explains the steps that are common to starting most Oracle Identity Management installations and configurations. It begins with starting the Installer and ends after you complete the steps on the Prerequisites Check screen.
Note:
Starting the Installer as theroot user is not supported.Perform the following steps to start an Oracle Identity Management installation:
Extract the contents of the iamsuite.zip file to a directory. By default, this directory is named iamsuite.
Move to the Disk1 directory under the iamsuite folder.
Start the Installer by executing one of the following commands:
UNIX: <full path to the runInstaller directory>/runInstaller -jreLoc <Middleware Home>/jrockit_160_17/jre
Windows: <full path to the setup.exe directory>\ setup.exe -jreLoc <Middleware Home>\jrockit_160_17\jre
Note:
The installer prompts you to enter the absolute path of the JDK that is installed on your system. When you install Oracle WebLogic Server, thejrockit_160_17 directory is created under your Middleware Home. You must enter the absolute path of the JRE folder located in this JDK when launching the installer. For example, on Windows, if the JRE is located in D:\oracle\Middleware\jrockit_160_17, then launch the installer from the command prompt as follows:
D:\setup.exe -jreLoc D:\oracle\Middleware\jrockit_160_17\jre
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.
After the Installer starts, continue by referring to Installing and Configuring OIM, OAM, OAAM, OAPM, and OIN (11.1.1.3.0).
To start the Oracle Fusion Middleware Configuration Wizard, which is used to configure Oracle Identity Management products in a new or existing WebLogic administration domain, run the <IDM_Home>/common/bin/config.sh script (on UNIX). On Windows, run the <IDM_Home>\common\bin\config.cmd script. The Oracle Fusion Middleware Configuration Wizard is displayed.
Note:
When you run theconfig.cmd or config.sh command, the following error message might be displayed:
*sys-package-mgr*: can't create package cache dir
The error message indicates that the default cache directory is not valid. You can change the cache directory by including the -Dpython.cachedir=<valid_directory> option in the command line.
After starting the Oracle Fusion Middleware Configuration Wizard, configure Oracle Identity Management products, as described in the following links:
Table 4-2 lists the executable files that are included in the Oracle WebLogic Server, Oracle Identity Management, Oracle SOA Suite, Oracle Web Tier, and Oracle HTTP Server 11g Webgate for Oracle Access Manager Installers.
| File | Description |
|---|---|
|
After you extract the contents of the |
Oracle Identity Management 11g Release 1 (11.1.1.3.0) Installer for Oracle Identity Manager, Oracle Access Manager, Oracle Adaptive Access Manager, Oracle Authorization Policy Manager, and Oracle Identity Navigator |
|
|
Oracle WebLogic Server 10.3.3 Installer |
|
After you extract the contents of the |
Oracle SOA Suite 11g Release 1 (11.1.1.2.0) Installer |
|
After you extract the contents of the |
Oracle SOA Suite 11g Release 1 (11.1.1.3.0) Patch Set Installer |
|
After you extract the contents of the |
Oracle Web Tier 11g Release 1 (11.1.1) Installer |
|
After you extract the contents of the |
Oracle HTTP Server 11g Webgate for Oracle Access Manager Installer |
|
After you extract the contents of the |
Oracle Fusion Middleware Repository Creation Utility (RCU) |
This topic describes directories you must identify in most Oracle Identity Management installations and configurations—it does not describe one particular Installer screen. During installation, you will have to identify other component-specific directories not described in this topic.
The common directories described in this section include the following:
Identify the location of your Oracle Middleware Home directory. The Installer creates an Oracle Home directory for the component you are installing under the Oracle Middleware Home that you identify in this field. The Oracle Middleware Home directory is commonly referred to as MW_HOME.
Enter a name for the Oracle Home directory of the component. The Installer uses the name you enter in this field to create the Oracle Home directory under the location you enter in the Oracle Middleware Home Location field.
The Installer installs the files required to host the component, such as binaries and libraries, in the Oracle Home directory. The Oracle Home directory is commonly referred to as ORACLE_HOME.
Note:
Avoid using spaces in the directory names, including Oracle Home. Spaces in such directory names are not supported.The Installer creates this directory under the location you enter in the Oracle Middleware Home Location field.
The Installer installs the Oracle Java Required Files (JRF) required to host the components, in the Oracle Common directory. There can be only one Oracle Common Home within each Oracle Middleware Home. The Oracle Common directory is commonly referred to as oracle_common.
A WebLogic domain includes a special WebLogic Server instance called the Administration Server, which is the central point from which you configure and manage all resources in the domain. Usually, you configure a domain to include additional WebLogic Server instances called Managed Servers. You deploy Java components, such as Web applications, EJBs, and Web services, and other resources to the Managed Servers and use the Administration Server for configuration and management purposes only.
Managed Servers in a domain can be grouped together into a cluster.
The directory structure of a domain is separate from the directory structure of the WebLogic Server home. It can reside anywhere; it need not be within the Middleware home directory. A domain is a peer of an Oracle instance.
The Oracle Fusion Middleware Configuration Wizard creates a domain in a directory named user_projects under your Middleware Home (MW_HOME).
Enter the path to your Oracle WebLogic Server Home directory. This directory contains the files required to host the Oracle WebLogic Server. It is commonly referred to as WL_HOME.
If you want to install an Oracle Identity Management 11g Release 1 (11.1.1) component against an existing Oracle Identity Management 11g Release 1 (11.1.1) component, you may need to identify the ports for the existing component. For example, if you want to install Oracle Identity Manager 11g Release 1 (11.1.1) against an existing Oracle Internet Directory 11g Release 1 (11.1.1) component, you must identify its port when you install Oracle Identity Manager.
This topic explains the steps that are common to completing most Oracle Identity Management installations and configurations. It begins with the steps on the Installation Summary screen and ends after the Installation Complete screen.
When the Installation Summary screen appears, perform the following steps to complete the installation:
Verify the installation and configuration information on the Installation Summary screen.
Click Save to save the installation response file, which contains your responses to the Installer prompts and fields. You can use this response file to perform silent installations. Refer to Performing a Silent Installation for more information.
Note:
The installation response file is not saved by default—you must click Save to retain it.Click Install. The Installation Progress screen appears.
Monitor the progress of your installation. The location of the installation log file is listed for reference. After the installation progress reaches 100%, click OK. The Installation Complete screen appears.
Click Save to save the installation summary file. This file contains information about the configuration, such as locations of install directories, that will help you get started with configuration and administration.
Note:
The installation summary file is not saved, by default—you must click Save to retain it.Click Finish to close and exit the Installer.
The Installer writes log files to the ORACLE_INVENTORY_LOCATION/logs directory on UNIX systems and to the ORACLE_INVENTORY_LOCATION\logs directory on Windows systems.
On UNIX systems, if you do not know the location of your Oracle Inventory directory, you can find it in the ORACLE_HOME/oraInst.loc file.
On Microsoft Windows systems, the default location for the inventory directory is C:\Program Files\Oracle\Inventory\logs.
The following install log files are written to the log directory:
installDATE-TIME_STAMP.log
installDATE-TIME_STAMP.out
installActionsDATE-TIME_STAMP.log
installProfileDATE-TIME_STAMP.log
oraInstallDATE-TIME_STAMP.err
oraInstallDATE-TIME_STAMP.log
Read this section only if the user name for the WebLogic Administrator for the domain is not weblogic. This task is required only if you are using Oracle Identity Manager.
If your WebLogic administrator user name is not weblogic, complete the following steps:
Ensure that the Oracle Identity Manager Managed server is up and running.
Log in to Oracle Enterprise Manager Fusion Middleware Control using your WebLogic Server administrator credentials.
Click Identity and Access > oim > oim(11.1.1.2.0). Right-click and select System MBean Browser. The System MBean Browser page is displayed.
Under Application Defined MBeans, select oracle.iam > Server:oim_server1 > Application: oim > XMLConfig > config > >XMLConfig.SOAConfig > SOAConfig.
View the attribute username. By default, the value of the attribute is weblogic. Change this value to your WebLogic administrator user name.
Click Apply. Exit Oracle Enterprise Manager Fusion Middleware Control.
On the command line, use the cd command to move from your present working directory to the Oracle_IDM2/common/bin directory. Oracle_IDM2 is the example IDM_Home directory for Oracle Identity Manager, Oracle Access Manager, Oracle Adaptive Access Manager, Oracle Authorization Policy Manager, and Oracle Identity Navigator.
Launch the WebLogic Scripting Tool (WLST) interface as follows:
On UNIX: Run ./wlst.sh on the command line.
On Windows: Run wlst.cmd.
At the WLST command prompt (wls:/offline>), type the following:
connect()
You are prompted to enter the WebLogic Administration Server user name, password, and URL. For more information about using the WLST interface, see the topic "Using the WebLogic Scripting Tool" in the guide Oracle Fusion Middleware Oracle WebLogic Scripting Tool.
Run the deleteCred WLST command:
deleteCred(map="oim", key="SOAAdminPassword");
Run the createCred WLST command, and replace the ADMIN_PASSWORD with your WebLogic administrator password:
createCred(map="oim", key="SOAAdminPassword", user="xelsysadm",password="<ADMIN_PASSWORD>");
Run the following WLST command to verify the values:
listCred(map="oim", key="SOAAdminPassword");
Type exit() to exit the WLST command shell.
Open the Oracle Identity Manager Administration Console, and log in as user xelsysadm.
Create a new user for the user name of your WebLogic administrator.
Search for the Administrators role. Open the role details, and click the Members tab.
Remove all the existing members of the Administrators role.
Add the newly created user (the one with your WebLogic administrator user name) as a member of the Administrators role.
Restart Oracle Identity Manager Managed Server, as described in Starting the Stack.