Add an application service resource to a messaging service to define direct, connection-based access to an internal application server.
Add an application service to define the protocol that is used for communications between an internal application server and the messaging service. The service definition identifies the port that is reserved for communication between an application on messaging client devices and the messaging service. Client applications include a specific set of header information inside the data stream. The messaging service uses this information to map the traffic to the internal application server. HCL SafeLinx supports the following application service type:
- Provides traffic flow for applications between internal application servers and messaging client
devices. Between the internal application server and the messaging service, the traffic flows over a
UDP or TCP connection, or a secured TCP connection. Between messaging client devices and the
messaging service, traffic flows over all MNCs, except SMTP, SNPP, or dial-based MNCs.
For example, a POP3 email client on a messaging device connects to the SafeLinx Server by using an SMS protocol. The messaging service converts the data stream to the UDP or TCP protocol and forwards the requests directly to the POP3 server. When responses are returned from the POP3 server, they are converted back to the SMS protocol and returned to the email client on the messaging device.
A generic application service can be configured to add client device identification information as a header to the application data stream. The application that receives the data stream is responsible for interpreting the header. For more information about the Messaging Services and Push Toolkit, see the Programming reference.
You can also configure generic applications services to run secure TCP transactions. Application services are available only as add-ons to an existing messaging service.