Server configuration details
The servers and clients used by the Web DataWindow can run
on the same or different machines. The following diagram shows typical configurations
with the Web server and page server on the same machine and the
component server and database on separate machines, but any or all
of the servers can run on the same computer. In your development environment,
the client browser could be on the same computer too.
Using the Web DataWindow
with PowerDynamo
If you install EAServer and PowerDynamo on the same computer,
most of the configuration is done for you. You can use PowerBuilder
Web Target wizards to perform any additional setup tasks.
However, if you design your own custom class user objects,
you must generate and compile the stubs, making sure that the compiled
stubs are included in the PowerDynamo class path.
CLASSPATH environment variable If you are not running your Web server as a service and you
have a user CLASSPATH environment variable, make sure that this
variable includes the paths to all classes needed for communication
between the Web server and the component server. This includes the
SybaseEAServerhtmlclasses directory and
the path to any component stubs that you generate for use with your
Web pages (if these are in a different directory). When you install EAServer,
the path information for the server is placed only in the system
CLASSPATH variable, not the user variable.
Using the Web DataWindow with Tomcat
To use Web DataWindows
and access EAServer components in JSP pages that you deploy to a
Tomcat server, you must add the following JAR files and classes
to the class path used by Tomcat at startup:
- pbjdbc1290.jar
- jconn2.jar
- easclient.jar
- easj2ee.jar
- EAServer_homehtmlclasses
- EAServer_homejavaclasses
where EAServer_home is the full
path to the EAServer where the Web DataWindow component is installed.
To add the required files to the Tomcat class path, you need to
edit the catalina.bat file in the Tomcat bin directory.
Using the Web DataWindow with a COM component
You can also use the Web
DataWindow with Microsoft servers, but more configuration tasks
are required. On MTS or IIS,
you access the COM version of the generic server component (PowerBuilder.HTMLDataWindow)
using automation methods called from any page server, such as PowerDynamo
or ASP. For example, to instantiate the generic COM component from
ASP:
|
1 |
dwMine = Server.CreateObject(<br /> "PowerBuilder.HTMLDataWindow") |
The COM server component is provided in PBDWR90.DLL.
You can also write your own custom class user object based on the
sample source code in PBDWRMT.PBL.
For more information about building Web pages that use the
Web DataWindow server component, see “Instantiating and configuring
the server component”.
You need to register the COM server component and install
PowerBuilder runtime files and the PBL or PBD containing your DataWindow
objects on the MTS or IIS server
computer.
Transaction server configuration
tasks
The following table summarizes the configuration tasks you
need to perform on the transaction server:
| Server | Tasks | ||
|---|---|---|---|
| EAServer, IIS, or MTS |
Copy the PBLs, PBDs, SRDs, or PSRs containing the definitions of your DataWindow objects to a directory on the EAServer server’s path or the system path if the server component is running as a service (always true for MTS or IIS). |
||
| EAServer | Set up a DSN and a connection cache for your data source. |
||
| IIS or MTS |
|
||
| MTS | If MTS is hosting the server component and running on a different computer from IIS, create a client install package using MTS Explorer and install it on the IIS machine. For more information, see the MTS documentation. |
Page server configuration tasks
The following table summarizes the configuration tasks you
need to perform on the page server:
| Server | Tasks |
|---|---|
| PowerDynamo or ASP | Copy the HTML pages, scripts, images, and other application files to the page server. You can use the Web target deployment controller for PowerDynamo or ASP to copy them to the server. |
| JSP | Copy the JSPs, custom tag libraries, scripts, images, and other files to the page server. You can use the Web target deployment controller for JSP to copy them to the server. Although a custom tag library you add to a page is placed For information about the Web DataWindow custom tag library, see |
| PowerDynamo (with any component server) | Create a Web site and define a mapping in Sybase Central that associates the connection profile for your database with the Web site pathname you will use in the URL. (The PowerDynamo Web Site target wizard can do this for you.) |
| PowerDynamo (with EAServer as the component server) | If PowerDynamo and EAServer are not installed on the same computer:
In Sybase Central, open the General Settings folder in the PowerDynamo Configuration |
| ASP (with EAServer as the component server) | If ASP and EAServer are not installed on the same computer:
If you designed your own custom class user object, generate TLB |