|
Field
|
Description
|
|
AdminServer
|
Select an AdminServer for the PAS for OpenEdge instance.
If you have created multiple remote AdminServers in OpenEdge Management or OpenEdge Explorer ( > ), this field is displayed for you to select an AdminServer.
|
|
Instance name
|
Specify a name for the PAS for OpenEdge instance. This is a mandatory field.
Note: The PAS for OpenEdge instance name is case-sensitive. It can include any character except periods (.) or square brackets ([ ]). The name must be unique among all configured PAS for OpenEdge names.
|
|
Location
|
Select the location of the PAS for OpenEdge instance:
 Local: OpenEdge Management has access to the machine where PAS for OpenEdge runs through an AdminServer. PAS for OpenEdge can be running either through a remote AdminServer or through an AdminServer in the same location as OpenEdge Management.
Remote: The PAS for OpenEdge instance is in a different location than OpenEdge Management, that is, the instance exists in a location without an AdminServer. When you select the location as Remote, you cannot not use OpenEdge Management to start or stop a PAS for OpenEdge instance.
OpenEdge Management monitors only the local installation of new PAS for OpenEdge instances. If you have installed PAS for OpenEdge as a stand-alone product and have not installed an OpenEdge product that includes an AdminServer, select Remote to monitor the instance.
The OpenEdge manager web application, oemanager, must be installed on PAS for OpenEdge for you to use the PAS for OpenEdge instance from a remote location.
|
|
Security model
|
Select a security model:
Production: The oemanager and manager Web applications need to be deployed separately.
Make configuration changes to adjust security settings to ensure your application operates correctly in a production instance.
Developer: The oemanager and manager Web applications are deployed by default.
Development mode minimizes or eliminates any accessibility restrictions, so a developer can quickly use the product “out of the box” to develop, test, and debug applications.
|
|
URL
|
Specify the URL of the PAS for OpenEdge instance if PAS for OpenEdge is running remotely. The format of the URL must be http(s)://server:port/oemanager.
Note: For a local instance, OpenEdge Management or OpenEdge Explorer constructs the URL using localhost and port for secure communication. If you want to use HTTP to monitor the instance, you must specify the URL manually. For using secure communication, you must install all the required certificates in $DLC/certs.
|
|
No host verification for SSL
|
Select the check box if you do not want to validate the hostname in the URL of the PAS for OpenEdge instance that is enabled for secure communication.
|
|
Instance directory
|
Specify the name of the directory where the PAS for OpenEdge instance resides. This is an optional field.
Note: If you do not provide the name of the instance directory, the PAS for OpenEdge instance is created in the working directory set during OpenEdge installation. The name of the instance is used as the name of the directory where the PAS for OpenEdge installation is created. The directory must not already exist (either when provided, or when using the default location).
|
|
HTTP port
|
Specify an unused port number associated with the PAS for OpenEdge HTTP. By default, this is set to 8080.
Note: Each new PAS for OpenEdge instance that you create uses the default configuration. However, the port number must be unique for each PAS for OpenEdge instance for the instance to operate properly. If you specify a port number that is used by another PAS for OpenEdge instance, you are prompted to confirm whether you want to use the port number.
|
|
HTTPS port
|
Specify an unused port number associated with the PAS for OpenEdge HTTPS. By default, this is set to 8443.
Note: If you specify a port number that is used by another PAS for OpenEdge instance, you are prompted to confirm whether you want to use the port number.
|
|
Shutdown port
|
Specify an unused port number for shutdown. If you are creating a PAS for OpenEdge instance on a Windows machine, this is a mandatory field.
Note: If you specify a port number that is used by another PAS for OpenEdge instance, you are prompted to confirm whether you want to use the port number.
|
|
Autostart
|
Set the Autostart option to automatically start PAS for OpenEdge every time you start the AdminServer.
|
|
Tomcat manager login
|
Specify the login ID of the Tomcat Web application that hosts the PAS for OpenEdge instance. If you are using the Tomcat Web server shipped with OpenEdge, then the default login ID is tomcat.
You can also specify your own login ID other than the default ID, and it is stored in the tomcat-users.xml file.
|
|
Tomcat manager password
|
Specify the password of the Tomcat Web application that hosts the PAS for OpenEdge instance. If you are using the Tomcat Web server shipped with OpenEdge, then the default password is tomcat.
You can also specify your own login password other than the default password, and it is stored in the tomcat-users.xml file.
|
|
License
|
Security Model
|
Result
|
|
Progress Dev AS for OE
|
Developer
|
oemanager and manager are installed.
|
|
Progress Dev AS for OE
|
Production
|
oemanager and manager are not installed.
|
|
Progress Prod AS for OE
|
Developer
|
oemanager and manager are not installed.
|
|
Progress Prod AS for OE
|
Production
|
oemanager and manager are not installed.
|
|
Progress Dev AS for OE and Progress Prod AS for OE
|
Developer
|
oemanager and manager are installed.
|
|
Progress Dev AS for OE and Progress Prod AS for OE
|
Production
|
oemanager and manager are not installed.
|