Date Created: Fri 25-Feb-2011

Related Document Categories:





    Create a Deployment Manager and Single Node
    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

    ./manageprofiles.sh -create -profileName dmgr -profilePath /opt/IBM/WAS/AppServer/profiles/dmgr -templatePath /opt/IBM/WAS/AppServer/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.

    Creating a Node (node01)
    vi /etc/hosts

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

    ./manageprofiles.sh -create -profileName node01 -profilePath /opt/IBM/WAS/AppServer/profiles/node01 -templatePath /opt/IBM/WAS/AppServer/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 /opt/IBM/WAS/AppServer/profiles/node01/logs/AboutThisProfile.txt for more information about this profile.

    Note you can use: tail -f /opt/IBM/WAS/AppServer/logs/manageprofiles/node01_create.log to watch the profiles creation process

    Federating node01 to the dmgr

    1. Start the dmgr

    [/opt/IBM/WAS/AppServer/profiles/dmgr/bin/startManager.sh

    2. Check we can access it

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




    wasadmin/wasadmin


    ========

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

    cd /opt/IBM/WAS/AppServer/profiles/node01/bin

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

    Result

    ADMU0116I: Tool information is being logged in file
    /opt/IBM/WAS/AppServer/profiles/node01/logs/addNode.log
    ADMU0128I: Starting tool with the node01 profile
    CWPKI0308I: Adding signer alias "CN=l488pp054_pub, OU=Root Certi" to local
    keystore "ClientDefaultTrustStore" with the following SHA digest:
    38:D9:AA:FA:DD:7A:C4:89:96:C6:A7:8E:4F:10:85:83:BD:77:DC:14
    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:
    /opt/IBM/WAS/AppServer/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:
    5570814


    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.

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


    [/opt/IBM/WAS/AppServer/profiles/node01/bin] > ps -ef | grep -i websphere



    root 4587770 1 0 05:47:40 pts/1 0:36 /opt/IBM/WAS/AppServer/java/bin/java -Declipse.security -Dwas.status.socket=46728 -Dosgi.install.area=/opt/IBM/WAS/AppServer -Dosgi.configuration.area=/opt/IBM/WAS/AppServer/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:/opt/IBM/WAS/AppServer/java/jre/lib/ext/ibmorb.jar:/opt/IBM/WAS/AppServer/java/jre/lib/ext/ibmext.jar -classpath /opt/IBM/WAS/AppServer/profiles/dmgr/properties:/opt/IBM/WAS/AppServer/properties:/opt/IBM/WAS/AppServer/lib/startup.jar:/opt/IBM/WAS/AppServer/lib/bootstrap.jar:/opt/IBM/WAS/AppServer/lib/jsf-nls.jar:/opt/IBM/WAS/AppServer/lib/lmproxy.jar:/opt/IBM/WAS/AppServer/lib/urlprotocols.jar:/opt/IBM/WAS/AppServer/deploytool/itp/batchboot.jar:/opt/IBM/WAS/AppServer/deploytool/itp/batch2.jar:/opt/IBM/WAS/AppServer/java/lib/tools.jar -Dibm.websphere.internalClassAccessMode=allow -Xms50m -Xmx256m -Dws.ext.dirs=/opt/IBM/WAS/AppServer/java/lib:/opt/IBM/WAS/AppServer/profiles/dmgr/classes:/opt/IBM/WAS/AppServer/classes:/opt/IBM/WAS/AppServer/lib:/opt/IBM/WAS/AppServer/installedChannels:/opt/IBM/WAS/AppServer/lib/ext:/opt/IBM/WAS/AppServer/web/help:/opt/IBM/WAS/AppServer/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime -Dderby.system.home=/opt/IBM/WAS/AppServer/derby -Dcom.ibm.itp.location=/opt/IBM/WAS/AppServer/bin -Djava.util.logging.configureByServer=true -Duser.install.root=/opt/IBM/WAS/AppServer/profiles/dmgr -Djavax.management.builder.initial=com.ibm.ws.management.PlatformMBeanServerBuilder -Dwas.install.root=/opt/IBM/WAS/AppServer -Dpython.cachedir=/opt/IBM/WAS/AppServer/profiles/dmgr/temp/cachedir -Djava.util.logging.manager=com.ibm.ws.bootstrap.WsLogManager -Dserver.root=/opt/IBM/WAS/AppServer/profiles/dmgr -Dcom.ibm.security.jgss.debug=off -Dcom.ibm.security.krb5.Krb5Debug=off -Djava.security.auth.login.config=/opt/IBM/WAS/AppServer/profiles/dmgr/properties/wsjaas.conf -Djava.security.policy=/opt/IBM/WAS/AppServer/profiles/dmgr/properties/server.policy com.ibm.wsspi.bootstrap.WSPreLauncher -nosplash -application com.ibm.ws.bootstrap.WSLauncher com.ibm.ws.runtime.WsServer /opt/IBM/WAS/AppServer/profiles/dmgr/config cell01 dmgr dmgr


    root 5570814 1 0 05:55:24 pts/0 0:13 /opt/IBM/WAS/AppServer/java/bin/java -Declipse.security -Dwas.status.socket=56639 -Dosgi.install.area=/opt/IBM/WAS/AppServer -Dosgi.configuration.area=/opt/IBM/WAS/AppServer/profiles/node01/configuration -Dosgi.framework.extensions=com.ibm.cds,com.ibm.ws.eclipse.adaptors -Xshareclasses:name=webspherev70_%g,groupAccess,nonFatal -Xscmx50M -Xbootclasspath/p:/opt/IBM/WAS/AppServer/java/jre/lib/ext/ibmorb.jar:/opt/IBM/WAS/AppServer/java/jre/lib/ext/ibmext.jar -classpath /opt/IBM/WAS/AppServer/profiles/node01/properties:/opt/IBM/WAS/AppServer/properties:/opt/IBM/WAS/AppServer/lib/startup.jar:/opt/IBM/WAS/AppServer/lib/bootstrap.jar:/opt/IBM/WAS/AppServer/lib/jsf-nls.jar:/opt/IBM/WAS/AppServer/lib/lmproxy.jar:/opt/IBM/WAS/AppServer/lib/urlprotocols.jar:/opt/IBM/WAS/AppServer/deploytool/itp/batchboot.jar:/opt/IBM/WAS/AppServer/deploytool/itp/batch2.jar:/opt/IBM/WAS/AppServer/java/lib/tools.jar -Dibm.websphere.internalClassAccessMode=allow -Xms50m -Xmx256m -Dws.ext.dirs=/opt/IBM/WAS/AppServer/java/lib:/opt/IBM/WAS/AppServer/profiles/node01/classes:/opt/IBM/WAS/AppServer/classes:/opt/IBM/WAS/AppServer/lib:/opt/IBM/WAS/AppServer/installedChannels:/opt/IBM/WAS/AppServer/lib/ext:/opt/IBM/WAS/AppServer/web/help:/opt/IBM/WAS/AppServer/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime -Dderby.system.home=/opt/IBM/WAS/AppServer/derby -Dcom.ibm.itp.location=/opt/IBM/WAS/AppServer/bin -Djava.util.logging.configureByServer=true -Duser.install.root=/opt/IBM/WAS/AppServer/profiles/node01 -Djavax.management.builder.initial=com.ibm.ws.management.PlatformMBeanServerBuilder -Dwas.install.root=/opt/IBM/WAS/AppServer -Dpython.cachedir=/opt/IBM/WAS/AppServer/profiles/node01/temp/cachedir -Djava.util.logging.manager=com.ibm.ws.bootstrap.WsLogManager -Dserver.root=/opt/IBM/WAS/AppServer/profiles/node01 -Djava.awt.headless=true -Djava.security.auth.login.config=/opt/IBM/WAS/AppServer/profiles/node01/properties/wsjaas.conf -Djava.security.policy=/opt/IBM/WAS/AppServer/profiles/node01/properties/server.policy com.ibm.wsspi.bootstrap.WSPreLauncher -nosplash -application com.ibm.ws.bootstrap.WSLauncher com.ibm.ws.runtime.WsServer /opt/IBM/WAS/AppServer/profiles/node01/config cell01 node01 nodeagent

    4. Restart the dmgr

    /opt/IBM/WAS/AppServer/profiles/dmgr/bin/stopManager.sh

    you have to user wasadmin/wasadmin for password to stop, 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



    /opt/IBM/WAS/AppServer/profiles/dmgr/bin/startManager.sh

    5. stop and restart the node agent to proove 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 /opt/IBM/WAS/AppServer/bin'
    alias cdwbd='cd /opt/IBM/WAS/AppServer/profiles/dmgr/bin'
    alias cdwbn='cd /opt/IBM/WAS/AppServer/profiles/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.

Middleware Mentor - Steven Charles Robinson

About Me

Steve Robinson has been working in IT for over 15 years and has provided solutions for many large-enterprise corporate companies across the world. Steve specialises in Java and Middleware consulting. Steve comes from both an administration and development background.

Before moving to JEE, Steve was an accomplished developer and consultant for both IBM Lotus Notes and Microsoft .NET Technologies.

Follow Steve as @stevencrobinson on twitter.

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

WebSphere Categories

Oracle WebLogic Categories

JBoss Categories

Other Categories