This chapter describes how to install and deinstall the Oracle Identity and Access Management software from the command line. This is often referred to as installing or deinstalling in silent mode, since it does not involve use of the Oracle Universal Installer (OUI) graphical user interface.
This chapter contains the following content:
Section 4.3, "Typical Silent Installation Procedures for Oracle Fusion Middleware Products"
Section 4.4, "End-to-End Silent Installation and Configuration for Oracle Identity Manager"
Silent installation eliminates the need to monitor your product installation because no graphical output is displayed and no input by the user is required.
Silent installation of your Oracle Fusion Middleware product is accomplished by using the -silent flag on the command line when you start the installer. In most cases, you will need to supply the location and name of a file containing certain variable and parameter values (for example, installation location). These are the values that would be asked for during a typical installation using the graphical user interface.
For Oracle Fusion Middleware products, this file is typically called a response file. For more information, see Section 4.2, "Understanding Response Files".
Note:
For UNIX users, if this is a first time installation of any Oracle product, you must create the oraInst.loc file before starting. Please refer to Section 4.3.1.1, "UNIX Users: Creating the oraInst.loc File" for more information.
Following installation of your product, you need to run the root.sh script as the root user. The root.sh script detects settings of environment variables and enables you to enter the full path of the local bin directory.
Note:
For Windows users, if this is a first time installation of any Oracle product, you must create the registry keys before starting. Registry key creation is described in Section 4.3.1.2, "Windows Users: Creating the Registry Key"
Before doing a silent installation, you must provide information specific to your installation in a response file. The installer will fail if you attempt an installation using a response file that is not configured correctly. Response files are text files that you can create or edit in a text editor.
Oracle recommends creating a response file in the following manner:
Run your product's graphical installer or configuration tool, as described in your product installation or configuration guide.
On the Installation Summary screen of the installer (or on the summary screen of the configuration tool), click Save to save your installation or configuration parameters to a response file.
You will be prompted for a name and location where you want to create this response file. After it is created, you can use it exactly as-is to replicate the installation on other systems, or modify it as needed.
Pre-existing sample response files for most Oracle Fusion Middleware product installers are provided in the Disk1/stage/Response (on UNIX operating systems) or Disk1\stage\Response (on Windows operating systems) directory in the location where you unzipped your downloaded archive files for installation.
Refer to your product installation guide for more detailed descriptions of the sample installation and deinstallation response files that are provided for each product.
Your response files contain certain passwords required by the installer. To minimize security issues regarding these passwords in the response file, follow these guidelines:
Set the permissions on the response files so that they are readable only by the operating system user who will be performing the silent installation.
If possible, remove the response files from the system after the silent installation is completed.
The following sections provide general information for using silent installation, configuration, and deinstallation procedures for most Oracle Fusion Middleware products:
Section 4.3.5, "Silent Product Configuration for Oracle Fusion Middleware Products"
Section 4.3.6, "Silent Product Deinstallation for Oracle Fusion Middleware Products"
This section covers the pre-installation tasks that may be required before you are able to perform a silent installation.
The following topics are covered:
oraInst.loc FileThe Oracle inventory directory is used by the installer to keep track of all Oracle products installed on the computer. The inventory directory is stored in a file called oraInst.loc. If this file does not already exist on your system, you must create it before starting a silent installation. This file is used by the installer.
Log in as the root user.
prompt> su
Using a text editor such as vi or emacs, create the oraInst.loc file in the directory of your choice. The contents of the file consist of the following two lines:
inventory_loc=oui_inventory_directory inst_group=oui_install_group
Replace oui_inventory_directory with the full path to the directory where you want the installer to create the inventory directory. Then, replace oui_install_group with the name of the group whose members have write permissions to this directory.
Exit from the root user.
# exit
If you have not installed Oracle SOA Suite on your computer, then you need to create the following Registry key and value:
HKEY_LOCAL_MACHINE / SOFTWARE / Oracle / inst_loc = [inventory_directory]
Replace Inventory_Directory with the full path to your installer files. For example:
C:\Program Files\Oracle\Inventory
If your Oracle Fusion Middleware product requires database schemas, you must first create the schemas in your database before installing and configuring your product.
For instructions on how to create the schemas in silent mode, refer to "Running Repository Creation Utility (RCU) from the Command Line" in Oracle Fusion Middleware Repository Creation Utility User's Guide.
Installation of all Oracle Fusion Middleware products requires the presence of an Oracle Middleware home directory, which can be created by installing Oracle WebLogic Server.
To install Oracle WebLogic Server in silent mode, refer to "Running the Installation Program in Silent Mode" in Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server.
To install your Oracle Fusion Middleware product in silent mode, use the -silent mode from the command line. The full syntax for running the installer from the command line on UNIX operating systems is shown below:
runInstaller [-mode] [-options] [(<CommandLinevariable=Value>)*]
On Windows operating systems:
setup.exe [-mode] [-options] [(<CommandLinevariable=Value>)*]
Table 4-1 lists the valid command line parameters for silent installation.
Table 4-1 Installer Command Line Parameters
| Parameter | Description |
|---|---|
|
Installation Modes - Only One Mode Can be Specified |
|
|
|
Launches the installer in GUI mode. This is the default mode and is used if no mode is specified on the command line. |
|
|
Install in silent mode. The installer must be passed either a response file or command line variable value pairs. |
|
|
Launches the installer in GUI mode for deinstallation. NOTE - this option is only available when you start the deinstaller from the |
|
|
Launches the installer in GUI mode but only checks the prerequisites. No software is installed. |
|
|
Launches the installer in GUI mode and performs all prerequisite and validation checking, but does not install any software. |
|
|
Performs all prerequisite and validation checking in silent mode. You must pass the installer either a response file or a series of command line variable value pairs. |
|
Installation Options |
|
|
|
Displays the usage parameters for the |
|
|
Pointer to the inventory location file. Replace file with the full path and name of the |
|
|
Pointer to the response file. Replace file with the full path and name of the response file. See Section 4.2, "Understanding Response Files" for information about creating the response files. |
|
|
Pointer to the location where Java Runtime Environment (JRE) is installed. Replace location with the full path to the |
|
|
Specify the level of logging performed by the installer; all messages with a lower priority than the specified level will be recorded. Valid levels are:
|
|
|
Obtain debug information from the installer. |
|
|
Allow the silent installation to proceed in a non-empty directory. |
|
|
Log debugging information pertaining to disk usage. |
|
|
Log debugging information pertaining to memory usage. |
|
|
Log debugging information pertaining to time usage. This command causes the |
|
|
Windows only - the installer will wait for completion instead of spawning the Java engine and exiting. |
|
|
Messages will not be displayed to the console window. |
|
|
Ignore the results of the system prerequisite checks and continue with the installation. |
|
|
Execute the system prerequisite checks only, then exit. |
|
|
Specify the full path to the |
|
|
Disables all validation checking performed by the installer. |
|
|
For the GUI install, several screens have information or default values pre-populated. Specifying this option disables this behavior so that no information or values are pre-populated. |
|
Command Line Variables |
|
|
Installer Variables |
Installer variables are specified using ORACLE_HOME=/home/Oracle/Middleware/as_1 On a Windows operating system: ORACLE_HOME=C:\products\Oracle\Middleware\as_1 |
|
Session Variables |
Session variables are specified using |
|
Component Variables |
Component variables are specified using |
If this is the first time you are installing on your system (meaning there is no pre-existing Oracle Inventory location), use the following command to perform a silent installation on UNIX systems:
./runInstaller -silent -response file -invPtrLoc file
On Windows systems:
setup.exe -silent -response file -invPtrLoc file
Below is a full example of this command for UNIX systems:
./runInstaller -silent -response /home/Oracle/response/devSOA.rsp -invPtrLoc /home/jdoe/oraInst.loc
On Windows operating systems:
setup.exe -silent -response C:\home\Oracle\response\devSOA.rsp -invPtrLoc c:\home\Oracle\oraInst.loc
If you have already installed an Oracle product on your system and do not need to specify an inventory location, then you can use a command similar to the following on UNIX systems:
./runInstaller -silent -response file
On Windows systems:
setup.exe -silent -response file
Below is a full example of this command on a UNIX system:
./runInstaller -silent -response /home/Oracle/response/devSOA.rsp
On Windows operating systems:
setup.exe -silent -response c:\home\Oracle\response\devSOA.rsp
Below is a sample output from a silent Oracle SOA Suite installation using the sampleResponse_wls.rsp template:
$ ./runInstaller -jreLoc /home/Oracle/Middleware/jdk160_21/ -silent -response /home/Oracle/response/sampleResponse_wls.rsp Platform is Linux X86 32 bit Starting Oracle Universal Installer... Checking if CPU speed is above 300 MHz. Actual 2999 MHz Passed Checking Temp space: must be greater than 150 MB. Actual 69669 MB Passed Checking swap space: must be greater than 512 MB. Actual 1395 MB Passed Preparing to launch Oracle Universal Installer from /tmp/OraInstall2009-04-03_10-49-20PM. Please wait ...[jdoe@examplehost Disk1]$ Log: /home/Oracle/oraInventory/logs/install2009-04-03_10-49-20PM.log Copyright © 1999, 2011, Oracle and/or its affiliates. All rights reserved. Reading response file.. Expected result: One of enterprise-4,enterprise-5,redhat-4,redhat-5,SuSE-10 Actual Result: enterprise-4 Check complete. The overall result of this check is: Passed CertifiedVersions Check: Success. Checking for gcc-3.4.3-22.1; found gcc-3.4.6-10.0.1-i386. Passed Checking for gcc-c++-3.4.3-22.1; found gcc-c++-3.4.6-10.0.1-i386. Passed Checking for openmotif21-2.1.30-11.RHEL4.4 ; found openmotif21-2.1.30-11.0.1.RHEL4.6-i386. Passed Checking for setarch-1.6-1; found setarch-1.6-1-i386. Passed Checking for pdksh-5.2.14-30; found pdksh-5.2.14-30.6-i386. Passed Checking for sysstat-5.0.5-1; found sysstat-5.0.5-19.el4-i386. Passed Checking for gnome-libs-1:1.4.1.2.90-44.1; found gnome-libs-1:1.4.1.2.90-44.2-i386. Passed Checking for libstdc++-3.4.3-22.1 ; found libstdc++-3.4.6-10.0.1-i386. Passed Checking for libstdc++-devel-3.4.3-22.1; found libstdc++-devel-3.4.6-10.0.1-i386. Passed Checking for compat-libstdc++-296-2.96-132.7.2; found compat-libstdc++-296-2.96-132.7.2-i386. Passed Checking for compat-db-4.1.25-9; found compat-db-4.1.25-9-i386. Passed Checking for control-center-2.8.0-12; found control-center-1:2.8.0-12.rhel4.5-i386. Passed Checking for glibc-common-2.3.4-2.9; found glibc-common-2.3.4-2.41-i386. Passed Checking for binutils-2.15.92.0.2-13; found binutils-2.15.92.0.2-25-i386. Passed Checking for make-1:3.80-5; found make-1:3.80-7.EL4-i386. Passed Checking for xscreensaver-4.18-5.rhel4.2; found xscreensaver-1:4.18-5.rhel4.14.0.1-i386. Passed Check complete. The overall result of this check is: Passed Packages Check: Success. Checking for VERSION=2.6.9; found VERSION=2.6.9-78.0.0.0.1.ELxenU. Passed Checking for hardnofiles=4096; found hardnofiles=4096. Passed Checking for softnofiles=4096; found softnofiles=4096. Passed Check complete. The overall result of this check is: Passed Kernel Check: Success. Expected result: ATLEAST=2.3.4-2.19 Actual Result: 2.3.4-2.41 Check complete. The overall result of this check is: Passed GLIBC Check: Success. Expected result: 922MB Actual Result: 4000MB Check complete. The overall result of this check is: Passed TotalMemory Check: Success. Verifying data...... Copying Files... -----------20%----------40%----------60%----------80%--------100% The installation of Oracle SOA Suite 11g completed successfully.
The way in which you can configure your Oracle Fusion Middleware product from the command line varies depending on the type of product.
See the following sections for more information:
If your product contains system components (for example, Oracle Web Tier, Oracle Portal, Forms, Reports and Discoverer, or Oracle Identity Management), you can use the same commands as described in Section 4.3.4, "Silent Product Installation".
These products use the same engine for both installation and configuration, so the contents of the response file determine whether you are only installing the software, only configuring existing software, or installing and configuring at the same time.
As mentioned in Section 4.2, "Understanding Response Files", the recommended way to create these response files is to run the graphical installer once and save the configuration to a response file. Each product also comes with sample response files that you can use. Refer to the product installation guides for more information.
If your product contains Java components (for example, Oracle SOA Suite, or Oracle WebCenter), the installer and the Configuration Wizard are essentially different products and therefore you cannot configure your products silently using the same silent installation commands.
Instead, silent configuration for Java components must be done using WebLogic Scripting Tool (WLST) commands.
For more information, refer to:
To deinstall the Oracle Fusion Middleware product software on your system (both system and java components), use the -d or -deinstall parameter from the command line. You must start the deinstaller from the ORACLE_HOME/oui/bin (on UNIX operating systems) or ORACLE_HOME\oui\bin (on Windows operating systems) directory; this is the only directory where the -d or -deinstall parameters are accepted.
On UNIX operating systems:
./runInstaller -silent -deinstall -response file
On Windows operating systems:
setup.exe -silent -deinstall -response file
Table 4-2 lists the valid command line parameters for silent deinstallation.
Table 4-2 Deinstaller Command Line Parameters
| Parameter | Description |
|---|---|
|
Installation Modes - Only One Mode Can be Specified |
|
|
|
Launches the installer in GUI mode for deinstallation. |
|
Installation Options |
|
|
|
Displays the usage parameters for the |
|
|
Pointer to the inventory location file. Replace file with the full path and name of the |
|
|
Pointer to the response file. Replace file with the full path and name of the response file. |
|
|
Pointer to the location where Java Runtime Environment (JRE) is installed. Replace location with the full path to the |
|
|
Specify the level of logging performed by the installer; all messages with a lower priority than the specified level will be recorded. Valid levels are:
|
|
|
Obtain debug information from the installer. |
|
|
Allow the silent installation to proceed in a non-empty directory. |
|
|
Log debugging information pertaining to disk usage. |
|
|
Log debugging information pertaining to memory usage. |
|
|
Log debugging information pertaining to time usage. This command causes the |
|
|
Windows only - the installer will wait for completion instead of spawning the Java engine and exiting. |
|
|
Messages will not be displayed to the console window. |
|
|
Ignore the results of the system prerequisite checks and continue with the installation. |
|
|
Execute the system prerequisite checks only, then exit. |
|
|
Specify the full path to the |
|
|
Disables all validation checking performed by the installer. |
|
|
For the GUI install, several screens have information or default values pre-populated. Specifying this option disables this behavior so that no information or values are pre-populated. |
|
Command Line Variables |
|
|
Installer Variables |
Installer variables are specified using ORACLE_HOME=/home/Oracle/Middleware/as_1 On a Windows operating system: ORACLE_HOME=C:\products\Oracle\Middleware\as_1 |
|
Session Variables |
Session variables are specified using |
|
Component Variables |
Component variables are specified using |
Below is a sample output from a silent deinstall using the deinstall_oh.rsp template:
$ ./runInstaller -silent -deinstall -jreLoc /home/Oracle/Middleware/jdk160_21/ -response /home/Oracle/Response/deinstall_oh.rsp Starting Oracle Universal Installer... Checking swap space: must be greater than 500 MB. Actual 4047 MB Passed Preparing to launch Oracle Universal Installer from /tmp/OraInstall2010-03-26_10-01-21AM. Please wait ...[]$ Log: /home/oraInventory/logs/deinstall2010-03-26_10-01-21AM.log Reading response file.. Starting silent deinstallation... Starting Oracle Home deinstallation... Completed deinstallation of Oracle Home.
The following sections provide an example of how you can perform the end-to-end installation and configuration of the Oracle Identity Manager software using a series of silent installation tools, product-specific scripts, and command-line procedures.
Note:
The procedures in this section apply only to Oracle Identity Manager. For the other Oracle Identity and Access Management products, refer to Section 4.3, "Typical Silent Installation Procedures for Oracle Fusion Middleware Products".
Refer to the following sections for more information:
Before you can begin the automated silent installation procedure, you must:
Download the required software you will be installing in this chapter.
For more information, see "Obtaining the Oracle Fusion Middleware Software" in the Oracle Fusion Middleware Installation Guide for Oracle Identity and Access Management.
Install and configure an instance of a supported Oracle Database.
The database is required for the Oracle Identity and Access Management product schemas.
For more information about the supported database releases, see the Oracle Fusion Middleware Supported System Configurations.
Install the required Java Development Kit (JDK).
For more information about the supported Java Development Kit releases, see the Oracle Fusion Middleware Supported System Configurations.
The following sections describes how to a use set of command line scripts and utilities to install and configure the Oracle Identity Manager software on a single host computer:
Section 4.4.2.1, "About the Silent Installation and Configuration on a Single Host"
Section 4.4.2.3, "Performing the Silent Installation and Configuration on a Single Host"
The command-line steps described here correspond to the standard installation steps described in "Installation and Configuration Roadmap for Oracle Identity Manager" in the Oracle Fusion Middleware Installation Guide for Oracle Identity and Access Management.
Each of the tools and utilities that you use to install and configure Oracle Identity Management has its own command-line or silent operation features. This procedure shows how you can use these tools and features together to perform a complete, end-to-end silent installation of Oracle Identity Management on a single host computer.
The key directory locations referenced in the single-host, silent installation and configuration instructions include the following:
The Oracle home created during the Oracle Identity and Access Management installation. This is the location of the Oracle Identity and Access Management binary software files.
This directory is identified by the variable, IAM_HOME. When referenced, replace this variable with the complete path to the Oracle Identity and Access Management Oracle home.
The Oracle SOA Suite Oracle home created when you install the Oracle SOA Suite software. This directory is identified by the variable SOA_HOME.
The MW_HOME, which refers to the Middleware home, which is where the Oracle Identity Manager and Oracle SOA Suite Oracle homes reside.
The JDK_HOME, which refers to the location of the JDK used to install the Oracle Identity Management software. Replace this variable with the full path to your supported JDK.
For more information, see Section 4.4.1, "Preparing for an Oracle Identity Manager Silent Installation".
The DOWNLOADS_DIR, which refers to the location where you downloaded and unpacked the software archives. This is location from which you run the installer.
The DOMAIN_HOME directory, which refers to the Oracle WebLogic Server domain home directory, which is created when you initially configure the domain.
The end-to-end process of installing and configuring Oracle Identity Manager on a single host involves the following steps:
Step 1, "Download and Edit the Required Domain Configuration Scripts"
Step 2, "Create or Edit a Response File for Each Installation and Configuration Tool"
Step 4, "Silently Install Oracle SOA Suite 11g Release 1 (11.1.1.7)"
Step 5, "Silently Install the Oracle Identity Manager Software"
Step 6, "Apply Mandatory Patches for Oracle SOA Suite 11g Release 1 (11.1.1.7)"
Step 7, "Silently Create the Required Schemas in a Supported Database"
Step 8, "Silently Upgrade the OPSS Schema Using the Patchset Upgrade Assistant"
Step 9, "Silently Create an Oracle WebLogic Server Domain for Oracle Identity Manager"
Step 11, "Start the Oracle WebLogic Server Domain and SOA Managed Server"
Step 13, "Restart the Administration Server and SOA Managed Server"
The end-to-end silent installation of Oracle Identity Manager requires a set of custom Python scripts, which are used to configure the Oracle Identity Manager domain.
Use the following procedure to download and edit the custom scripts:
Refer to "Mandatory Patches Required for Installing Oracle Identity Manager" in the Oracle Fusion Middleware Release Notes for information on where and how to download the Oracle Identity Manager domain configuration scripts.
The download archive contains the scripts listed in Table 4-3.
Open each of the scripts in Table 4-3 with a text editor and follow the instructions in the file.
The instructions in each script identify the variables that you must modify to match the values required for your specific Oracle Identity Manager environment. Each variable you must edit is marked with angle brackets, such as <HOST_NAME>. In this example, replace the variable with the name of the host on which you are performing the specific action.
Replace each of these variables with the actual values required for your Oracle Identity Manager installation.
Table 4-3 Oracle WebLogic Server Domain Configuration Scripts
| Script Name | Description |
|---|---|
|
create_domain.py |
Creates the initial Oracle WebLogic Server domain for the Oracle Identity Manager software. |
|
config_jrf.py |
Configures the domain with Java Required Files (JRF) software, which provides a set of libraries and other technologies required by Fusion Middleware products. |
|
config_em.py |
Configures the domain for Oracle Enterprise Manager Fusion Middleware Control, which is used to managed the Fusion Middleware products in the domain. |
|
config_opss.py |
Configures the domain for Oracle Platform Security Servers (OPSS). |
|
config_wsm.py |
Configures the domain for Oracle Web Services Manager (OWSM). |
|
config_soa.py |
Configures the domain for Oracle SOA Suite 11g Release 1 (11.1.1.7). |
|
config_oim.py |
Prepares the domain for use with Oracle Identity Manager. |
Each of the Oracle Identity Manager installation and configuration tools requires a response file when it is run in silent mode. The response file contains the values to be used when selecting specific options and features within each tool.
You can create the response files yourself by running the tool, selecting the options you require, and then saving the response file at the end of the session.
Alternatively, a set of response files for each tool is included with the custom domain configuration scripts described in Step 1. These response files are listed in Table 4-4. The table describes each sample response file provided, as well as where to find information about creating the files yourself.
Table 4-4 Response and Input Files Required by the Oracle Identity Manager Silent Installation
| Sample Response or Input File Name | Used for... | More Information |
|---|---|---|
|
|
Silent installation of Oracle WebLogic Server. |
"Creating a silent.xml File for Silent-Mode Installation" in Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server |
|
|
Silent installation of Oracle SOA Suite 11g Release 1 (11.1.1.7); created by saving the response file from the Oracle SOA Suite installer. |
|
|
|
Silent installation of Oracle Identity Manager, which is part of the Oracle Identity and Access Management software download |
|
|
|
The passwords required for connecting to the database and the passwords you want to assign to each schema being created. Note: It is important that the first password in the file is the database connection password (for the SYS user), followed by the password for each schema. |
"Using the -silent Command" in the Oracle Fusion Middleware Repository Creation Utility User's Guide |
|
|
Upgrading the Oracle Platform Security Services (OPSS) schema with the Oracle Fusion Middleware Patchset Assistant; created by saving the response file from the Oracle Fusion Middleware Patchset Assistant. |
|
|
|
Configuring Oracle Identity Manager; created by saving the response file from the Oracle Identity Manager Configuration Wizard. |
Use the following command to silently install Weblogic Server in a new Oracle home:
JDK_HOME/bin/java -Xms512m -Xmx1024m -XX:CompileThreshold=8000 \ -XX:PermSize=256m -XX:MaxPermSize=512m \ -Djava.io.tmpdir=TMP_DIR \ -jar wls_generic.jar \ -mode=silent \ -silent_xml=WLSsilent.xml \ -log=LOG_FILE_LOC \ -log_priority=info
For example:
disk01/java/linux64/jdk6/bin/java -Xms512m -Xmx1024m
-XX:CompileThreshold=8000 \
-XX:PermSize=256m -XX:MaxPermSize=512m \
-Djava.io.tmpdir=/dua0/logs/tmpDir \
-jar /downloads/wls_generic.jar \
-mode=silent \
-silent_xml=/myResponseFiles/WLSsilent.xml \
-log=/dua0/logs/install.log \
-log_priority=info
Oracle SOA Suite is required by the Oracle Identity Manager software. Use the following command to install Oracle SOA Suite in silent mode:
Unzip the Oracle SOA Suite download archives into a local directory.
For example:
unzip -o '/downloads/soa/shiphome/soa*.zip' -d /installers/Oracle_SOA
Install the Oracle SOA Suite software:
DOWNLOADS_DIR/Disk1/runInstaller \ -jreLoc JDK_HOME \ -printtime \ -printmemory \ -printdiskusage \ -invPtrLoc INVENTORY_LOC \ -novalidation \ -ignoreSysPrereqs \ -nocheckForUpdates \ -force \ -silent \ -response RESP_FILE_LOC \ -waitforcompletion
For example:
/dua0/installers/Oracle_SOA/Disk1/runInstaller \
-jreLoc /dua0/java/linux64/jdk6 \
-printtime \
-printmemory \
-printdiskusage \
-invPtrLoc /dua0/oraInventory/oraInst.loc \
-novalidation \
-ignoreSysPrereqs \
-nocheckForUpdates \
-force \
-silent \
-response /dua0/myResponseFiles/SOAResponseFile.txt \
-waitforcompletion
Use the following command to silently install the Oracle Identity Manager software:
Unzip Oracle Identity and Access Management download archive in local directory.
For example:
$ unzip -o '/downloads/iam/iamsuite*.zip' -d /installers/IAM
Install the Oracle Identity Manager software:
DOWNLOADS_DIR/Disk1/runInstaller \ -jreLoc JDK_HOME \ -printtime \ -printmemory \ -printdiskusage \ -invPtrLoc INVENTORY_LOC \ -longterm \ -ignoreSysPrereqs \ -nocheckForUpdates \ -force \ -silent \ -response RESP_FILE_LOC \ -waitforcompletion
For example:
/dua0/installers/IAM/Disk1/runInstaller \
-jreLoc /dua0/java/linux64/jdk6 \
-printtime \
-printmemory \
-printdiskusage \
-invPtrLoc /dua0/oraInventory/oraInst.loc \
-longterm \
-ignoreSysPrereqs \
-nocheckForUpdates \
-force \
-silent \
-response /dua0/myResponseFiles/IDMInstallResponseFile.txt \
-waitforcompletion
After installing Oracle SOA Suite 11g Release 1 (11.1.1.7), you must apply a set of mandatory SOA patches before installing Oracle Identity Manager. These patches are included in a ZIP file in the Oracle Identity and Access Management installation download.
For more information, see "Mandatory Patches Required for Installing Oracle Identity Manager" topic in the 11g Release 2 Oracle Fusion Middleware Release Notes.
Use the following procedure to apply the Oracle SOA Suite patches that are included with the Oracle Identity and Access Management software download:
Change directory to the Disk1 directory of the unpacked Oracle Identity and Access Management software archive.
For example:
cd /installers/IAM/Disk1
Unzip the ZIP that includes the required Oracle SOA Suite patches:
unzip OIM_11.1.2.2_SOAPS6_PREREQS.zip
When you unzip the OIM_11.1.2.2_SOAPS6_PREREQS.zip file, a directory called SOAPATCH is created.
Move to the SOAPATCH directory, and use the OPatch software that is installed in the Oracle SOA Suite Oracle home to apply the mandatory patches in the SOAPATCH directory:
cd /installers/IAM/Disk1/SOAPATCH
SOA_HOME/OPatch/opatch napply \
-oh SOA_ORACLE_HOME \
-verbose \
-silent
For example:
/dua0/Oracle/products/mw_home/Oracle_SOA1/OPatch/opatch napply \ -oh /dua0/Oracle/products/mw_home/Oracle_SOA1 \ -verbose \ -silent
Use the Oracle Fusion Middleware Repository Creation Utility (RCU) command-line to create the required Oracle Identity and Access Management schemas in a supported Oracle database.
Note the following before you perform this step:
You must have an existing, supported Oracle Database instance available, as described in Section 4.4.1, "Preparing for an Oracle Identity Manager Silent Installation".
The example in this section assumes you created an RCU password file, which contains the values required for the Custom Variables screen in RCU. For more information, see "Using the -silent Command" in the Oracle Fusion Middleware Repository Creation Utility User's Guide.
To run RCU in silent mode:
Unzip RCU shiphome to a local directory.
For example:
unzip DOWNLOADS_DIR/installers/rcuHome.zip -d /LOCAL_DISK/installers/RCU
Use RCU to create the required schemas in the database.
RCU_HOME/bin/rcu \ -silent \ -createRepository -connectString DB_HOST:DB_PORT:DB_SID \ -dbUser sys \ -dbRole sysdba \ -schemaPrefix <PREFIX> \ -component MDS \ -component OPSS \ -component OIM \ -component IAU \ -component SOAINFRA \ -component ORASDPM \ -f < RCU_PWD_FILE_LOC
For example:
/dua0/installers/RCU/bin/rcu \
-silent \
-createRepository \
-connectString db42.example.com:1521:orcl.example.com \
-dbUser sys \
-dbRole sysdba \
-schemaPrefix DEV \
-component MDS \
-component OPSS \
-component OIM \
-component IAU \
-component SOAINFRA \
-component ORASDPM \
-f < RCUpwd.txt
Before you can configure the Oracle WebLogic Server domain for Oracle Identity Manager, you must upgrade OPSS Schema you installed with the Oracle Fusion Middleware Metadata Repository Creation Utility (RCU).
You perform this step using the Patchset Upgrade Assistant (PSA).
To perform this step using a response file, use the following command:
IAM_HOME/bin/psa -response RESP_FILE_LOC
For example:
/dua0/Oracle/products/mw_home/Oracle_IDM1/bin/psa \
-response /dua0/myResponseFiles/response_psa.txt
To make it easier to create an Oracle WebLogic Server domain for Oracle Identity Manager, Oracle provides a set to Python scripts, which can be run from the WebLogic Scripting Tool (WLST) command shell.
The required Python scripts are listed in Table 4-3.
To use these scripts to create the domain:
Create the Oracle WebLogic Server domain, use the create_domain.py script:
IAM_HOME/common/bin/wlst.sh create_domain.py > CREATE_DOMAIN_LOG
For example:
/dua0/Oracle/products/Middleware/Oracle_IDM1/common/bin/wlst.sh \
/dua0/myResponseFiles/create_domain.py > /dua0/logs/create_domain.log
Configure the prerequisite Oracle Fusion Middleware software in the domain, by using the following scripts.
All of these software components are required before you can configure Oracle Identity Manager in the domain, so you must run the following scripts to prepare the domain for Oracle Identity Manager:
IAM_HOME/common/bin/wlst.sh config_jrf.py > CONFIG_JRF_LOG_FILE IAM_HOME/common/bin/wlst.sh config_em.py > CONFIG_EM_LOG_FILE IAM_HOME/common/bin/wlst.sh config_opss.py > CONFIG_OPSS_LOG IAM_HOME/common/bin/wlst.sh config_wsm.py > CONFIG_WSM_LOG IAM_HOME/common/bin/wlst.sh config_soa.py > CONFIG_SOA_LOG IAM_HOME/common/bin/wlst.sh config_oim.py > CONFIG_OIM_LOG
Before you start the Oracle WebLogic Server domain and configure Oracle Identity Manager, you must configure the Oracle Platform Security Services (OPSS) security store.
Note that the configureSecurityStore.py script referenced in this step is not part of the download archive that contains the custom domain creation scripts and sample response files for this procedure. Instead, the configureSecuriryStore.py script is installed on disk automatically as part of the Oracle Identity and Access Management installation.
Run the following command to configure security store:
IDM_HOME/common/bin/wlst.sh IDM_HOME/common/tools/configureSecurityStore.py \ -d DOMAIN_HOME \ -c IAM -m create -p OPSS_SCHEMA_PASSWORD
For an explanation of the command-line arguments to the configureSecurityStore script, 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.
Start the Oracle WebLogic Server domain:
Run the following command to start Administration Server in the Oracle WebLogic Server domain:
DOMAIN_HOME/startWeblogic.sh \ -Dweblogic.management.username=WLS_ADMIN_USER_NAME \ -Dweblogic.management.password=WLS_ADMIN_PWD
Run the following command to start SOA Managed Server
DOMAIN_HOME/bin/startManagedWeblogic.sh soa_server1 WLS_URL \ -Dweblogic.management.username=WLS_ADMIN_USER_NAME \ -Dweblogic.management.password=WLS_ADMIN_PWD
For example:
DOMAIN_HOME/bin/startManagedWebLogic.sh soa_server1 \
http://hostname:7003 \
-Dweblogic.management.username=weblogic \
-Dweblogic.management.password=weblogic1
For more information about the startManagedWebLogic.sh script, see "Starting Managed Servers with a Startup Script" in the Oracle Fusion Middleware Managing Server Startup and Shutdown for Oracle WebLogic Server.
Run the following command to configure Oracle Identity Management:
IAM_HOME/bin/config.sh \ -jreLoc JDK_HOME \ -printtime \ -printmemory \ -printdiskusage \ -invPtrLoc INVENTORY_LOC \ -longterm \ -ignoreSysPrereqs \ -force \ -silent \ -response RESP_FILE_LOC \ -waitforcompletion
Replace RESP_FILE_LOC with the complete path to the Oracle Identity Manager Configuration Wizard response file. This can be a response file you created by running the Configuration Wizard, or it can be an edited copy of the OIMPostConfig.txt file, described in Table 4-4.
After you configure Oracle Identity Manager, you must restart the SOA Managed Servers by stopping them and then starting them again.
If you used the startWebLogic.sh script to start the Administration Server, you can stop the server by pressing Ctrl/C in the terminal window where you are running the startWebLogic.sh command. Start the Administration Server by running the startWebLogic.sh script again.
Use the following command to stop the SOA Managed Server:
DOMAIN_HOME/bin/stopManagedWebLogic.sh soa_server1
Use the following command to start the Managed Server:
DOMAIN_HOME/bin/startManagedWeblogic.sh server_name \ WLS_URL \ -Dweblogic.management.username=WLS_USER_NAME \ -Dweblogic.management.password=WLS_PWD
For example:
DOMAIN_HOME/bin/startManagedWebLogic.sh soa_server1 \
http://hostname:7003 \
-Dweblogic.management.username=weblogic \
-Dweblogic.management.password=weblogic1
Use the following command to start the Managed Server:
DOMAIN_HOME/bin/startManagedWeblogic.sh server_name \ WLS_URL \ -Dweblogic.management.username=WLS_USER_NAME \ -Dweblogic.management.password=WLS_PWD
For example:
DOMAIN_HOME/bin/startManagedWebLogic.sh oim_server1 \
http://hostname:7003 \
-Dweblogic.management.username=weblogic \
-Dweblogic.management.password=weblogic1
To verify the successful installation, configuration, and startup of the Oracle Identity Manager environment, refer to "Verifying the Oracle Identity Manager Installation" in the Oracle Fusion Middleware Installation Guide for Oracle Identity and Access Management
The following procedure describes how to use a set of command line scripts and utilities to install and configure the Oracle Identity Manager software in a typical cluster environment, where two instances of Oracle Identity Management are installed on two separate host computers.
Refer to the following sections for more information:
Section 4.4.3.1, "About the End-to-End Silent Installation and Configuration on Multiple Hosts"
Section 4.4.3.3, "Performing the Silent Installation and Configuration on Multiple Hosts"
The command-line steps described here are similar to the standard installation steps described in "Installation and Configuration Roadmap for Oracle Identity Manager" in the Oracle Fusion Middleware Installation Guide for Oracle Identity and Access Management. However, they include steps for performing these steps on multiple host computers.
In addition, they involve the use of standard Oracle WebLogic Server and Oracle Fusion Middleware 11g high availability procedures and best practices, such as the pack and unpack commands used to propagate domain configuration settings from one host to another. For more information about these features, refer to the following resources:
"Overview of the Pack and Unpack Commands" in the Oracle Fusion Middleware Creating Templates and Domains Using the Pack and Unpack Commands
In the multi-host, silent installation and configuration instructions, note the following:
The instructions assume you are installing and configuring Oracle Identity Management on two host computers. The example here can be used as a guideline for performing these steps on more than two hosts.
The instructions refer to the two host computers are HOST1 and HOST2. HOST1 is the host computer where the Oracle WebLogic Server Administration Server is installed and configured.
The key directory locations referenced in the single-host, silent installation and configuration instructions include the following:
The Oracle home created during the Oracle Identity and Access Management installation. This is the location of the Oracle Identity and Access Management binary software files.
This directory is identified by the variable, IAM_HOME. When referenced, replace this variable with the complete path to the Oracle Identity and Access Management Oracle home.
The Oracle SOA Suite Oracle home created when you install the Oracle SOA Suite software. This directory is identified by the variable SOA_HOME.
The JDK_HOME, which refers to the location of the JDK used to install the Oracle Identity Management software. Replace this variable with the full path to your supported JDK.
For more information, see Section 4.4.1, "Preparing for an Oracle Identity Manager Silent Installation".
The DOWNLOADS_DIR, which refers to the location where you downloaded and unpacked the software archives. This is location from which you run the installer.
The DOMAIN_HOME directory, which refers to the Oracle WebLogic Server domain home directory, which is created when you initially configure the domain.
The end-to-end process of installing and configuring Oracle Identity Manager on multiple hosts involves the following steps:
Step 1, "Download and Edit the Required Domain Configuration Scripts"
Step 2, "Create or Edit a Response File for Each Installation and Configuration Tool"
Step 3, "Silently Install Oracle WebLogic Server (HOST1 and HOST2)"
Step 4, "Silently Install Oracle SOA Suite 11g Release 1 (11.1.1.7) (HOST1 and HOST2)"
Step 5, "Silently Install the Oracle Identity Manager Software"
Step 6, "Apply Mandatory Patches for Oracle SOA Suite 11g Release 1 (11.1.1.7) (HOST1 and HOST2)"
Step 7, "Silently Create the Required Schemas in a Supported Database (HOST1)"
Step 8, "Silently Upgrade the OPSS Schema Using the Patchset Upgrade Assistant (HOST1)"
Step 9, "Silently Create an Oracle WebLogic Server Domain for Oracle Identity Manager (HOST1)"
Step 12, "Configure Oracle Coherence for Oracle SOA Suite (HOST1)"
Step 13, "Start the Oracle WebLogic Server Domain and SOA Managed Server (HOST1)"
Step 14, "Silently Configure Oracle Identity Manager (HOST1)"
Step 15, "Restart the Administration Server and SOA Managed Server (HOST1)"
Step 19, "Configure Oracle Coherence for Oracle SOA Suite (HOST2)"
Step 22, "Start the Oracle Identity Manager Server (HOST1 and HOST2)"
The end-to-end silent installation of Oracle Identity Manager requires a set of custom Python scripts, which are used to configure the Oracle Identity Manager domain.
Use the following procedure to download and edit the custom scripts:
Refer to "Mandatory Patches Required for Installing Oracle Identity Manager" in the Oracle Fusion Middleware Release Notes for information on where and how to download the Oracle Identity Manager domain configuration scripts.
The download archive contains the scripts listed in Table 4-3.
Open each of the scripts in Table 4-3 with a text editor and follow the instructions in the file.
The instructions in each script identify the variables that you must modify to match the values required for your specific Oracle Identity Manager environment. Each variable you must edit is marked with angle brackets, such as <HOST_NAME>. In this example, replace the variable with the name of the host on which you are performing the specific action.
Replace each of these variables with the actual values required for your Oracle Identity Manager installation.
Each of the Oracle Identity Manager installation and configuration tools requires a response file when it is run in silent mode. The response file contains the values to be used when selecting specific options and features within each tool.
You can create the response files yourself by running the tool, selecting the options you require, and then saving the response file at the end of the session.
Alternatively, a set of response files for each tool is included with the custom domain configuration scripts described in Step 1. These response files are listed in Table 4-4. The table describes each sample response file provided, as well as where to find information about creating the files yourself.
Use the following command to silently install Weblogic Server in a new Oracle home.
Perform this command first while logged in to HOST1, and then again while logged in to HOST2. Be sure to use the same user account and the same privileges on each host.
JDK_HOME/bin/java -Xms512m -Xmx1024m -XX:CompileThreshold=8000 \ -XX:PermSize=256m -XX:MaxPermSize=512m \ -Djava.io.tmpdir=TMP_DIR \ -jar wls_generic.jar \ -mode=silent \ -silent_xml=WLSsilent.xml \ -log=LOG_FILE_LOC \ -log_priority=info
For example:
disk01/java/linux64/jdk6/bin/java -Xms512m -Xmx1024m
-XX:CompileThreshold=8000 \
-XX:PermSize=256m -XX:MaxPermSize=512m \
-Djava.io.tmpdir=/dua0/logs/tmpDir \
-jar /downloads/wls_generic.jar \
-mode=silent \
-silent_xml=/myResponseFiles/WLSsilent.xml \
-log=/dua0/logs/install.log \
-log_priority=info
Oracle SOA Suite is required by the Oracle Identity Manager software. Use the following command to install Oracle SOA Suite in silent mode.
Perform this command first while logged in to HOST1, and then again while logged in to HOST2. Be sure to use the same user account and the same privileges on each host.
Unzip the Oracle SOA Suite download archives into a local directory.
For example:
unzip -o '/downloads/soa/shiphome/soa*.zip' -d /installers/Oracle_SOA
Install the Oracle SOA Suite software:
DOWNLOADS_DIR/Disk1/runInstaller \ -jreLoc JDK_HOME \ -printtime \ -printmemory \ -printdiskusage \ -invPtrLoc INVENTORY_LOC \ -novalidation \ -ignoreSysPrereqs \ -nocheckForUpdates \ -force \ -silent \ -response RESP_FILE_LOC \ -waitforcompletion
For example:
/dua0/installers/Oracle_SOA/Disk1/runInstaller \
-jreLoc /dua0/java/linux64/jdk6 \
-printtime \
-printmemory \
-printdiskusage \
-invPtrLoc /dua0/oraInventory/oraInst.loc \
-novalidation \
-ignoreSysPrereqs \
-nocheckForUpdates \
-force \
-silent \
-response /dua0/myResponseFiles/SOAResponseFile.txt \
-waitforcompletion
Use the following command to silently install the Oracle Identity Manager software.
Perform this command first while logged in to HOST1, and then again while logged in to HOST2. Be sure to use the same user account and the same privileges on each host.
Unzip Oracle Identity and Access Management download archive in local directory.
For example:
$ unzip -o '/downloads/iam/iamsuite*.zip' -d /installers/IAM
Install the Oracle Identity Manager software:
DOWNLOADS_DIR/Disk1/runInstaller \ -jreLoc JDK_HOME \ -printtime \ -printmemory \ -printdiskusage \ -invPtrLoc INVENTORY_LOC \ -longterm \ -ignoreSysPrereqs \ -nocheckForUpdates \ -force \ -silent \ -response RESP_FILE_LOC \ -waitforcompletion
For example:
/dua0/installers/IAM/Disk1/runInstaller \ -jreLoc /dua0/java/linux64/jdk6 \ -printtime \ -printmemory \ -printdiskusage \ -invPtrLoc /dua0/oraInventory/oraInst.loc \ -longterm \ -ignoreSysPrereqs \ -nocheckForUpdates \ -force \ -silent \ -response /dua0/myResponseFiles/IDMInstallResponseFile.txt \ -waitforcompletion
After installing Oracle SOA Suite 11g Release 1 (11.1.1.7), you must apply a set of mandatory SOA patches before installing Oracle Identity Manager. These patches are included in a ZIP file in the Oracle Identity and Access Management installation download.
For more information, see "Mandatory Patches Required for Installing Oracle Identity Manager" topic in the 11g Release 2 Oracle Fusion Middleware Release Notes.
Use the following procedure to apply the Oracle SOA Suite patches that are included with the Oracle Identity and Access Management software download.
Perform this command first while logged in to HOST1, and then again while logged in to HOST2. Be sure to use the same user account and the same privileges on each host.
Change directory to the Disk1 directory of the unpacked Oracle Identity and Access Management software archive.
For example:
cd /installers/IAM/Disk1
Unzip the ZIP that includes the required Oracle SOA Suite patches:
unzip OIM_11.1.2.2_SOAPS6_PREREQS.zip
When you unzip the OIM_11.1.2.2_SOAPS6_PREREQS.zip file, a directory called SOAPATCH is created.
Move to the SOAPATCH directory, and use the OPatch software that is installed in the Oracle SOA Suite Oracle home to apply the mandatory patches in the SOAPATCH directory:
cd /installers/IAM/Disk1/SOAPATCH
SOA_HOME/OPatch/opatch napply \
-oh SOA_ORACLE_HOME \
-verbose \
-silent
For example:
/dua0/Oracle/products/mw_home/Oracle_SOA1/OPatch/opatch napply \ -oh /dua0/Oracle/products/mw_home/Oracle_SOA1 \ -verbose \ -silent
Use the Oracle Fusion Middleware Repository Creation Utility (RCU) command-line to create the required Oracle Identity and Access Management schemas in a supported Oracle database.
Note the following before you perform this step:
You must have an existing, supported Oracle Database instance available, as described in Section 4.4.1, "Preparing for an Oracle Identity Manager Silent Installation".
The example in this section assumes you created an RCU password file, which contains the values required for the Custom Variables screen in RCU. For more information, see "Using the -silent Command" in the Oracle Fusion Middleware Repository Creation Utility User's Guide.
Perform this command while logged in to HOST1 only.
To run RCU in silent mode:
Unzip RCU shiphome to a local directory.
For example:
unzip LOCAL_DIR/downloads/rcuHome.zip -d /LOCAL_DISK/installers/RCU
Use RCU to create the required schemas in the database.
RCU_HOME/bin/rcu \ -silent \ -createRepository -connectString DB_HOST:DB_PORT:DB_SID \ -dbUser sys \ -dbRole sysdba \ -schemaPrefix <PREFIX> \ -component MDS \ -component OPSS \ -component OIM \ -component IAU \ -component SOAINFRA \ -component ORASDPM \ -f < RCU_PWD_FILE_LOC
For example:
/dua0/installers/RCU/bin/rcu \
-silent \
-createRepository \
-connectString db42.example.com:1521:orcl.example.com \
-dbUser sys \
-dbRole sysdba \
-schemaPrefix DEV \
-component MDS \
-component OPSS \
-component OIM \
-component IAU \
-component SOAINFRA \
-component ORASDPM \
-f < RCUpwd.txt
Before you can configure the Oracle WebLogic Server domain for Oracle Identity Manager, you must upgrade OPSS Schema you installed with the Oracle Fusion Middleware Metadata Repository Creation Utility (RCU).
You perform this step using the Patchset Upgrade Assistant (PSA).
Perform this command while logged in to HOST1 only:
IAM_HOME/bin/psa -response RESP_FILE_LOC
For example:
/dua0/Oracle/products/mw_home/Oracle_IDM1/bin/psa \
-response /dua0/myResponseFiles/response_psa.txt
To make it easier to create an Oracle WebLogic Server domain for Oracle Identity Manager, Oracle provides a set to Python scripts, which can be run from the WebLogic Scripting Tool (WLST) command shell.
The required Python scripts are listed in Table 4-3.
To use the scripts to create the domain on HOST1 only:
Create the Oracle WebLogic Server domain, use the create_domain.py script:
IAM_HOME/common/bin/wlst.sh create_domain.py > CREATE_DOMAIN_LOG
For example:
/dua0/Oracle/products/Oracle_IDM1/common/bin/wlst.sh \ /dua0/myResponseFiles/create_domain.py > /dua0/logs/create_domain.log
Configure the prerequisite Oracle Fusion Middleware software in the domain, by using the following scripts.
All of these software components are required before you can configure Oracle Identity Manager in the domain, so you must run the following scripts to prepare the domain for Oracle Identity Manager:
IAM_HOME/common/bin/wlst.sh config_jrf.py > CONFIG_JRF_LOG_FILE IAM_HOME/common/bin/wlst.sh config_em.py > CONFIG_EM_LOG_FILE IAM_HOME/common/bin/wlst.sh config_opss.py > CONFIG_OPSS_LOG IAM_HOME/common/bin/wlst.sh config_wsm.py > CONFIG_WSM_LOG IAM_HOME/common/bin/wlst.sh config_soa.py > CONFIG_SOA_LOG IAM_HOME/common/bin/wlst.sh config_oim.py > CONFIG_OIM_LOG
Before you start the Oracle WebLogic Server domain and configure Oracle Identity Manager, you must configure the Oracle Platform Security Services (OPSS) security store.
Perform this step on HOST1 only.
Run the following command to configure security store:
IDM_HOME/common/bin/wlst.sh IDM_HOME/common/tools/configureSecurityStore.py \ -d DOMAIN_HOME \ -c IAM -m create -p OPSS_SCHEMA_PASSWORD
For an explanation of the command-line arguments to the configureSecurityStore script, 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 start the Managed Server(s) using the WebLogic Administration console, you must start the Node Manager. In order to start the Node Manager, you must set the property StartScriptEnabled in the nodemanager.properties file to true. Run the following command to set the property StartScriptEnabled=true:
On UNIX: ORACLE_COMMON_HOME/common/bin/setNMProps.sh On Windows: ORACLE_COMMON_HOME\common\bin\setNMProps.cmd
Start the Node Manager on HOST1 by running the following command:
On UNIX: MW_HOME/wlserver_10.3/server/bin/startNodeManager.sh On Windows: MW_HOME\wlserver_10.3\server\startNodeManager.cmd
To configure Oracle Coherence for Oracle SOA Suite:
Locate the following file and open it with a text editor:
DOMAIN_HOME/bin/setDomainEnv.sh
Search for the following entry in the setDomainEnv.sh file:
JAVA_OPTIONS="${JAVA_OPTIONS} ${JAVA_PROPERTIES} \
Append the following entries at the end of the JAVA_OPTIONS entry in the setDomainEnv.sh file:
On HOST1:
-Dtangosol.coherence.wka1=SOAHOST1 \ -Dtangosol.coherence.wka2=SOAHOST2" -Dtangosol.coherence.localhost=SOAHOST1
Be sure to include this entry all on one line, with no line breaks. Note the single quotation marks in the entry.
Replace SOAHOST1 with the actual names of the host computers in you environment.
Start the Oracle WebLogic Server domain:
Run the following command to start Administration Server in the Oracle WebLogic Server domain:
DOMAIN_HOME/startWeblogic.sh \ -Dweblogic.management.username=WLS_ADMIN_USER_NAME \ -Dweblogic.management.password=WLS_ADMIN_PWD
Run the following command to start SOA Managed Server
DOMAIN_HOME/bin/startManagedWeblogic.sh soa_server1 WLS_URL \ -Dweblogic.management.username=WLS_ADMIN_USER_NAME \ -Dweblogic.management.password=WLS_ADMIN_PWD
For example:
DOMAIN_HOME/bin/startManagedWebLogic.sh soa_server1 \
http://hostname:7003 \
-Dweblogic.management.username=weblogic \
-Dweblogic.management.password=weblogic1
For more information about the startManagedWebLogic.sh script, see "Starting Managed Servers with a Startup Script" in the Oracle Fusion Middleware Managing Server Startup and Shutdown for Oracle WebLogic Server.
Run the following command on SOAHOST1 to configure Oracle Identity Management:
IAM_HOME/bin/config.sh \ -jreLoc JDK_HOME \ -printtime \ -printmemory \ -printdiskusage \ -invPtrLoc INVENTORY_LOC \ -longterm \ -ignoreSysPrereqs \ -force \ -silent \ -response RESP_FILE_LOC \ -waitforcompletion
Replace RESP_FILE_LOC with the complete path to the Oracle Identity Manager Configuration Wizard response file. This can be a response file you created by running the Configuration Wizard, or it can be an edited copy of the OIMPostConfig.txt file, described in Table 4-4.
After you configure Oracle Identity Manager, you must restart the Administration Server and SOA Managed Servers on HOST1 by stopping them and then starting them again.
If you used the startWebLogic.sh script to start the Administration Server, you can stop the server by pressing Ctrl/C in the terminal window where you are running the startWebLogic.sh command. Start the Administration Server by running the startWebLogic.sh script again.
Use the following command to stop the SOA Managed Server:
DOMAIN_HOME/bin/stopManagedWebLogic.sh soa_server1
Use the following command to start the Managed Server:
DOMAIN_HOME/bin/startManagedWeblogic.sh server_name \ WLS_URL \ -Dweblogic.management.username=WLS_USER_NAME \ -Dweblogic.management.password=WLS_PWD
For example:
DOMAIN_HOME/bin/startManagedWebLogic.sh soa_server1 \
http://hostname:7003 \
-Dweblogic.management.username=weblogic \
-Dweblogic.management.password=weblogic1
After you create the Oracle WebLogic Server domain on HOST1, you can then copy the domain configuration to HOST2, using the Oracle WebLogic Server pack and unpack commands.
For more information, see "Overview of the Pack and Unpack Commands" in the Oracle Fusion Middleware Creating Templates and Domains Using the Pack and Unpack Commands.
To pack up the domain configuration on HOST1:
Log in to HOST1 as the same user who installed and configured the domain.
Run the following command to create a template jar file that contains the configuration data for the domain:
MW_HOME/oracle_common/bin/pack.sh \ -managed=true -domain=DOMAIN_HOME \ -template=TEMPLATE_LOC \ -template_name=TEMPLATE_NAME
In this example, replace the variables as follows:
Replace MW_HOME with the complete path to the Middleware home, in which the Oracle Identity and Access Management Oracle home resides.
Replace DOMAIN_HOME with the complete path to the Domain home directory.
Replace TEMPLATE_LOC with the complete path and name of the template jar file you want to create.
Replace TEMPLATE_NAME with the name of the template you are about to create; for example, oim_domain_template.jar.
Use this step to copy the domain configuration information to HOST2:
Copy the domain template jar file you created in Step 16 to HOST2.
Log in to HOST2 and unpack the domain configuration template jar file into the domain directory on HOST2:
MW_HOME/oracle_common/bin/unpack.sh \ -domain=DOMAIN_HOME \ -template=TEMPLATE_LOC
In this example, replace the variables as follows:
Replace MW_HOME with the complete path to the Middleware home, in which the Oracle Identity and Access Management Oracle home resides.
Replace DOMAIN_HOME with the complete path to the Domain home directory.
Replace TEMPLATE_LOC with the complete path and name of the template jar file you are unpacking.
Use a copy or FTP to copy the SOA composites from HOST1 to HOST2.
Copy them from the following location in Domain home on HOST1 to the same location within the Domain home on HOST2:
DOMAIN_HOME/soa/
If you are using a copy utility, then be sure to copy the directories within the directory recursively, so all the SOA composite artifacts are copied.
To configure Oracle Coherence for Oracle SOA Suite:
Locate the following file and open it with a text editor:
DOMAIN_HOME/bin/setDomainEnv.sh
Search for the following entry in the setDomainEnv.sh file:
JAVA_OPTIONS="${JAVA_OPTIONS} ${JAVA_PROPERTIES} \
Append the following entries at the end of the JAVA_OPTIONS entry in the setDomainEnv.sh file:
On HOST2:
-Dtangosol.coherence.wka1=SOAHOST1 \ -Dtangosol.coherence.wka2=SOAHOST2" -Dtangosol.coherence.localhost=SOAHOST2
Be sure to include this entry all on one line, with no line breaks. Note the single quotation marks in the entry.
Replace SOAHOST2 with the actual names of the host computers in you environment.
To start the Managed Server(s) using the WebLogic Administration console, you must start the Node Manager. In order to start the Node Manager, you must set the property StartScriptEnabled in the nodemanager.properties file to true. Run the following command to set the property StartScriptEnabled=true:
On UNIX: ORACLE_COMMON_HOME/common/bin/setNMProps.sh On Windows: ORACLE_COMMON_HOME\common\bin\setNMProps.cmd
Start the Node Manager on HOST2 by running the following command:
On UNIX: MW_HOME/wlserver_10.3/server/bin/startNodeManager.sh On Windows: MW_HOME\wlserver_10.3\server\startNodeManager.cmd
Use the following command to start the Managed Server:
DOMAIN_HOME/bin/startManagedWeblogic.sh server_name \ WLS_URL \ -Dweblogic.management.username=WLS_USER_NAME \ -Dweblogic.management.password=WLS_PWD
For example:
DOMAIN_HOME/bin/startManagedWebLogic.sh soa_server2 \
http://hostname:7003 \
-Dweblogic.management.username=weblogic \
-Dweblogic.management.password=weblogic1
Use the following command to start the Managed Servers.
Perform this task on both HOST1 and then on HOST2:
DOMAIN_HOME/bin/startManagedWeblogic.sh server_name \ WLS_URL \ -Dweblogic.management.username=WLS_USER_NAME \ -Dweblogic.management.password=WLS_PWD
For example:
DOMAIN_HOME/bin/startManagedWebLogic.sh oim_server1 \
http://hostname:7003 \
-Dweblogic.management.username=weblogic \
-Dweblogic.management.password=weblogic1
To verify the successful installation, configuration, and startup of the Oracle Identity Manager environment, refer to "Verifying the Oracle Identity Manager Installation" in the Oracle Fusion Middleware Installation Guide for Oracle Identity and Access Management