This functionality (connecting a local copy of Progress Development Studio for OpenEdge to a remote Pacific Application Server ) is not fully supported in 11.5.
This functionality is available in the 11.6 version of OpenEdge.
In 11.6, the following steps will allow a Progress Development Studio to connect to a remote Pacific AppServer instance.
After setting up and starting the Pacific AppServer (PAS) it is necessary to configure the Progress Development Studio for OpenEdge (PDSOE) to communicate with the remote PAS.
- In the PDSOE select the menu Window.
- Select the option Preferences
- Expand the option Progress OpenEdge
- Expand the option Server
- Select the option OpenEdge Explorer Connections
- Click on the button Add
- Define the connection to the remote AdminServer where the PAS is running (normally the hostname and the port are needed as well as the login credentials to access the AdminServer).
- Make sure to click the button for Create Servers which will configure the remote servers which are running in the remote AdminServer as available options in the PDSOE.
Note: It is NOT
possible to add a PASOE instance from a PROD license to PDSOE
. These steps only work with DEV PASOE
PASOE licenses do NOT include OEE/OEM, a product with OEE/OEM needs to be installed on the remote machine where the remote PASOE instance is running.
OEM is usually a separate license, for a list of products that include OEE checkout the doc page below: https://documentation.progress.com/output/ua/OpenEdge_latest/index.html#page/oemgs%2Fopenedge-explorer-overview.html%23
To test the connection is now valid the following example steps will make a new project then connect the project to the remote PAS.
- Within the PDSOE make a new OpenEdge project.
- Select ABL Web App as the project type.
- Click Next.
- The oepas1 instance (or whatever instance(s) are defined in the remote AdminServer) will be available for selection.