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
  • SNMP

---

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 6.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, stats and tracking parameters.
<logfile>.log	For information concerning the connection between Wireless Data Server and DCE modem. See the [<DCE>] logfile, debug, errlog, stats and trace parameters in wds.ini.

Table 6.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.

SNMP

You can also monitor Wireless Data Server using the Simple Network Monitoring Protocol (SNMP), a protocol developed to allow remote monitoring and administration of operating systems and applications.

Using an SNMP client application, you may view a variety of information and statistics concerning your Wireless Data Server installations, including message throughput, memory usage and configuration options. This information is read-only; it may not be set through your SNMP client.

In addition to providing this monitoring information, Wireless Data Server will also alert your SNMP client to certain events, such as losing or regaining connections to the calendar server, wireless network and IM server.

For full details on the monitoring information maintained by Wireless Data Server, see Appendix C, "Wireless Data Server MIBs."

In order to take advantage of Wireless Data Server's SNMP monitoring capabilities, you must have an SNMP client such as Hewlett-Packard's OpenView. You must also install Wireless Data Server's SNMP subagent to communicate with your operating system's SNMP agent; consult the Wireless Data Server subagent readme file for installation instructions and Appendix A, "Server parameters," for details on its configuration parameters.

SNMP configuration -- WDS side

The parameters mentioned below can be found in the /etc/config/wds.ini file within the Wireless Data Server core installation directory.

SNMP subagent port

Use the [WDS] snmpport parameter to specify the port to use to communicate with the Wireless Data Server subagent.

Refresh intervals

To set the interval at which Wireless Data Server sends updated information to the SNMP subagent, use the [WDS] snmprefreshinterval parameter. To set the interval at which Wireless Data Server sends ALL information to the SNMP subagent, regardless of whether it has been changed since the last update, use the [WDS] snmprefreshallinterval parameter.

SNMP configuration -- subagent side

The parameters mentioned below can be found in the /etc/config/wdssnmp.ini file within the Wireless Data Server subagent installation directory.

WDS instances to monitor

For each Wireless Data Server instance you want your subagent to monitor, create a new section within wdssnmp.ini, and configure the host, port, index and id parameters accordingly. Note that the port parameter in each section should match the value of the wds.ini [WDS] snmpport parameter used by that instance of Wireless Data Server.

When these sections are complete, add their names to the list in the wdssnmp.ini [WDSSNMP] wds parameter.

Timeout for idle messages

Use the [WDSSNMP] timeout parameter to set a timeout for Wireless Data Server's subagent. If this timeout is reached without any data being exchanged, the subagent will send an idle message to check that the server is still running, and to let it know the subagent is still running.

Copyright information