tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lisa D Beggs/AC/VCU <ldbe...@vcu.edu>
Subject Re: Trouble setting up virtual host
Date Mon, 27 Jul 2009 15:28:20 GMT
I am sorry, I don't usually post on forums.  I am sorry if I am making 
this difficult to read.  I hope this is better.  I am only copying what 
you are giving me and then responding.

>> another note.....now that I have changed port from 8080 to 80,
> How exactly did you do this ?  I changed the configuration in the 
> server.xml file based on guidance from my vendor.

Unfortunately, I wasn't there, so I do not know what your vendor told 
you to do, nor what you really did.
So, what did you change, where in the server.xml ? 

See Q11




Did you keep a copy of how it was before you changed it ?

YES

> 
>   I cannot see my default URL (http://adm138/InfoViewApp) either on user 

> workstation not sure if same or different issue, can see on server with 
no problem) 
> 
> 
> Q6.5 :
> Can you explain what you mean by "can see on server with no problem" ? 
If 
> I type in my url in the browser on my server (http://adm138/InfoViewApp) 

> with the 8080, the page comes up, I can not do this on a user 
> workstation...if I change the port back to 8080 in the server.xml 
> file....I can bring it up again on the user work station but I must add 
> adm138:8080 in the url name.

Could you re-read the question, and your answer, and see if to you it 
makes sense ? To me, it doesn't.

If I type in http://adm138:8080/InfoViewApps or http://adm138/InfoViewApps 
on the server, the application comes up.  Before when I had it directed to 
port 8080, from a user's workstation I could get the application to come 
up using the http://adm138:8080/InfoViewApps URL, after I changed it to 
port 80, I could not get the http://adm138/InfoViewApps URL to work from 
the user's workstation, it only worked from the server.  Is that a better 
explanation?

> 
> Do you mean that if you open a browser directly on the server console, 
> then you can see the Tomcat default page when you enter :
> either
> http://www.fmdreports.vcu.edu
> and/or
> http://adm138
> ?  NO, still can not see them.  However, I see the default Tomcat home 
> page if I enter these URLS on the server.
> 

Same thing.  Worse, in fact.

> But if you do this on any other workstation, you get a "cannot display 
> this page" answer ?  Right :)
> 
> 
> A whole bunch of new questions :
> 
> Q7:
> In which directory is Tomcat installed on this server ?  C:\Program 
> Files\Business Objects\Tomcat55
> 
OK. (but leave space)

> Q8:
> Supposing for now that this directory is "c:\tomcat", then under this 
> directory, are there the following subdirectories :
> - C:\Program Files\Business Objects\Tomcat55\conf
> - C:\Program Files\Business Objects\Tomcat55\conf
> - C:\Program Files\Business Objects\Tomcat55\webapps\ROOT
> - C:\Program Files\Business Objects\Tomcat55\webapps\InfoViewApp\
> 
The second line doesn't match the question, but OK, I get the idea.

> 
> Q9:
> Is there any other (than InfoViewApp) Tomcat-based application running 
> on that server ?  NO

Good, that makes it easier.  See the additional info at end.


> 
> Will there be other applications there in the near future ?  No we don't 

> intend there to be

Good also.

> 
> Q10:
> Suppose that we set this server up so that /both/ the URLs :
> http://www.fmdreports.vcu.edu
> and
> http://adm138
> return directly the login page of your application, would this be a 
> problem ?  That should not be a problem, should that cause any future 
> issues?

Not right now.  And by the time it becomes an issue, there will be 
someone else on the list to help you with it, I'm sure.


> 
> Or do you need that "http://adm138" still returns the default Tomcat 
> homepage ?

I thus guess not.

Neither http://www.fmdreports.vcu.edu or http://adm138 work from any 
workstation ('cannot display the page').  And if enter in the browser from 
the server, they return the Tomcat default home page.


> 
> Q11:
> In the "\conf" subdirectory of your Tomcat installation, there is a file 

> named "server.xml".  In that file, there is a section resembling the 
> following (the ports may be different) :
> 
>      <!-- Define a non-SSL HTTP/1.1 Connector on port 8180 -->
>      <Connector port="8180" maxHttpHeaderSize="8192"
>         maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
>         enableLookups="false" redirectPort="8443" acceptCount="100"
>         connectionTimeout="20000" disableUploadTimeout="true" />
> 
> 
> Is this what you are looking for?  I don't have the one above......
> 
>    <Connector URIEncoding="UTF-8" acceptCount="100" 
> connectionTimeout="20000" disableUploadTimeout="true" 
> enableLookups="false" maxHttpHeaderSize="8192" maxSpareThreads="75" 
> maxThreads="150" minSpareThreads="25" port="80" redirectPort="8443"/>
> 

I said "resembling", I did not say "the same".  The only significant 
difference is the order of the attributes, which technically does not 
matter here.
But it's ok.  At least now, I know that there /should/ be a Tomcat 
listening on port 80.  But see below, we're not out of the woods yet.

By the way, this very portion of your server.xml above, is probably 
where your vendor told you to change the port between 80 and 8080, right ?

YES :)


> 
> Q12:
> On the server, in a command window, enter the following command :
> netstat -anb -p tcp
> then also paste the response in your answer here.
>

Now this is a real bummer.  Based on what you show below, there is no 
Tomcat on that system listening on any port.
There is just one tomcat5.exe, which seems to be having a conversation 
with a CMS.exe running on your server also.

What I'm saying is that you missed a whole bunch of lines that were the 
output of that command, and which probably scrolled off the top of the 
screen before you had a chance to copy them.
It's a pity, because they were just the interesting ones.
;-)

So, do it again, but this time use this :

netstat -anb -p tcp | more


Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator>netstat -anb -p tcp | more

Active Connections

  Proto  Local Address          Foreign Address        State           PID
  TCP    0.0.0.0:13             0.0.0.0:0              LISTENING 5764
  [D4.exe]

  TCP    0.0.0.0:37             0.0.0.0:0              LISTENING 5764
  [D4.exe]

  TCP    0.0.0.0:135            0.0.0.0:0              LISTENING       712
  RpcSs
  [svchost.exe]

  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING       4
  [System]

  TCP    0.0.0.0:1025           0.0.0.0:0              LISTENING       460
  [lsass.exe]

  TCP    0.0.0.0:1069           0.0.0.0:0              LISTENING 2284
  [dsm_om_connsvc32.exe]

  TCP    0.0.0.0:1086           0.0.0.0:0              LISTENING 2428
  [ManagementAgentNT.exe]

  TCP    0.0.0.0:1087           0.0.0.0:0              LISTENING 2428
  [ManagementAgentNT.exe]

  TCP    0.0.0.0:1311           0.0.0.0:0              LISTENING 2284
  [dsm_om_connsvc32.exe]

  TCP    0.0.0.0:1592           0.0.0.0:0              LISTENING 6828
  [tmcsvc.exe]

  TCP    0.0.0.0:2070           0.0.0.0:0              LISTENING 4900
  [tomcat5.exe]

  TCP    0.0.0.0:2858           0.0.0.0:0              LISTENING       844
  [JobServer.exe]

  TCP    0.0.0.0:2859           0.0.0.0:0              LISTENING       524
  [JobServer.exe]

  TCP    0.0.0.0:2860           0.0.0.0:0              LISTENING 6872
  [JobServer.exe]

  TCP    0.0.0.0:2861           0.0.0.0:0              LISTENING 4436
  [fileserver.exe]

  TCP    0.0.0.0:2864           0.0.0.0:0              LISTENING 6212
  [fileserver.exe]

  TCP    0.0.0.0:2871           0.0.0.0:0              LISTENING 7796
  [EventServer.exe]

  TCP    0.0.0.0:2875           0.0.0.0:0              LISTENING 8164
  [JobServer.exe]

  TCP    0.0.0.0:2878           0.0.0.0:0              LISTENING 5836
  [crproc.exe]

  TCP    0.0.0.0:2937           0.0.0.0:0              LISTENING 5596

  TCP    0.0.0.0:2963           0.0.0.0:0              LISTENING 4316
  [java.exe]

  TCP    0.0.0.0:3389           0.0.0.0:0              LISTENING 5404
  TermService
  [svchost.exe]

  TCP    0.0.0.0:5001           0.0.0.0:0              LISTENING 4900
  [tomcat5.exe]

  TCP    0.0.0.0:6400           0.0.0.0:0              LISTENING 2804
  [CMS.exe]

  TCP    0.0.0.0:6410           0.0.0.0:0              LISTENING 7748
  [sia.exe]

  TCP    0.0.0.0:6415           0.0.0.0:0              LISTENING 2804
  [CMS.exe]

  TCP    0.0.0.0:6416           0.0.0.0:0              LISTENING 1932
  [crcache.exe]

  TCP    0.0.0.0:6418           0.0.0.0:0              LISTENING       512
  [crystalras.exe]

  TCP    0.0.0.0:8000           0.0.0.0:0              LISTENING 2284
  [dsm_om_connsvc32.exe]

  TCP    0.0.0.0:8080           0.0.0.0:0              LISTENING 4900
  [tomcat5.exe]

  TCP    0.0.0.0:8192           0.0.0.0:0              LISTENING 2636
  [RouterNT.exe]

  TCP    0.0.0.0:8193           0.0.0.0:0              LISTENING 2636
  [RouterNT.exe]

  TCP    0.0.0.0:8194           0.0.0.0:0              LISTENING 2636
  [RouterNT.exe]

  TCP    0.0.0.0:9535           0.0.0.0:0              LISTENING       196
  [issuser.exe]

  TCP    0.0.0.0:9593           0.0.0.0:0              LISTENING 3428
  [residentagent.exe]

  TCP    0.0.0.0:9594           0.0.0.0:0              LISTENING 3428
  [residentagent.exe]

  TCP    0.0.0.0:9595           0.0.0.0:0              LISTENING 3428
  [residentagent.exe]

  TCP    0.0.0.0:33354          0.0.0.0:0              LISTENING 6828
  [tmcsvc.exe]

  TCP    127.0.0.1:1732         0.0.0.0:0              LISTENING 3428
  [residentagent.exe]

  TCP    127.0.0.1:8005         0.0.0.0:0              LISTENING 4900
  [tomcat5.exe]

  TCP    127.0.0.1:9592         0.0.0.0:0              LISTENING 3428
  [residentagent.exe]

  TCP    127.0.0.1:21584        0.0.0.0:0              LISTENING 5996
  [collector.exe]

  TCP    127.0.0.1:53001        0.0.0.0:0              LISTENING 6532
  [LDregwatch.exe]

  TCP    128.172.12.129:139     0.0.0.0:0              LISTENING       4
  [System]

  TCP    192.168.21.101:139     0.0.0.0:0              LISTENING       4
  [System]

  TCP    127.0.0.1:1070         127.0.0.1:1071         ESTABLISHED 2428
  [ManagementAgentNT.exe]

  TCP    127.0.0.1:1071         127.0.0.1:1070         ESTABLISHED 2428
  [ManagementAgentNT.exe]

  TCP    127.0.0.1:1073         127.0.0.1:1074         ESTABLISHED 2636
  [RouterNT.exe]

  TCP    127.0.0.1:1074         127.0.0.1:1073         ESTABLISHED 2636
  [RouterNT.exe]

  TCP    127.0.0.1:1682         127.0.0.1:9535         ESTABLISHED 4664
  [rcgui.exe]

  TCP    127.0.0.1:9535         127.0.0.1:1682         ESTABLISHED     196
  [issuser.exe]

  TCP    128.172.12.129:2014    128.172.12.129:6415    ESTABLISHED 4316
  [java.exe]

  TCP    128.172.12.129:2019    128.172.12.129:6415    ESTABLISHED 4900
  [tomcat5.exe]

  TCP    128.172.12.129:2616    128.172.12.129:6415    ESTABLISHED 5836
  [crproc.exe]

  TCP    128.172.12.129:2793    128.172.6.109:1433     ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:2814    128.172.6.109:1433     ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:2815    128.172.6.109:1433     ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:2817    128.172.6.109:1433     ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:2821    128.172.6.109:1433     ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:2823    128.172.6.109:1433     ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:2824    128.172.12.129:6415    ESTABLISHED 7748
  [sia.exe]

  TCP    128.172.12.129:2825    128.172.6.109:1433     ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:2826    128.172.6.109:1433     ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:2827    128.172.6.109:1433     ESTABLISHED 2804
  [CMS.exe]

 
  TCP    128.172.12.129:2828    128.172.6.109:1433     ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:2829    128.172.6.109:1433     ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:2830    128.172.6.109:1433     ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:2831    128.172.6.109:1433     ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:2832    128.172.6.109:1433     ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:2858    128.172.12.129:2887    ESTABLISHED     844
  [JobServer.exe]

  TCP    128.172.12.129:2859    128.172.12.129:2897    ESTABLISHED     524
  [JobServer.exe]

  TCP    128.172.12.129:2860    128.172.12.129:2892    ESTABLISHED 6872
  [JobServer.exe]

  TCP    128.172.12.129:2861    128.172.12.129:2945    ESTABLISHED 4436
  [fileserver.exe]

  TCP    128.172.12.129:2861    128.172.12.129:2893    ESTABLISHED 4436
  [fileserver.exe]

  TCP    128.172.12.129:2861    128.172.12.129:2935    ESTABLISHED 4436
  [fileserver.exe]

  TCP    128.172.12.129:2863    128.172.12.129:6415    ESTABLISHED     844
  [JobServer.exe]

  TCP    128.172.12.129:2864    128.172.12.129:2889    ESTABLISHED 6212
  [fileserver.exe]

  TCP    128.172.12.129:2864    128.172.12.129:2936    ESTABLISHED 6212
  [fileserver.exe]

  TCP    128.172.12.129:2864    128.172.12.129:2946    ESTABLISHED 6212
  [fileserver.exe]

  TCP    128.172.12.129:2867    128.172.12.129:6415    ESTABLISHED 4436
  [fileserver.exe]

  TCP    128.172.12.129:2870    128.172.12.129:6415    ESTABLISHED 6872
  [JobServer.exe]

  TCP    128.172.12.129:2871    128.172.12.129:2894    ESTABLISHED 7796
  [EventServer.exe]

  TCP    128.172.12.129:2873    128.172.12.129:6415    ESTABLISHED 6212
  [fileserver.exe]

  TCP    128.172.12.129:2874    128.172.12.129:6415    ESTABLISHED     524
  [JobServer.exe]

  TCP    128.172.12.129:2875    128.172.12.129:2898    ESTABLISHED 8164
  [JobServer.exe]

  TCP    128.172.12.129:2877    128.172.12.129:6415    ESTABLISHED 7796
  [EventServer.exe]

  TCP    128.172.12.129:2878    128.172.12.129:2926    ESTABLISHED 5836
  [crproc.exe]

  TCP    128.172.12.129:2878    128.172.12.129:2947    ESTABLISHED 5836
  [crproc.exe]

  TCP    128.172.12.129:2880    128.172.12.129:6415    ESTABLISHED 8164
  [JobServer.exe]

  TCP    128.172.12.129:2882    128.172.12.129:6415    ESTABLISHED 1932
  [crcache.exe]

  TCP    128.172.12.129:2886    128.172.12.129:6415    ESTABLISHED 5836
  [crproc.exe]

  TCP    128.172.12.129:2887    128.172.12.129:2858    ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:2889    128.172.12.129:2864    ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:2891    128.172.12.129:6416    ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:2892    128.172.12.129:2860    ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:2893    128.172.12.129:2861    ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:2894    128.172.12.129:2871    ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:2897    128.172.12.129:2859    ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:2898    128.172.12.129:2875    ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:2903    128.172.12.129:6415    ESTABLISHED     512
  [crystalras.exe]

  TCP    128.172.12.129:2904    128.172.12.129:6416    ESTABLISHED 5836
  [crproc.exe]

  TCP    128.172.12.129:2908    128.172.12.129:6418    ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:2926    128.172.12.129:2878    ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:2935    128.172.12.129:2861    ESTABLISHED 5836
  [crproc.exe]

  TCP    128.172.12.129:2936    128.172.12.129:2864    ESTABLISHED 5836
  [crproc.exe]

  TCP    128.172.12.129:2937    128.172.12.129:2991    ESTABLISHED 5596
  [crproc.exe]

  TCP    128.172.12.129:2940    128.172.12.129:6415    ESTABLISHED 5596
  [crproc.exe]

  TCP    128.172.12.129:2945    128.172.12.129:2861    ESTABLISHED 5596
  [crproc.exe]

  TCP    128.172.12.129:2946    128.172.12.129:2864    ESTABLISHED 5596
  [crproc.exe]

  TCP    128.172.12.129:2947    128.172.12.129:2878    ESTABLISHED 1932
  [crcache.exe]

  TCP    128.172.12.129:2963    128.172.12.129:2968    ESTABLISHED 4316
  [java.exe]

  TCP    128.172.12.129:2968    128.172.12.129:2963    ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:2991    128.172.12.129:2937    ESTABLISHED 5836
  [crproc.exe]

  TCP    128.172.12.129:3009    128.172.12.129:6415    ESTABLISHED 4900
  [tomcat5.exe]

  TCP    128.172.12.129:3014    128.172.12.129:6415    ESTABLISHED 4900
  [tomcat5.exe]

  TCP    128.172.12.129:3172    128.172.30.98:389      ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:3303    128.172.10.73:8194     ESTABLISHED 2636
  [RouterNT.exe]

  TCP    128.172.12.129:3374    128.172.30.98:389      ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:3375    128.172.30.98:389      ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:3376    128.172.30.98:389      ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:3377    128.172.30.98:389      ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:4372    128.172.12.129:6415    ESTABLISHED 4900
  [tomcat5.exe]

  TCP    128.172.12.129:4794    128.172.12.129:6415    ESTABLISHED 4900
  [tomcat5.exe]

  TCP    128.172.12.129:4842    128.172.12.129:6415    ESTABLISHED 4900
  [tomcat5.exe]

  TCP    128.172.12.129:4889    128.172.12.129:6415    ESTABLISHED 4900
  [tomcat5.exe]

  TCP    128.172.12.129:6415    128.172.12.129:2903    ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:6415    128.172.12.129:4372    ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:6415    128.172.12.129:2863    ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:6415    128.172.12.129:2867    ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:6415    128.172.12.129:4842    ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:6415    128.172.12.129:2940    ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:6415    128.172.12.129:4794    ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:6415    128.172.12.129:2873    ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:6415    128.172.12.129:4889    ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:6415    128.172.12.129:3009    ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:6415    128.172.12.129:2616    ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:6415    128.172.12.129:2870    ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:6415    128.172.12.129:2886    ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:6415    128.172.12.129:2019    ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:6415    128.172.12.129:2882    ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:6415    128.172.12.129:2877    ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:6415    128.172.12.129:2880    ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:6415    128.172.12.129:2014    ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:6415    128.172.12.129:2824    ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:6415    128.172.12.129:3014    ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:6415    128.172.12.129:2874    ESTABLISHED 2804
  [CMS.exe]

  TCP    128.172.12.129:6416    128.172.12.129:2904    ESTABLISHED 1932
  [crcache.exe]

  TCP    128.172.12.129:6416    128.172.12.129:2891    ESTABLISHED 1932
  [crcache.exe]

  TCP    128.172.12.129:6418    128.172.12.129:2908    ESTABLISHED     512
  [crystalras.exe]

  TCP    128.172.12.129:9535    128.172.193.85:2338    ESTABLISHED     196
  [issuser.exe]

  TCP    192.168.21.101:1085    192.168.21.101:8194    ESTABLISHED 2428
  [ManagementAgentNT.exe]

  TCP    192.168.21.101:1087    192.168.21.101:1088    ESTABLISHED 2428
  [ManagementAgentNT.exe]

  TCP    192.168.21.101:1088    192.168.21.101:1087    ESTABLISHED 2636
  [RouterNT.exe]

  TCP    192.168.21.101:8194    192.168.21.101:1085    ESTABLISHED 2636
  [RouterNT.exe]

  TCP    127.0.0.1:1192         127.0.0.1:9592         CLOSE_WAIT 4372
  [policy.client.invoker.exe]

  TCP    127.0.0.1:1257         127.0.0.1:9592         CLOSE_WAIT 4372
  [policy.client.invoker.exe]

  TCP    127.0.0.1:4452         127.0.0.1:9592         CLOSE_WAIT 4372
  [policy.client.invoker.exe]

  TCP    127.0.0.1:4925         127.0.0.1:9592         CLOSE_WAIT 4372
  [policy.client.invoker.exe]

  TCP    127.0.0.1:53001        127.0.0.1:2220         TIME_WAIT       0
  TCP    128.172.12.129:1709    128.172.12.129:6415    TIME_WAIT       0
  TCP    128.172.12.129:2165    128.172.4.60:135       TIME_WAIT       0
  TCP    128.172.12.129:2166    128.172.4.60:1025      TIME_WAIT       0
  TCP    128.172.12.129:2223    128.172.12.129:2963    TIME_WAIT       0
  TCP    128.172.12.129:2234    128.172.12.129:6410    TIME_WAIT       0
  TCP    128.172.12.129:2235    128.172.12.129:6410    TIME_WAIT       0
  TCP    128.172.12.129:2244    128.172.12.129:2963    TIME_WAIT       0
  TCP    128.172.12.129:2255    128.172.12.129:6410    TIME_WAIT       0
  TCP    128.172.12.129:2256    128.172.12.129:6410    TIME_WAIT       0
  TCP    128.172.12.129:6400    128.172.12.129:2221    TIME_WAIT       0
  TCP    128.172.12.129:6400    128.172.12.129:2242    TIME_WAIT       0


C:\Documents and Settings\Administrator>

I hope I got all of these that you need.



and copy and paste each screen, typing a CR only when you are done with 
one screen, to see the next one and cut-and-paste it.

The lines of particular interest, are the ones around where 
[tomcat5.exe] appears.
If you send just those, it's OK too.  But don't miss one.








Now some advance information, which will unfortunately only become 
really useful when we've sorted out this port 80/8080 and these other 
workstations issues.

Based on your answer to Q8, complemented by your answers to Q9 and Q10 :

There are two separate issues, which can be dealt with separately :

1) make the application respond to
http://www.fmdreports.vcu.edu
(without any :8080 or /InfoViewApp at the end)

2) make the other workstations able to connect to your server.

Let tackle (1) first :

- stop Tomcat

- rename the directory
C:\Program Files\Business Objects\Tomcat55\webapps\ROOT
to become
C:\Program Files\Business Objects\Tomcat55\webapps\old-default

- rename the directory
C:\Program Files\Business Objects\Tomcat55\webapps\InfoViewApp
to become
C:\Program Files\Business Objects\Tomcat55\webapps\ROOT
(in other words, just change "InfoViewApp" to "ROOT")

- restart Tomcat

That should be it.  It means that now, instead of the default Tomcat 
page, your application (which was "InfoViewApp") has become Tomcat's 
/default application/, the one that users will see when they enter the URL
http://www.fmdreports.vcu.edu

If I understand well what you have tried to communicate above, this 
should work right away, but only from the browser running on the server.
And, for the time being, you may need to add a ":8080" at the end, it's 
a bit hard to tell right now.

Once that bit is working, we can address issue # 2 later.


I have not tried the above.  I just found out that we might have other 
departments that may come on and use our Crystal Reports server.  Before I 
make any changes I felt like I should find out that if they wanted to do 
the same thing as we are attempting to do, what the implications of doing 
the above would be.  I should probably set this up in the beginning with 
the expectations that we may have other departments who may want to have 
their own 'page' to the application.


Ironically, that's what Hassan told you many messages ago.
But maybe he was a bit short.  I have more time.


Additional information, just if you want to learn something from this : 

THANK YOU FOR THE BELOW INFORMATION!!!

In a URL like "http://www.fmdreports.vcu.edu:8080/InfoViewApp", there 
are separate parts.  The whole is known as the URL, but each part also 
has a name and a separate function :

*http://* is the "protocol".  That is like the "language" that the 
browser speaks to the server. (For example, "https://" would mean a 
different protocol, or language).  The browser and the server must speak 
the same protocol, otherwise they cannot communicate.

*www.fmdreports.vcu.edu*  is the "hostname".  That is just a name for 
humans, that can be translated by the DNS system into an IP address. 
This IP address is what the browser uses to send his request to the 
correct server.
Different hostnames can correspond to the same IP address.  In that 
case, they are called "aliases" of one another.  In your case thus, 
whether the browser uses "www.fmdreports.vcu.edu" or "adm138" as the 
hostname does not matter, because ultimately these requests go to the 
same IP address, and thus to the same server.

*:8080*  is an (optional) port number.  This is really another part of 
the IP address.  To use a telephone analogy, let's say that the IP 
address is the general telephone number of a company, and the port is 
the individual extension within that company's telephone system.
In TCP/IP terms, the IP address is the address of the server, and the 
port is the internal extension of a "service" within this server (like 
Tomcat).
Each "protocol" is usually associated with a "default port".  For the 
"http://" protocol, this default port is 80.  That is why it is optional 
, if the webserver is listening on the default port 80, to specify this 
port in the URL.  But if the server is listening on any other, 
non-default port (like 8080), then you need to specify it in the URL.

And finally, what comes after the
protocol://hostname:port/
is "the rest", known as a combination of a path and possibly a query.
That's your "/InfoViewApp".  It indicates which application the browser 
wants to talk to, within the Tomcat service.

An empty path, indicated as just "/", is also a valid path.  It 
indicates that the browser wants the "default application" of that 
service.

In the case of Tomcat, the various applications are usually organised 
under the Tomcat/webapps/ sub-directory.
Currently thus, you application is located in the directory
Tomcat/webapps/InfoViewApp.
And a browser, to request it, must use a URL like
protocol://hostname(:port)/InfoViewApp

In order to avoid confusion, the Tomcat default application is located 
under Tomcat/webapps/ROOT/. (The capitals in ROOT do matter).
That is the application that browsers get when they request just
protocol://hostname(:port)/

That is why, earlier, by renaming the existing ROOT application (which 
displays the Tomcat default page), and renaming yours to ROOT, we made 
your application become the default, so that browsers can now access it 
via
  protocol://hostname(:port)/

Note that the old default Tomcat page is still there.  But to get it, 
now in the browser you have to use the URL
http://www.fmdreports.vcu.edu(:8080)/old-default
(do you understand why ?)


One inconvenient of this scheme, is that you cannot have TWO default 
applications.  You need to choose one of them to be the default (and go 
under Tomcat/webapps/ROOT/).
So, if later you decide to add another different application to the same 
server, then that one cannot be the default, because yours already is.
This other application (suppose it is called "AnotherApp") will then be 
placed in the subdirectory Tomcat/webapps/AnotherApp, and will have to 
be accessed by browsers as
http://www.fmdreports.vcu.edu/AnotherApp

Is it now clearer ?

It may all looks rather mysterious at first, but it is really quite 
simple and logical.  A bit of dedication, and you'll end up as the 
Tomcat guru, you'll see.
;-)



_____________________________________________
"Change is the essence of life. Be willing to surrender what you are, for 
what you could become". 

Lisa D. Beggs 
Information Technology Specialist
Business Application Services
Phone:  804 828-2098
Fax:   804 828-0322

Don't be a phishing victim - VCU and other reputable organizations will 
never use email to request that you reply with your password, social 
security number or confidential personal information.  For more details 
visit http://infosecurity.vcu.edu/phishing.html 





Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message