Novell Home

My Favorites

Close

Please to see your favorites.

Configuring iChain to work with the DigiChat client.

(Last modified: 06Jun2006)

This document (10096546) is provided subject to the disclaimer at the end of this document.

goal

Configuring iChain to work with the DigiChat client.

fact

Novell iChain

Novell iChain 2.3

Novell iChain 2.2

DigiChat

fix

There are a variety of ways that iChain can be configured to work successfully with the Digi-Net Technologies' DigiChat client.  Following is a description of the changes that were made for this particular implementation.  For complete documentation on DigiChat, including an explanation of all the available options, please consult the DigiChat documentation.

This configuration was used to enable the DigiChat client to work when referenced from the customer's main website.  For the purposes of this TID we will say that the site being accelerated is http://www.mysite.com/.

The main content for the www.mysite.com web site is located on a different server than will host the DigiChat software.

In addition to the main accelerator for this site (mysite), two additional child accelerator services were created.  These child accelerator services are path-based multi-home services (digichat and digiserv).  Pertinent items of the configuration are as follows:

digichat accelerator (used for the DigiChat client applets)

  • Name: digichat
  • DNS name: www.mysite.com
  • Web server addresses: (ip address of DigiChat server)
  • Enable multi-homing
    • Multi-homing Options
      • Path-based multi-homing
      • Sub-path match string: /DigiChat
      • Do not remove sub-path from URL
    • Multi-home master: mysite

digiservlet accelerator (used for the HTTPTunnelingServlet)

  • Name: digiserv
  • DNS name: www.mysite.com
  • Web server address: (ip address of servlet server running Tomcat)
  • Web server port: 8080 (default Tomcat port)
  • Enable multi-homing
    • Multi-homing Options
      • Path-based multi-homing
      • Sub-path match string: /servlet/HttpTunnelingServlet
      • Do not remove sub-path from URL
    • Multi-home master: mysite

Once these accelerator services are configured appropriately, the HTML page containing the instructions for starting the DigiChat client needs to be modified accordingly.  Specifically, the lines referencing the APPLET CODEBASE and HttpServlet parameters need to be present and configured appropriately for the above configuration.  Following are example lines used in this configuration:

  •    <APPLET NAME='DigiChat' CODEBASE='http://www.mysite.com/DigiChat/DigiClasses/'>
  •    <PARAM NAME='HttpServlet' VALUE='http://www.mysite.com/servlet/HttpTunnelingServlet'>

The above lines should be specified in the appropriate location in the HTML page as specified by the DigiChat documentation (referenced above).

For this configuration the following ports would need to be open on any firewalls between iChain and :

  • 80 from Internet to iChain
  • 80 from iChain to DigiChat server
  • 8080 from iChain to servlet server

note

If the site used to host the DigiChat applet(s) is also configured to use Secure Exchange, an additional change is necessary for the digichat accelerator service.  To work around an IE "feature", check the "Allow pages to be cached at the browser" option.  IE has problems displaying/downloading certain types of content (including .cab files) from an HTTPS web server if the "Content-control: no-cache" and "Cache-control: no-store" headers are present in the HTTP response.  Checking this option in iChain prevents these headers from being added, allowing IE to function as expected.

Additionally, if SecureExchance is enabled it will also be necessary to open port 443 between iChain and the Internet.

It should be noted that an alternate proxy configuration was not tested, which may not have required the use of the HttpTunnelingServlet.  This alternate configuration would have had another accelerator service created as a tunnel service for port 8396 (a default DigiChat port), redirecting the traffic from the iChain box directly back to the DigiChat server on the same port.  If this configuration had been used the chat client would likely have worked with fewer changes, without requiring the use of the HttpTunnelingServlet on the Tomcat server or the accompanying path-based child accelerator service, thereby eliminating an additional possible point of failure.  Following is a list of pertinent parameters for this alternate accelerator configuration:

  • Name: digitunl
  • DNS name: www.mysite.com
  • Act as a tunnel (check this box)
  • Web server addresses: (ip address of DigiChat server)
  • Web server port: 8396 (or 58396 if preferred)
  • Accelerator IP addresses: (same ip address as for www.mysite.com)
  • Accelerator proxy port: 8396 (or 58396 if preferred - should match web server port chosen above)

For this configuration to work, port 8396 (or 58396 if preferred) would need to be open on any firewalls between the iChain box and the Internet, as well as between the iChain box and the DigiChat server.

disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.

  • Document ID:
  • 10096546
  • Solution ID: NOVL100943
  • Creation Date: 07Feb2005
  • Modified Date: 06Jun2006
    • NetIQiChain

Did this document solve your problem? Provide Feedback