To: "John Yin" Subject: Re: summary demo report In-reply-to: Your message of "Sat, 08 Feb 2003 11:31:42 PST." <003601c2cfa8$b8d509e0$03fea8c0@JOHNYINTOSHIBA> Date: Sat, 08 Feb 2003 14:36:20 -0500 From: Geoffrey Fox > This is a multi-part message in MIME format. > > ------=_NextPart_000_0037_01C2CF65.AAB1C9E0 > Content-Type: text/plain; > charset="us-ascii" > Content-Transfer-Encoding: 7bit > > * Last week, we have continued to try to use and show Impromptu to > our > > customers, which include TO DATE: > > Park Nicollet Hospital (1st PC OK, 2nd time PC has Sun > > JVM, no Admin right) > * This is a known issue. > > Kaiser Permanente (Does not allow port > > 8080 access) > * For production, you need 2 servers. This was the same issue > with Avery. So you run web server on 1 machine on port 80. Then HTTP > tunneling on the 3rd server on port 80. In this case, audio most likely > will work through SSL ports so no need for 3rd server. I don't understand whether you mean 2 or 3 servers! what is function of the 3? > > > Loanet (after openning 8080 in > > firewall, still have Error: Cannot Connect to Server) > > Pape Group (OK) > > West Telemarketing (OK) > > These are probably HTTP Tunneling related. It would be > useful to note whether or not the client sees a IMPORTANT do not close > this window . I suspect many large corporations do not allow port 8080 > so it could cause these problems. If you do it in the production setup, > probably some or all of these will go away. So HTTP tunneling will fix essentially all? > > > Material Services (Error: Cannot Connect > > to Server) > > Lehigh Valley Hospital (Error: Cannot Connect to > > Server) > > Pitney Bowes (Error: Cannot Connect to > > Server) > > St. Vincent Hospital (OK) > > Western Union (Error: Cannot Connect to > > Server) > > > > * in all of the above cases, I made sure Sun JVM is not configured > > > > > ------=_NextPart_000_0037_01C2CF65.AAB1C9E0 > Content-Type: text/html; > charset="us-ascii" > Content-Transfer-Encoding: quoted-printable > > > xmlns:o=3D"urn:schemas-microsoft-com:office:office" = > xmlns:w=3D"urn:schemas-microsoft-com:office:word" = > xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" = > xmlns=3D"http://www.w3.org/TR/REC-html40"> > > > charset=3Dus-ascii"> > > > > > > > namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" > name=3D"PlaceName"/> > namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" > name=3D"PlaceType"/> > namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" > name=3D"place"/> > > > > > > style=3D'tab-interval:.5in'> > >
> >
> >

style=3D'margin-left:.75in;text-indent:-.25in;mso-list:l0 level1 lfo1; > tab-stops:list .75in'> face=3DWingdings> style=3D'font-size:12.0pt;font-family:Wingdings;mso-fareast-font-family:W= > ingdings; > mso-bidi-font-family:Wingdings'> style=3D'mso-list:Ignore'>Ø face=3D"Times New Roman"> Roman"'>      > Last week, we have = > continued to > try to use and show Impromptu to our
> > customers, which include TO DATE:
> > Park Nicollet Hospital (1st PC OK, 2nd time PC has Sun
> > JVM, no Admin right) style=3D'color:blue'>

> >

style=3D'margin-left:.75in;text-indent:-.25in;mso-list:l0 level1 lfo1; > tab-stops:list .75in'> face=3DWingdings> style=3D'font-size:12.0pt;font-family:Wingdings;mso-fareast-font-family:W= > ingdings; > mso-bidi-font-family:Wingdings'> style=3D'mso-list:Ignore'>Ø face=3D"Times New Roman"> Roman"'>      > This is a known issue.
> > Kaiser Permanente (Does not allow port
> > 8080 access)

> >

style=3D'margin-left:.75in;text-indent:-.25in;mso-list:l0 level1 lfo1; > tab-stops:list .75in'> face=3DWingdings> style=3D'font-size:10.0pt;font-family:Wingdings;mso-fareast-font-family:W= > ingdings; > mso-bidi-font-family:Wingdings'> style=3D'mso-list:Ignore'>Ø face=3D"Times New Roman"> Roman"'>       > face=3DArial> style=3D'font-size:10.0pt;font-family:Arial;color:blue'>For > production, you need 2 servers.  = > This was > the same issue with Avery.   = > So you run > web server on 1 machine on port 80. style=3D'mso-spacerun:yes'> Then > HTTP tunneling on the 3rd server on port 80. style=3D'mso-spacerun:yes'>  In this case, audio most likely = > will work > through SSL ports so no need for 3rd = > server.

> >

face=3D"Times New Roman"> style=3D'font-size:12.0pt'>
> > Loanet (after openning 8080 in
> > firewall, still have Error: Cannot Connect to Server)
> > Pape Group (OK)
> > West Telemarketing (OK) style=3D'color:blue'>

> >

style=3D'font-size: > 10.0pt;font-family:Arial;color:blue'> 

> >

style=3D'font-size: > 10.0pt;font-family:Arial;color:blue'> style=3D'mso-tab-count:1'>        = > ;     These > are probably HTTP Tunneling related. style=3D'mso-spacerun:yes'>  It > would be useful to note whether or not the client sees a IMPORTANT do = > not close > this window … style=3D'mso-spacerun:yes'>  I > suspect many large corporations do not allow port 8080 so it could cause = > these > problems.  If you do it in = > the production > setup, probably some or all of these will go = > away.

> >

face=3D"Times New Roman"> style=3D'font-size:12.0pt'>
> > Material Services (Error: Cannot Connect
> > to Server)
> > Lehigh = > Valley > Hospital (Error: Cannot = > Connect to
> > Server)
> > Pitney Bowes (Error: Cannot Connect to
> > Server)
> > St. Vincent = > Hospital > (OK)
> > Western Union (Error: Cannot Connect to
> > Server)
> >
> > * in all of the above cases, I made sure Sun JVM is not = > configured
> >

> >
> >
> >

face=3DArial> style=3D'font-size:10.0pt;font-family:Arial'>  nt>

> >
> >
> > > > > > ------=_NextPart_000_0037_01C2CF65.AAB1C9E0-- > > Geoffrey Fox gcf@indiana.edu FAX 8128567972 Phones Cell 315-254-6387 Home 8123239196 Lab 8128567977 CS 8128553788