Try OpenEdge Now
skip to main content
Online Help
Introducing WebSpeed support in Progress Developer Studio for OpenEdge : Tasks : Managing Eclipse WTP servers : Creating a WebSpeed server
Creating a WebSpeed server
You create a WebSpeed server to handle the publishing of your code to a specific WebSpeed broker. The broker can be local or remote. You create multiple WebSpeed servers when you want to publish to a number of brokers and runtime environments. Typically, you would create at least one WebSpeed server for your development environment and another for your deployment environment.
To create a WebSpeed server:
1. From the main menu bar of Progress Developer Studio for OpenEdge, select File > New > Server. The New Server wizard appears.
An alternative method is to right-click on the Servers view in the OpenEdge Servers perspective and select New > Server from the context menu.
2. On the first page of the New Server wizard, choose OpenEdge WebSpeed from the Select the server type list.
3. If necessary, change the defaults for Server's host name, Server name, and/or Server runtime environment.
Note: By default, the only available runtime environment is the OpenEdge 11 AVM. You can add other available versions of the OpenEdge AVM after clicking Add. Or, you can click Configure runtime environments to add, remove, or edit runtime environments.
4. Click Next. The Define a new WebSpeed broker page opens.
5. Choose an OpenEdge Explorer connection.
The OpenEdge Explorer connection is necessary for publishing your code to the server. The default connection is Explorer 1 on the local host. You can add, edit, or remove connections by clicking Configure to open the OpenEdge Explorer Connections preference page.
Note: To support publishing remotely, you can configure OpenEdge Explorer connections for remote hosts. To create a remote connection, you must have the host name or IP address, the Web server port (9090 by default), and the login information for the remote machine.
6. Choose the WebSpeed broker that will be the target for your published code. The list of available brokers is based on the resources managed under the OpenEdge Explorer connection that you chose in the previous step.
Note: If you see no available brokers, it is possible that you are not properly logged in to the OpenEdge Explorer connection. This can occur after you have changed the default password (admin) after starting OpenEdge Explorer for the first time. To update the password, click Configure next to the OpenEdge Explorer connection field. Select the connection and click Edit. Update the password and verify the other connection configuration parameters. You can click Test Connection to verify that the connection is functioning.
7. Type a server name.
The default server name includes the name of the broker, the type of the broker (WebSpeed or AppServer). the runtime environment, and the host. This convention is useful for identifying multiple servers when you are publishing to different machines and different runtime environments. However, you can change the name to suit your own conventions.
8. Click Next. The Define publishing rules page opens.
9. Select Use custom publish directory if you want to change the default publish location in the workspace for a local broker and add the custom location to the Publish directory field. This does not change the actual publish directory for the broker itself. It modifies the metadata of the workspace and does not affect users that are accessing the broker remotely. The default publish location is the working directory of the broker, which is specified in a file. You cannot edit the file directly from Progress Developer Studio for OpenEdge, but you can specify a publish location that differs from the working directory.
Note: You cannot specify a custom publish directory for a remote broker in the New Server wizard. If you chose a remote broker on the previous page of the wizard, the custom publish option will be disabled.
Use OpenEdge Explorer (OpenEdge > Admin > OpenEdge Explorer) to change a broker's working directory or publish directory. Keep in mind that the publish directory must be included in the PROPATH for the application to compile and run successfully.
You can also modify the working directory of brokers as a launch configuration setting in the Run Configurations dialog. Select Run > Run Configurations from the main menu bar of Progress Developer Studio for OpenEdge. Open the Startup tab to modify the working directory.
10. Clear the Publish source code and/or Publish r-code check boxes if it is preferable to exclude either source or r-code from publishing.
11. Select Compile on publish if you want to compile with the broker's AVM rather than the project's AVM.
Note: The Compile on publish option is only available if the broker is remote.
12. Click Next. The Define a new Web server page opens.
13. Specify a Web server.
By default, Web Server URL is selected. A URL to the WebSpeed broker that you specified on page two of New Server wizard is specified.
Note: If you intend to accept the default Web server, be sure to check that the path to the scripts directory on the Web server is correct. The default specifies the Microsoft IIS standard (/Scripts/... on Windows and /cgi-bin/... on Linux).
An alternative is to select the Web Server option and choose from the available Web servers in the workspace. (To add a Web server to the workspace, see Creating an HTTP server.)
14. Click Next. The Add and Remove resources page opens.
15. From the Available list, select the projects that contain the resources that you want to publish.
16. Add the selected projects to the Configured list.
17. Click Finish.
To publish the resources that you configured for this server, right-click on the server name in the Servers view and select Publish from the context menu.