The messaging database stores in-flight messages in a messaging cache as part of a queue so they can be delivered.
By default, an embedded Advantage Database Server® is used as the messaging database.
Administration considerations
Depending on your network or system topology, install the messaging database either with the Unwired Server, or separately, on its own physical hardware. If you install multiple Unwired Servers in a load-balancing cluster, all Unwired Servers in the same cluster must share the messaging database. Sybase recommends that you install the messaging database separately on a failover cluster that uses a shared-disk array. You can install the messaging database and consolidated database together on the same physical hardware.
Depending on you environment, the location of the messaging database file varies:
- In cluster environment, the default file location is <UnwiredPlatform_InstallDir>\Data\Messaging\.
- For all other environments, the default file location is <UnwiredPlatform_InstallDir>\Servers\MessagingServer\Data.
Data in the messaging database
The messaging database include:
- Permanent store of device connection information – all registered messaging devices store their connection
information in this database. During the first device connection, a physical device identifier is
obtained by the messaging runtime client and is stored together with the connection
information. Subsequently, the physical device identifier validates the device on every
connection. Unwired Server accept messages from the device, but only when the identity is
valid. This validation occurs even before the actual mobile application is authenticated by
an Unwired Server security provider.
- Transient store for messages – the transient store in the messaging database holds business
data only for a short amount of time. Once the data is delivered to the device, Unwired
Server deletes the data from this database.