Web DataWindow on EAServer

You can run the Web DataWindow server component on EAServer using JSP as the page server. The component transaction server and the page server can run on the same or on different computers.

Files required on the transaction server

Two types of files are required on the transaction server:

You also need to create a connection cache for the database the component will access. For more information, see the DataWindow Programmer’s Guide.

NoteCustom components You can create a custom version of the DataWindow component and configure its properties for more efficient reuse. For more information, see the DataWindow Programmer’s Guide.

Files required on the dynamic page server

To use JSP as the page server and connect to the EAServer component using Java, you must have the following files on the JSP server computer:

HTML pages, templates, and scripts These are the files that you created for your application. If you used a JSP target to generate these files, you can use the built-in deployment controller to install them. For more information, see Working with Web and JSP Targets.

EAServer client software for Java The files listed in Table 41-19 are required on the JSP server.

Table 41-19: EAServer client files required on JSP server

Name

Description

easclient.jar

Java class required for clients

easj2ee.jar

Java class required for J2EE support

Sun Java Development Kit (JDK) Any versions of the JDK that were installed with EAServer are located in the Sybase\Shared\Sun directory. The JDK that is installed with PowerBuilder is located in the Sybase\Shared\PowerBuilder directory.

If you are using JDK 1.2 or 1.3, make sure that the JRE\bin\classic subdirectory of the JDK is listed in the system PATH environment variable.

If you are using JDK 1.4, make sure that the JRE\bin\client subdirectory of the JDK is listed in the system PATH environment variable.