Date Created: Tue 29-Mar-2011

Get my WebSphere Application Server course here >> http://www.themiddlewareshop.com/products/



    Installing WebSphere in AIX silently (Automatically)

    This document will show you how to install WebSphere binaries using configuration files and simplified response files.

    Binaries are installed:

    /<path>/installers/ND/WAS

    We are going to install WAS 7 ND on AIX. We have two choices,

    1. All node profiles and the deployment manager profile will share the same binaries
    - This method means if you upgrade the binaries all profiles are upgraded.
    2. The deployment manager and nodes will each have their own installation binaries
    - This method means if you can upgrade the dmgr and nodes individually

    I am using option 1 below as an example:

    You can see sample template called Create a file called responsefile.nd.txt within the WAS installation folder.

    I created a new file called responsefile.nd7.txt and copid in the following values

    -OPT silentInstallLicenseAcceptance="true"
    -OPT disableOSPrereqChecking="true"
    -OPT installType="installNew"
    -OPT feature="noFeature"
    -OPT installLocation="/var/apps/was7nd
    -OPT profileType="none"
    -OPT traceLevel=INFO

    Notice I have not included any profiles. I will use manageprofiles.sh to do this later.

    Run the following command

    ./install -options "/<responsefile.path>/responsefile.nd.txt" -silent

    For example:

    ./install -options "/home/u0008521/installers/ND/WAS/responsefile.nd7.txt" -silent

    =======================

    Example of domains I used in my example:

    172.29.151.189 dmgr.testnd.com
    172.29.151.189 node01.testnd.com
    172.29.151.189 node02.testnd.com

    How to Create a Deployment Manager profile and Single Node profile using the command line.

    Note: The manageprofiles.sh command on AIX doesn't like hostnames, you need to use a FQDN ie hostname.domain.com. In this example we presume you have already installed the binaries in /opt/IBM/WAS/AppSerer

    We will do this example logged in a root on AIX through a Putty session.

    Creating the Deployment Manager Profile (dmgr)
    vi /etc/hosts

    <ipaddress> dmgr.testnd.com

    Run the following command from the WebSphere installation root bin folder e.g /var/apps/was7nd/bin

    ./manageprofiles.sh -create -profileName dmgr -profilePath /var/apps/was7nd/profiles/dmgr -templatePath /var/apps/was7nd/profileTemplates/dmgr -cellName cell01 -hostName dmgr.testnd.com -nodeName dmgr -isDefault -enableAdminSecurity true -adminUserName wasadmin -adminPassword wasadmin

    Result:
    CWMBU0002I: The deployment manager profile template has been deprecated and replaced by the management profile template with a deployment manager server.
    INSTCONFSUCCESS: Success: Profile dmgr now exists. Please consult /opt/IBM/WAS/AppServer/profiles/logs/AboutThisProfile.txt for more information about this profile.

    You can tail logs in: /var/apps/was7nd/logs/manageprofiles/

    tail -f dmgr_create.log

    Creating a Node (node01)
    vi /etc/hosts

    <ipaddress> dmgr.testnd.com node01.testnd.com

    ./manageprofiles.sh -create -profileName node01 -profilePath /var/apps/was7nd/profiles/node01 -templatePath /var/apps/was7nd/profileTemplates/managed -cellName node01 -hostName node01.testnd.com -nodeName node01 -enableAdminSecurity true -adminUserName wasadmin -adminPassword wasadmin

    Result:
    INSTCONFSUCCESS: Success: Profile node01 now exists. Please consult /var/apps/was7nd/profiles/node01/logs/AboutThisProfile.txt for more information about this profile.

    Note you can use: tail -f /var/apps/was7nd/logs/manageprofiles/node01_create.log to watch the profiles creation process

    Federating node01 to the dmgr

    1. Start the dmgr

    [/var/apps/was7nd/profiles/dmgr/bin/startManager.sh

    l488pp029_pub[/var/apps/was7nd] > /var/apps/was7nd/profiles/dmgr/bin/startManager.sh
    ADMU0116I: Tool information is being logged in file
    /var/apps/was7nd/profiles/dmgr/logs/dmgr/startServer.log
    ADMU0128I: Starting tool with the dmgr profile
    ADMU3100I: Reading configuration for server: dmgr
    ADMU3200I: Server launched. Waiting for initialization status.
    ADMU3000I: Server dmgr open for e-business; process id is 5832912

    2. Check we can access it

    http://<FQDNs>:9060/ibm/console

    https://dmgr.testnd.com:9043/ibm/console/logon.jsp

    wasadmin/wasadmin




    ========

    3. Add node 01 by using the addNode.sh command

    cd /var/apps/was7nd/profiles/node01/bin

    ./addNode.sh dmgr.testnd.com 8879 -conntype soap -profileName node01 -username wasadmin -password wasadmin

    Result

    l488pp029_pub[/var/apps/was7nd/profiles/node01/bin] > ./addNode.sh dmgr.testnd.com 8879 -conntype soap -profileName node01 -username wasadmin -password wasadmin
    ADMU0116I: Tool information is being logged in file
    /var/apps/was7nd/profiles/node01/logs/addNode.log
    ADMU0128I: Starting tool with the node01 profile
    CWPKI0308I: Adding signer alias "CN=l488pp029_pub, OU=Root Certi" to local
    keystore "ClientDefaultTrustStore" with the following SHA digest:
    13:2A:62:4F:3E:D9:28:36:80:35:C1:B2:8E:39:9C:F5:D8:CA:33:A8
    CWPKI0308I: Adding signer alias "datapower" to local keystore
    "ClientDefaultTrustStore" with the following SHA digest:
    A9:BA:A4:B5:BC:26:2F:5D:2A:80:93:CA:BA:F4:31:05:F2:54:14:17
    ADMU0001I: Begin federation of node node01 with Deployment Manager at
    dmgr.testnd.com:8879.
    ADMU0009I: Successfully connected to Deployment Manager Server:
    dmgr.testnd.com:8879
    ADMU0507I: No servers found in configuration under:
    /var/apps/was7nd/profiles/node01/config/cells/node01/nodes/node01/servers
    ADMU2010I: Stopping all server processes for node node01
    ADMU0024I: Deleting the old backup directory.
    ADMU0015I: Backing up the original cell repository.
    ADMU0012I: Creating Node Agent configuration for node: node01
    ADMU0014I: Adding node node01 configuration to cell: cell01
    ADMU0016I: Synchronizing configuration between node and cell.
    ADMU0018I: Launching Node Agent process for node: node01
    ADMU0020I: Reading configuration for Node Agent process: nodeagent
    ADMU0022I: Node Agent launched. Waiting for initialization status.
    ADMU0030I: Node Agent initialization completed successfully. Process id is:
    5439796


    ADMU0300I: The node node01 was successfully added to the cell01 cell.


    ADMU0306I: Note:
    ADMU0302I: Any cell-level documents from the standalone cell01 configuration
    have not been migrated to the new cell.
    ADMU0307I: You might want to:
    ADMU0303I: Update the configuration on the cell01 Deployment Manager with
    values from the old cell-level documents.


    ADMU0306I: Note:
    ADMU0304I: Because -includeapps was not specified, applications installed on
    the standalone node were not installed on the new cell.
    ADMU0307I: You might want to:
    ADMU0305I: Install applications onto the cell01 cell using wsadmin $AdminApp or
    the Administrative Console.


    ADMU0003I: Node node01 has been successfully federated.

    ==============================


    ps -ef | grep -i websphere | grep -v grep

    l488pp029_pub[/var/apps/was7nd/bin] > ps -ef | grep -i websphere | grep -v grep
    root 5832912 1 0 15:42:18 pts/1 0:38 /var/apps/was7nd/java/bin/java -Declipse.security -Dwas.status.socket=41731 -Dosgi.install.area=/var/apps/was7nd -Dosgi.configuration.area=/var/apps/was7nd/profiles/dmgr/configuration -Djava.awt.headless=true -Dosgi.framework.extensions=com.ibm.cds,com.ibm.ws.eclipse.adaptors -Xshareclasses:name=webspherev70_%g,groupAccess,nonFatal -Xscmx50M -Xbootclasspath/p:/var/apps/was7nd/java/jre/lib/ext/ibmorb.jar:/var/apps/was7nd/java/jre/lib/ext/ibmext.jar -classpath /var/apps/was7nd/profiles/dmgr/properties:/var/apps/was7nd/properties:/var/apps/was7nd/lib/startup.jar:/var/apps/was7nd/lib/bootstrap.jar:/var/apps/was7nd/lib/jsf-nls.jar:/var/apps/was7nd/lib/lmproxy.jar:/var/apps/was7nd/lib/urlprotocols.jar:/var/apps/was7nd/deploytool/itp/batchboot.jar:/var/apps/was7nd/deploytool/itp/batch2.jar:/var/apps/was7nd/java/lib/tools.jar -Dibm.websphere.internalClassAccessMode=allow -Xms50m -Xmx256m -Dws.ext.dirs=/var/apps/was7nd/java/lib:/var/apps/was7nd/profiles/dmgr/classes:/var/apps/was7nd/classes:/var/apps/was7nd/lib:/var/apps/was7nd/installedChannels:/var/apps/was7nd/lib/ext:/var/apps/was7nd/web/help:/var/apps/was7nd/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime -Dderby.system.home=/var/apps/was7nd/derby -Dcom.ibm.itp.location=/var/apps/was7nd/bin -Djava.util.logging.configureByServer=true -Duser.install.root=/var/apps/was7nd/profiles/dmgr -Djavax.management.builder.initial=com.ibm.ws.management.PlatformMBeanServerBuilder -Dwas.install.root=/var/apps/was7nd -Dpython.cachedir=/var/apps/was7nd/profiles/dmgr/temp/cachedir -Djava.util.logging.manager=com.ibm.ws.bootstrap.WsLogManager -Dserver.root=/var/apps/was7nd/profiles/dmgr -Dcom.ibm.security.jgss.debug=off -Dcom.ibm.security.krb5.Krb5Debug=off -Djava.security.auth.login.config=/var/apps/was7nd/profiles/dmgr/properties/wsjaas.conf -Djava.security.policy=/var/apps/was7nd/profiles/dmgr/properties/server.policy com.ibm.wsspi.bootstrap.WSPreLauncher -nosplash -application com.ibm.ws.bootstrap.WSLauncher com.ibm.ws.runtime.WsServer /var/apps/was7nd/profiles/dmgr/config cell01 dmgr dmgr
    root 5439796 1 0 15:51:25 pts/1 0:13 /var/apps/was7nd/java/bin/java -Declipse.security -Dwas.status.socket=53940 -Dosgi.install.area=/var/apps/was7nd -Dosgi.configuration.area=/var/apps/was7nd/profiles/node01/configuration -Dosgi.framework.extensions=com.ibm.cds,com.ibm.ws.eclipse.adaptors -Xshareclasses:name=webspherev70_%g,groupAccess,nonFatal -Xscmx50M -Xbootclasspath/p:/var/apps/was7nd/java/jre/lib/ext/ibmorb.jar:/var/apps/was7nd/java/jre/lib/ext/ibmext.jar -classpath /var/apps/was7nd/profiles/node01/properties:/var/apps/was7nd/properties:/var/apps/was7nd/lib/startup.jar:/var/apps/was7nd/lib/bootstrap.jar:/var/apps/was7nd/lib/jsf-nls.jar:/var/apps/was7nd/lib/lmproxy.jar:/var/apps/was7nd/lib/urlprotocols.jar:/var/apps/was7nd/deploytool/itp/batchboot.jar:/var/apps/was7nd/deploytool/itp/batch2.jar:/var/apps/was7nd/java/lib/tools.jar -Dibm.websphere.internalClassAccessMode=allow -Xms50m -Xmx256m -Dws.ext.dirs=/var/apps/was7nd/java/lib:/var/apps/was7nd/profiles/node01/classes:/var/apps/was7nd/classes:/var/apps/was7nd/lib:/var/apps/was7nd/installedChannels:/var/apps/was7nd/lib/ext:/var/apps/was7nd/web/help:/var/apps/was7nd/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime -Dderby.system.home=/var/apps/was7nd/derby -Dcom.ibm.itp.location=/var/apps/was7nd/bin -Djava.util.logging.configureByServer=true -Duser.install.root=/var/apps/was7nd/profiles/node01 -Djavax.management.builder.initial=com.ibm.ws.management.PlatformMBeanServerBuilder -Dwas.install.root=/var/apps/was7nd -Dpython.cachedir=/var/apps/was7nd/profiles/node01/temp/cachedir -Djava.util.logging.manager=com.ibm.ws.bootstrap.WsLogManager -Dserver.root=/var/apps/was7nd/profiles/node01 -Djava.awt.headless=true -Djava.security.auth.login.config=/var/apps/was7nd/profiles/node01/properties/wsjaas.conf -Djava.security.policy=/var/apps/was7nd/profiles/node01/properties/server.policy com.ibm.wsspi.bootstrap.WSPreLauncher -nosplash -application com.ibm.ws.bootstrap.WSLauncher com.ibm.ws.runtime.WsServer /var/apps/was7nd/profiles/node01/config cell01 node01 nodeagent



    4. Restart the dmgr

    /var/apps/was7nd/profiles/dmgr/bin/stopManager.sh -username wasadmin -password wasadmin

    you have to user wasadmin/wasadmin for password to stop, or we can change this by editing soap.client.props for each profile ie dmgr/node01



    #------------------------------------------------------------------------------
    # SOAP Client Security Enablement
    # - security enabled status ( false[default], true )
    #------------------------------------------------------------------------------
    com.ibm.SOAP.securityEnabled=true

    #------------------------------------------------------------------------------
    # - authenticationTarget ( BasicAuth[default], KRB5. These are the only supported selection
    # on a pure client for JMX SOAP Connector Client. )
    #------------------------------------------------------------------------------
    com.ibm.SOAP.authenticationTarget=BasicAuth

    com.ibm.SOAP.loginUserid=wasadmin
    com.ibm.SOAP.loginPassword=wasadmin


    /var/apps/was7nd/profiles/dmgr/bin/startManager.sh

    5. stop and restart the node agent to prove it is ok to a restart

    /opt/IBM/WAS/AppServer/profiles/node01/bin/stopNode.sh
    /opt/IBM/WAS/AppServer/profiles/node01/bin/startNode.sh

    ======================

    I would recommend that you create aliases in ksh.rc etc

    for example

    alias cdwb='cd /var/apps/was7nd/bin'
    alias cdwbd='cd /var/apps/was7nd/profiles/dmgr/bin'
    alias cdwbn='cd /var/apps/was7nd/node01/bin'




    Create a Cluster












    Next, then finish

    Comments
    You can also add other servers to the cluster of you want two servers in the cluster. You can test a cluster with one single server if all you are testing is cluster JNDI scopes

    If you wish to test HA then you need another server (member=clone) added to the cluster, just edit the cluster and add another member.

    Get my WebSphere Application Server course here >> http://www.themiddlewareshop.com/products/


Steve Robinson - IBM Champion 2013

About Me

Steve Robinson has been working in IT for over 20 years and has provided solutions for many leading brands around the world. Steve specialises in JEE, DevOps and Thought Leadership.

In January 2013, I was awarded the prestigous 'IBM Champion' accolade.


Read my books?

IBM WebSphere Application Server 8.0 Administration Guide

IBM WebSphere Application Server 8.0 Administration Guide

WebSphere Application Server 7.0 Administration Guide

WebSphere Application Server 7.0 Administration Guide

Courses

Articles

WebSphere Categories

Other Categories