This section describes some basic guidelines for building a Java program using the Host Access Beans. For information on how to use the Host Access Beans in a JavaBeans Visual Development Environment such as Sun's BeanBox or the IBM WebSphere Studio Site Developer, see Using Host Access Beans in Visual Development Environments.
This section does not cover all the topics necessary to use your Host Access Beans program in a browser. For topics such as security and making classes visible in the browser environment, please see your browser documentation.
Java programs that use the Host Access Beans must import the Host Access Beans packages to obtain class definitions and other compile-time information. The Host Access Beans packages can be imported into a Java source file using the following statements:
import com.ibm.eNetwork.beans.HOD.*; import com.ibm.eNetwork.beans.HOD.event.*;
Some Host Access Beans methods require use of Host Access Class Library (HACL) constants. To use the HACL classes, Java programs must import the Host Access Class Library package by using the following statement:
import com.ibm.eNetwork.ECL.*;
Host Access Beans files are located in the install_dir\toolkit\jars directory, where install_dir is the directory where you installed the Host Access Toolkit files. Both Java 1 and Java 2 environments are supported. Java archive (JAR) and cabinet (CAB) files for the Java 1 environment and JAR files for the Java 2 environment are located in the following directories:
where install_dir is the directory into which the Toolkit files are installed (by default, C:\Program Files\IBM\Host Access Toolkit). The following files contain full Host Access Beans support (except for a few noted exceptions):
These files are suitable for Bean Builder environments and for writing Java applications. However, since they are not signed, they are not suitable for downloading over the web through a web browser.
For downloading applets, the Host Access Beans support has been divided into several smaller signed component archive files. JAR files are provided for Netscape and Appletviewer environments and browsers that support a Java 2 plug-in. CAB files are provided for Microsoft Internet Explorer environments. Since download delays are important in web browser environments, the component archive files will allow users to specify only those components which will actually be used and will avoid costly delays of downloading support that will never be used.
To further optimize download times, release versions of the components are also provided. The release versions of the components have the trace code removed which means they will be smaller and download faster than their debug counterparts. Most users will predominantly use the release versions of the components for web environments and only use the debug versions when problem determination is required. For Java application environments, users can use either release or debug components (or even the habeans.jar file) since download times are not a factor.
Most components have debug and release versions, stored in subdirectories of the same name. However, some components, such as host code pages, only have a release version. Except for the host code page archives, you cannot mix some release versions and some debug versions. If problem determination is needed, or you are using debug components since download times are not important, you must use all debug components.
The table shown below shows all the different components, their release and debug names, and the components that they depend on.
Note: Except for hafntib, hafntap, hafnthe, hafntar, and the host code pages, the Java 2 versions of these components have a "2" on the end of the JAR file name (for example, habase2 and habasen2).
SSH (Secure Shell) support. Java 2 required. The Java 1 jar/cab files are dummy ones. |
||||
The following table shows the component names for the host code pages:
All applications will use the habase (or habeans) and hacp archive files since those contain the core Host Access Beans files and core codepage files respectively.
To successfully compile and run your application, the CLASSPATH environment variable must be updated to include the JAR files needed by your application. For example, if you need 5250 file transfer, you would need to include ha5250xn.jar, ha5250n.jar, haxfern.jar, and hamacrtn.jar in your CLASSPATH. You can also set the classpath using the Java compiler's -classpath parameter when compiling your application.
To find the Host Access Beans classes in the jar file, the classpath variable (or -classpath parameter) must point directly to the jar files. For example, if your application uses 3270 and SSL functions, and the JAR files are located in the c:\jars directory, the classpath should look like this:
CLASSPATH=c:\jars\habasen.jar;c:\jars\hacp.jar;c:\jars\ha3270n.jar;
c:\jars\hassln.jar
When an applet that uses the Host Access Beans is run in a browser environment, the browser must be able to find the Host Access Beans classes. See your browser documentation for information on how to expose classes in the browser environment.
When running an applet using the appletviewer or running your program as
an application, you need to make sure the CLASSPATH environment variable contains the
fully qualified path name of the Host Access Beans JAR files used.
Optionally, you can use one of three loadable applet interfaces:
com.ibm.eNetwork.HOD.common.cached.LoadableAppletInterface
com.ibm.eNetwork.HOD.common.cached.WSLoadableAppletInterface
com.ibm.eNetwork.HOD.common.cached.LoadableJSAppletInterface
[ Top of Page | Previous Page | Next Page | Table of Contents ]