Try OpenEdge Now
skip to main content
Introducing PAS for OpenEdge
Overview of WebSpeed Support in PAS for OpenEdge : What's new and different in WebSpeed on PAS for OpenEdge
 

What's new and different in WebSpeed on PAS for OpenEdge

These are some of the issues that you should take into account if you are migrating from classic WebSpeed to WebSpeed on PAS for OpenEdge.
*PAS for OpenEdge supports the three most common types of WebSpeed Web objects: static HTML, Embedded SpeedScript, and CGI Wrapper. It does not support HTML Mapped Web objects.
You should be able to migrate existing Web objects (other than HTML Mapped Web objects) to PAS for OpenEdge with few, if any, changes.
Basically, migration is just a matter of moving static and application files to the PAS for OpenEdge instance. Static files should be copied to the instance's /webapps/web_application/static directory. The standard location for application files is a directory under an instance's /openedge folder. Add any folders that contain WebSpeed application r-code files to the instance agent's PROPATH. See Migrating classic WebSpeed applications and Migration notesfor more information.
*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. WebSpeed application developers often modified web-disp.p to customize the Web object execution environment.
The web-disp.p control program does not exist in PAS for OpenEdge. Web object execution is controlled by a built-in handler object, web-handler.p. This default handler can be modified to implement any web-disp.p customizations that you want to replicate. However, you cannot migrate web-disp.p to a PAS for OpenEdge instance.
*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).
*PAS for OpenEdge supports standard HTTP verbs and status codes. Classic WebSpeed only supports GET and POST, and did not allow you to control status codes.
*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.
*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.
*WebSpeed Workshop is not supported for 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.
*The classic WebSpeed utilities WSCONFIG and WTBMAN are not supported. Use the TCMAN utility for configuring and managing WebSpeed on PAS for OpenEdge.
For more information on configuring and managing WebSpeed on PAS for OpenEdge, see Progress Application Server for OpenEdge: Administration Guide. For more information on application migration and development, see Progress Application Server for OpenEdge: Application Migration and Development Guide.