This chapter describes how to install and configure Oracle Directory Integration Platform (DIP) and Oracle Directory Services Manager (ODSM). As noted in Section 4.1.1, "Directory Services-only Topologies," some customers may be interested in deploying a directory services topology that does not include Oracle Directory Integration Platform.
This chapter includes the following topics:
Section 5.1, "Extending the Oracle WebLogic Domain with DIP and ODSM"
Section 5.3, "Provisioning the Managed Servers on the Local Disk"
Section 5.4, "Validating the Application Tier Configuration"
Section 5.5, "Backing Up the Application Tier Configuration"
The application tier consists of multiple computers hosting the Oracle Directory Integration Platform, Oracle Directory Services Manager, and Oracle Access Manager instances. In the complete configuration, requests are balanced among the instances on the application tier computers to create a performant and fault tolerant application environment.
Note:
Oracle Directory Integration Platform uses Quartz to maintain its jobs and schedules in the database. For the Quartz jobs to be run on different Oracle Directory Integration Platform nodes in a cluster, it is recommended that the system clocks on the cluster nodes be synchronized.Follow these steps to install and configure Oracle Directory Integration Platform and Oracle Directory Services Manager on IDMHOST1:
Ensure that the system, patch, kernel and other requirements are met. These are listed in the Oracle Fusion Middleware Installation Guide for Oracle Identity Management manual in the Oracle Fusion Middleware documentation library for the platform and version you are using.
If you plan on provisioning the Instance Home or the Managed Server domain directory on shared storage, ensure that the appropriate shared storage volumes are mounted on IDMHOST1 as described in Section 2.4, "Shared Storage and Recommended Directory Structure."
Ensure that port 7006 is not in use by any service on the computer by issuing these commands for the operating system you are using. If a port is not in use, no output is returned from the command.
On UNIX:
netstat -an | grep "7006"
If the port is in use (if the command returns output identifying the port), you must free it.
On UNIX:
Remove the entries for port 7006 in the /etc/services file and restart the services, or restart the computer.
If you plan on provisioning the Instance Home or the Managed Server domain directory on shared storage, ensure that the appropriate shared storage volumes are mounted on IDMHOST1 as described in Section 2.4, "Shared Storage and Recommended Directory Structure."
Copy the staticports.ini file from the Disk1/stage/Response directory to a temporary directory.
Edit the staticports.ini file that you copied to the temporary directory to assign the following custom port:
# The port for ODSM Server port ODS Server Port No = 7006
Start the Oracle Identity Management 11g Configuration Assistant by running the config.sh script located under the ORACLE_HOME/bin directory on IDMHOST1. For example:
/u01/app/oracle/product/fmw/idm/bin/config.sh
On the Welcome screen, click Next.
On the Select Domain screen, select Extend Existing Domain and enter the domain details:
Hostname: idmhost-vip.mycompany.com
Port: 7001
User Name: weblogic
User Password: <enter user password>
Click Next.
A dialog box with the following message appears:
The selected domain is not a valid Identity Management domain or the installer cannot determine if it is a valid domain. If you created the domain using the Identity Management installer, you can ignore this message and continue. If you did not create the domain using the Identity Management installer, refer to the Identity Management documentation for information on how to verify the domain is valid.
Click OK to continue.
This is a benign warning that you can ignore.
On the Specify Installation Location screen, specify the following values (the values for the Oracle Middleware Home Location and the Oracle Home Directory fields are prefilled. The values default to the Middleware Home and Oracle Home previously installed on IDMHOST1 in Section 3.2, "Configuring the WebLogic Server Domain on IDMHOST1":
Oracle Middleware Home Location:
/u01/app/oracle/product/fmw
Oracle Home Directory: idm
WebLogic Server Directory:
/u01/app/oracle/product/fmw/wlserver_10.3
Oracle Instance Location:
/u01/app/oracle/admin/idm_inst1
Oracle Instance Name:
idm_inst1
Click Next.
On the Specify Email for Security Updates screen, specify these values:
Email Address: Provide the email address for your My Oracle Support account.
Oracle Support Password: Provide the password for your My Oracle Support account.
Check the check box next to the I wish to receive security updates via My Oracle Support field.
Click Next.
On the Configure Components screen, select Oracle Directory Integration Platform, Management Components - Oracle Directory Services Manager and deselect all the other components.
Select the Clustered check box.
Click Next.
On the Configure Ports screen, select Specify Ports Using Configuration File and enter the full path name to the staticports.ini file that you edited in the temporary directory
Click Next.
On the Specify OID Details screen, specify the following:
Hostname: oid.mycompany.com
Port: 389
Username: cn=orcladmin
Password: ******
Click Next.
On the Specify Schema Database screen, specify the following values:
Connect String:
infradbhost1-vip.mycompany.com:1521:idmdb1^infradbhost2-vip.mycompany.com:1521:idmdb2@idmedg.mycompany.com
Note:
The RAC database connect string information needs to be provided in the format host1:port1:instance1^host2:port2:instance2@servicename.During this installation, it is not required for all the RAC instances to be up. If one RAC instance is up, the installation can proceed.
It is required that the information provided above is complete and accurate. Specifically, the correct host, port, and instance name must be provided for each RAC instance, and the service name provided must be configured for all the specified RAC instances.
Any incorrect information entered in the RAC database connect string has to be corrected manually after the installation.
User Name: ODSSM
Password: ******
Click Next.
On the Installation Summary screen, review the selections to ensure that they are correct (if they are not, click Back to modify selections on previous screens), and click Configure.
On the Configuration Progress screen, multiple configuration assistants are launched in succession; this process can be lengthy. Wait until it completes.
On the Installation Complete screen, click Finish to confirm your choice to exit.
The following sections include the steps for extending the WebLogic Server Domain on IDMHOST2:
Follow these steps to install and configure Oracle Directory Integration Platform and Oracle Directory Service Manager on IDMHOST2:
Ensure that the system, patch, kernel and other requirements are met. These are listed in the Oracle Fusion Middleware Installation Guide for Oracle Identity Management manual in the Oracle Fusion Middleware documentation library for the platform and version you are using.
If you plan on provisioning the Instance Home or the Managed Server domain directory on shared storage, ensure that the appropriate shared storage volumes are mounted on IDMHOST2 as described in Section 2.4, "Shared Storage and Recommended Directory Structure."
Ensure that port number 7006 is not in use by any service on the computer by issuing this command for the operating system you are using. If a port is not in use, no output is returned from the command.
On UNIX:
netstat -an | grep "7006"
If the port is in use (if the command returns output identifying the port), you must free it.
On UNIX:
Remove the entries for port 7006 in the /etc/services file if the port is in use by a service and restart the services, or restart the computer.
Copy the staticports.ini file from the Disk1/stage/Response directory to a temporary directory.
Edit the staticports.ini file that you copied to the temporary directory to assign the following custom port:
#The port for ODSM Server port ODS Server Port No: 7006
Start the Oracle Identity Management 11g Installer as follows:
On UNIX, issue this command: runInstaller
The runInstaller file is in the ../install/platform directory where platform is a platform such as Linux or Solaris.
The Specify Oracle Inventory screen is displayed.
On the Specify Inventory Directory screen, enter values for the Oracle Inventory Directory and the Operating System Group Name. For example:
Specify the Inventory Directory: /u01/app/oraInventory
Operating System Group Name: oinstall
A dialog box appears with the following message:
"Certain actions need to be performed with root privileges before the install can continue. Please execute the script /u01/app/oraInventory/createCentralInventory.sh now from another window and then press "Ok" to continue the install. If you do not have the root privileges and wish to continue the install select the "Continue installation with local inventory" option"
Login as root and run the "/u01/app/oraInventory/createCentralInventory.sh"
This sets the required permissions for the Oracle Inventory Directory and then brings up the Welcome screen.
Note:
The Oracle Inventory screen is not shown if an Oracle product was previously installed on the host. If the Oracle Inventory screen is not displayed for this installation, make sure to check and see:If the /etc/oraInst file exists
If the file exists, the Inventory directory listed is valid
The user performing the installation has write permissions for the Inventory directory
On the Welcome screen, click Next.
On the Select Installation Type screen, select Install and Configure and then click Next.
On the Prerequisite Checks screen, the installer completes the prerequisite checks. If any fail, please fix them and restart your Installation.
Click Next.
On the Select Domain screen, select the Expand Cluster option and specify these values:
Hostname: idmhost-vip.mycompany.com
Port: 7001
UserName: weblogic
User Password: <Enter the password for the webLogic user>
Click Next.
A dialog box with the following message appears:
The selected domain is not a valid Identity Management domain or the installer cannot determine if it is a valid domain. If you created the domain using the Identity Management installer, you can ignore this message and continue. If you did not create the domain using the Identity Management installer, refer to the Identity Management documentation for information on how to verify the domain is valid.
Click OK to continue.
This is a benign warning that you can safely ignore.
On the Specify Installation Location screen, specify these values:
Oracle Middleware Home Location:
/u01/app/oracle/product/fmw
Oracle Home Directory: idm
WebLogic Server Directory:
/u01/app/oracle/product/fmw/wlserver_10.3
Oracle Instance Location:
/u01/app/oracle/admin/idm_inst2
Oracle Instance Name: idm_inst2
Click Next.
On the Email for Security Updates screen, specify these values:
Email Address: Provide the email address for your My Oracle Support account.
Oracle Support Password: Provide the password for your My Oracle Support account.
Check the check box next to the I wish to receive security updates via My Oracle Support field.
Click Next.
On the Configure Components screen, de-select all the products except Oracle DIP and Management Components and then click Next.
On the Configure Ports screen, select Specify Ports Using Configuration File and enter the full path name to the staticports.ini file that you edited in the temporary directory.
Click Next.
On the Installation Summary screen, review the selections to ensure that they are correct (if they are not, click Back to modify selections on previous screens), and click Install.
On the Installation Progress screen on UNIX systems, a dialog box appears that prompts you to run the oracleRoot.sh script. Open a window, log in as root, and run the script, following the prompts in the window.
Click Next.
On the Configuration Progress screen, multiple configuration assistants are launched in succession; this process can be lengthy. Wait until it completes.
On the Installation Complete screen, click Finish to confirm your choice to exit.
In the previous section, the installer created a second Managed Server, wls_ods2 on IDMHOST2. However, the Oracle Directory Integration Platform application is not deployed on IDMHOST2 and the newly created Managed Server is not automatically started. Also, the WebLogic Administration Console shows the state of the wls_od2 Managed Server on IDMHOST2 as UNKNOWN.
Follow the post-installation steps in this section to complete the installation and configuration of the Oracle Directory Integration Platform and Oracle Directory Services Manager applications on IDMHOST2.
Copy the Oracle Directory Integration Platform application from IDMHOST1 to IDMHOST2.
Copy the following directory on IDMHOST1:
MW_HOME/user_projects/domains/IDMDomain/config/fmwconfig/servers/wls_ods1/applications
to the following location on IDMHOST2:
MW_HOME/user_projects/domains/IDMDomain/config/fmwconfig/servers/wls_ods2/applications.
For example, from IDMHOST1, execute this command:
scp -rp \ MW_HOME/user_projects/domains/IDMDomain/config/fmwconfig/servers/wls_ods1/applications \ user@IDMHOST2:/MW_HOME/user_projects/domains/IDMDomain/config/fmwconfig/servers/wls_ods2/applications
Set the listen address for the WLS_ODS1 and WLS_ODS2 Managed Servers to the host name of their respective nodes using the Oracle WebLogic Administration Server:
Using a web browser, bring up the Oracle WebLogic Administration Server console and log in using the weblogic user credentials.
In the left pane of the WebLogic Administration Server Console, click Lock & Edit to edit the server configuration.
In the left pane of the WebLogic Server Administration Console, expand Environment and select Servers.
On the Summary of Servers page, click on the link for the wls_ods1 Managed Server.
On the Settings page for the wls_ods1 Managed Server, update the Listen Address to idmhost1.mycompany.com. This is the host name of the server where wls_ods1 is running.
Click Save to save the configuration.
Repeat steps 2 to 6 to update the Listen Address for the wls_ods2 Managed Server to idmhost2.mycompany.com. This is host name of the server where wls_ods2 is running.
Click Activate Changes to update the server configuration.
Follow these steps to start the newly created wls_ods2 Managed Server in a cluster on IDMHOST2:
In the left pane of the Oracle WebLogic Server Administration Console, expand Environment and select Clusters.
Select the cluster (cluster_ods) containing the Managed Server (wls_ods2) you want to start.
Select Control.
Under Managed Server Instances in this Cluster, select the check box next to the Managed Server (wls_ods2) you want to start and click Start.
On the Server Life Cycle Assistant page, click Yes to confirm.
Node Manager starts the server on the target machine. When the Node Manager finishes its start sequence, the server's state is indicated in the State column in the Server Status table.
This section provides the steps to provision the Managed Server on the local disk. Proceed as follows:
Stop the Admin Server and the Managed Servers (wls_ods1 and wls_ods2) using the Oracle WebLogic Administration Console.
Stop the Node Manager running on both IDMHOST1 and IDMHOST2.
On IDMHOST1, pack the Managed Server domain using the pack command located under the ORACLE_HOME/common/bin directory. Make sure to pass managed=-true flag to pack the managed server. Type:
ORACLE_HOME/common/bin/pack.sh -managed=true \
-domain=path_to_installer_created_domain -template=templateName.jar \
-template_name=templateName
For example
ORACLE_HOME/common/bin/pack.sh -managed=true \
-domain=/u01/app/oracle/product/fmw/user_projects/domains/IDMDomain \
-template=/u01/app/oracle/product/fmw/templates/managedServer.jar \
-template_name=ManagedServer_Template
Unpack the Managed Server to the local disk on IDMHOST2 using the unpack command located under the ORACLE_HOME/common/bin directory.
ORACLE_HOME/common/bin/unpack.sh -domain=path_to_domain_on_localdisk \ -template=templateName.jar -app_dir=path_to_appdir_on_localdisk
For example:
ORACLE_HOME/common/bin/unpack.sh \ -domain=/u01/app/oracle/admin/IDMDomain/mserver/IDMDomain \ -template=/u01/app/oracle/product/fmw/templates/managedServer.jar \ -app_dir=/u01/app/oracle/admin/IDMDomain/mserver/applications
Copy the Managed Server template directory from IDMHOST1 to IDMHOST2. For Example:
scp -rp /u01/app/oracle/products/fmw/templates user@IDMHOST2://u01/app/oracle/products/fmw/templates
Unpack the Managed Server to the local disk on IDMHOST2 using the unpack command located under the ORACLE_HOME/common/bin directory.
ORACLE_HOME/common/bin/unpack.sh -domain=path_to_domain_on_localdisk \ -template=templateName.jar -app_dir=path_to_appdir_on_localdisk
For example:
ORACLE_HOME/common/bin/unpack.sh \ -domain=/u01/app/oracle/admin/IDMDomain/mserver/IDMDomain \ -template=/u01/app/oracle/product/fmw/templates/managedServer.jar \ -app_dir=/u01/app/oracle/admin/IDMDomain/mserver/applicationsStatus
Start the Node Manager on IDMHOST1 and IDMHOST2 using the startNodeManager.sh script located under the WL_HOME/server/bin directory. For Example:
/u01/app/oracle/product/fmw/wlserver_10.3/server/bin/startNodeManager.sh > /tmp/nm.log &
Start the Administration server from the shared disk on IDMHOST1 using the startWebLogic.sh script. For example:
/u01/app/oracle/admin/IDMDomain/aserver/IDMDomain/bin/startWebLogic.sh > \ /tmp/adminServer.out 2>1 &
Validate that the Administration Server started up successfully by opening a browser accessing the Administration Console http://idmhost-vip.us.oracle.com:7001/console.
Also validate the Oracle Enterprise Manager Fusion Middleware Control Console by opening a browser and accessing the Fusion Middleware Control Console at http://idmhost-vip.us.oracle.com:7001/em.
Start the Managed Servers on IDMHOST1 and IDMHOST2 by using the Admin Console by following the steps below
In the left pane of the Oracle WebLogic Server Administration Console, expand Environment and select Clusters
Select the cluster (cluster_ods) containing the Managed Servers (wls_ods1, wls_ods2) you want to start.
Select Control.
Under Managed Server Instances in this Cluster, select the Managed Servers (wls_ods1, wls_ods2) and click Start.
On the Server Life Cycle Assistant page, click Yes to confirm.
Delete the MW_HOME/user_projects directory on IDMHOST1 and IDMHOST2. This directory is created by the Oracle Universal Installer when the domain is originally configured and is no longer required after the provisioning the Managed Server to the local disk.
This section includes steps for validating Oracle Directory Services Manager and Oracle Directory Integration Platform.
Follow these steps to validate the Oracle Directory Services Manager installation:
Bring up the Oracle Directory Services Manager (ODSM) Administration Console in a web browser. The URL to access the ODSM Administration Console is:
http://hostname.mycompany.com:port/odsm/faces/odsm.jspx
For example, on IDMHOST1, enter this URL:
http://idmhost1.mycompany.com:7006/odsm/faces/odsm.jspx
And on IDMHOST2, enter this URL:
http://idmhost2.mycompany.com:7006/odsm/faces/odsm.jspx
Validate that Oracle Directory Services Manager can create connections to Oracle Internet Directory and Oracle Virtual Directory. Follow these steps to create connections to Oracle Internet Directory and Oracle Virtual Directory:
To create connections to Oracle Internet Directory, follow these steps:
Launch Oracle Directory Services Manager from IDMHOST1:
http://idmhost1.mycompany.com:7006/odsm/faces/odsm.jspx
Create a connection to the Oracle Internet Directory virtual host by providing the information shown below in the ODSM Console:
Host: oid.mycompany.com Port: 636 Enable the SSL option User: cn=orcladmin Password: <ldap-password>
To create connections to Oracle Virtual Directory, follow these steps. Create connections to each Oracle Virtual Directory node separately. Using the Oracle Virtual Directory load balancer virtual host from the ODSM Console is not supported:
Launch Oracle Directory Services Manager from IDMHOST1:
http://idmhost1.mycompany.com:7006/odsm/faces/odsm.jspx
Create a direct connection to Oracle Virtual Directory on OVDHOST1 providing the information shown below in the ODSM Console:
Host: ovdhost1.mycompany.com Port: 8899 (The Oracle Virtual Directory proxy port) Enable the SSL option User: cn=orcladmin Password: <ldap-password>
Validate the Oracle Directory Integration Platform installation by using the WLST dipStatus command. To run this command, follow these steps:
Set the ORACLE_HOME environment variable to the directory where you installed the Identity Management binaries. For example:
export ORACLE_HOME=/u01/app/oracle/product/fmw/idm
Set the WLS_HOME environment variable to the directory where you installed the WebLogic Server. For example:
export WLS_HOME=/u01/app/oracle/product/fmw/wlserver_10.3
Run the ORACLE_HOME/bin/dipStatus -h hostName -p port -D wlsuser command.
For example, on IDMHOST1, the command and output look like this:
ORACLE_HOME/bin/dipStatus -h idmhost1.mycompany.com -p 7006 -D weblogic
[Weblogic user password]
Connection parameters initialized.
Connecting at idmhost1.mycompany.com:7006, with userid "weblogic"..
Connected successfully.
ODIP Application is active at this host and port.
For example, on IDMHOST2, the command and output look like this:
ORACLE_HOME/bin/dipStatus -h idmhost2.mycompany.com -p 7006 -D weblogic
[Weblogic user password]
Connection parameters initialized.
Connecting at idmhost2.mycompany.com:7006, with userid "weblogic"..
Connected successfully.
ODIP Application is active at this host and port.
Follow these steps to validate the failover of the WebLogic Administration Server and Oracle Enterprise Manager Fusion Middleware Control from IDMHOST1 to IDMHOST2:
Make sure that the Administration Server is not running on IDMHOST1. If it is running, use the WebLogic Administration Console to stop the Administration Server on IDMHOST1.
Make sure that the virtual IP has been disabled on IDMHOST1. If it is not disabled, then disable it using the ifconfig command. In a UNIX environment, run this command as the root user. For example:
/sbin/ifconfig networkCardInterface down
Enable the virtual IP on IDMHOST2 using the ifconfig command. The syntax and usage for the ifconfig command is shown below. In a UNIX environment, run the ifconfig command as the root user.
/sbin/ifconfig networkCardInterface IPAddress netmask netMask
For example:
/sbin/ifconfig eth0:1 139.185.140.200 netmask 255.255.255.0
Update the routing tables using the arping command. In a UNIX environment, run the arping command as the root user.
/sbin/arping -q -U -c 3 -I networkCardInterface VirtualIPAddress
For example:
/sbin/arping -q -U -c 3 -I eth0 139.185.140.200
Unmount the shared disk from IDMHOST1 as the root user. For Example:
umount /u01/app/oracle/admin/domainName/aserver
For example:
umount /u01/app/oracle/admin/IDMDomain/aserve
Mount the shared disk on IDMHOST2 as the root user. For example:
mount storageHost:/Path_to_AdminVolume_on_SharedDisk \ /u01/app/oracle/admin/domainName/aserver -t nfs \ -o rw,bg,hard,nointr,tcp,vers=3,timeo=300,rsize=32768,wsize=32768
For example:
mount storageHost:/vol/adminVol /u01/app/oracle/admin/IDMDomain/aserver \ -t nfs -o rw,bg,hard,nointr,tcp,vers=3,timeo=300,rsize=32768,wsize=32768
Start the NodeManager on IDMHOST2 using the startNodeManager.sh script located under the ORACLE_HOME/wlserver_10.3/server/bin directory, if it is not already running.
Start the WebLogic Administration Server on IDMHOST2 using the startweblogic.sh script located under the ORACLE_BASE/admin/IDMDomain/aserver/IDMDomain/bin directory.
After the Administration Server starts up, validate that you can access the WebLogic Server Administration Console and the Oracle Enterprise Manager Fusion Middleware Control using the virtual IP.
For example, to access the WebLogic Administration Server Console using the virtual IP address, open a web browser and enter this URL:
http://idmhost-vip.mycompany.com:7777/console
To access the Oracle Enterprise Manager Fusion Middleware Control using the virtual IP address, open a web browser and enter this URL:
http://idmhost-vip.mycompany.com:7777/em
Log into each by specifying the credentials for the weblogic user.
Follow these steps to failback the WebLogic Administration Server and Oracle Enterprise Manager Fusion Middleware Control from IDMHOST2 to IDMHOST1:
Make sure that the Administration Server is not running on IDMHOST2. If it is running, use the WebLogic Administration Console to stop the Administration Server on IDMHOST2.
Make sure that the virtual IP has been disabled on IDMHOST2. If it is not disabled, then disable it using the ifconfig command. In a UNIX environment, run this command as the root user.
/sbin/ifconfig networkCardInterface down
Enable the virtual IP on IDMHOST1 using the ifconfig command. The syntax and usage for the ifconfig command is shown below. In a UNIX environment, run the ifconfig command as the root user.
/sbin/ifconfig networkCardInterface IPAddress netmask netMask
For example:
/sbin/ifconfig eth0:1 139.185.140.200 netmask 255.255.255.0
Update the routing tables using the arping command. In a UNIX environment, run the arping command as the root user.
/sbin/arping -q -U -c 3 -I networkCardInterface VirtualIPAddress
For example:
/sbin/arping -q -U -c 3 -I eth0 139.185.140.200
Unmount the shared disk from IDMHOST2 as the root user.
umount /u01/app/oracle/admin/domainName/aserver
For Example:
umount /u01/app/oracle/admin/IDMDomain/aserve
Mount the shared disk on IDMHOST1 as the root user.
mount storageHost:/Path_to_AdminVolume_on_SharedDisk \ /u01/app/oracle/admin/domainName/aserver -t nfs \ -o rw,bg,hard,nointr,tcp,vers=3,timeo=300,rsize=32768,wsize=32768
For example:
mount storageHost:/vol/adminVol /u01/app/oracle/admin/IDMDomain/aserver \ -t nfs -o rw,bg,hard,nointr,tcp,vers=3,timeo=300,rsize=32768,wsize=32768
Start the NodeManager on IDMHOST1 using the startNodeManager script located under the ORACLE_HOME/wlserver_10.3/server/bin directory, if it is not already started.
Start the WebLogic Administration Server on IDMHOST1 using the startweblogic.sh script located under the ORACLE_BASE/admin/IDMDomain/aserver/IDMDomain/bin directory.
After the Administration Server starts up, validate that you can access the WebLogic Server Administration Console and the Oracle Enterprise Manager Fusion Middleware Control using the virtual IP.
For example, to access the WebLogic Administration Server Console using the virtual IP address, open a web browser and enter this URL:
http://idmhost-vip.mycompany.com:7777/console
To access the Oracle Enterprise Manager Fusion Middleware Control using the virtual IP address, open a web browser and enter this URL:
http://idmhost-vip.mycompany.com:7777/em
Log into each by specifying the credentials for the weblogic user.
It is an Oracle best practices recommendation to create a backup file after successfully completing the installation and configuration of each tier or a logical point. Create a backup of the installation after verifying that the install so far is successful. This is a quick backup for the express purpose of immediate restore in case of problems in later steps. The backup destination is the local disk. This backup can be discarded once the enterprise deployment setup is complete. After the enterprise deployment setup is complete, the regular deployment-specific Backup and Recovery process can be initiated. More details are described in the Oracle Fusion Middleware Administrator's Guide.
For information on database backups, refer to the Oracle Database Backup and Recovery User's Guide.
To back up the installation to this point, follow these steps:
Back up the application tier:
Shut down the instance using opmnctl located under the ORACLE_INSTANCE/bin directory:
ORACLE_INSTANCE/bin/opmnctl stopall
Create a backup of the Middleware Home on the application tier as the root user:
tar -cvpf BACKUP_LOCATION/apptier.tar MW_HOME
Create a backup of the Instance Home on the application tier as the root user:
tar -cvpf BACKUP_LOCATION/instance_backup.tar ORACLE_INSTANCE
Start up the instance using opmnctl located under the ORACLE_INSTANCE/bin directory:
ORACLE_INSTANCE/bin/opmnctl startall
Perform a full database backup (either a hot or cold backup). Oracle recommends that you use Oracle Recovery Manager. An operating system tool such as tar can be used for cold backups.
Back up the Administration Server domain directory. This saves your domain configuration. The configuration files all exist under the ORACLE_BASE/admin/domainName/aserver directory.
IDMHOST1> tar cvf edgdomainback.tar ORACLE_BASE/admin/domainName/aserver
Note:
Create backups on all machines in the application tier by following the steps shown above.For information about backing up the application tier configuration, see Section 9.4, "Performing Backups and Recoveries."