Configuring the Web Connector for SOCKS servers
Complete these steps if the Web Connector must communicate through a SOCKS server when it sends information to the WCS.
To configure the Web Connector on Windows
- Start the CCM.
- Stop the World Wide Web Publishing Service.
On the toolbar, click Configure web connector.
- In the Web Component Servers area, click Add.
If your WCS Host Name is already listed, select it and click Edit.
- In the WCS Host Name field, type the name of the machine that is running the WCS.
- If you have customized the WCS so that it listens on a port other than the default, type your new port number in the Port field. Otherwise, ensure that the default port number (6401) appears.
- Click Specify SOCKS, then click Add.
- In the SOCKS Proxy dialog box, type the Server Name or IP Address of your SOCKS server.
- In the Server Port field, type the number of the port that the SOCKS server is listening on.
- Select the SOCKS version that you are running (Ver 4 or Ver 5).
If you are using version 5 and you would like to secure access to the server, select the authentication check box, and then enter your user name and password.
- Click OK.
If more than one SOCKS server separates the Web Connector from the WCS, repeat steps 7 to 11 for each SOCKS server. Then click Up and Down to order the SOCKS servers. The SOCKS server closest to the Web Connector must appear at the top of the list, and the SOCKS server closest to the WCS must be at the bottom of the list.
- Click OK in all three dialog boxes to return to the CCM.
- Start the World Wide Web Publishing Service.
To configure the Web Connector on UNIX
If your web server is running on UNIX, you must stop the web server and then modify the definition of the Crystal Enterprise WCSHOST or WCSHosts variable. This variable is defined in the configuration file that corresponds to your web server. Depending on the web server and Web Connector you are using, the environment variable is typically defined in one of these files:
| Web Server
| Path
|
|---|
Apache with ASAPI
| crystal/enterprise/platform/wcs/conf/asapi.conf
|
iPlanet 6.x with NSAPI
| In the iPlanet magnus.conf file.
|
iPlanet 4.x with NSAPI
| In the iPlanet obj.conf file.
|
Any web server with CGI
| crystal/enterprise/platform/wcs/bin/wcscgi.cgi
|
For more information about the configuration files for your web server, see Web Connector virtual path mappings.
The syntax that denotes the WCS through a SOCKS server can be considerably complex. This section shows a complete connection string and then describes its component parts. The complete connection string for specifying the WCS through a SOCKS server is as follows:
socks://Version;User:Password@SOCKSServer:Port/WCSmachine:Port
This string consists of two main parts: the SOCKS connection information (Version;User:Password@SOCKSServer:Port) followed by the WCS destination (WCSmachine:Port). The variable components in this string are as follows:
- Version is the SOCKS version in use (4 or 5).
- User is a SOCKS user name of length < 256 characters.
- Password is the corresponding password of length < 256 characters.
- SOCKSServer:Port is the name or IP4 of the SOCKS server, along with its port.
- WCSmachine:Port is the name or IP4 of the WCS, along with its port.
For example, suppose that you are running SOCKS version 5 on a server called socksmachine. You need to provide the user name socksuser and the password secret to connect to a WCS named sales1. The WCS is listening on its default port (6401). In this case, in the configuration file appropriate to your web server, you would type the following definition for the WCSHOST or WCSHosts variable:
socks://5;socksuser:secret@socksmachine/sales1:6401
To specify a sequence of SOCKS servers, list them in the connection string by preceding each additional SOCKS server with the ampersand symbol (&), as follows:
socks://Version;User:Password@SOCKSServer1:Port&Version;User:Password@
SOCKSServer2:Port/WCSmachine:Port