| Oracle® Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter Content 11g Release 1 (11.1.1) Part Number E15483-05 |
|
|
PDF · Mobi · ePub |
| Oracle® Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter Content 11g Release 1 (11.1.1) Part Number E15483-05 |
|
|
PDF · Mobi · ePub |
This chapter describes how to create a domain using the Oracle Fusion Middleware Configuration Wizard, Oracle WebLogic Server Administration Console, and Oracle Enterprise Manager. You can extend the domain to add Fusion Middleware (FMW) components: Oracle SOA Suite, Oracle WebCenter Content and, optionally, its Imaging and Inbound Refinery feature sets. This will be addressed in later chapters in this document.
Note:
Before starting the setup process, read the release notes for additional installation and deployment information. They are available on the Oracle Fusion Middleware Documentation Library at http://download.oracle.com/docs/cd/E21764_01/relnotes.htm.
This chapter contains the following sections:
Section 8.3, "Running the Configuration Wizard on SOAHOST1 to Create a Domain"
Section 8.5, "Configuring Oracle HTTP Server for the WebLogic Domain"
Table 8-1 lists the steps for creating a WebLogic domain, including post-configuration tasks.
Table 8-1 Steps for Creating a WebLogic Domain
| Step | Description | More Information |
|---|---|---|
|
Enabling VIP1 in SOAHOST1 |
Enable ADMINVHN for the SOAHOST1 hostname. |
|
|
Create a WebLogic Domain |
Run the Configuration Wizard to create a WebLogic domain. |
Section 8.3, "Running the Configuration Wizard on SOAHOST1 to Create a Domain" |
|
Post-Configuration and Verification Tasks |
Follow the instructions for post-configuration and validation tasks. |
|
|
Configure the Oracle HTTP Server with the WebLogic domain |
Configure Oracle HTTP Server with the WebLogic domain and validate the configuration. |
Section 8.5, "Configuring Oracle HTTP Server for the WebLogic Domain" |
|
Back Up the Domain |
Back up the newly configured WebLogic domain. |
Once this domain is created and configured you can extend the domain to include Oracle SOA and Oracle WebCenter Content components as described in the next chapters.
This step is required for failover of the Administration Server, regardless of whether or not other Fusion Middleware components are installed later.
You are associating the Administration Server with a virtual host name (ADMINVHN). This virtual host name must be mapped to the appropriate VIP (VIP1) either by a DNS server or by a custom /etc/hosts entry. Check that ADMINVHN is available according to your name resolution system (DNS server, /etc/hosts) in the required nodes in your Oracle WebCenter Content topology. The VIP (VIP1) that is associated to this virtual host name (ADMINVHN) must be enabled in SOAHOST1.
To enable the virtual IP on Linux:
Run the ifconfig command as root:
/sbin/ifconfig interface:index IP_address netmask netmask /sbin/arping -q -U -c 3 -I interface IP_address
For example:
/sbin/ifconfig ethX:Y 100.200.140.206 netmask 255.255.255.0
Enable your network to register the new location of the virtual IP, for example:
/sbin/arping -q -U -c 3 -I ethX 100.200.140.206
Validate that the address is available by pinging it from another node, for example:
/bin/ping 100.200.140.206
In this example, ethX is the ethernet interface (eth0 or eth1) and Y is the index (0, 1, 2, and so on).
Run the Oracle Fusion Middleware Configuration Wizard from the Oracle Common home directory to create a domain containing the Administration Server. You will extend the domain to contain other components later.
Ensure that the database where you installed the repository is running. For Oracle RAC databases, it is recommended that all instances are running, so that the validation check later on becomes more reliable.
On SOAHOST1, change the directory to the location of the Oracle Fusion Middleware Configuration Wizard (created in Chapter 5, "Installing the Software for an Enterprise Deployment"):
cd ORACLE_COMMON_HOME/common/bin
Start the Configuration Wizard:
./config.sh
In the Welcome screen, select Create a new WebLogic Domain, and click Next.
The Select Domain Source screen opens (Figure 8-1).
In the Select Domain Source screen, do the following:
Select Generate a domain configured automatically to support the following products.
Select the following products:
Basic WebLogic Server Domain - 10.3.6.0 [wlserver_10.3] (this should be selected automatically)
Oracle Enterprise Manager - 11.1.1.0 [oracle_common]
If you accidentally deselect some of the targets, make sure that the following selections are made in this screen:
Oracle Enterprise Manager
Oracle JRF
Click Next.
In the Specify Domain Name and Location screen, enter the domain name (domain_name).
Make sure that the domain directory matches the directory and shared storage mount point recommended in Chapter 3, "Preparing the Network for an Enterprise Deployment": enter ORACLE_BASE/admin/domain_name/aserver for the domain directory and ORACLE_BASE/admin/domain_name/aserver/applications for the application directory. This directory should be in shared storage.
Click Next.
In the Configure Administrator User Name and Password screen, enter the username and password to be used for the domain's administrator.
Click Next.
In the Configure Server Start Mode and JDK screen, do the following:
For WebLogic Domain Startup Mode, select Production Mode.
For JDK Selection, select JROCKIT SDK1.6.0_version.
Click Next.
In the Select Optional Configuration screen, select the following:
Administration Server
Managed Servers, Clusters and Machines
Click Next.
In the Configure the Administration Server screen, enter the following values:
Name: AdminServer
Listen address: ADMINVHN.
Listen port: 7001
SSL listen port: N/A
SSL enabled: Leave this checkbox unselected.
Click Next.
In the Configure Managed Servers screen, click Next.
In the Configure Clusters screen, click Next.
In the Configure Machines screen, open the Unix Machine tab and then click Add to add the following machine:
Leave all other fields to their default values. Please note that the machine name does not need to be a valid host name or listen address; it is just a unique identifier of a Node Manager location.
Click Next.
In the Assign Servers to Machines screen, assign servers to machines as follows:
ADMINVHN:
AdminServer
Click Next.
In the Configuration Summary screen, click Create.
In the Create Domain screen, click Done.
After configuring the domain with the Configuration Wizard, follow these instructions for post-configuration and verification.
The section includes the following topics:
Section 8.4.1, "Creating boot.properties for the Administration Server on SOAHOST1"
Section 8.4.3, "Starting the Administration Server on SOAHOST1"
Section 8.4.4, "Validating the Administration Server Configuration"
Section 8.4.5, "Disabling Host Name Verification for the Administration Server"
Create a boot.properties file for the Administration Server on SOAHOST1. This file enables the Administration Server to start without prompting you for the administrator username and password.
Create the following directory structure on SOAHOST1:
mkdir -p ORACLE_BASE/admin/domain_name/aserver/domain_name/servers/AdminServer/security
In a text editor, create a file called boot.properties in the directory created in the previous step, and enter the following lines in the file:
username=Admin_Username password=Password
Note:
When you start the Administration Server, the username and password entries in the file get encrypted. You start the Administration Server in Section 8.4.3, "Starting the Administration Server on SOAHOST1." For security reasons, you want to minimize the time the entries in the file are left unencrypted. After you edit the file, you should start the server as soon as possible so that the entries get encrypted.
Save the file and close the editor.
To start Node Manager on SOAHOST1, set the StartScriptEnabled property to true, and then start Node Manager using startNodeManager.sh.
To start Node Manager on SOAHOST1:
Run the setNMProps.sh script, which is located in the ORACLE_COMMON_HOME/common/bin directory, to set the StartScriptEnabled property to true before starting Node Manager:
cd ORACLE_COMMON_HOME/common/bin
./setNMProps.sh
Note:
You must use the StartScriptEnabled property to avoid class loading failures and other problems. See also Section 16.11.3, "Incomplete Policy Migration After Failed Restart of SOA Server."
Start Node Manager:
cd WL_HOME/server/bin
export JAVA_OPTIONS=-DDomainRegistrationEnabled=true
./startNodeManager.sh
Note:
It is important that the -DDomainRegistrationEnabled=true parameter is set whenever a Node Manager is started which must manage the Administration Server. If there is no Administration Server on the machine and the machine is not an Administration Server failover node, then Node Manager can be started using
./startNodeManager.sh
(without the export command).
Note:
Verify that Node Manager is using the appropriate stores and alias from the Node Manager output. Node Manager should prompt out the following:
CustomIdentityKeyStoreFileName=ORACLE_BASE/admin/domain_name/aserver/domain_name/certs/appIdentityKeyStore.jks CustomIdentityAlias=appIdentityX
Host name verification works if you apply a test configuration change to the servers, and it succeeds without Node Manager reporting any SSL errors.
The Administration Server is started and stopped using Node Manager. However, the first start of the Administration Server with Node Manager requires changing the default username and password that the Oracle Fusion Middleware Configuration Wizard set for Node Manager. You must therefore use the start script for the Administration Server for the first start. Follow these steps to start the Administration Server using Node Manager (steps 1 through 4 are required for the first start; all subsequent starts require only step 4):
On SOAHOST1, start the Administration Server using the start script in the domain directory:
cd ORACLE_BASE/admin/domain_name/aserver/domain_name/bin ./startWebLogic.sh
Use the Administration Console to update the Node Manager credentials:
Open a web browser and go to http://ADMINVHN:7001/console.
Log in as the administrator.
Click Lock & Edit.
Click domain_name, then Security, then General, and then expand the Advanced options at the bottom.
Enter a new username for Node Manager or make a note of the existing one and update the Node Manager password.
Save and activate the changes.
Stop the Administration Server process, either using Ctrl+C in the shell where it was started or by the standard process identification and kill commands in the operating system.
Start the Oracle WebLogic Scripting Tool (WLST) and connect to Node Manager with nmconnect and the credentials set in the previous steps, and start the Administration Server using nmstart:
cd ORACLE_COMMON_HOME/common/bin
./wlst.sh
Once in the WLST shell, execute the following command (make sure Node Manager is up and running):
wls:/offline>nmConnect("Admin_User","Admin_Pasword", "SOAHOST1","5556","domain_name","/u01/app/oracle/admin/domain_name/aserver/domain_name")
wls:/nm/domain_name> nmStart("AdminServer")
Note:
SOAHOST1 is the address of the node where the domain was created, not the listen address of the Administration Server.
Also, the username and password are only used to authenticate connections between Node Manager and clients. They are independent from the server admin ID and password, and are stored in the ORACLE_BASE/admin/domain_name/aserver/domain_name/config/nodemanager/nm_password.properties file.
To ensure that the Administration Server for the domain you have created is properly configured, validate the configuration by logging into the Oracle WebLogic Server Administration Console and verifying the managed servers and the cluster are listed, and log in to Oracle Enterprise Manager.
To verify that the administration server is properly configured:
Open a Web browser and go to http://ADMINVHN:7001/console.
Log in as the administrator.
Check that you can access Oracle Enterprise Manager at http://ADMINVHN:7001/em.
Log in to the Oracle Enterprise Manager console with the user name and password you specified in Section 8.4.1, "Creating boot.properties for the Administration Server on SOAHOST1."
This step is required if you have not set up the appropriate certificates to authenticate the different nodes with the Administration Server (see Chapter 13, "Setting Up Node Manager"). If you have not configured the server certificates, you will receive errors when managing the different WebLogic servers. To avoid these errors, disable host name verification while setting up and validating the topology, and enable it again once the enterprise deployment topology configuration is complete as described in Chapter 13, "Setting Up Node Manager."
To disable host name verification:
Log in to Oracle WebLogic Server Administration Console.
Click Lock & Edit.
Expand the Environment node in the Domain Structure window.
Click Servers.
On the Summary of Servers page, select AdminServer(admin) in the Names column of the table.
On the settings page for the server, open the SSL tab.
Expand the Advanced section of the page.
Set host name verification to None.
Click Save.
Save and activate the changes.
The change will not take effect until the Administration Server is restarted (Node Manager must be up and running):
Stop the Administration Server using the following command:
wls:/nm/domain_name>nmKill("AdminServer")
Start the Administration Server again as described in Section 8.4.3, "Starting the Administration Server on SOAHOST1."
This section describes tasks for configuring Oracle HTTP Server for the WebLogic domain, and for verifying the configuration.
This section includes the following topics:
Section 8.5.1, "Configuring Oracle HTTP Server for the Administration Server"
Section 8.5.2, "Turning on the WebLogic Plug-In enabled Flag"
Section 8.5.3, "Registering Oracle HTTP Server with WebLogic Server"
Section 8.5.5, "Validating Access Through Oracle HTTP Server"
Section 8.5.6, "Manually Failing Over the Administration Server to SOAHOST2"
To enable Oracle HTTP Server to route to the Administration Server, you must set the corresponding mount points in your HTTP server configuration:
For each of the web servers on WEBHOST1 and WEBHOST2, add the following lines to the file ORACLE_INSTANCE/config/OHS/component_name/ mod_wl_ohs.conf:
# Admin Server and EM <Location /console> SetHandler weblogic-handler WebLogicHost ADMINVHN WeblogicPort 7001 WLProxySSL OFF WLProxySSLPassThrough OFF </Location> <Location /consolehelp> SetHandler weblogic-handler WebLogicHost ADMINVHN WeblogicPort 7001 WLProxySSL OFF WLProxySSLPassThrough OFF </Location> <Location /em> SetHandler weblogic-handler WebLogicHost ADMINVHN WeblogicPort 7001 WLProxySSL OFF WLProxySSLPassThrough OFF </Location>
For each of the web servers on WEBHOST1 and WEBHOST2, make sure the file ORACLE_INSTANCE/config/OHS/component_name/httpd.conf includes the following lines:
NameVirtualHost *:7777 <VirtualHost *:7777> ServerName admin.mycompany.com:80 ServerAdmin you@your.address RewriteEngine On RewriteOptions inherit </VirtualHost>
Note:
Values such as 7777, admin.mycompany.com:80, and you@your.address that are noted in this document serve as examples only. Enter values based on the actual environment.
Restart Oracle HTTP Server on both WEBHOST1 and WEBHOST2:
ORACLE_BASE/admin/instance_name/bin/opmnctl restartproc ias-component=ohsX
For WEBHOST1, use ohs1 for ias-component and for WEBHOST2 use ohs2.
For security purposes, and since the load balancer terminates SSL requests (Oracle HTTP Server routes the requests as non-SSL to WebLogic Server), once SSL is configured for the load balancer, turn on the WebLogic plug-in enabled flag for the domain. Make sure you do this only if SSL is configured for the load balancer. To perform this procedure, follow these steps:
Log in to the Administration Console.
Click the domain name in the navigation tree on the left.
Open the Web Applications tab.
Click Lock & Edit.
Select the WebLogic Plugin Enabled checkbox.
Save and activate the changes.
Restart the administration server (even though the WLS console may not specifically prompt for that).
Once an Oracle WebLogic domain is created, the Oracle web tier can be linked to the domain. The advantage of doing this is that the Oracle web tier can be managed and monitored using the Oracle Enterprise Manager Fusion Middleware Control console.
To associate the Oracle web tier with the WebLogic domain, use the following commands on WEBHOST1:
cd ORACLE_BASE/admin/instance_name/bin ./opmnctl registerinstance -adminHost ADMINVHN -adminPort 7001 -adminUsername weblogic
You must also run this command from WEBHOST2 for OHS2.
After registering Oracle HTTP Server, it should appear as a manageable target in the Oracle Enterprise Manager console. To verify this, log in to the Oracle Enterprise Manager console. The WebTier item in the navigation tree should show that Oracle HTTP Server has been registered.
When you access the Oracle WebLogic Server Administration Console using a load balancer, it is required to change the Administration Server's frontend URL so that the user's web browser is redirected to the appropriate load balancer address.
The Oracle WebLogic Server Administration Console application tracks changes made to ports, channels and security using the console. When changes made through the console are activated, the console validates its current listen address, port and protocol. If the listen address, port and protocol are still valid, the console redirects the HTTP request replacing the host and port information with the Administration Server's listen address and port.
To change the Administration Server's frontend URL:
Log in to Oracle WebLogic Server Administration Console.
Click Lock & Edit.
Expand the Environment node in the Domain Structure window.
Click Servers.
On the Summary of Servers page, select Admin Server in the Names column of the table.
On the settings page for AdminServer(admin), open the Protocols tab.
Open the HTTP tab.
Set the Front End Host field to admin.mycompany.com and the Frontend HTTP Port field to 80 (modify accordingly if HTTPS is used for the admin URL).
Save and activate the changes.
Disable tracking on configuration changes in the Oracle WebLogic Server Administration Console so that the console does not trigger the reloading of configuration pages when activation of changes occurs.
Log in to the Oracle WebLogic Server Administration Console.
Click the Preferences link in the banner.
Open the Shared Preferences tab.
Clear the Follow Configuration Changes checkbox.
Click Save.
Note:
If you have any issues activating any configuration changes after modifying the Frontend Host and Port settings, then refer to Section 16.11.10, "Redirecting of Users to Login Screen After Activating Changes in Administration Console."
Verify that the server status is reported as Running in the Administration Console. If the server is shown as Starting or Resuming, wait for the server status to change to Started. If another status is reported (such as Admin or Failed), check the server output log files for errors. See Section 16.11, "Troubleshooting the Oracle WebCenter Content Enterprise Deployment Topology" for possible causes.
Validate the Administration Console and Oracle Enterprise Manager through both Oracle HTTP Server instances using the following URLs:
http://WEBHOST1:7777/console
http://WEBHOST2:7777/console
http://WEBHOST1:7777/em
http://WEBHOST2:7777/em
http://admin.mycompany.com/console
http://admin.mycompany.com/em
After setting the frontend URL to the load balancer address, access to the console through the WEBHOSTn addresses will be redirected by the console to the frontend URL, thus validating the correct configuration of both Oracle HTTP Server and the load balancer.
For information on configuring system access through the load balancer, see Section 3.3, "Configuring the Load Balancer."
After registering Oracle HTTP Server as described in Section 8.5.3, "Registering Oracle HTTP Server with WebLogic Server," it should appear as a manageable target in the Oracle Enterprise Manager console. To verify this, log in to the Oracle Enterprise Manager console. The WebTier item in the navigation tree should show that Oracle HTTP Server has been registered.
In case a node fails, you can fail over the Administration Server to another node. This section describes how to fail over the Administration Server from SOAHOST1 to SOAHOST2:
Section 8.5.6.2, "Validating Access to SOAHOST2 Through Oracle HTTP Server"
Section 8.5.6.3, "Failing the Administration Server Back to SOAHOST1"
Please note the following assumptions:
The Administration Server is configured to listen on ADMINVHN, and not on ANY address. See step 13 in Section 8.3, "Running the Configuration Wizard on SOAHOST1 to Create a Domain".
The Administration Server is failed over from SOAHOST1 to SOAHOST2, and the two nodes have these IP addresses:
SOAHOST1: 100.200.140.165
SOAHOST2: 100.200.140.205
ADMINVHN: 100.200.140.206. This is the VIP where the Administration Server is running, assigned to ethX:Y, available in SOAHOST1 and SOAHOST2.
The domain directory where the administration server is running in SOAHOST1 is on a shared storage and is mounted also from SOAHOST2.
Oracle WebLogic Server and Oracle Fusion Middleware components have been installed in SOAHOST2 as described in Chapter 5, "Installing the Software for an Enterprise Deployment" (that is, the same paths for ORACLE_HOME and MW_HOME that exist on SOAHOST1 are also available on SOAHOST2).
Procedure
The following procedure shows how to fail over the Administration Server to a different node (SOAHOST2):
Stop the Administration Server if it is running.
Migrate the IP address to the second node:
Run the following command as root on SOAHOST1 (where X:Y is the current interface used by ADMINVHN):
/sbin/ifconfig ethX:Y down
Run the following command on SOAHOST2:
/sbin/ifconfig interface:index IP_address netmask netmask
For example:
/sbin/ifconfig eth0:1 100.200.140.206 netmask 255.255.255.0
Note:
Make sure that the netmask and interface to be used match the available network configuration in SOAHOST2. Also, make sure that the location of the administration server application directory is mounted as described in Section 4.3, "Recommended Locations for the Different Directories."
Update the routing tables on SOAHOST2 using arping, for example:
/sbin/arping -b -A -c 3 -I eth0 100.200.140.206
Start Node Manager in SOAHOST2 as described in Section 8.4.2, "Starting Node Manager on SOAHOST1."
Start the Administration Server on SOAHOST2 as described in Section 8.4.3, "Starting the Administration Server on SOAHOST1."
Test that you can access the Administration Server on SOAHOST2 as follows:
Ensure that you can access the Oracle WebLogic Server Administration Console at http://ADMINVHN:7001/console.
Check that you can access and verify the status of components in Oracle Enterprise Manager at http://ADMINVHN:7001/em.
Perform the same steps as in Section 8.5.5, "Validating Access Through Oracle HTTP Server." This is to check that you can access the Administration Server when it is running on SOAHOST2.
This step checks that you can fail back the Administration Server; that is, stop it on SOAHOST2 and run it on SOAHOST1 again. To do this, migrate ADMINVHN back to the SOAHOST1 node as follows:
Make sure the Administration Server is not running.
Run the following command on SOAHOST2.
/sbin/ifconfig ethZ:N down
Run the following command on SOAHOST1:
/sbin/ifconfig ethX:Y 100.200.140.206 netmask 255.255.255.0
Note:
Make sure that the netmask and interface to be used match the available network configuration in SOAHOST1.
Update the routing tables using arping. Run the following command from SOAHOST1:
/sbin/arping -b -A -c 3 -I ethZ 100.200.140.206
Start the Administration Server again on SOAHOST1 as described in Section 8.4.3, "Starting the Administration Server on SOAHOST1."
Test that you can access the Oracle WebLogic Server Administration Console at http://ADMINVHN:7001/console.
Check that you can access and verify the status of components in Oracle Enterprise Manager at http://ADMINVHN:7001/em.
After you have verified that the extended domain is working, back up the installation. This is a quick backup for the express purpose of immediate restore in case of problems in the further steps. The backup destination is the local disk. This backup can be discarded once the enterprise deployment setup is complete. At that point, the regular deployment-specific backup and recovery process can be initiated. The Oracle Fusion Middleware Administrator's Guide provides further details. For information on describing the Oracle HTTP Server data that must be backed up and restored, refer to the "Backup and Recovery Recommendations for Oracle HTTP Server" section in that guide. For information on how to recover components, see the "Recovery of Components" and "Recovery After Loss of Component" sections in the guide. For recommendations specific to recovering from the loss of a host, see the "Recovering Oracle HTTP Server to a Different Host" section in the guide. Also refer to the Oracle Database Backup and Recovery Guide for information on database backup.
To back up the installation from at this point:
Back up the web tier from WEBHOST1:
Shut down the instance using opmnctl:
ORACLE_BASE/admin/instance_name/bin/opmnctl stopall
Back up the Middleware Home on the web tier using the following command (as root):
tar -cvpf BACKUP_LOCATION/web.tar MW_HOME
Back up the Oracle instance on the web tier using the following command:
tar -cvpf BACKUP_LOCATION/web_instance_name.tar ORACLE_INSTANCE
Start the instance using opmnctl:
cd ORACLE_BASE/admin/instance_name/bin opmnctl startall
Repeat step 1 for WEBHOST2.
Back up the database. This is a full database backup (either hot or cold) using Oracle Recovery Manager (recommended) or operating system tools such as tar for cold backups if possible.
Stop the Administration Server and back up its domain directory to save your domain configuration. The configuration files all exist in the ORACLE_BASE/admin/domain_name directory. Run the following command on SOAHOST1 to create the backup:
tar -cvpf edgdomainback.tar ORACLE_BASE/admin/domain_name
Do not forget to restart the Administration Server again.
|
 Copyright © 2010, 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|