Software AG communication information for your product is stored in one or more Software AG Directory Servers. The client's send message includes the target server name. Your Software AG product forwards the name and a use qualifier to the Directory Server, which returns an appropriate qualified URL (Universal Resource Locator) for the target back to your product.
Physical connection information (transport protocol , protocol specific parameters, timeout, and so on) must be entered in Directory Server target entries as qualified URLs before this communication can occur. The qualified URL contains the information required to direct the message to the correct target. The qualifier identifies which target URL is to be returned, based on the use implied by the qualifier. For example, a client send request returns an access target URL .
Directory Server target entries can be added manually using the System Management Hub. For more information, read Maintaining Targets.
This document covers the following topics:
Physical connection information (transport protocol , protocol specific parameters, timeout, and so on) must be entered in the Directory Server target entries as qualified URLs before the Directory Server can be used for Software AG communication. Each qualified URL is specified in this format:
qualifier.protocol://host:port[?parm=value][&parm=value]...
For example:
access.tcpip://serverhost:3001?retry=3
| Entry | Meaning |
|---|---|
| "qualifier" | The use of this target URL. Three types of qualifiers are supported: "access", "connect", and "listen". For more information, read Qualifiers. |
| "protocol" | The communication protocol that will be used to connect to the server. For more information, read Protocols. |
| "host" | The name of the host computer where the server runs. |
| "port" | The server's port. The port is a destination or a receiving port, depending upon URL usage. Refer to the documentation for the specific server application to identify its valid port numbers and how they are assigned. |
| "parm" | One of multiple optional parameters that can be used. The first parameter is preceded by a "?" and subsequent parameters, if any, are preceded by an "&". For more information, read Parameters. |
| "value" | The value of the parameter. |
URLs are qualified in the Directory Server target entries by their use. Qualifiers are used to specify this use. Three qualifiers (uses) of a URL are supported in the Software AG Directory Server, as described in the following table:
| Qualifier (Use) | Description |
|---|---|
| access | Defines a communication path between the client and the server. The path provides the means for the client to communicate with the server either directly or through a proxy; this communication path tells the client where to find the server. Internally, a URL with this specification appears as an "XTSaccess" URL. |
| listen | Defines a listen port for the server or the proxy. Internally, a URL with this specification appears as an "XTSlisten" URL. |
| connect | Defines an active connection between a server and a proxy or between a proxy and an Entire Net-Work node. Internally, a URL with this specification appears as an "XTSconnect" URL. |
The following communication protocols can be used in Directory Server URLs.
| Protocol | Description |
|---|---|
| HTTP11 | Although this protocol is still listed on Directory Server administration screens in the System Management Hub, this protocol is no longer supported. |
| MHDR | Only Software AG products that require the proxy can use this protocol. The MHDR protocol allows the proxy to communicate with these Software AG products. The MHDR protocol supports two-byte database IDs; therefore, databases with database IDs greater than "255" can be accessed using this protocol. |
| RDA | Only Software AG products that require the proxy can use this protocol. The RDA protocol allows the proxy to communicate with these Software AG products. The RDA protocol does not support two-byte database IDs; therefore access is limited to database IDs less than "256". |
| SSL | The SSL (Secure Sockets Layer) protocol enables
secure TCP/IP point-to-point connections.
Note: |
| TCP/IP | The TCP/IP protocol is the standard communication protocol used. It provides the most basic and efficient service. |
The parameters you can specify in a qualified URL vary, depending on the protocol and qualifier selected. The following table describes the parameters available and indicates which protocols and qualifiers support them.
