|
midrange.com
If you are able to start the application server from the administrative
console (in V5.0), then you are using the WebSphere Application Server
Network Deployment V5 (ND) product (as opposed to WebSphere Application
Server V5 - also known as "Base edition"). The ND product allows you to
manage multiple WebSphere Application Server V5 (Base) instances (also
known as "nodes" or "federated base instances"). Each base instance
managed by an ND instance consists of a node agent and one or more
application servers.
Enough background...
I suspect that when someone cancelled the application server job, they also
cancelled the nodeagent job running in QEJBAS5 subsystem as well. In order
for the Network Deployment (also known as the Deployment Manager)
administrative console to "manage" the application server, the node agent
for the Base instance must be started.
Use the startNode script (located under /QIBM/ProdData/WebAS5/Base/bin) to
start the node agent for your Base instance. If you are using the default
instance shipped with the product, do the following (this is most likely
your case):
STRQSH
/QIBM/ProdData/WebAS5/Base/bin/startNode
NOTE: When you start the QEJBAS5 subsystem (if you are using the default
instance), the nodeagent job should start automatically for you.
Once the node agent process is up and running, it will "discover" the
deployment manager and the deployment manager will "discover" the nodeagent
as well. You should then be able to click the admin console's refresh
button on the application server page and see the correct status for your
application server. (you may need to logout of the console and then log
back in - but generally you should not need to).
If you are using an instance other than the default instance, do this:
STRQSH
/QIBM/ProdData/WebAS5/Base/bin/startNode -instance instancename
Note: instancename is case sensitive
Frances Stewart
WebSphere Application Server for iSeries
External web site: http://www.iseries.ibm.com/websphere
Team web site: http://w3.rchland.ibm.com/~was
E-mail: francess@xxxxxxxxxx
Tie-line: 553-2795, External: 507 253-2795
IBM Rochester
"Raikov, Leonid"
<RaikovL1@xxxxxxxxx To:
"'JAVA400-L@xxxxxxxxxxxx'" <JAVA400-L@xxxxxxxxxxxx>
> cc:
Sent by: Subject: WAS 5.0
administration
java400-l-bounces@m
idrange.com
12/03/2003 08:21 AM
Please respond to
Java Programming on
and around the
iSeries / AS400
WE just installed WAS5.0 and configured an application server instance.
So far so good. We started the server from the admin console and again
everything was OK. After that somebody cancelled the application server
instance job on the iSeries.
That was the sequence of events. Now the problem. In admin console the
status of the application server is Inactive. When we start it using the
console function the job on the iSeries starts and eventually reports
that the server is up and running. However, the admin console would
report a server failure suggesting we take a look in the JVM logs. But
JVM error log is clean and the last message on the output log reads
"Server is ready". Whatever we did from that point we could not make the
admin console recognise that the application server is actually up and
running. What are we doing wrong?
Lo
_______________________________________________
This is the Java Programming on and around the iSeries / AS400 (JAVA400-L)
mailing list
To post a message email: JAVA400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/java400-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
