Wireless Data Server 2.5

This file was last modified 02.08.09

Thank you for choosing Wireless Data Server. This file contains installation instructions for the Wireless Data Server core and Data Circuit-terminating Equipment (DCE) plug-in.

Contents of this readme

How to report problems

Please contact Oracle's technical support department at support@steltor.com or call (514) 733-8500.

Other available components and documentation

Wireless Data Server core

Please see the release notes for supported platforms, system requirements, a list of included features and a description of known problems. Please see the Wireless Data Server Administrator's Guide (HTML | PDF) for configuration, maintenance and administration instructions, and the Wireless Data Server User's Guide (HTML | PDF) for information on using this product.

smsnotify

For calendar notifications and reminders, you must install the smsnotify utility. Please see the smsnotify readme for installation instructions.

Wireless network plug-ins

This version of Wireless Data Server includes a plug-in that connects to the wireless network through Data Circuit-terminating Equipment (DCE). To connect to the wireless network in a different way, continue installing this product, then install the appropriate plug-in. A different plug-in supports connections through the Short Message Peer to Peer (SMPP) protocol.

Installing Wireless Data Server

NOTE: On UNIX platforms, different versions of Wireless Data Server installed on the same machine must be installed under different user accounts. Multiple installations of the same version should also be under different accounts if possible.

NOTE: If you install Wireless Data Server on a UNIX calendar server host, it must be installed under a different user account than the calendar server to avoid conflicts between different versions of shared libraries.

  1. Unzip the Wireless Data Server archive in a directory on your disk (referred to hereafter as <wds>).
  2. If you use a Solaris platform, set the LD_LIBRARY_PATH variable to <wds>/bin.
    If you use an HP-UX platform, set the SHLIB_PATH variable to <wds>/bin and set the number of file descriptors to the maximum (at least 1024).
  3. See your Administrator's Guide for detailed information on configuring Wireless Data Server for use in your environment. You will need to modify the following parameters in the wds.ini file, located in the <wds>/etc/config directory on UNIX platforms (<wds>\etc\config on Windows platforms).
    Table 1: Wireless Data Server configuration parameters
    Section Parameter Value
    [WDS] smscconnection A list of all section names of all DCE connections, separated by commas and enclosed in {}

    		smsccharset MSCP437

    		smscplugin UNIX: <wds>/bin/libsmscdce.sl
    Windows: <wds>\bin\smscdce.dll

    		blockedmsisdns A list of MSISDN numbers to which Wireless Data Server will not send SMS messages, separated by commas and enclosed in {}

    		unisonconnections A list of all section names of all calendar server connections, separated by commas and enclosed in {}
    [<UNISON1, UNISON2, etc...>] 1 host Host name of the calendar server

    		node Node-ID
    [<DCE1, DCE2, etc...>] 2 smscmsisdn MSISDN number of the SMSC

    		msisdn MSISDN number of the WDS modem

    		port Serial port to which the DCE is connected

    		speed Data rate in bps
    1 For each calendar server connection, define a new section and set these parameters.
     2 For each DCE connection, define a new section and set these parameters.
     3 For each Instant Messaging connection, define a new section and set these parameters.

  4. Encrypt and set the password for the SYSOP of each calendar server connection using the cspasswd utility: 
    cspasswd -f <wds>/etc/config/wds.ini -s <UNISON1> -k passwd
cspasswd -f <wds>/etc/config/wds.ini -s <UNISON2> -k passwd
    For Windows platforms, replace forward slashes ("/") with backslashes ("\"). See the Administrator's Guide for details on the use and syntax of the cspassword utility.
  5. Run the following command line:
    wds -i
    Windows operating systems also allow the following optional flags:
    • -n <servicename>
      where <servicename> is the name of the service. Default value is wds.
    • -d "<displayname>"
      where <displayname> is the display name of the service. Default value is Wireless Data Server.
    • -s <starttype>
      where <starttype> is the start type of the service, either auto (automatic) or demand (manual). Default value is demand.
    See the Administrator's Guide for details on the use and syntax of the wds command.

Configuring the DCE

NOTE: On UNIX platforms, the user account under which Wireless Data Server is installed must have read and write access to the serial port used by the DCE. In addition, because Wireless Data Server must lock the port, the same user account must have read and write access to the /var/spool/locks directory.

  1. Using HyperTerminal, connect to the port to which the DCE is attached. You will configure the DCE by typing AT commands.
  2. Enter AT&S0 to set the Data Set Ready (DSR) signal to be always ON.
  3. Enter AT&W to save the configuration.

Remember also to match the value of the wds.ini [DCE] speed parameter to the data rate of your DCE.

Consult your vendor's documentation for details on configuring your DCE.

Starting Wireless Data Server

  1. Execute the following command:
    <wds>/bin/wdsctrl start
    On Windows platforms, replace forward slashes in the path name with backslashes. See the Administrator's Guide for details on the use and syntax of the wdsctrl command.
  2. Check the wds.log file for errors.

Stopping Wireless Data Server

Uninstalling Wireless Data Server

Copyright © 1999, 2002, Oracle Corporation. All rights reserved.