Node agent cannot start

Any update

This is websphere nodeagent issue. Can someone tell me hwo can reslvoe this issue

Thanks
Sudhakar

Node agent logs while starting. Pasted below

Caused by: org.omg.CORBA.COMM_FAILURE: CAUGHT_EXCEPTION_WHILE_CONFIGURING_SSL_CLIENT_SOCKET: JSSL0080E: javax.net.ssl.SSLHandshakeException - The client and server could not negotiate the desired level of security.  Reason: com.ibm.jsse2.util.h: No trusted certificate found  vmcid: 0x49421000  minor code: 70  completed: No
        at com.ibm.ws.security.orbssl.WSSSLClientSocketFactoryImpl.createSSLSocket(WSSSLClientSocketFactoryImpl.java:504)

What is in the startServer.log in the nodeagent directory?

For example, on my machine, the logs directory is:

C:\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\nodeagent

If you open a command prompt to the profiles\<profileName>\bin, e.g.,

cd C:\IBM\WebSphere\AppServer\profiles\AppSrv01\bin

and execute:

serverStatus -all

or for a Unix type of system:

./serverStatus.sh -all

What does it show as the nodeagent status?

ooh, I missed your exception information...  looking.

C:\IBM\WebSphere\AppServer\profiles\AppSrv01\bin>wsadmin -lang jython -conntype none
WASX7357I: By request, this scripting client is not connected to any server process. Certain configuration and application operations will be available in local mode.
WASX7031I: For help, enter: "print Help.help()"
wsadmin>print Help.message( 'JSSL0080E' )
Explanation: The client and server could not negotiate the desired level of security. The connection is no longer usable.
 User action: Ensure that the trust store of the server has the signer certificate from the client.
----------------------------------------------------------------------

So, it looks like the server trust store doesn't have the appropriate signer certificate for the partner.

Here is a good article about SSL, certs, and trust store files by someone who really knows this stuff.  I got a chance to hear Keys Botzum (yes, that really is his name) last week in Las Vegas at Impact 2008.

http://www.ibm.com/developerworks/websphere/techjournal/0612_birk/0612_birk.html

another alternative is that the partners couldn't agree on an appropriate security level (e.g., client request indicates support for security types A, B, and C; but server [i.e., nodeagent] only supports security types X, Y, and Z)

The issue is already resloved. Anyway thanks for replying.  You guys doing great job

I will update if i get any other issue

Thanks
Sudhakar

Oh, that's the great news.

What was the solution?

its resloved by disabling some security.

Thanks
Sudhakar

Can you please look into issue below. We are unable to synchronization node agent

4/21/08 11:57:45:987 EDT] 00000096 NodeSync      E   ADMS0012E: The system is unable to create an administrative client connection: com.ibm.websphere.management.exception.AdminException: Admin client connection to deployment manager is unavailable; nodeagent has not discovered the dmgr
        at com.ibm.ws.management.sync.NodeSync.getAdminClient(NodeSync.java:470)
        at com.ibm.ws.management.sync.NodeSync.getCellRepositoryEpoch(NodeSync.java:345)
        at com.ibm.ws.management.sync.NodeSyncTask.doSync(NodeSyncTask.java:230)
        at com.ibm.ws.management.sync.NodeSyncTask.run(NodeSyncTask.java:150)
        at java.lang.Thread.run(Thread.java:797)


Thanks
Sudhakar

Have you verified that your Deployment Manager (DM) is active?
Do you have a firewall between your nodeagent and your DM?
What is the network like between your nodeagent and your DM?
Can you display the administrative console?

Cannot start node agent

Caused by: org.omg.CORBA.COMM_FAILURE: CAUGHT_EXCEPTION_WHILE_CONFIGURING_SSL_CLIENT_SOCKET: JSSL0080E: javax.net.ssl.SSLHandshakeException - The client and server could not negotiate the desired level of security.  Reason: com.ibm.jsse2.util.h: No trusted certificate found  vmcid: 0x49421000  minor code: 70  completed: No
        at com.ibm.ws.security.orbssl.WSSSLClientSocketFactoryImpl.createSSLSocket(WSSSLClientSocketFactoryImpl.java:504)
        at com.ibm.ws.orbimpl.transport.WSSSLTransportConnection.createSocket(WSSSLTransportConnection.java:227)
        at com.ibm.ws.orbimpl.transport.WSSSLTransportConnection.createSocket(WSSSLTransportConnection.java:303)
        at com.ibm.CORBA.transport.TransportConnectionBase.connect(TransportConnectionBase.java:356)
        at com.ibm.ws.orbimpl.transport.WSTransport$1.run(WSTransport.java:489)
        at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118)
        at com.ibm.ws.orbimpl.transport.WSTransport.getConnection(WSTransport.java:486)
        at com.ibm.CORBA.transport.TransportBase.getConnection(TransportBase.java:163)
        at com.ibm.rmi.iiop.TransportManager.get(TransportManager.java:93)
        at com.ibm.rmi.iiop.GIOPImpl.getConnection(GIOPImpl.java:115)
        at com.ibm.rmi.iiop.GIOPImpl.locate(GIOPImpl.java:189)
        at com.ibm.rmi.corba.ClientDelegate.locate(ClientDelegate.java:1904)
        at com.ibm.rmi.corba.ClientDelegate._createRequest(ClientDelegate.java:1929)
        at com.ibm.rmi.corba.ClientDelegate.createRequest(ClientDelegate.java:1208)
        at com.ibm.CORBA.iiop.ClientDelegate.createRequest(ClientDelegate.java:1287)
        at com.ibm.rmi.corba.ClientDelegate.createRequest(ClientDelegate.java:1141)
        at com.ibm.CORBA.iiop.ClientDelegate.createRequest(ClientDelegate.java:1253)
        at com.ibm.rmi.corba.ClientDelegate.request(ClientDelegate.java:1807)
        at com.ibm.CORBA.iiop.ClientDelegate.request(ClientDelegate.java:1209)
        at org.omg.CORBA.portable.ObjectImpl._request(ObjectImpl.java:458)
        at com.ibm.WsnOptimizedNaming._NamingContextStub.resolve_complete_info(_NamingContextStub.java:488)
        at com.ibm.ws.naming.jndicos.CNContextImpl.cosResolve(CNContextImpl.java:4351)
        at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1901)

Again you have a certificate issue.  Please see my note from above:

https://www.experts-exchange.com/questions/23327456/Node-agent-cannot-start.html?anchorAnswerId=21390701#a21390701

I am very new to Websphere.  Can some one tell me what is right option  to our environment like us


We have only 5-10 developer who will be using the websphere for java deployment.  We have only linux server where i have to install the websphere application 6.1 server.   Can someone please  tell me right choice e for install for small client like us from following options

(1)  Websphere Standalone application server
(2) Websphere network deployment

Thanks
Sudhakar

Unfortunately, the right answer is "it depends".  :-)

It depends upon what you, and your developers are trying to do, and how you are trying to use th e product.

I presume that your developers are interested in developing web applications for your production environment.  If that is the case, then a big question is:

Do you have the Rational Application Developer (RAD) product?
This is an Eclipse development environment that allows a developer to write, and test their web applications, and package them in such a way as to make them easy to deploy onto a production Application Server.

If not, you might want to consider getting the "open source" Eclipse integrated development environment for them to use.  It doesn't have all the "bells and whistles" as the RAD product, but it is similar.

A Network Deployment machine (also known as a Deployment Manager) is a specialized Application Server that is to be used to manage/administer a collection of application Servers.  If application servers are "identical" (i.e., have all of the same applications deployed onto them), then they are cluster members, and the administrator is able to configure session failover should one of the application servers become unavailable in the middle of a session.  End users might see a slight delay while the session is being "moved" from an inactive cluster member to the backup cluster member, but nothing would be lost.  It all depends upon the speed of your machines, and the configuration choices that you have made.

For a simple (small) production environment, you may not want, or need multiple application servers.  I don't know.  Again, it depends upon your requirements.

This is a huge topic, and requires quite a bit of information/education.

I suggest that you take some time to look into information that is available from the IBM "RedBooks" site (http://www.redbooks.IBM.com).  For example:

WebSphere Application Server V6.1: Planning and Design
http://www.redbooks.ibm.com/abstracts/sg247305.html?Open

WebSphere Application Server V6.1: Technical Overview
http://www.redbooks.ibm.com/abstracts/redp4191.html?Open

IBM WebSphere Application Server V6.1 Security Handbook
http://www.redbooks.ibm.com/abstracts/sg246316.html?Open

Hopefully this helps you some.

Our production server is clusterd and its maintained by IBM.  and i was just asking about the development environment where we have only one single server to install and used by 6 to 10 people.  MY only question is do we really need Websphere network deployment  or we can go ahead and install Websphere Standalone application server.

Thanks
Sudhakar

Ah, just install the Application Server, and set up some scripts that you (or the developers) can use to deploy/remove the applications being tested.

I can see no reason for you to have ND installed for this type of simple environment, unless you will be developing specific "clustered" applications that need to be tested as far as session replication, and session affinity is required.

With standalone applicatione server will i have all the features like network deployment for adminstration from console?  I dont want to fight from back end at server side apart from console

Thanks
Sudhakar

You won't have network deployment (ND), but you won't need it because of only having one application server.  Network Deployment enables more advanced topologies that provide workload management, scalability, high availability, and central management of multiple application servers.

In a single server (i.e., stand-alone application server) environment, the administrative console application is deployed on the application server, and is used to administer resources on the application server.  However, there are things that you can't do for this application server using the single-server administrative console.  For example, you can't stop and start the application server.

  In an ND environment, you have the ND application server, which is a "special" application server on which the administrative console and other ND related functions exist.  User applications are not executed on this application server.

  On each of the "nodes" (machines) in the Application Server "cell" there is also a nodeagent application server, which is also a specialized application server on which user applications do not execute.  The (ND) Administrative console interacts with the nodeagent application to manage the resources within the cell (e.g., application servers, applications, datasources, etc.)

  Hopefully this helps your understanding, and answers your questions.

Hello Thanks for all your help. I just started the installation and lauched the lauched pad but when i chick on (Lauch the installation wizard for webshpere Application  Server) its just hangs and i am getting second page. what could be the reason

Thanks

On what kind of operating system are you doing the installation?

Are you directly connected to the "console" (i.e., the main display/screen) at the target computer, or are you remotely connected (e.g., using telnet/ssh/PUtty)?

i am using Real vnc and its remote desktop

Thanks
Sudhakar

To what kind of machine?  Windows, or a *nix type operating system?  Exactly which kind & version?

I am installing on Redhat linux 4ES and i am doing Real Vnc connect from windows to linux desktop and trying to install. I am able to get mozilla first page but when i click on Lauch the installation wizard for webshpere Application) and its just hangs

Thanks
Sudhakar

Look in the /tmp directory for a file created about the time that you tried starting the installation.  I believe that the file might be called install.log or something similar.  What messages does it contain?

I dont have file like that. I am just at first page of install. Can you please let me know what i need to check before i install the websphere in Redhat linux 4 ES.  

Thanks
Sudhakar

ok, if it doesn't get that far, I need you to open a command prompt, and "cd" to the installation image directory.  For example, if you have a CD, and have it mounted at something like

/mnt/cdrom

then you can

cd /mnt/cdrom

Then, I need you to:

find . -type f -name java -print -exec file {} \;

and provide the output here.

Here the output

/JDK/jre.pak/repository/package.java.jre/java/jre/bin/java
./JDK/jre.pak/repository/package.java.jre/java/jre/bin/java: ELF 64-bit LSB executable, AMD x86-64, version 1 (SYSV), for GNU/Linux 2.4.0, dynamically linked (uses shared libs), not stripped

What kind of hardware are you using?

Intel (I hope)...

What's the output from:

file `which which`

Yes its intel dell poweredge server. I am not getting your second question

well if you execute the command

file `which which`

The "which which" (surrounded by back tics - the character on my keyboard on the key beside the '1'), causes this command to be executed, and the result returned to be used in the reset of the expression.

In this case, it (the which command) should provide the fully qualified path to an executable file that exists on your machine.  If you type "which which" at a command prompt, I would expect the result (output) to be something like:

/usr/bin/which

So, when I execute:

file `which which`

I see:

/usr/bin/which: ELF 64-bit LSB executable, AMD x86-64, version 1 (SYSV), for GNU/Linux 2.6.4, dynamically linked (uses shared libs), for GNU/Linux 2.6.4, stripped

which tells me the kind of hardware being used by existing executables.

If your output differs from what you saw when you executed the find command,
it would indicate that the WebSphere installation image that you have is for a different kind of machine than you are using.

If this is the case, you would need a different installation image (i.e., one for the kind of hardware that you have).

Hopefully that make sense.  If not, let me know.

This is resloved after uninstalling sun java and installing iBM java under root user.  Thanks all who all suppported me

Thanks
Sudhakar

I installed standalone websphere application and i have created the profile called atlas_dev. The default  Websphere application server is server1. Can i create multiple server instances like server1 , server2 .. under same profile. ??

Thanks
Sudhakar

Interesting work-around/solution.  Thanks for sharing.

Yes, you can create multiple Application Server profiles.
Since the question is related to a nodeagent, that implies that you have a network deployment (or deployment manager) package.

If you want additional servers on an existing (managed) node/machine:

From the Administrative Console
- Select/Expand the "Servers" section
- Select the "Application Servers" entry
- Click the "New" button to initiate the creation process

If you want to create a server on a new machine, you have to install product, and during the profile creation, specify that you want a "stand-alone" application server.

Once the new server is created, you can use the addNode command to federate it to the existing deployment manager cell.

Here is the documentation for the addNode command:

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/rxml_addnode.html

I dont see below option as i installed standalone application server, so i cant installed additional instance apart from server1 instance?
Please let me know if anyway we can create  additional servers apart server1(default) server
From the Administrative Console
- Select/Expand the "Servers" section
- Select the "Application Servers" entry
- Click the "New" button to initiate the creation process

Thanks
Sudhakar

Ah, since you installed the stand alone server, and not the deployment manager, you need to create a profile using one of the options documented here:

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/tpro_profiles.html

Fomr below command i created additional profile
root@164118-web3 bin]# ./manageprofiles.sh -create -profileName atlas_dev -profilePath /mnt/drive1/IBM/WebSphere/AppServer/profiles/atlas_dev -templatePath /mnt/drive1/IBM/WebSphere/AppServer/profileTemplates/default -nodeName 164118-web3Node01   -cellName 164118-web3Node01Cell -hostName 164118-web3.proxicom.com

Now i have two profiles AppSrv01 and atlas_dev. I started both of them using following command

./startServer.sh server1 -username admin -password admin
./startServer.sh server1 -profileName atlas_dev

I am able to see AppSrv01 server instance(server1) from console but i dont see atlas_dev apps server instance on the console. Can you tell me what is the use of creating additional profiles(atlas_dev) when i cant see the servers from console

Thanks
Sudhakar

Can someone update this please

Exactly.

"am able to see AppSrv01 server instance(server1) from console but i dont see atlas_dev..."

That is because you are using a stand-alone profile, and not the deployment manager/network deployment profile.

A stand-alone application server does not know anything about any other application server.

To manage that other (i.e., atlas_dev), you need to either:

- use scripting (wsadmin), or
- an adminstration console deployed onto that other (unmanaged) appServer

What profile directories exist under your WebSphere/AppServer/profiles directory?

Looking on mine, I see:
--------------------------------------------------------------------------------
C:\IBM\WebSphere\AppServer\profiles>dir
...
 Directory of C:\IBM\WebSphere\AppServer\profiles

09/24/2007  09:09 AM    <DIR>          .
09/24/2007  09:09 AM    <DIR>          ..
11/26/2007  05:04 PM    <DIR>          AppSrv01
08/09/2007  05:21 PM    <DIR>          AppSrv02
09/24/2007  03:53 PM    <DIR>          Dmgr01
--------------------------------------------------------------------------------

I can "cd" into the AppSrv02\bin directory, and use the "serverStatus" command to show the status of each of the application servers defined in this profile:

--------------------------------------------------------------------------------
C:\IBM\WebSphere\AppServer\profiles\AppSrv02\bin>serverStatus -all
ADMU0116I: Tool information is being logged in file
           C:\IBM\WebSphere\AppServer\profiles\AppSrv02\logs\serverStatus.log
ADMU0128I: Starting tool with the AppSrv02 profile
ADMU0503I: Retrieving server status for all servers
ADMU0505I: Servers found in configuration:
ADMU0506I: Server name: s1
ADMU0506I: Server name: s2
ADMU0506I: Server name: server1
ADMU0509I: The Application Server "s1" cannot be reached. It appears to be
           stopped.
ADMU0509I: The Application Server "s2" cannot be reached. It appears to be
           stopped.
ADMU0509I: The Application Server "server1" cannot be reached. It appears to be
           stopped.
--------------------------------------------------------------------------------

  This shows that I have 3 servers defined:

server1, s1, and s2

  What do you see in your atlas_dev profile?

My problem is resloved. After creating the  profile(atlas_dev) i login to that application server console by chaning the port to 9044. But under this profile if i want to create server2 instead of server1 with below command what should i change to

./manageprofiles.sh -create -profileName atlas_dev -profilePath /mnt/drive1/IBM/WebSphere/AppServer/profiles/atlas_dev -templatePath /mnt/drive1/IBM/WebSphere/AppServer/profileTemplates/default -nodeName 164118-web3Node01   -cellName 164118-web3Node01Cell -hostName 164118-web3.proxicom.com

Attached the scree shot from ps -ef |grep java command

When creating new profile i want to give differenct name not like below

/mnt/drive1/IBM/WebSphere/AppServer/profiles/atlas_dev/bin
[root@164118-web3 bin]# ./serverStatus.sh -all
ADMU0116I: Tool information is being logged in file
           /mnt/drive1/IBM/WebSphere/AppServer/profiles/atlas_dev/logs/serverStatus.log
ADMU0128I: Starting tool with the atlas_dev profile
ADMU0503I: Retrieving server status for all servers
ADMU0505I: Servers found in configuration:
ADMU0506I: Server name: server1
ADMU0508I: The Application Server "server1" is STARTED

Well, the reason that the administration console is on a different port is that each application server has its own administration console, and in order for them to be able to execute at the same time, they have to use unique ports.

I don't believe that there is a way, using the manageprofiles command to define the name of the server to be created.

To do that, I use scripting, as shown here:

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/txml_createserver.html

From your environment i can see your are using network deployment. but here its stand alone. So ur saying we cannot create additional application server under same profile with standalone application server installation.

I just want to create additional application server apart from default(server1) in same AppSrv01.

Thanks
Sudhakar

No, I'm not saying that.

You can use either the ProfileCreation utility

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/tpro_instances.html

or with scripting.

I have done both on a stand-alone (aka Base) Application Server.

I want to more clear what i am looking for. Under followign direcoty we have server1 application server  which is created while installating standalone application server
 ========================================================  
[root@164118-web3 bin]# pwd
/mnt/drive1/IBM/WebSphere/AppServer/profiles/AppSrv01
====================================================
cd bin
[root@164118-web3 bin]# ./serverStatus.sh -all -username admin -password admin
ADMU0116I: Tool information is being logged in file
           /mnt/drive1/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/serverStatus.log
ADMU0128I: Starting tool with the AppSrv01 profile
ADMU0503I: Retrieving server status for all servers
ADMU0505I: Servers found in configuration:
ADMU0506I: Server name: server1
ADMU0508I: The Application Server "server1" is STARTED
================================================================
Under same profile i want to create three application server like server2,,,,,, server3 ,,,,,,,server3.

Can you tell is it possible

sorry for my bad english. I just waiting for this to get reslove

Thanks

Yes.

1. Copy the attached files to your AppServer machine and put them somewhere convenient
2. Rename them to remove the txt extensions
3. Use the CreateTempate script to create an AppServer template using an existing application server (i.e., server1).  For example:

   wsadmin -lang jython -f CreateTemplate.py -s server1 -t T1

4. Use the CreateServer script to create as many application servers as you want
    For example:

    wsadmin -lang jython -f CreateServer.py -s server2 -t T1

CreateTemplate.py.txt

oops.  Here's the other one.
CreateServer.py.txt

For each script, if you don't specify any parameters, complete Usage information will be displayed.

oh, the example wsadmin statements shown above, expect the Jython scripts to be in the same directory as the wsadmin script utility (e.g., AppServer/profiles/AppSvr01/bin).

And to execute wsadmin on a Unix machine, the command would be something like:

./wsadmin.sh -lang jython -f /tmp/CreateTemplate.py -s server1 -t T1

Of course, this expects the Jython script to be in the /tmp directory.

Wow Who ever it is .. i am very thank full to you .. Let me try and i will let you know soon

The CreateTemplate.py  is successed

[root@164118-web3 bin]# ./wsadmin.sh -username admin -password admin -lang jython -f CreateTemplate.py -s server1 -t T1
WASX7209I: Connected to process "server1" on node 164118-web3Node01 using SOAP connector;  The type of process is: UnManagedProcess
WASX7303I: The following options are passed to the scripting environment and are available as arguments that are stored in the argv variable: "[-s, server1, -t, T1]"
CreateTemplate --serverName server1 --nodeName 164118-web3Node01 --templateName T1
CreateTemplate completed successfully

Second script failed

[root@164118-web3 bin]# ./wsadmin.sh -username admin -password admin -lang jython -f CreateServer.py -s atlas_dev -t T1
WASX7209I: Connected to process "server1" on node 164118-web3Node01 using SOAP connector;  The type of process is: UnManagedProcess
WASX7303I: The following options are passed to the scripting environment and are available as arguments that are stored in the argv variable: "[-s, atlas_dev, -t, T1]"
Missing or invalid required parameter: --serverName

Command: CreateServer

Purpose: WebSphere (wsadmin) script used to create an Application Server
         using an existing Appliction Server template.

  Usage: CreateServer [options]

Required switches:
  -s | --serverName   <name> = Name of server to be created
  -t | --templateName <name> = Name of template to be used

Optional switches:
  -d | --description  <text> = Text to be associated with server
  -n | --nodeName     <name> = Name of node on which server should be created

Notes:
- Long form option values may be separated/delimited from their associated
  value using either a space, or an equal sign ('=').

- Short form option values may be sepearated from their associated value using
  an optional space.

- Description text containing blanks should be enclosed in double quotes.

Examples:
  wsadmin -lang jython -f CreateServer.py --serverName=s1 --templateName T1

  wsadmin -lang jython -f CreateServer.py -ss1 -t T1 -d "My AppServer"

The below script failed. Please see above message
./wsadmin.sh -username admin -password admin -lang jython -f CreateServer.py -s atlas_dev -t T1

hi sir

can you update this please

i will check this in hour

hm... checking...  (please accept my apologies for the failure)...

Thanks for helping me with this. This is one of very good solution i ever got

Thank you for all your help

Great, I'm glad to hear it.

Thanks for allowing me to be of some help to you.

Thanks also for the grade and points.

Good luck

One more question

After creating this server one of our java develper trying to deploy jar file on this servers(atlas_dev) but she is getting this eror


cannot be started because it is installed on a different server


Can you help with this

One more question

After creating this server one of our java develper trying to deploy jar file on this servers(atlas_dev) but she is getting this eror


cannot be started because it is installed on a different server


Can you help with this

Sounds like the deploy didn't get the correct server association.

how about a new question?

Server is runninng from linux server. From below command
ps -ef |grep java
root     30434     1  5 14:22 pts/2    00:00:21 /mnt/drive1/IBM/WebSphere/AppServer/java/bin/java -Declipse.security -Dwas.status.socket=46385 -Dosgi.install.area=/mnt/drive1/IBM/WebSphere/AppServer -Dosgi.configuration.area=/mnt/drive1/IBM/WebSphere/AppServer/profiles/AppSrv01/configuration -Djava.awt.headless=true -Dosgi.framework.extensions=com.ibm.cds -Xshareclasses:name=webspherev61_%g,groupAccess,nonFatal -Xscmx50M -Xbootclasspath/p:/mnt/drive1/IBM/WebSphere/AppServer/java/jre/lib/ext/ibmorb.jar:/mnt/drive1/IBM/WebSphere/AppServer/java/jre/lib/ext/ibmext.jar -classpath /mnt/drive1/IBM/WebSphere/AppServer/profiles/AppSrv01/properties:/mnt/drive1/IBM/WebSphere/AppServer/properties:/mnt/drive1/IBM/WebSphere/AppServer/lib/startup.jar:/mnt/drive1/IBM/WebSphere/AppServer/lib/bootstrap.jar:/mnt/drive1/IBM/WebSphere/AppServer/lib/j2ee.jar:/mnt/drive1/IBM/WebSphere/AppServer/lib/lmproxy.jar:/mnt/drive1/IBM/WebSphere/AppServer/lib/urlprotocols.jar:/mnt/drive1/IBM/WebSphere/AppServer/deploytool/itp/batchboot.jar:/mnt/drive1/IBM/WebSphere/AppServer/deploytool/itp/batch2.jar:/mnt/drive1/IBM/WebSphere/AppServer/java/lib/tools.jar -Dibm.websphere.internalClassAccessMode=allow -Xms50m -Xmx256m -Dws.ext.dirs=/mnt/drive1/IBM/WebSphere/AppServer/java/lib:/mnt/drive1/IBM/WebSphere/AppServer/profiles/AppSrv01/classes:/mnt/drive1/IBM/WebSphere/AppServer/classes:/mnt/drive1/IBM/WebSphere/AppServer/lib:/mnt/drive1/IBM/WebSphere/AppServer/installedChannels:/mnt/drive1/IBM/WebSphere/AppServer/lib/ext:/mnt/drive1/IBM/WebSphere/AppServer/web/help:/mnt/drive1/IBM/WebSphere/AppServer/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime -Dderby.system.home=/mnt/drive1/IBM/WebSphere/AppServer/derby -Dcom.ibm.itp.location=/mnt/drive1/IBM/WebSphere/AppServer/bin -Djava.util.logging.configureByServer=true -Duser.install.root=/mnt/drive1/IBM/WebSphere/AppServer/profiles/AppSrv01 -Djavax.management.builder.initial=com.ibm.ws.management.PlatformMBeanServerBuilder -Dwas.install.root=/mnt/drive1/IBM/WebSphere/AppServer -Dpython.cachedir=/mnt/drive1/IBM/WebSphere/AppServer/profiles/AppSrv01/temp/cachedir -Djava.util.logging.manager=com.ibm.ws.bootstrap.WsLogManager -Dserver.root=/mnt/drive1/IBM/WebSphere/AppServer/profiles/AppSrv01 -Djava.security.auth.login.config=/mnt/drive1/IBM/WebSphere/AppServer/profiles/AppSrv01/properties/wsjaas.conf -Djava.security.policy=/mnt/drive1/IBM/WebSphere/AppServer/profiles/AppSrv01/properties/server.policy com.ibm.wsspi.bootstrap.WSPreLauncher -nosplash -application com.ibm.ws.bootstrap.WSLauncher com.ibm.ws.runtime.WsServer /mnt/drive1/IBM/WebSphere/AppServer/profiles/AppSrv01/config 164118-web3Node01Cell 164118-web3Node01 atlas_dev2