Presented at Impact 2013, “Build and Administer Your Own Liberty Application Cluster” takes you through setting up a collective, configuring a cluster, and executing administrative actions using Jython scripting.

The lab takes approximately 1.5 hours to complete, and guides you through each step. At the end of the lab, you will have configured a highly available Liberty collective and deployed applications into a Liberty cluster using the sample scripts available in the repository.

Liberty profile Network Deployment can be downloaded as a trial if you do not already have a WebSphere license.

Lab instructions:

Lab materials:

9 Comments on "Lab: Build and Administer Your Own Liberty Application Cluster"

  1. I made it to step 2.7, adding the member and I get an error:

    bin\collective join member1 –host=localhost –port=9443 –user=admin –password=adminpwd –keystorePassword=member1
    Joining the collective with target controller localhost:9443…
    This may take a while.

    Aborting join collective.

    The specified port 9443 could not be reached. Confirm the port is correct.

    I made sure that the controller was running. I also checked netstat -na found that something is listening on the port.

    Any ideas?

  2. Does Liberty Profile ND support Java EE 7 feature?

  3. Hi, I tried to run the script but there is an error occur: “from restConnector import JMXRESTConnector
    ImportError: No module named restConnector

    I already set up the environment:”# export CLASSPATH=$WLP_INSTALL_DIR/clients/restConnector.jar
    # export JYTHONPATH=$WLP_INSTALL_DIR/clients/jython/:

    and I donot know why and can someone help me with this?

  4. Hi all, thanks for the lab.

    For all stop/start // Server/Custer python script I got an error 30
    I read it’s mean the Java version is not correct… is that right?

    #jython ./ – –serverUsrdir=/opt/wlp/usr –serverName=member1 –host=localhost –port=9443 –user=admin –password=adminpwd –truststore=/opt/wlp/usr/servers/controller1/resources/security/trust.jks –truststorePassword=password –debug

    Connecting to the server…
    Successfully connected to the server “localhost:9443″
    stdErr= None
    stdOut= None
    returnCode= 30
    Server did not stop: return code = 30

    However I use java 1.7 (I got the same error with 1.6)

    #java -version
    java version “1.7.0”
    Java(TM) SE Runtime Environment (build pxi3270sr1ifix-20120419_02(SR1+IV19490+IV19661))
    IBM J9 VM (build 2.6, JRE 1.7.0 Linux x86-32 20120322_106209 (JIT enabled, AOT enabled)

    #tail /opt/wlp/usr/servers/member1/logs/console.log
    Launching member1 (WebSphere Application Server on IBM J9 VM, version pxi32forks-20120419_01 (SR1+IV19490+IV19661) (en_US)

    Thanks for your help

    • I found the origin of the problem. It come from my system config. For unknown reason the controller use the java command defined by “alternatives” to communicate with members, not the java defined in the PATH or in java_home… That’s weird, but the problem doesn’t come from the lab or the script…

      After deleting the old java 1.4 I get a “java not found” error as a return from the java server….

  5. Return code 2 from the stopServer script means the server cannot be
    found. Your member might be registered with the real host name. Please try again with –serverHost=.

  6. Dave Westerman July 26, 2013

    Should this lab work on Windows 7? I think I’ve translated everything correctly between Linux and Windows, but I’m getting the following error, when I try to start or stop a server (those are the only two commands I’ve tried so far):

    C:IBMWLPND855>jython –serverHost=localhost –serverUsrdir=%WLP_INSTALL_DIR%usr –serverName=myMember1 –host=localhost –port=9443 –user=admin –password=adminpswd –truststore=usrserversmyControllerresourcessecuritytrust.jks –truststorePassword=password
    Connecting to the server…
    Successfully connected to the server “localhost:9443″
    Server did not stop: return code = 2

    Is there some trace I can turn on to see some details about what might be going wrong?

    And yes, the server is running when I try to stop it, and not running when I try to start it.

Join The Discussion

Your email address will not be published. Required fields are marked *