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.
Two types of files are required on the transaction server:
The PBLs or PBDs containing the definitions of your DataWindow objects
Make sure they are installed in a directory in the server’s path. If EAServer is running as a service, they must be on the system path or the names of the PBLs or PBDs must be fully qualified.
PowerBuilder runtime files (including pbvm125.dll, pbshr125.dll, pbjag125.dll, and pbdwe125.dll on Windows) and pbdwr125.pbd, which contains the implementation of the DataWindow HTMLGenerator125 component
You can use the PowerBuilder VM installer, available in the PBVM folder on the DVD, to install these files. For more information about required files, see “PowerBuilder components on EAServer”.
You also need to create a connection cache for the database the component will access. For more information, see the DataWindow Programmers Guide.
Custom 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 Programmers Guide.
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.
EAServer client software for Java The files listed in Table 36-15 are required on the 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 or Sybase\Shared\Sun directory, depending on the version of EAServer you are using. 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 or later, make sure that the JRE\bin\client subdirectory of the JDK is listed in the system PATH environment variable.
