Developing applet client code

 

Overview

Applet clients have the following setup requirements:

• These clients are available on the Windows XP or Windows 2000 platforms. Check the prerequisites page for information on new platform support.

• They require one of these browsers:

  • Internet Explorer version 5.0 and later

  • Netscape Browser 4.7

  • Netscape version 6.x or 7.x

  • Mozilla version 1.x

• 

  Application clients support Netscape browsers and Mozilla browsers on Windows systems. However, the Applet application client MIME type used in V5.1 and previous releases of the product is not supported in WebSphere Application Server application clients, V5.1.1. Because the product supports Software Development Kit V1.4.2, the Applet application client MIME type is not provided.

  Prior to V5.1.1, you needed to use the product applet client MIME type, application/x-websphere-client, in a Netscape version 4.x browser. However, since both Netscape version 6.x or 7.x browsers and Mozilla browsers are now supported, use the standard Java Applet MIME type in your applet HTML page. For example,

  application/x-java-applet;jpi-version=1.4
  application/x-java-applet;jpi-version=1.4.2

  If your applet HTML page is still referring to the WebSphere Applet Client MIME type, application/x-websphere, change the reference to the standard Java Applet MIME type. For more information, see the Sun Microsystems article, "Java Mime Type ."

• The browser installation precedes the client code installation.

 

Overview

Unlike typical applet clients that reside on either Web servers or WebSphere Application Servers and can only communicate using the HTTP protocol, applet clients are capable of communicating over the HTTP protocol and the RMI-IIOP protocol. This additional capability gives the applet client direct access to enterprise beans.

1. Run the WebSphere Application Server clients installation.

2. Select the Applet client option.

3. Install the Applet client.

4. Install the WebSphere Application Server plug-in for the browser. The installation creates the following Java Runtime Parameters for the Java Plug-in for the user who installed the Applet client.

   -Djava.security.policy=<product_installation_dir>\properties\client.policy
   -Dwas.install.root=<product_installation_dir>
   -Djava.ext.dirs=<product_installation_dir>\classes;
   <product_installation_dir>\java\jre\lib\ext;
   <product_installation_dir>\java\jre\lib;
   <product_installation_dir>\lib;<product_installation_dir>\properties
   -Dcom.ibm.CORBA.ConfigURL=file:<product_installation_dir>\properties\sas.client.props
   -classpath <product_installation_dir>\properties

   Note: If a user other than the one who installed the applet client runs an applet client sample, then that user must enter these entries.

   • The Java Run-Time Parameters field is similar to the command prompt when using command line options. Therefore, you can enter most options available from the command prompt (for example, -cp, classpath, and others) in this field as well.

   • Start the Java Plug-in control panel.

     There are two ways to start the IBM Java Plug-in control panel, and set the Java Virtual Machine (JVM) run-time properties for the Applet client:

     1. Select the icon, Java Plug-in, located in the Windows control panel.

     2. Execute the following command: <install_root>/java/jre/bin/IBMJavaPlugin142.exe to launch the IBM Java Plug-in control panel.

   • The Java Run-Time Parameters field is in the Advance tab of the Java Plug-in control panel.

   • The applet container is the Web browser and the Java plug-in combination. You must first install the WebSphere Application Server Applet client so that the browser recognizes the IBM product Java plug-in.

   View the Samples gallery for more information about application clients. Before you run the basicCalculator Sample, ensure the JMS Server is started.

---

Applet client tag requirements
Applet client code requirements
    

 

---