Administration

---

This chapter covers general administration tasks such as starting and stopping the server, as well as strategies for maintaining your server and monitoring its operations.

• General procedures
  • Starting Wireless Data Server
  • Stopping Wireless Data Server
• System maintenance
• System monitoring
  • Log files

---

General procedures

Starting Wireless Data Server

Use the bin/wdsctrl command to start the server:

% wdsctrl start

For details on the use and syntax of wdsctrl, see Appendix B, "Server utilities."

Stopping Wireless Data Server

Use the bin/wdsctrl command to stop the server:

% wdsctrl stop

For details on the use and syntax of wdsctrl, see Appendix B, "Server utilities."

---

System maintenance

Daily procedures

• Ensure that Wireless Data Server is running. Use the bin/wdsctrl command:

  % wdsctrl status

  For details on the use and syntax of wdsctrl, see Appendix B, "Server utilities." Alternatively, do one of the following:

  UNIX
  

  Grep the output of a ps command for the string "wds".

  NT
  

  From the Start menu, select Settings | Control Panel | Services, and verify that the WDS service is flagged as "Started".

• Check the WDS log files for errors.

Weekly procedures

• Archive all log files (optional).
• Stop and restart the WDS service (optional).

---

System monitoring

Log files

To view a Wireless Data Server log file, go to the appropriate directory and open the file using a text editor. Wireless Data Server creates log files on its local host in the /wds/log directory, and on the calendar server's host in the /users/unison/log/ directory.

Table 5.1 · Wireless Data Server log files created on WDS host

Filename	Description
wds.log	Any error Wireless Data Server encounters. Also any information output by the [WDS] debug and trace parameters.
<logfile>.log	For information concerning the connection between Wireless Data Server and DCE modem. See the [<DCE>] logfile, debug, errlog and trace parameters in wds.ini.

Table 5.2 · Wireless Data Server log files created on calendar server host

Filename	Description
smsnotify.log	Created by smsnotify. Logs any errors encountered when passing wireless notification messages from the calendar server to Wireless Data Server.
cws.log	Log file for Corporate-Wide Services. As the CWS daemon is responsible for sending SMS messages to the smsnotify program, it will create an entry within /users/unison/log/cws.log for each SMS message processed. CWS supports more verbose logging, according to the configuration of unison.ini. Refer to the calendar server administration guide for more details.

Interpreting log files

Much of the content of the Wireless Data Server log files is self-explanatory. Interpreting other sections may require the knowledge and resources of a qualified support representative. If you are uncertain about the content of a log file, contact your technical support representative for further assistance.

Copyright information