Installing the Relay Server Components to IIS on Windows

After installing Sybase Unwired Platform, unzip the relay server component files to the Web site home directory, create an application pool, and enable the relay server Web extensions.

1. Find the appropriate relay server ZIP file located on deployment edition of the installation media in /modules/relayserver, and copy it to your relay server system. There are two versions:
   • for 32-bit operating systems use relayserver.zip
   • for 64-bit operating systems, use relayserver_x64.zip

   The ZIP file contains the directory \ias_relay_server with two subdirectories, \Client and \Server, which contain the required executables and DLLs for the relay server.

2. Unzip relayserver.zip under the Web site home directory that you use for the relay server, typically, C:\Inetpub\wwwroot.
3. Create an application pool:
   1. Start IIS Manager Console by opening a command prompt and running: mmc %systemroot%\system32\inetsrv\iis.msc
   2. Right-click Application Pools and create a new application pool, for example, RSOE_AP.
   3. Right-click the application pool and select Properties to edit the properties for the outbound enabler application pool. Select the Performance tab, and unselect Shutdown Worker Processes After Being Idle.
   4. In the Recycling tab, unselect Recycle Worker Processes (In Minutes).
4. Enable relay server Web extensions in the IIS Manager Console:
   1. Select the Directory tab to edit the properties of ias_relay_server. Set execute permissions to Scripts And Executables.
   2. Click Create under Application Settings.
   3. Select the application pool you created in step 3.
   4. Under Web Server Extensions, allow both rs_server.dll and rs_client.dll to be run as ISAPI.
5. Configure IIS for Unwired Platform device clients to communicate with relay server:
   1. Run IIS admin scripts, which are located in \Inetpub\AdminScripts.
   2. Run the following console commands:

      cscript adsutil.vbs set w3svc/1/uploadreadaheadsize 0
      iisreset

   If you do not perform this configuration step, you see this error message:

   Could not connect to the Server. Session did not complete.