Configuring and Testing Apache for Relay Server on SUSE Enterprise

Modify the Apache HTTP Server configuration and environment, as needed for Relay Server on SUSE Enterprise (Linux) host.

Prerequisites

Create a Relay Server configuration file and deploy it on the Relay Server (Apache) host.

Task

Modify the default-server.conf file to configure Apache for Relay Server usage by adding these entries:

LoadModule iarelayserver_client_module modules/mod_rs_ap_client.so 
LoadModule iarelayserver_server_module modules/mod_rs_ap_server.so 
<LocationMatch /cli/iarelayserver/* > 
SetHandler iarelayserver-client-handler 
</LocationMatch> 
<Location /srv/iarelayserver/* > 
SetHandler iarelayserver-server-handler 
RSConfigFile /etc/httpd/modules/rs.config 
</Location> 
ServerName <your server name>

The Relay Server is now ready to test.

Start Apache and RelayServer with these commands:
- Apache – /etc/rc.d/apache2 start
- Relay Server – /usr/lib64/apache2/rshost –o /usr/relay.log –f rs.config
By default the Apache Server does not automatically start after a reboot, so you must change the Services for the appropriate Runlevel:
1. Open YaST Control Center.
2. Open the System Services (Runlevel).
3. Select the apache2 service and click the runlevel 3 and 5 check boxes.

Logging – If the Relay Server is running as a service the log is always located at /tmp. The Relay Server log file is named ias_relay_server_host.log by default, unless another file name was defined during State Manager service setup. The Apache logs (access_log and error_log) can be found at /etc/httpd/log.
Relay Server Status Request – Request Relay Server status from a Web browser at http://<relay server hostname>/srv/iarelayserver/. If no Outbound Enabler has connected the "Overall availability" is None. If one or more Outbound Enablers are connected, the "Overall availability" is Partial or Full.