Try OpenEdge Now
skip to main content
Application Migration and Development Guide
Application Development with PAS for OpenEdge : Programming ABL Client Applications : Connecting to a PAS for OpenEdge instance : Establishing a connection with the CONNECT( ) method : Connection URL syntax for the APSV transport
Connection URL syntax for the APSV transport
Following is the URL syntax for the APSV transport, which OpenEdge supports to connect ABL clients or Java and .NET Open Clients to a PAS for OpenEdge instance:
Specifies either HTTP or HTTPS.
Note: Internet-secure connections to a PAS for OpenEdge instance using HTTPS require the management of a certificate store for public key certificates on the client (SSL client) and a certificate and key store for private keys and certificates on the PAS for OE instance (SSL server). For information on configuring both OpenEdge clients and PAS for OpenEdge instances for HTTPS connections, see Digital certificate management in this manual.
Specifies the user login credentials required to connect to the specified OE ABL Web application on the PAS for OpenEdge instance, according to the authentication model configured for the Web application. If the authentication model is Anonymous, no user credentials are required. If the model is HTTP Basic Authentication, you must provide a valid username (username) and password (passphrase) known to the user account systems configured for the Web application and its APSV transport.
Note: The APSV transport does not support HTTP Forms authentication.
Specifies the name or domain of the PAS for OpenEdge host.
Specifies the port for the host connection. Typically, HTTP uses 8810 and HTTPS uses 8811.
Specifies the OE ABL Web application and ABL client (or Open Client) transport (apsv) to connect with, where web-app-name is the name of an OE ABL Web application other than the default, ROOT (oeabl.war), and any other combination, including no OE ABL Web application specification at all, specifies a connection to the default ROOT OE ABL Web application.
For example, assuming a given a PAS for OpenEdge instance (scheme, host, and port (.)), an ABL client connection to an OE ABL Web application deployed in a WAR file named inventory.war is represented as:
An ABL client connection to the default OE ABL Web application on the same host can be represented by either one of the following URIs: