OHS installation & configuration, DM and GOC Cluster configuration

Please note that below commands/ports/hostname or other configuration details are

shown as examples only
For the environment you are going to work on; please replace with correct
port/hostname or other configuration details accordingly.
Take backup of /u01/adfmwprd and /nfsofm/adfmwprd before proceeding with the
below steps.
Pre-req check:
Check for at least 5GB free space is available under /u01 or /u02 where you are going
to install OHS
Check for at least 6 GB free RAM space available on the server(s)
check if all the LBRs to be used are ready; if not then request n/w Team to create the
LBR accordingly
GOC and DM Managed Server and Cluster creation:
login to adfconsole ( http://herbalife-fusion.hrbl.net:11000/adfconsole) as weblogic
user
go to Environment -> servers
click on new (if the link is embossed, click lock and edit)

Provide the details:

Server Name: DM_MSn11 (n denotes the node number)
Server Listen Address: uscosprdofmap01.hrbl.net
Server Listen Port: 5101
Click on
Yes, create a new cluster for this server.
Then click next

Provide the details:

Name: DM_CLS1
Click on Finish
Similarly create GOC_MSn11 on port 5201 with GOC_CLS1 cluster. (n denotes the
node number)
set serverstart parameter as follows:
for DM_MSn11 : -Xms1024M Xmx1024M
for GOC_MSn11: -Xms2048M -Xmx2048M
Target the library deployments listed below to include DM_CLS1 and
GOC_CLS1
adf.oracle.businesseditor(1.0,11.1.1.2.0)
adf.oracle.domain(1.0,11.1.1.2.0)
adf.oracle.domain.webapp(1.0,11.1.1.2.0)
jsf(2.0,1.0.0.0_2-0-2)
jstl(1.2,1.2.0.1)
ohw-rcf(5,5.0)
ohw-uix(5,5.0)
oracle.adf.dconfigbeans(1.0,11.1.1.2.0)
oracle.adf.desktopintegration(1.0,11.1.1.2.0)
oracle.adf.desktopintegration.model(1.0,11.1.1.2.0)
oracle.adf.management(1.0,11.1.1.2.0)
oracle.dconfig-infra(11,11.1.1.1.0)
oracle.jrf.system.filter
oracle.jsp.next(11.1.1,11.1.1)
oracle.pwdgen(11.1.1,11.1.1.2.0)
oracle.wsm.seedpolicies(11.1.1,11.1.1)
orai18n-adf(11,11.1.1.1.0)
UIX(11,11.1.1.1.0)

ApplyJRF Do the following steps:

cd /u01/adfmwprd/Oracle/Middleware/oracle_common/common/bin
Run wlst.sh
Run the following command
In our case :
CLUSTER_NAME = GOC_CLS1
PATH = /u01/adfmwprd/admin/adf_domain/aserver/adf_domain
wls:/offline> applyJRF('<CLUSTER_NAME>', 'PATH')
applyJRF('GOC_CLS1', '/u01/adfmwprd/admin/adf_domain/aserver/adf_domain')
CLUSTER_NAME = DM_CLS1
PATH = /u01/adfmwprd/admin/adf_domain/aserver/adf_domain
wls:/offline> applyJRF('<CLUSTER_NAME>', 'PATH')
applyJRF('DM_CLS1', '/u01/adfmwprd/admin/adf_domain/aserver/adf_domain')
Start only GOC MS and make sure there are no errors in the log/out file for the Managed Server.
As we are not using DM cluster now, we should keep DM Managed Servers Down as of now.

Installing Oracle HTTP Server:

Start the Oracle Universal Installer from the Oracle Fusion Middleware 11g WebTier
and Utilities DVD by issuing this command:
[adfmwprd@uscosprdofmap01 Disk1]$ pwd
/stageofm/Dumps/OHS_11.1.1.2.0/Disk1
[adfmwprd@uscosprdofmap01 Disk1]$ ./runInstaller

If the Specify Inventory Directory screen appears, enter the location for the inventory
and the user group and then click OK;

In the Welcome screen, click Next.

In the Select Installation Type screen, select Install and Configure, and click Next.

In the Prerequisite Checks screen, ensure that all the prerequisites are met, then click
Next.

In the Specify Installation Location screen, do the following:

Oracle Middleware Home: /u01/adfmwprd/Oracle/Middleware_WEB
Oracle Home Directory: ADF_WEB
Ignore the warning below and click on Next

In the Configure Components screen, do the following:

Select Oracle Http Server.
Do not select Oracle Web Cache.
Do not select Associate Selected Components with WebLogic Domain because you
have not yet installed WebLogic Server.
Click Next.

In the Specify Component Details screen, do the following:

Instance Home Location:
/u01/adfmwprd/admin/web/instances/adf_ohs1
Instance Name: adf_ohs1
OHS Component Name: ohs1
Click Next.

In the Configure Ports screen, do the following:

Select Specify Ports using Configuration File and copy the staticports.ini template file
from your installation disk (the file is located in the /Disk1/stage/Response directory)
to you user's home (/home/adfmwprd). Then use the Browse button to select this file.
Click View/Edit File to open the staticports.ini file in an editor.
Change the Oracle HTTP Server port in that file to 5200.
Save the file.
Click Next.

In the Specify Security Updates screen, enter your e-mail address to receive e-mail
notifications of security issues (if required). Enter your Oracle Support Password to
receive security updates through My Oracle Support.

In the Installation Summary screen, ensure that the selections are correct, and click
Install.

In the Configuration screen, multiple configuration assistants are launched in

succession, which can be a lengthy process. When it completes, the Configuration
Completed screen appears.

In the Installation Completed screen, click Finish to exit.

Upgrade to OHS 11.1.1.5

[adfmwprd@uscosprdofmap01 Disk1]$ pwd
/stageofm/Dumps/OHS_11.1.1.5.0/Disk1

[adfmwprd@uscosprdofmap01 Disk1]$ ./runInstaller

Click Retry

Similarly do the OHS installation and upgrade on ap02/ap03/ap04 servers as

applicable.
3.2 Setting up Oracle HTTP Server through the Load Balancer
Take backup of httpd.conf before editing it.
In httpd.conf file under
/u01/adfmwprd/admin/web/instances/adf_ohsn/config/OHS/ohsn (n=1/2/3/4) directory
put the below entries:
Listen 5200
Listen 5100
Listen 5000
Take backup of mod_wl_ohs.conf before editing it.
In mod_wl_ohs.conf under
/u01/adfmwprd/admin/web/instances/adf_ohsn/config/OHS/ohsn (n=1/2/3/4) directory.
Add the following entries to the file:
# NOTE : This is a template to configure mod_weblogic.
LoadModule weblogic_module "${ORACLE_HOME}/ohs/modules/mod_wl_ohs.so"

# This empty block is needed to save mod_wl related configuration from EM to this file when changes are
made at the Base Virtual Host Level
<IfModule weblogic_module>
</IfModule>
<Location / >
SetHandler weblogic-handler
WebLogicCluster uscosprdofmap01.hrbl.net:5201, uscosprdofmap02.hrbl.net:5201,
uscosprdofmap03.hrbl.net:5201, uscosprdofmap04.hrbl.net:5201
PathTrim /GOC
PathPrepend /GOC
</Location>
NameVirtualHost *:5000
<VirtualHost *:5000>
ServerName herbalife-fusionapps.hrbl.net
ServerAdmin you@your.address
RewriteEngine On
RewriteOptions inherit
<Location /console >
SetHandler weblogic-handler
WebLogicCluster herbalife-admprd.hrbl.net:4001
</Location>
</VirtualHost>
NameVirtualHost *:5100
<VirtualHost *:5100>
ServerName herbalife-dm.hrbl.net:80
ServerAdmin you@your.address
RewriteEngine On
RewriteOptions inherit
<Location / >
SetHandler weblogic-handler
WebLogicCluster uscosprdofmap01.hrbl.net:5101, uscosprdofmap02.hrbl.net:5101,
uscosprdofmap03.hrbl.net:5101, uscosprdofmap04.hrbl.net:5101
PathTrim /DM
PathPrepend /DM
</Location>
</VirtualHost>

Make sure that you restart OHS servers after modifying the httpd.conf files:
[adfmwprd@uscosprdofmap01 bin]$ cd
/u01/adfmwprd/admin/web/instances/adf_ohs1/bin
[adfmwprd@uscosprdofmap01 bin]$ ./opmnctl stopall
[adfmwprd@uscosprdofmap01 bin]$ ./opmnctl startall
Similarly, bounce OHS on other nodes accordingly.
Verify that the server status is reported as "Running" in the Admin 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 10.6, "Troubleshooting" for possible causes.

Register new ohs with adf domain

opmnctl registerinstance -adminHost herbalife-admts4.hrbl.net -adminPort 4001 -adminUsername
fusion_admin

New URLs after above configurations would be as follows:

ADF adminconsole: http://herbalife-fusionapps.hrbl.net:5000/console (Please
verify if you can login to the ADF admin console using this url)
GOC : http://herbalife-goc.hrbl.net or http://goc.hrbl.net
DM : http://herbalife-dm.hrbl.net or http://dm.hrbl.net
Please share the above urls to the Migration Team and Interface Monitoring Team and
ask them to use the newly configured ADF adminconsole url to login to ADF admin
console and to deploy the GOC application targeting to GOC_CLS1
Verification:
1) Please verify if you can login to the ADF admin console using this url
http://herbalife-fusionapps.hrbl.net:5000/console
2) Once the GOC application is deployed, you should be able to access it using
http://goc.hrbl.net or http://herbalife-goc.hrbl.net or through the host-specific
individual urls listed under testing tab of the deployment.

****End of Document****