IBM SG24-6526-00 User Manual
Chapter 6. Tips and techniques
155
Figure 6-7 The NETSTAT command showing ports 900 and 902
If you have trouble connecting a console to the administration server, although the job says
that it is ready, then it may be a name problem. If a console is started, then you can find the
full name of the administration server job by selecting the node and looking for Process ID on
the General page.
that it is ready, then it may be a name problem. If a console is started, then you can find the
full name of the administration server job by selecting the node and looking for Process ID on
the General page.
The job log of the administration server job has messages that indicate when individual
application servers were started and stopped, for example:
application servers were started and stopped, for example:
WebSphere application server job 033456/QEJB/SALESORDER started.
If these messages do not correspond to an explicit start or stop request, then there may be a
time out problem. For more information, see “Constrained performance” on page 132.
time out problem. For more information, see “Constrained performance” on page 132.
6.3.3 Specifying ports
The WebSphere console and some other IBM tools, for example the Resource Analyzer, have
a special provision for alternative instances and ports. The console takes two parameters.
The first parameter is the name of the WebSphere server, and the second parameter is the
port. Both are optional. The first defaults to the current system and is never appropriate if you
are running WebSphere on the iSeries. The second defaults to 900 and may be omitted for
the standard instance.
a special provision for alternative instances and ports. The console takes two parameters.
The first parameter is the name of the WebSphere server, and the second parameter is the
port. Both are optional. The first defaults to the current system and is never appropriate if you
are running WebSphere on the iSeries. The second defaults to 900 and may be omitted for
the standard instance.
If you are using an additional instance, you need to know the port that it is using and specify
this as the second parameter to the console.
this as the second parameter to the console.
Many clients may lack this explicit support for alternative instances. However, it is still
normally possible to attach the clients to an alternative instance. Using system:port in place of
the system name works with most clients.
normally possible to attach the clients to an alternative instance. Using system:port in place of
the system name works with most clients.
6.3.4 Application server jobs
For each application server that is started by any instance, there is a job running in the
QEJBSBS subsystem. The name of the job is the name of the application if it is acceptable as
an OS/400 job name. If the name is too long, then it is truncated and unusual characters may
be omitted.
QEJBSBS subsystem. The name of the job is the name of the application if it is acceptable as
an OS/400 job name. If the name is too long, then it is truncated and unusual characters may
be omitted.
The name of the instance is not used as part of the job name. If you have the same
application server name in multiple instances, it is not obvious which job belongs to which
instance. To see the full name of the job (including its OS/400 job number), enter
application server name in multiple instances, it is not obvious which job belongs to which
instance. To see the full name of the job (including its OS/400 job number), enter
5
next to it.