WebLogic 12.1.2 Per Domain Nodemanger Command Line Arguments

Stepping out of any WebLogic admin training you will know that before WebLogic 12.1.2 we could start the node manager (NM) using its listen address and its port number as command-line arguments overwriting the settings in the nodemanager.properties file.

This is still possible, but doesn’t work OOTB for the per domain NM which was introduced in 12.1.2.

The reason is, that the start script in

DOMAIN_HOME/bin/startNodeManager.sh

is calling

WL_HOME/server/bin/startNodemanager.sh

The script located in WL_HOME is still okay, but the one in DOMAIN_HOME doesn’t forward the command-line parameters. So if you just want to be able to run it as before, then replace

${WL_HOME}/server/bin/startNodeManager.sh

with

${WL_HOME}/server/bin/startNodeManager.sh ${1} ${2}

in the startNodeManager.sh in DOMAIN_HOME/bin.

Have a great day!

ps. Are you observing this 12.1.2 NM bug? Let me know if you don’t.

Comments

  1. Jens Schipkowski says:

    Hi Frank,

    Your solution is good and works great, but our management refuses to modify generated scripts. So I created a script which sets the variables LISTEN_PORT and LISTEN_ADDRESS which are used in ${WL_HOME}/server/bin/startNodeManager.sh.

    #!/bin/sh

    export DOMAIN_HOME=/my/domain/home
    export LISTEN_PORT=5556
    export LISTEN_ADDRESS=`/sbin/ifconfig eth0 | grep ‘inet addr:’ | cut -d: -f2 | awk ‘{ print $1}’`
    ${DOMAIN_HOME}/bin/startNodeManager.sh $*

    Regards,
    Jens

  2. Hi Dr. Munz,

    I am not sure if this is the right place to ask my weblogic scalability question.

    We are running Weblogic 10.3.6 for years on production environment. There are 10 managed servers running at the same time by processing 20K active users.
    I am creating another managed server where transactions processing will be expanding 2 – 3 folds in 6 months in terms of transaction volumes and the end

    user traffic to our most web applications.
    Currently we have a weblogic clusters for each managed servers with 2 nodes.
    What is the best practice approach to be able to scale up (or out) without losing throughputs and processing power.
    I would like to get feedback on scalability architecture.

    1) Should I create another Weblogic domain to be able to route the new traffics to the new managed server to allow scalability?
    2) or should I create another managed server (3rd node) and create that managed server on the 3rd server.

    The new managed server will be expanding more than other 10 managed servers in the next 6 month. What are the pros and cons for the 2 mentioned approaches

    or is there any other way I can scale up or out my environment?

    Thanks in advance,
    Aren

Speak Your Mind

*