WFM 5.2 Create Managed Servers

Version B.05.05.161
050552

This set of instructions covers the initial installation of the managed servers for WFM 5.2, during which a single managed server per WFM application and per application host is created.

Prerequisites:

The installation of WebLogic Server 8.1 SP3 must be complete prior to this installation.
The installation of WLS 8.1 WFM 5.2 Patch 2.1.0 must be complete prior to this installation.
The installation of WFM 5.2 Domain Creation Software must be complete prior to this installation.
The creation the WFM 5.2 domains per the WFM 5.2 Create Domains installation guide is complete.

Application Server Preparation
   Create Users and Home Directories                      BLT required
   Create the /opt/sasuapps/wfmsvc File System        BLT required
   Obtain a .profile File Having . (dot) In Its Path
   WFM Domain Control Server Installation
   Create Application and Instance Partitions
Create WFM Managed Servers
   Run the createManagedServers.sh Script
   Remove GCM Managed Server From AM Tertiary Server
   Start the Admin Server

IG Notes:

If printing, print in landscape mode only.
Checks made in step checkboxes do not get saved once you close this document.

1–Application Server Preparation

1a–Create Users and Home Directories

Open a BLT on each of the application servers to perform the following steps.

Region

Application Servers

hpat615.atl.hp.com

hpat616.atl.hp.com

hpat705.atl.hp.com

eelink05.sdc.hp.com

eelink06.sdc.hp.com

eelink04.sdc.hp.com

sgpux138.sgp.hp.com

sgpux139.sgp.hp.com

sgpux281.sgp.hp.com

Log in to the <hostname>.<domain>.hp.com application server as user root.
```
Example:

hpat615.atl.hp.com
```
Skip this step if the /homewfm file system is present.

Open a BLT to request the following new file system be created on the control and application servers. Note in the BLT for the control servers that the file system needs to be made part of the wlsgprd1.<domain>.hp.com ServiceGuard package.
```
  Filesystem: /homewfm
  Size:       2 GB
```
Skip this step if the following users are already present on each AM-region application server.
Open a BLT on each AM-region application server to request the following new users be created. Note in the BLT that all UNIX users' home folders need to be linked to the /homewfm file system.
Note: Where <user> is weshipri, weslopri, gcm and mwfl, respectively.
```
  User:                   <user>
  Group:                  eia
  Home directory:         /home/<user>
  Link home directory to: /homewfm/<user>
```
Open a BLT on each AM-region application server to request the auxiliary group eia8 be added for each of these users: weshipri, weslopri, gcm, and mwfl.
Skip this step if the following users are already present on each EU- and AP-region application server.
Open a BLT on each EU- and AP-region application server to request the following new users be created. Note in the BLT that all UNIX users' home folders need to be linked to the /homewfm file system.
Note: Where <user> is weshipri, weslopri and mwfl, respectively.
```
  User:                   <user>
  Group:                  eia
  Home directory:         /home/<user>
  Link home directory to: /homewfm/<user>
```
Open a BLT on each EU- and AP-region application server to request the auxiliary group eia8 be added for each of these users: weshipri, weslopri and mwfl.

1b–Obtain a .profile File Having . (dot) In Its Path

Perform the following sections 1b and 1c for each of the following users.

Region	Users
AM	weshipri, weslopri, gcm, mwfl
EU & AP	weshipri, weslopri, mwfl

Note: Skip section 1c if the .profile file has the following two entries:

. (dot) is in the $PATH
umask is set to 002

Obtain an appropriate .profile file.

  ftp hpat615.rose.hp.com
  Name: weblogic
  Password: <password>

  ftp> cd /opt/weblogic
  ftp> ascii
  ftp> get .profile
  ftp> quit

Change to the < user> home directory.
```
  cd /home/<user>
```
Change permission for the .profile file.
```
  chmod +w .profile
```
Open the .profile file for editing.
```
  vi .profile
```
Set the umask for <user> to 002 by modifying the following line.
```
Original value:

  umask 022

Modified value:

  umask 002
```
Close the editor while saving your changes.
Source in the updated .profile file in order to effectively add the changes.
```
. ~/.profile
```
Create a staging directory.
```
  mkdir staging
```
Logout of the UNIX session.
```
  exit
```
Repeat sections 1c and 1d for each remaining user. Repeat for each user on the remaining application server.

1d–Create Application and Instance Partitions

Directory to be Created	Owner:Group	Permission
/opt/sasuapps/wfmsvc/instances	weblogic:eia8	775
/opt/sasuapps/wfmsvc/applications	weblogic:eia8	775

Open a BLT to request the following directories (refer to table above) be created on each regional application server.

Open a BLT to request the following partition be created on AM-region application servers hpat615 and hpat616 only for the gcm user. (GCM is not deployed on hpat705.)

Note: For this step, the filesystem reference to GCM must be uppercase. The owner reference to gcm must be lowercase.
```
  File system: /opt/sasuapps/wfmsvc/applications/GCM
  Owner:        gcm:eia8
  Size:         4 GB
  Permission:   775
```
Open a BLT to request the following single partition be created on all application servers for the mwfl user.
Note: For this step, the filesystem reference to MWFL must be uppercase. The owner reference to mwfl must be lowercase.
```
  File system: /opt/sasuapps/wfmsvc/applications/MWFL
  Owner:       mwfl:eia8
  Size:        6 GB
  Permission:  775
```
Create a BLT to request the following partition be created on all regional application servers for the WAM application.
Note: The filesystem reference to WAM must be uppercase.
```
  File system: /opt/sasuapps/wfmsvc/applications/WAM
  Owner:       weslopri:eia8
  Size:        3 GB
  Permission:  775
```
Create a BLT to request the following partition be created on all regional application servers for the WASYNC application.
Note: The filesystem reference to WASYNC must be uppercase.
```
  File system: /opt/sasuapps/wfmsvc/applications/WASYNC
  Owner:       weslopri:eia8
  Size:        4 GB
  Permission:  775
```

Create a BLT to request the following partition be created on all regional application servers for the WES application.

Notes: Partition sizes vary according to region. The filesystem reference to WES must be uppercase.

  File system: /opt/sasuapps/wfmsvc/applications/WES
  Owner:       weshipri:eia8
  Size:        20 GB (AM and AP regions only)
  Size:        25 GB (EU region only)  
  Permission:  775

Create a BLT to request the following partition be created on each AM-region application server for the following user: gcm.
Note: For this step, the filesystem reference to GCM must be uppercase. The owner reference to gcm must be lowercase.
```
  File system: /opt/sasuapps/wfmsvc/applications/GCM
  Owner:       gcm:eia8
  Size:        1 GB
  Permission:  775
```
Create a BLT to request the following partition be created on all regional application servers for the following user: mwfl.
Note: For this step, the filesystem reference to MWFL must be uppercase. The owner reference to mwfl must be lowercase.
```
  File system: /opt/sasuapps/wfmsvc/instances/MWFL
  Owner:       mwfl:eia8
  Size:        2 GB
  Permission:  775
```
Create a BLT to request the following partitions be created on all regional application servers for the WAM application.
Note: For this step, the filesystem reference to WAM must be uppercase.
```
  File system: /opt/sasuapps/wfmsvc/instances/WAM
  Owner:       weslopri:eia8
  Size:        1 GB
  Permission:  775
```
Create a BLT to request the following partitions be created on all regional application servers for the WASYNC application.
Note: For this step, the filesystem reference to WASYNC must be uppercase.
```
  File system: /opt/sasuapps/wfmsvc/instances/WASYNC
  Owner:       weslopri:eia8
  Size:        2 GB
  Permission:  775
```
Create a BLT to request the following partition be created on each regional application server for the WES application.
Note: The filesystem reference to WES must be uppercase.
```
  File system: /opt/sasuapps/wfmsvc/instances/WES
  Owner:       weshipri:eia8
  Size:        7 GB
  Permission:  775
```

2–Create WFM Managed Servers

2a–Run the createManagedServers.sh Script

Perform the following steps on the control server package for each region.

Region Domain
Domain_Name

AM atl atconnct_RIBS_40

EU sdc SWconnct_EMEA

AP sgp AP_PROD

Log in to the wlsgprd1.<domain>.hp.com control server package as the user wfmsvc.
```
Example:

  wlsgprd1.atlhp.com
```
Run hostname to verify you are logged on to the wlsgprd1.<domain>.hp.com control server package before continuing.
```
  hostname

Sample output (AM region):

  i3107ei3 or i3107ei4
```
Skip to the next numbered step if the administration server is already running.
1. Change to the /opt/sasuapps/wfmsvc/domain/<domain_name>.
```
  cd /opt/sasuapps/wfmsvc/domain/<domain_name>

Example:

  cd /opt/sasuapps/wfmsvc/domain/wfm_domain_prod_AM
```
2. Start the admin server.
```
  startadmin
```

Change to the /opt/weblogic/installEIABase/P.05.03.021_EIA2/config directory.

  cd /opt/weblogic/installEIABase/P.05.03.021_EIA2/config

Example:

  cd /opt/weblogic/installEIABase/P.05.03.021_EIA2/config

Run the createManagedServers.sh script.

Note: Use the same <admin_user> and <admin_password> as used when creating the domain.

  ./createManagedServers.sh <domain_name> <admin_user> <admin_password>

Example:

  ./createManagedServers.sh wfm_domain_prod_AM <admin_user> <admin_password>

Expected output:

wfm_domain_prod_AM <admin_user> <admin_password>
createManagedServers.sh: 00:00:00: start
	.
	.
	.
Creating configuration for NodeManager: GCM_pri_hpat615 
wladmin create UnixMachine GCM_pri_hpat615 success.
wladmin set UUnixMachine GCM_pri_hpat615Notes success.
	.
	.
	.
Creating configuration for NodeManager: MWFL_pri_hpat615 
wladmin create UnixMachine MWFL_pri_hpat615 success.
wladmin set UUnixMachine MWFL_pri_hpat615 Notes success.
	.
	.
	.
Creating configuration for NodeManager: WAM_pri_hpat615 
wladmin create UnixMachine WAM_pri_hpat615 success.
wladmin set UUnixMachine WAM_pri_hpat615 Notes success.
	.
	.
	.
Creating configuration for NodeManager: WES_sec_hpat616
wladmin create UnixMachine WES_sec_hpat616 success.
wladmin set UUnixMachine WES_sec_hpat616 Notes success.
	.
	.
	.
Creating configuration for NodeManager: WASYNC_sec_hpat616 
wladmin create UnixMachine WASYNC_sec_hpat616 success.
wladmin set UUnixMachine WASYNC_sec_hpat616 Notes success.
	.
	.
	.
Creating configuration for Managed Server: GCM_sec_hpat616_01 
wladmin create Server GCM_sec_hpat616_01 success.
wladmin set Server GCM_sec_hpat616_01 Notes success.
	.
	.
	.
Updating configuration for Managed Server: AdminServer 
wladmin set Server AdminServer Notes success.
wladmin set ExecuteQueue weblogic.kernel.Default,Server=AdminServer ThreadCount success.
	.
	.
	.
createManagedServers.sh: 00:21:11: stop

2b–Remove GCM Managed Server From AM Tertiary Server

Perform the following steps on wlsgprd1.atl.hp.com (AM region) only.

Start the admin console in a Web browser.

  http://wlsgprd1.atl.hp.com:31600/console

Enter your username and password.
Expand the Servers branch in the left pane.
Right-click the GCM_ter_hpat705_01 entry.

Select the Delete GCM_ter_hpat705_01 item from the context-sensitive menu.

  Delete GCM_ter_hpat705_01

Sample output:

  Are you sure you want to permanently delete 
    GCM_ter_hpat705_01 from the domain configuration?

Click Yes.
Click Continue.
Close the admin console window.

2c–Start the Admin Server

Perform the following steps on the control server package for each region.

Change to the /opt/sasuapps/wfmsvc/domain/<domain_name>.

  cd /opt/sasuapps/wfmsvc/domain/<domain_name>

Example:

  cd /opt/sasuapps/wfmsvc/domain/atconnct_RIBS_40

Stop the admin server.

  stopWebLogic.sh

Expected output:

  Stopping Weblogic Server...

  Server "AdminServer" was force shutdown successfully ...

  Done.

Start the admin server.

  startadmin

Expected output:

  Redirecting stderr and stdout to startWebLogic.out

Sample startWebLogic.out content:

CLASSPATH=/opt/weblogic/jdk142_03/lib/tools.jar:
  /opt/weblogic/weblogic81/server/lib/weblogic_sp.jar:
  /opt/weblogic/weblogic81/server/lib/weblogic.jar:
	.
	.
	.
PATH=/opt/weblogic/weblogic81/server/bin:/opt/weblogic/jdk142_03/jre/bin:
  /opt/weblogic/jdk142_03/bin:/opt/perl/bin:/apps/bin:/usr/bin:/opt/ansic/bin:/usr/ccs/bin:
  /usr/contrib/bin:/opt/nettladm/bin:/opt/fc/bin:/opt/fcms/bin:/opt/upgrade/bin:/opt/pd/bin:
	.
	.
	.
***************************************************
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http://[hostname]:[port]/console *
***************************************************
<Apr 1, 2005 5:11:50 PM PST> <Info> <WebLogicServer> <BEA-000377> 
  <Starting WebLogic Server with Java HotSpot(TM) VM Version 
  1.4.2 1.4.2.03-040401-18:59-PA_RISC2.0 PA2.0 (aCC_AP) from 
  Hewlett-Packard Company> 
	.
	.
	.
<Apr 1, 2005 5:13:13 PM PST> <Notice> <WebLogicServer> <BEA-000331> 
  <Started WebLogic Admin Server "AdminServer" for domain "wfm_domain_conv_AM" 
  running in Development Mode> 
<Apr 1, 2005 5:13:13 PM PST> <Notice> <WebLogicServer> <BEA-000360> 
  <Server started in RUNNING mode>

Region	Domain	Domain_Name
AM	atl	atconnct_RIBS_40
EU	sdc	SWconnct_EMEA
AP	sgp	AP_PROD