Trace files

When the Presentation Client is executed as an applet in a browser, tracing information is written to the Java Console instead of the usual log file. You can cut and paste directly from the console if you need to get the tracing information. Although, this is also written to the trace file by the console when the Presentation Client is executed. The following extract is from the Java plug-in documentation:

"Java Plug-in Trace File: Similar to the Java Plug-in Console, this is a file that records all the System.out and System.err messages. The trace file is disabled by default but is automatically enabled when the Java Plug-in Console is enabled. The trace file is normally located in user.dir, and the file is called .plugin<version>.trace. For example, in Windows NT this file is located in C:\WINNT\Profiles\<username>\.plugin<version>.trace."

An <APPLET> tag example:

<APPLET
      archive="LINCViewer.jar,xmlParserAPIs.jar,xerceslmpl.jar,jh.jar,ViewerHelp.jar"
      name="LINCApplet"
      code="com.unisys.jellybeans.views.LINCViewerApplet"
      codebase="http://MyServer/MyClasses"
      width=380 height=70>
<param name="config" value="<configuration file name>">
<param name="system" value="<name of the system with which to connect>">
</APPLET>

Of particular interest in this example are the following attributes:

archive – Lists the .jar files required to run the Presentation Client.
codebase– Specifies the location of the .jar files and generated classes required to run the Presentation Client.
config and system parameters – Specify the name of the configuration file to use and the system with which to connect.

An <OBJECT> tag example:

<OBJECT
      classid="clsid:8AD9C840-044E-11D1-B3E9-00805F499D93"
      name="LINCApplet"
      width="380" height="70"
      codebase="http://java.sun.com/products/plugin/1.4/jinstall-14-
      win32.cab#Version=1,4,0,0">
<PARAM NAME="code" VALUE="com.unisys.jellybeans.views.LINCViewerApplet">
<PARAM NAME="type" VALUE="application/x-java-applet;version=1.3">
<PARAM NAME="codebase" VALUE="http://MyServer/MyClasses"
<PARAM NAME="name" VALUE="LINCApplet">
<PARAM NAME="archive" VALUE="LINCViewer.jar,xmlParserAPIs.jar,xercesImpl.jar,jh.jar,ViewerHelp.jar">
<PARAM NAME="config" VALUE="<configuration file name>">
<PARAM NAME="system" VALUE="<name of the system with which to connect>">
<br>This browser does not support the Java Runtime Environment v1.3 and above, in
order to run the Presentation Client Applet!
</OBJECT>

Of particular interest in this example are the following attributes:

classid – Specifies the class identifier for the installed Java plugin. For dynamic version support, you should use the classid shown in the example.
codebase – Specifies the location of a .cab file somewhere on the network. This allows download and installation of the plugin on the user's workstation when necessary. The example shows a URL pointing to a page on the Java Software website.
type parameter – Indicates the type of object being used and the required version of the plugin. The example shows the settings for dynamic versioning of a Java applet. The lowest level of the plugin required for the Presentation Client is JRE 6.0.

Note: Due to enhancements in the Java Runtime environment, it is recommended that the latest version of the JVM is used where possible.

An <EMBED> tag example:

<EMBED
      type="application/x-java-applet;version=1.3"
      width="380" height="70"
      name=LINCApplet"
      codebase="http://MyServer/MyClasses"
      code="com.unisys.jellybeans.views.LINCViewerApplet"
      archive="LINCViewer.jar,xmlParserAPIs.jar,xercesImpl.jar,jh.jar,ViewerHelp.jar"
      pluginspage="http://java.sun.com/j2se/1.4.1/download.html"
      config="<configuration file name>"
      system="<name of system with which to connect>">
<NOEMBED>
<br>This browser does not support the Java Runtime Environment v1.3 and above, in
order to run the Presentation Client Applet!
</NOEMBED>
</EMBED>

Of particular interest in this example is the following attribute:

pluginspage – Specifies the URL of an HTML page from where the Java plugin can be downloaded and installed when required.

Refer to Oracle’s Java website at http://www.oracle.com/technetwork/java/index.html for more information on how to use the Java plugin with various browsers.

In all the examples, the <configuration file name> value specifies the name of the configuration file to be loaded by the Presentation Client. The name must be expressed as an HTTP URL, typically in the following form:

http://<server>/<directory>/<file name>

For example:

<param name="config" value="http://MyServer/sample/config.xml">

To automatically establish a connection between the Presentation Client and the required system, the system parameter can be included, where value equals the system name defined in the configuration file:

<param name="system" value="Sample">

The HTML tag used to run the Presentation Client, instructs the browser to load and run the Component Enabler applet environment code, identified by com.unisys.jellybeans.views.LINCViewerApplet. The Presentation Client applet loads and runs the forms and data components generated from the Agile Business Suite System definition.

Note: Java applets normally run within the browser window that contains the applet initiation tag (that is, <OBJECT>, <EMBED>, or <APPLET>). The Presentation Client applet creates a separate window to accommodate its own menu bar. However, it is still linked to the browser window from which it was initiated. If the user closes the browser window, the Presentation Client window also closes. The supplied sample HTML page takes some measures to avoid this situation. The results however, vary between browsers, depending on the events that are supported. The sample home page dynamically creates a new browser window and initiates the Presentation Client in the new window. This leaves the user free to navigate away from the home page if desired. The Presentation Client is linked to the new dynamic browser window and continues to run unaffected.

You can load components from a .jar file or directly from the Web server, one at a time. You can also use a combination of these parameters as in the previous example, and load the Component Enabler components from the .jar file and the IspecModels selectively.

To load classes from a .jar file, specify the name of the .jar file with the achive parameter. Because Component Enabler might contain many components, it is usually more efficient to use a .jar file for loading Component Enabler.
You can download generated classes or IspecModels one at a time from a Web server using the codebase parameter. The codebase parameter specifies the URL where the components are located. This is only necessary if the class tree is in a different directory from the HTML files.

It is recommended that the site administrator define generic parameters in the configuration file to support all user requirements, as multiple users might access the HTML pages using different browsers.