|
|
|
| Hi,<br />
<br />
I have installed IBM Http Server (IHS) and WAS 5.1 on the same Windows 2003 box.<br />
I'd like to monitor specific ports on the WAS server to see if any communication between IHS and WAS is occurring.<br />
<br />
Any help would be greatly appreciated.<br />
<ul class="jive-dash">
<li>maestro</li>
</ul>
| |
|
| What about monitor the HTTP server logs ? Failure to establish a connection
between IHS and WAS will be logged as HTTP error 500. Response times are
logged as well.
| |
|
| I need more detailed monitoring.<br />
<br />
When IHS/WAS are running. There is a plugin file that configures the services.<br />
<br />
When a default server (server1) is created in WAS 5.1, 4 HTTP transports are created:<br />
<b>9080 - web server?</b><br />
9090 - admin console <br />
9043 - admin console ssl<br />
<b>9443 - web server ssl?</b><br />
<br />
The IHS server is running under ssl which is port 443 by default.<br />
<br />
So when request to the server <a class="jive-link-external" href="https://server/login">https://server/login</a> is issued the request goes thru the IHS server.<br />
Based on the configurations in the plugin the request continues on to WAS.<br />
But which port on WAS is the one that handles this request?<br />
<br />
My intent is to remove any useless port definitions as well as gain familiarity with a utility that can monitor specific ports.<br />
<br />
Regards,<br />
maestro
| |
|
| > My intent is to remove any useless port definitions as well as gain
> familiarity with a utility that can monitor specific ports.
The information in the plug-in configuration file is the result of your
configuration in the Administrative Console.
If you don't need HTTP transport for a certain application, remove the
transport port in the Console and it won't appear anymore in the plug-in
file.
| |
| maestro@pandorus.ca 2007-11-28, 7:40 am |
| Yes of course configuring the server and updating the plugin is how things are done.<br />
<br />
So when request to the server <a class="jive-link-external" href="https://server/login">https://server/login</a> is issued the request goes thru the IHS server.<br />
Based on the configurations in the plugin the request continues on to WAS.<br />
But which port on WAS is the one that handles this request?
| |
|
| > But which port on WAS is the one that handles this request?
The Servlet mapped to "/login" is in a Web Module mapped onto an Application
Server.
On this Application Server, you define the internal http transport ports (or
most likely they were assigned automatically by WebSphere).
Based on this information, the plug-in configuration file contains
information to route the request to the internal transport port.
So, to know the transport port of an Application Server, you need to look
into the Console under the Application Server item.
Or make the exercise of reading the XML file to find the route.
| |
| maestro@pandorus.ca 2007-11-28, 1:27 pm |
| If you look at the 3 post I list the HTTP Transport ports.<br />
There are question marks at the end of 2 ports.<br />
The question mark are just that questions.<br />
<br />
I'm looking for factual information and not some advice on reading an xml file.<br />
Nor do I have the time to hack away at playing with the ports.<br />
But it seems that I may have to do it this way.
| |
| Ken Hygh 2007-11-28, 1:27 pm |
| maestro@pandorus.ca wrote:
> If you look at the 3 post I list the HTTP Transport ports.<br />
> There are question marks at the end of 2 ports.<br />
> The question mark are just that questions.<br />
> <br />
> I'm looking for factual information and not some advice on reading an xml file.<br />
> Nor do I have the time to hack away at playing with the ports.<br />
> But it seems that I may have to do it this way.
>
9443
Ken
| |
| maestro@pandorus.ca 2007-11-28, 7:37 pm |
| Thanks Ken.<br />
<br />
But I did omit one important detail. There is a virtual host as well.<br />
So I decided to get to the bottom of this and put aside my work and lock the door for the afternoon.<br />
<br />
default_host (virtual) port 443<br />
server ports 9080, 9090, 9043 & 9443<br />
IHS virtual host port 443<br />
<br />
I removed the 9080 and 9443 ports from the server and updated the plugin.<br />
Restarted the services.<br />
The application is still running.<br />
So port 443 must be the one handling the requests.<br />
<br />
This has just blown my conceptual model apart!<br />
At least I have my answer. 
|
|
|
|