Fandom

Scratchpad

Lbtest

215,864pages on
this wiki
Add New Page
Discuss this page0 Share

Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.

WebSphere 6.0.x Install Document

Preparing for the install

Mount the /repos volume on the destination server if it isn’t already there

Copy the script files from /opt/et/scripts directory on sacinohhqssea94.info53.com to the /opt/et/WAS/6.0 install directory on the destination server:

Modify the copied files permissions so you can make changes to them.

chmod 740 /opt/et/WAS/6.0/*.*

Complete the Port assignment worksheet in the ## Error converting ##: [\\s1cinohdcmiis99.info53.com\Documentation\ETArchitecture\Standards\Active\ WebSphereStandards_6.0.doc].

Binary Install Only

Open the /opt/et/WAS/6.0/resp.parent.txt file for editing.

vi /opt/et/WAS/6.0/resp.parent.txt

If this is the first binary install of 6.0 on this server, leave the following line as its default:

-P wasProductBean.installLocation=/opt/et/WAS/6.0/a

For future installs of 6.0 binaries on this server, increment the last directory to the next alpha letter.

Save and close the file.

Note: If you are installing anywhere outside of the default /opt/et/WAS/6.0/a directory you must modify the patch response files to point to the proper install path. Edit all three patch response files in the opt/et/WAS/6.0 directory: patch602.txt, patch602sdk.txt, patchfp19.txt

Change the following line to point to the correct install directory:

-W product.location="/opt/et/WAS/6.0/a"

Run the following command to perform the installation and apply patches. You will need to modify this file for installations not going to /opt/et/WAS/6.0/a:

/opt/et/WAS/6.0/inst6.0.sh

Deployment Manager Install

Open the /opt/et/WAS/6.0/resp.parent.txt file for editing.

vi /opt/et/WAS/6.0/resp.parent.txt

If this is the first binary install of 6.0 on this server, leave the following line as its default:

-P wasProductBean.installLocation=/opt/et/WAS/6.0/a

For future installs of 6.0 binaries on this server, increment the last directory to the next alpha letter.

Remove the # from the beginning of the following line:

#-W ndsummarypanelInstallWizardBean.launchPCT="true"

Insert a # at the beginning of the following line:

-W ndsummarypanelInstallWizardBean.launchPCT="false"

Remove the # from the beginning of the following line:

#-W pctresponsefilelocationqueryactionInstallWizardBean.fileLocation="/opt/et/WAS/6.0/resp.nd.txt"

Save and close resp.parent.txt.

Open the /opt/et/WAS/6.0/resp.nd.txt file for editing.

vi /opt/et/WAS/6.0/resp.nd.txt

Refer to the standards document for completing the entries for Cell, Node, and profile. A completed sample is listed below. In the case of the sample the CELL name is SSI01 (First Internal Shared Server Environment). The node name is DM_ssea94 (DM = Deployment Manager. Ssea94 is the last six characters of the server’s host name). The profile name is a concatenation of the profile’s use and the cell name (dm=Deployment Manager + SSI01 which is the cell name). Because this is the first installation of the binaries on this host the install root is /opt/et/WAS/6.0/a. The next binary install root will be /opt/et/WAS/6.0/b, etc.:

# Profile name

#

-W profilenamepanelInstallWizardBean.profileName="dmSSI01"

# Profile location. Currently set to default for first dmgr on the server

#

-P installLocation="/opt/et/WAS/6.0/a/profiles/dmSSI01"

# Node name

#

-W nodehostandcellnamepanelInstallWizardBean.nodeName="DM_ssea94"

# Host name

#

-W nodehostandcellnamepanelInstallWizardBean.hostName="sacinohhqssea94"

# Cell name

#

-W nodehostandcellnamepanelInstallWizardBean.cellName="SSI01"

Use the Port assignment worksheet you created earlier to modify the ports if necessary. Remember to verify the ports are not already in use before beginning your install.

Save and close resp.nd.txt.

Run the following command to perform the installation. You will need to modify this file for installations not going to /opt/et/WAS/6.0/a:

/opt/et/WAS/6.0/inst6.0.sh

Run the following command to install patches.

Note: If you are installing anywhere outside of the default /opt/et/WAS/6.0/a directory you must modify the patch response files to point to the proper install path. Edit all three patch response files in the opt/et/WAS/6.0 directory: patch602.txt, patch602sdk.txt, patchfp19.txt

Change the following line to point to the correct install directory:

-W product.location="/opt/et/WAS/6.0/a"

/opt/et/WAS/6.0/patch60.sh

Once the script completes, start the deployment manager.

Node Agent Install

Verify that the dmgr you will federate with is running.

Open the /opt/et/WAS/6.0/resp.parent.txt file for editing.

vi /opt/et/WAS/6.0/resp.parent.txt

If this is the first binary install of 6.0 on this server, leave the following line as its default:

-P wasProductBean.installLocation=/opt/et/WAS/6.0/a

For future installs of 6.0 binaries on this server, increment the last directory to the next alpha letter.

Remove the # from the beginning of the following line:

#-W ndsummarypanelInstallWizardBean.launchPCT="true"

Insert a # at the beginning of the following line:

-W ndsummarypanelInstallWizardBean.launchPCT="false"

Remove the # from the beginning of the following line:

# -W pctresponsefilelocationqueryactionInstallWizardBean.fileLocation="/opt/et/WAS/6.0/resp.node.txt"

Save and close resp.parent.txt.

Open the /opt/et/WAS/6.0/resp.node.txt file for editing.

vi /opt/et/WAS/6.0/resp.node.txt

Refer to the standards document for completing the entries for Node and profile. A completed sample is listed below. In the case of the sample the node name is SSI01_ssew97 (SSI01= Cell Name. Ssew97 is the last six characters of the server’s host name). The profile name is a concatenation of the profile’s use and the cell name (na=Node Agent + SSI01 which is the cell name). Because this is the first installation of the binaries on this host the install root is /opt/et/WAS/6.0/a. The next binary install root will be /opt/et/WAS/6.0/b, etc.:

# Profile name

#

-W profilenamepanelInstallWizardBean.profileName="naSSI01"

# Profile location

# Note that the "a" in the path below will need to be incremented if this isn’t

# the first cell on this server.

#

-P installLocation="/opt/et/WAS/6.0/a/profiles/naSSI01"

# Node name

#

-W nodehostnamepanelInstallWizardBean.nodeName="SSI01_ssew97"

# Host name

#

-W nodehostnamepanelInstallWizardBean.hostName="sacinohhqssew97"

Use the Port assignment worksheet you created earlier to modify the ports if necessary. Remember to verify the ports are not already in use before beginning your install.

The default response file setting is to federate with the deployment manager after the install. In order to accomplish this you need to populate the deployment manager hostname and the appropriate DM port.

# Specify the host name of the deployment manager for federation.

#

-W pctfederationpanelInstallWizardBean.hostname="sacinohhqssea94"

# Specify the port number where the deployment manager (DMGR) is reachable on the

# above host. The first DMgr port on a particular server is set to 31106. The

# second DMgr port runs on 31206, etc.

#

-W pctfederationpanelInstallWizardBean.port="31106"

Save and close resp.node.txt.

Run the following command to perform the installation and apply patches. You will need to modify this file for installations not going to /opt/et/WAS/6.0/a:

/opt/et/WAS/6.0/inst6.0.sh

Run the following command to install patches.

Note: If you are installing anywhere outside of the default /opt/et/WAS/6.0/a directory you must modify the patch response files to point to the proper install path. Edit all three patch response files in the opt/et/WAS/6.0 directory: patch602.txt, patch602sdk.txt, patchfp19.txt

Change the following line to point to the correct install directory:

-W product.location="/opt/et/WAS/6.0/a"

/opt/et/WAS/6.0/patch60.sh

Modifying the installation to run as non-root

While logged in as root, stop the WebSphere processes for this install.

Change ownership of all files in the install path to the functional id. I.e.:

chown -R etwas60a /opt/et/WAS/6.0/a

SU to the functional id and start the WebSphere processes.

Also on Fandom

Random wikia