Connection Type dialog box

Use this dialog box to configure a connection type.

Direct Connection

By default, this component uses a direct connection, which does not ensure the confidentiality of data passed over the Internet or any unsecured network. The messages are passed as unencrypted plain text. If someone intercepts the plain text message, they may be able to view its content.

Non-secure Tunneling

Non-secure tunneling is when LAPI exchanges data with a Livelink/CS server by transmitting unencrypted (plaintext) Hypertext Transfer Protocol (HTTP) messages through the Web server integrated with a Livelink/CS server.

  • The server sends data in a HTTP request to the Web server integrated with the Livelink/CS server.
  • The Livelink/CS CGI process acts as a proxy that forwards the request to the Livelink/CS server (similar to how it responds to a request made over a socket connection).
  • The Livelink/CS server processes the server request, generates a response, and returns it to the Livelink/CS CGI.
  • The Livelink/CS CGI process forwards the Livelink/CS server's response to the Web server, which returns the response to the server.
Field Value
HTTP Username User name.
HTTP Password Password of the HTTP Username account.
Livelink CGI File URL to the Livelink/CS CGI integration process.

When this option is selected, the information on the General tab should be changed accordingly:

Option Description
Server The name of the machine on which the Web server is running.
Port The non-secure port to the Web server. The standard value for the non-secure port is 80.

Non-secure proxy server tunneling

Non-secure proxy server tunneling is when LAPI exchanges data with a Livelink server by transmitting unencrypted (plaintext) Hypertext Transfer Protocol (HTTP) messages through a Web Proxy Server, which passes messages to the Web server integrated with a Livelink/CS server.

  • The server sends data in a HTTP request to the Web proxy server, much like a Web browser requests data from a Web server through the Web proxy server.
  • The Web proxy server forwards the request to the Web server integrated with the Livelink/CS server.
  • The Livelink/CS CGI process acts as a proxy that forwards the request to the Livelink/CS server (similar to how it responds to a request made over a socket connection).
  • The Livelink/CS server processes server's request, generates a response, and returns it to the Livelink/CS CGI.
  • The Livelink/CS CGI process forwards the Livelink/CS server's response to the Web server, which returns the response to server application through the Web proxy server.
Field Value
HTTP Username User name known to the Web server.
HTTP Password Password of the HTTP Username account.
Livelink CGI File The full URL to the Livelink/CS CGI integration process in the form: http://host:port/livelink/livelink.exe, where host is the Livelink/CS host name and port is the Web server port number.

When this option is selected, the information on the General tab should be changed accordingly:

Option Description
Server The name of the machine on which the Web proxy server is running.
Port The port to the Web proxy server.

Secure Tunneling

This option requires Livelink Secure Connect. You must separately purchase and install Livelink Secure Connect before you can implement secure communications. Livelink Secure Connect includes RSA BSAFE cryptographic and security protocol software from RSA Security, Inc. The data is virtually impossible to decipher if intercepted but is easily converted to plaintext by the application that is intended to receive the data.

  • The server sends data in a Secure Hypertext Transfer Protocol (HTTPS) request to the Web server integrated with the Livelink/CS server. Browsers use the HTTPS protocol to encrypt user page requests and decrypt pages returned by a Web server.
  • The Web server negotiates the SSL connection with the server through a SSL handshake and decrypts the application's request.
  • The Livelink/CS CGI process acts as a proxy that forwards the request to the Livelink/CS server (similar to how it responds to a typical Livelink/CS request).
  • The Livelink/CS server processes server's request, generates a response, and returns it to the Livelink/CS CGI.
  • The Livelink/CS CGI process forwards the Livelink/CS server's response to the Web server, which encrypts the response and returns it to the server.
Field Value
HTTP Username User name known to the Web server.
HTTP Password Password of the HTTP Username account.
Livelink CGI File The full URL to the Livelink/CS CGI integration process in the form: https://host/livelink/livelink.exe, where host is the Livelink/CS host name.
CA Root Certificates A secure LAPI client application requires the root certificate of the Certificate Authority (CA) from the secure Web server integrated with a Livelink/CS Server to verify the authenticity of the certificate passed. In most cases, third-party CAs provide instructions on how to obtain their root certificates on their Web sites (for example, www.verisign.com or www.entrust.com). Optionally, you can export some CA root certificates from Microsoft Internet Explorer 5.0 and later.

When this option is selected, the information on the General tab should be changed accordingly:

Option Description
Server The name of the machine on which the Web server is running.
Port The secure port to the Web server. The standard value for the secure port is 443.