Try OpenEdge Now
skip to main content
Open Client Introduction and Programming
Programming Concepts : Connecting to an AppServer : Specifying the AppServer connection
 

Specifying the AppServer connection

The connection information includes character-string parameters that are passed to the AppServer. Typically you pass the following parameters:
*URL — AppServer connection information, depending on the connection type:
*Intranet connection (Java and .NET only) — AppServer protocol or SSL-enabled AppServer protocol for a secure intranet connection, specified using an AppServer URL that identifies the application service
*Internet connection (Java and .NET only using the AIA) — HTTP protocol or HTTPS protocol for a secure Internet connection, specified using an AppServer URL that identifies the application service
*Internet connection (Web services only, using a WSA) — HTTP protocol or HTTPS protocol for a secure Internet connection, specified using a Web service URL that identifies the SOAP Web service and that is specified during deployment of the Web service to the WSA
*User-ID and password — AppServer user identification and password
*AppServer Information — Application-specific information
Note: The combined length of the URL, User-ID, Password, and AppServer information fields must not exceed 30,000 non-Unicode characters when connecting to an AppServer.
In general, all connection parameters are optional, depending on the AppServer and SOAP Web service configuration and application requirements. For any parameter you do not specify, OpenEdge uses standard default values; however, you must ensure any defaults are valid for your application environment. For more information on the AppServer URL format, see the information on connecting to an AppServer using a URL in OpenEdge Application Server: Developing AppServer Applications. For more information on Web service URLs, see OpenEdge Development: Web Services.
Depending on the connection protocol, Open Client type, and various network conditions, your application might need to obtain information from the user in order to complete a connection. The following section describes some of these requirements for user information.