Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

SQL Anywhere 12.0.1 » Relay Server » Relay Server deployment

 

Deploying the Relay Server components to Microsoft IIS 7.0 or 7.5 on Windows Server 2008/Windows Server 2008 R2

Before running the Relay Server with IIS 7.0 or 7.5, you need to deploy Relay Server files to each computer in the Relay Server farm.

Prerequisites

The Microsoft IIS ISAPI Extensions feature is installed.

The Relay Server components are installed using the SQL Anywhere install. By default, all files are installed to %SQLANY12% and are based on the bitness of the computer:

  • %SQLANY12%\Bin32 and %SQLANY12%\Bin64 are used for DLLs and executables for administration.

  • %SQLANY12%\RelayServer\IIS\Bin32 and %SQLANY12%\RelayServer\IIS\Bin64 are used for Relay Server specific files under the appropriate folder (for example, Admin, Client, Monitor, or Server). The Server folder contains the rshost.exe and rs.config files.

Context and remarks

Interactive quick setup feature

An interactive quick setup feature, rs-setup.bat, is provided as an alternative to this procedure (refer to the readme file for a more detailed description of the quick setup feature). rs-setup.bat is located in the %SQLANY12%/RelayServer/IIS/quicksetup_iis7 directory and performs the following tasks:

  1. Installs IIS7 and turns on the required IIS7 features

  2. Configures IIS7 for the Relay Server

  3. Creates a demo application

  4. Generates a quick reference guide

The Relay Server for Windows consists of the following executables:

  • rs_client.dll
  • rs_server.dll
  • rs_monitor.dll
  • rshost.exe
  • dblgen12.dll
  • dbsvc.exe
  • dbfhide.exe
  • dbtool12.dll
  • dblib12.dll
  • dbicu12.dll
  • dbicudt12.dll
  • dbsupport.exe
  • dbghelp.dll

For information about which versions of IIS are supported, see [external link] http://www.sybase.com/detail?id=1061806.

IIS 7 setup scripts for Relay Server can be found in the %SQLANY12%\RelayServer\IIS\iis7_setup.txt directory.

 Deploy the Relay Server components to Microsoft IIS 7.0 or 7.5 on Windows Server 2008/Windows Server 2008 R2
  1. Backup the IIS configuration file applicationHost.config located in the c:\Windows\System32\inetsrv\config folder.

  2. To add an application pool for the Relay Server, edit the applicationHost.config file to add the following code to the <system.applicationHost> » <applicationPools> section.



    <add name="RelayServer" queueLength="65535" autoStart="true" managedRuntimeVersion="" managedPipelineMode="Integrated">
       <processModel identityType="LocalSystem" idleTimeout="00:00:00" maxProcesses="20" pingingEnabled="false"
             pingInterval="00:00:30" pingResponseTime="00:01:30" />
       <recycling disallowOverlappingRotation="true">
         <periodicRestart time="00:00:00">
           <schedule>
             <clear />
           </schedule>
         </periodicRestart>
       </recycling>
       <failure rapidFailProtection="false" />
       <cpu resetInterval="00:00:00" />
    </add>
    
    Note

    The rest of the steps refer the %SQLANY12%\RelayServer\IIS\BinXX directory as %rs_dir% in the applicationHost.config file. However, environment variable expansion is not fully supported in every section in the IIS configuration file, so the %rs_dir% variable needs to be fully expanded when you add it into the applicationHost.config file.

  3. To add the Relay Server application to the default site, edit the applicationHost.config file to add the following code to the <system.applicationHost> » <applicationPools> » <sites> » <site name="Default Web Site"> section.

    <application path="/rs" applicationPool="RelayServer">
      <virtualDirectory path="/" physicalPath="%rs_dir%"/>
    </application>
  4. To add the Relay Server ISAPI extensions, edit the applicationHost.config file to add the following code to the <system.webServer> » <security> » <isapiCgiRestriction> section.

    <add path="%rs_dir%\Admin\rs_admin.dll" allowed="true" />
    <add path="%rs_dir%\Client\rs_client.dll" allowed="true" />
    <add path="%rs_dir%\Monitor\rs_monitor.dll" allowed="true" />
    <add path="%rs_dir%\Server\rs_server.dll" allowed="true" />
  5. To enable access to the Relay Server extensions, edit the applicationHost.config file to add the following code to the <configuration> section.



    <location path="Default Web Site/rs">
      <system.webServer>
        <security>
          <authentication>
            <anonymousAuthentication userName="" />
          </authentication>
          <requestFiltering>
            <requestLimits maxAllowedContentLength="2147483647" />
          </requestFiltering>
        </security>
        <handlers accessPolicy="Execute, Script" />
      </system.webServer>
    </location>
    Note

    The Relay Server is set up for anonymous access based on these instructions. Proper security needs to be configured for IIS and the Relay Server based on the business requirements.

  6. To enforce HTTPS access to the Relay Server administration extension for security reasons, edit the applicationHost.config file to add the following code to the <configuration> section.

    <location path="Default Web Site/rs/Admin">
      <system.webServer>
        <security>
          <access sslFlags="Ssl" />
        </security>
      </system.webServer>
    </location>
  7. Save these changes to the applicationHost.config file.

  8. Set the Connection timeout property of the Default Web Site to a minimum of 60 seconds. By default this value should be 120 seconds, which is sufficient.

  9. Create the Relay Server configuration file rs.config using the following guidelines:

    • The file should have four sections:

      • Options section
      • Relay server section
      • Backend farm section
      • Backend server section
    • Each section starts with a section tag, made by enclosing a keyword that identifies the section name in square brackets.

    • Add the appropriate properties to each section. A property is defined by specifying the property name on the left side of an equal sign and its value on the right side of the equal sign. For example, propertyname = value.

    • The configuration file should contain only 7-bit ASCII characters.

  10. Copy the rs.config file to the %SQLANY12%\RelayServer\IIS\BinXX\Server directory.

  11. Ensure optimum performance by reviewing the performance tips.

  12. Start the Relay Server State Manager as a service using a command line similar to the following:

    dbsvc -a <administrator> -p <password> -s auto -t rshost -w RelayServer "%rs_dir%\Server\rshost.exe" -q -qc -f "%rs_dir%\Server\rs.config" -o "c:\temp\ias_relay_server.log"
    Note

    It is recommended that you start the State Manager as a service. However, it can also be started automatically by the Relay Server.

  13. Update the Relay Server configuration for Microsoft IIS on Windows:

    1. For each computer that belongs to the Relay Server farm you are updating, copy the updated configuration file to the %SQLANY12%\RelayServer\IIS\BinXX\Server directory under the Relay Server web site home directory. The configuration file must be called rs.config if auto start is used.

    2. From the %SQLANY12%\RelayServer\IIS\BinXX\Server directory, run the following command line to apply the configuration update:

      rshost -u -f rs.config
    3. Repeat the previous steps for each computer in the Relay Server farm that is being updated.

Results

The Relay Server configuration file is deployed to all computers in the Relay Server farm.

Next

None.

 See also