Try OpenEdge Now
skip to main content
Online Help
Introducing WebSpeed support in Progress Developer Studio for OpenEdge : Tasks : Creating a WebSpeed project
 

Creating a WebSpeed project

A WebSpeed project is an OpenEdge project specifically tailored for WebSpeed application development. It is usually configured with a WebSpeed server and an HTTP Server, which are servers based on the Eclipse Web Tools Platform. The primary function of these servers is to support publishing your code for running, testing, and deploying your application.
To verify that these servers are running, check the Servers view. The Servers view is one of the default views in the OpenEdge Server perspective. If it is not visible, you can start it by selecting Window > Show View > Other > Server > Servers. In the Servers view, you should see:>
*a WebSpeed server associated with a particular WebSpeed broker (for example, wsbroker1 WebSpeed 11.0 at mymachinename)
*an HTTP Server associated with a host that is running a Web server (for example, HTTP Server at localhost)
You can create either or both of these servers, or add additional servers to your workspace before you create your WebSpeed project. See Managing Eclipse WTP servers for more information. You can also create the project first and configure the servers afterward.
To create a WebSpeed project:
1. Select File > New > OpenEdge Project from the Progress Developer Studio for OpenEdge main menu bar or the Project Explorer view context (right-click) menu. The New OpenEdge Project wizard opens and displays the Create an OpenEdge Project page.
2. Type a name in the Project name field.
The root folder for the new project is created in your current Eclipse workspace, unless you specify a different location.
3. To choose a different location for the project, click and clear the Use default check box. Then either browse to, or enter the path to the desired location.
4. Select Client from the left section.
5. Select the Web Application option button and select the WebSpeed option button.
6. Click Next. The Select AVM and layout options page appears.
7. Choose whether to use a project-specific or a shared AVM.
8. Leave Use TTY for runtime selected.
By default, WebSpeed projects use TTY for the runtime environment. The only reason you would deselect this option is if you intend to enable a facet for this project that substitutes some other runtime environment.
9. Select the default project layout.
Leave Use project root directory for source and r-code selected if you intend to store source and r-code in the same folder. Choose the Use separate source and r-code directories option if you want to customize the default file location for source and r-code.
10. Click Next. The Define WebSpeed dynamic content module page appears.
11. Type a name in the Module name field. The default is the project name.
Modules are project directories that contain the source code that you intend to publish.
12. Type the location of source files in the WebSpeed source folder field.
The default is a folder named WebSpeed, which will be created as a child of the project folder if you chose Use project root directory for source and r-code. in step 8. If you chose the Use separate source and r-code directories option, the folder will be a child of whatever you specified in the Source directory field.
13. Select the WebSpeed server from the list of supported servers that will be the destination for your published web objects.
The primary function of these servers is to support publishing your code for running, testing, and deploying your application. The default list contains two servers named:
wsbroker1 WebSpeed OE_Versionathost_name
wsdynamics WebSpeed OE_Versionathost_name
Select wsdynamics only if you are using the Progress Dynamics framework as a development environment.
If there are no available servers, you can create them and associate them with the project after you finish creating the project.
14. Type a destination folder for the .w files that are generated when SpeedScript files are compiled. The default is SpeedScriptGen in the project root folder.
15. Click Next. The Define static web content module page appears.
16. Type the name of the destination folder where static HTML pages will be published in the Context root field.
The folder will be created as a child of the scripts folder on your web server. The default is to use the same name as the project.
17. Type the name of the folder in the project where static HTML source files will be saved. The default is HTML Content in the project root directory.
18. Select the Web server static from the list of supported servers where static content should be published.
19. Click Next. Specify the PROPATH to use for the project.
20. Click Next. Specify the database connection(s) to use for the project.
21. Click Finish. If the OpenEdge Server perspective is not already open, you will see a message asking if you want to open it. Since the OpenEdge Server perspective supports WebSpeed application development, you should click Yes.
You will see your project and its resources in the project view. Your next step is Configuring WTP servers.