Use the New Server wizard to define a connection to OpenEdge Explorer and select an AppServer broker to manage. Note that you cannot create or define a new AppServer broker from within Progress Developer Studio for OpenEdge. To create a new AppServer broker, use OpenEdge Explorer.
1. From the Servers view in the OpenEdge Server perspective, right-click and choose New > Server from the Context menu. The Define a New Server dialog appears, allowing you to choose either OpenEdge AppServer or OpenEdge WebSpeed as the type of server you want to define.
2. To choose AppServer as the server type, either:
Type AppServer in the Select the server type field, which filters the results to show only available AppServers.
Select Progress Software Corporation > OpenEdge AppServer as the server type from the list provided.
Note: The server host name localhost is prefilled.The Server name and the Server runtime environment details are also listed in the dialog.
3. If you want to specify a different server runtime environment, click Add. The New Server Runtime Environment dialog appears.
4. Type the runtime environment name and the OpenEdge version number in the fields provided; then click Finish.
5. To set up the runtime environment, click Configure runtime environments and follow the steps provided in Defining the OpenEdge AVM runtime.
Select the name of the connection from the OpenEdge Explorer connection dropdown list.
Click Configure. The Progress OpenEdge > Server > OpenEdge Explorer Connections Preferences page opens. For information about how to configure an OpenEdge Explorer connection, see Adding an OpenEdge Explorer connection. To return to the Define a new AppServer broker dialog, click OK.
8. Select the broker from the dropdown list, or click the Refresh button to verify that you are selecting from all available brokers. The list of brokers includes all local and remote brokers, in alphabetical order, that are managed by the OpenEdge Explorer connection you specify. The machine name is appended to the broker name, so that you can distinguish among brokers that have the same name but reside on different hosts.
Note: Remember that you cannot create a new AppServer broker in Progress Developer Studio for OpenEdge; to create a broker, use OpenEdge Explorer. When you select the broker, the server name is updated to identify the name of the broker, the name of the selected runtime, and the name of the host where the broker resides.
9. Click Next to define the publishing rules. You can choose a custom publish directory for a local broker. (For a broker that resides remotely, the option to choose a custom publish directory is unavailable.)
10. Choose one:
To publish to a custom publish directory for a local broker, select the check box and type the path to the directory in the Publish directory field; if you prefer, you can click Browse to locate the directory on the local machine. The publish directory you specify is created as a broker property in the ubroker.properties file for the local host. If you prefer not to use a custom publish directory for a local broker, do not select the check box. The broker's working directory will be used as the publish location.
To publish to a directory for a remote broker, you must configure the publish directory by using Open Edge Explorer. See Adding an OpenEdge Explorer connection for more information.
11. Select or deselect the Publish source code and/or the Publish r-code options. (These options are selected by default.)
Note: If you select only the Publish source code option, you can select the Compile on publish check box. Selecting this option means that whenever you publish source code to a server, it is compiled.
12. Click Next. The Add and Remove dialog appears, showing the available project modules.
13. To configure an available project module, either select the module in the Available list and click Add, or double-click the module in the Available list. To configure all the available project modules, click Add All.
Note: You can also remove a project module from the Configured list by either selecting the module and clicking Remove or double-clicking the module in the Configured list. You can also select more than one project module and click Remove All.
14. Click Finish.
Note: The wizard validates the connection and broker name information. The server queries the broker properties for PROPATH, startup parameters, and connection procedures and stores them with a new launch configuration associated with the server. This launch configuration is created and used as the default launch configuration when the server starts. For more information about launch configurations, see Launch configurations for running and debugging programs.
Type AppServer in the Select the server type field, which filters the results to show only available AppServers.