Integration Guide

Table Of Contents
Architecture Overview
______________________________________________________________________________
WaveWorks PSS, Integration Guide, 1.10 Page 5
© 2000, Symbol Technologies, Inc. February 1, 2000
WaveWorks MessagesThe WaveWorks messaging service uses a common message format
for all WaveWorks messages. This format contains a fixed header, followed by zero or more
application dependent data fields. TCP is used as the transport protocol for all WaveWorks
messages. This permits the business logic tier to reside on a remote system, if desired. The
messages form the "glue" that cements the client interface tier of the application to the business
logic tier. The messaging service can also be used to implement direct "client-to-client"
messaging.
Business Service ObjectsContain the vertical business application logic, implemented as
Microsoft COM automation server objects. The term "Service Object" is used to describe the
COM interface subset to which all WaveWorks-managed objects must adhere.
Transaction ModelWaveWorks uses a transaction Id scheme to provide namespace services
for purposes of automatically routing request messages to a capable Business Server for
execution.
Development Tools (Optional Component)An application interface development tool (Screen
Maker) supports rapid development of thin client radio applications. A radio terminal simulation
tool (Screen Runner) permits testing of Screen Maker applications without the need for an actual
radio network. A WaveWorks C++ foundation class library is also available, which includes
classes that support ODBC data access, WaveWorks messaging, INI file access, Date / Time
manipulation,and more.