wIntegrate - Java client demo instructions


See the wIntegrate Administration manual more information about:

  • how the Java client works
  • installation
  • the Administrator
  • the Monitor
Install wIntegrate Server

The Java client is a screen-and-keyboard interface to the core wIntegrate functionality executing in the wIntegrate Server, normally running on a remote server.

Run SetupServer.exe to install the wIntegrate Server. You'd normally install the wIntegrate Server to a remote server, but for testing purposes you can install it to your own PC.

Installing the wIntegrate Server automatically installs the Administrator. You might also want to install the Monitor using SetupMonitor.exe.

Install Windows thin client

We recommend you install the Windows client using SetupClient.exe. Though the Windows client is not essential to run the Java client, it makes sense to get it working before attempting to use the Java client.

With the Windows client running, you can try the Administrator and Monitor.

Install Java client

The files for the Java client are installed with the wIntegrate Server, provided you turn on the Java Client option during installation. These files are installed in the Program Files\wIntServ\wIntJava folder:

  • wIntJavaPage.htm - the example HTML page with the Java client
  • wIntJavaApplet.jar - the Java client code
  • Instructions.htm - how to use the Java client (this page)
  • wIntjc.css - the stylesheet used by the html pages
  • wIntJava.gif - a customisable image shown on the initial login. You can save your own GIF image with the name wIntJava.gif. You might want the image to represent the server from which the page is running. The image is not restricted to 32x32 pixels.
  • - a zipped file containing help in HTML format. If you want to make help available to users of the Java client, these files should be copied to your server.

You may want to edit the wIntJavaPage.htm file to change the PARAM fields Host and UserName for the wIntegrate Server.  These are the same as you would enter into the login for the Windows client, and not the login to your host U2 server.

Note that it is the classid field which specifies that the Java runtime is present, otherwise it is downloaded.

If the wIntegrate Server is not on the same machine as the Web Server, the security must be set to allow the applet to connect to another server.

The HTML page can run the Java applet in two different ways. By default the Java client runs as a standard applet, which is compatible with Java on all hardware platforms. Alternatively, if you're experienced in HTML, you can comment out the applet code and comment in the code which uses the Java plugin for Windows. This technique will only work on Windows.

You can make dialogs appear as separate popups on top of the character screen, or in the browser replacing the character screen. Use the embeddialogs parameter to set the default behavior, then use the DialogBox Options E and P to override the default setting. See the parameters in the wIntJavaPage.htm file.

Applet security

The Java client contains an SSL certificate. When you run the applet a dialog will appear telling you about the certificate. It asks if you trust the publisher. There are three possible answers:

  • Yes: trusts the publisher for this execution only
  • No: runs the applet in a sandbox without access to your PC's resources, such as the hard disk.
  • Always: trusts the applet and allows access to the machine's resources indefinitely.