Messaging services

Messaging services enable a web application server to send messages from a wired network to a client on a wireless network.

Messaging services enable an application to send messages to messaging clients, such as a pager or a phone, over a wireless network. Messaging services include support for the following message modes:
  • Short message service (SMS)
  • Short message delivery over proprietary networks
  • Simple mail transfer protocol (SMTP)
  • Wireless communications transfer protocol (WCTP)
  • Simple network paging protocol (SNPP)

Messaging services support a range of message operations, including delivery of news, stock quotes, pager notifications, weather information, broadcast messages, and notification of events such as email arrival.

Messaging services are supported on SafeLinx Server installations on Linux only. Messaging services are not supported on Windows. You can add only one messaging services instance to each SafeLinx Server.

For more information about the mobile network connections that are supported for messaging services, see Available MNCs for messaging services connections.

Short message delivery operation

A short message delivery operation starts when a message processing application or servlet uses the IBM® SafeLinx Messaging Services and Push APIs to send a message. The messaging services forward the message to a short message service center (SMS-C), an SMTP server, or other network server for subsequent delivery to a client.

Mobile-originated message operation

A mobile-originated message operation starts when a client sends a message to a network provider for delivery to the messaging services. Messaging services use an HTTP post operation to forward the message to an application or servlet. The application or servlet then uses the IBM® SafeLinx Messaging Services and Push APIs.

How the messaging service interacts with clients

Messaging services on the SafeLinx Server receive information from a messaging processing application on the internal network, and transmit the information to mobile devices outside the firewall. Another remote client sends a mobile-originated message to the messaging service on the SafeLinx Server, which forwards the message to a message-processing application on the internal network.
The preceding figure shows the two methods in which the messaging service on the Connection Manager interacts with clients.
  • A messaging service that supports a message-originating application receives information from the application server and then transmits the information to mobile devices.
  • A messaging service that supports a message-processing application receives messages that are sent by mobile devices and then forwards them to the messaging processing application or servlet.