Beginning in OpenEdge Release 11.6, Pacific Application Server (PAS) for OpenEdge is available as a host for WebSpeed applications
You can migrate existing WebSpeed applications to PAS for OpenEdge, or you can use the Progress Developer Studio for OpenEdge to develop new WebSpeed applications that run on PAS for OpenEdge.
The most notable differences between WebSpeed on PAS for OpenEdge and classic WebSpeed are:
- WebSpeed Workshop is not supported for WebSpeed on PAS for OpenEdge.
- The classic WebSpeed utilities WSCONFIG and WTBMAN are not supported. Use the TCMAN utility for configuring and managing WebSpeed on PAS for OpenEdge.
- Classic WebSpeed's configuration properties are specified in a ubroker.properites file. On PAS for OpenEdge, WebSpeed configuration properties are specified in an instance's /conf/openedge.properties file.
- PAS for OpenEdge supports the three most common types of WebSpeed Web objects: static HTML, Embedded SpeedScript, and CGI Wrapper. But, it does not support HTML Mapped Web objects.
- The ABL DISPLAY statement is not supported for WebSpeed applications running on PAS for OpenEdge.
- In classic WebSpeed, applications ran under a WebSpeed Transaction Server, which employs a control program, web-disp.p, that runs on all agents and executes Web objects. This control program does not exist in PAS for OpenEdge. Web object execution is controlled by a built-in handler object (web/object/web-handler.p), which can be modified to implement any web-disp.p customizations that you want to replicate.
- PAS for OpenEdge does not support stateful applications in the same way they are supported in classic WebSpeed. In classic WebSpeed, a WSEU cookie instructs WebSpeed to lock an agent process to a specific client. Instead of locking an agent process, PAS for OpenEdge maintains a stateful application by using JSESSIONID cookies. They are passed between the client and the server, and refer to session data stored on the server.
Some of the advantages of WebSpeed on PAS for OpenEdge compared to classic WebSpeed are:
- WebSpeed on PASOE employs a more integrated architecture compared to classic WebSpeed because both the Web server and the WebSpeed Transaction sever are combined in a single instance.
- WebSpeed on PASOE is more efficient than classic WebSpeed regarding the management and the availability of the agents that handle client requests.
- Classic WebSpeed only supported the GET and POST HTTP verbs.WebSpeed on PASOE supports all standard HTTP verbs.
- WebSpeed on PASOE supports event procedures that were not supported on classic WebSpeed.
- PAS for OpenEdge includes support for multiple servers in a single instance; you do not need to configure and run separate Web server, WebSpeed Transaction server, and AppServer instances.
- PAS for OpenEdge shares a single security context among the WEB transport that supports WebSpeed and the other transports (REST, SOAP, and APSV).
- Security issues that are inherent in CGI-compatible Web servers for classic WebSpeed are absent from the Pacific Application Server.
- Application deployment in WebSpeed on PAS for OpenEdge is simplified because all files (static, dynamic, executable) can be combined in a single package.
- Classic WebSpeed only supports a limited set of file types for uploading.WebSpeed on PAS for OpenEdge supports all media types for uploading and downloading.You can now, for example, stream binary files, PDFs, etc.
- If you are creating new WebSpeed applications, you can take advantage of an ABL-based OpenHTTP object oriented layer for Web application development (similar to Java servlet APIs).
- Classic WebSpeed does not have access to a number of server attributes of the SESSION system handle. PAS for OpenEdge can access the following attributes:
- SERVER-CONNECTION-BOUND
- SERVER-CONNECTION-BOUND-REQUEST
- SERVER-CONNECTION-CONTEXT
- SERVER-CONNECTION-ID
- SERVER-OPERATING-MODE
- The following new classes were added to the ABL to support creating handlers for WebSpeed and other HTTP Web applications:
- OpenEdge.Web.WebHandler class
- OpenEdge.Web.WebResponseWriter class
- OpenEdge.Web.WebResponse class
- OpenEdge.Web.WebRequest class
- OpenEdge.Web.CompatibilityHandler class
Classic Webspeed allows GUI widgets to be realized where the PASOE doesn't.This is because Classic WebSpeed is not running in batch mode, even though it's running as a background process.
The PASOE does run in batch mode. See Article:
The following Article provides further reference materials and caveats to consider when migrating a classic Webspeed application to PASOE :
