Securing Passwords How to Configure a Driver

11-12 Oracle Fusion Middleware Administrator’s Guide for Oracle SOA Suite

11.4.1.3.4 Client API MessageInfo Support These properties are message delivery related

which are specified through client API. Table 11–5 describes if the protocol or driver implementation honors such properties.

11.4.1.4 Configuring the SMPP Driver

SMPP Short Message Peer-to-Peer is one of the most popular GSM SMS protocols. User Messaging Service includes a pre-built implementation of the SMPP protocol as a driver that is capable of both sending and receiving short messages. If the sending feature is enabled, the SMPP driver opens one TCP connection to the SMS-C Short Message Service Center as a transmitter for sending. If the driver’s receiving feature is enabled, it opens another connection to the SMS-C as a receiver for receiving. Only two TCP connections both initiated by the driver are needed for all communication between the driver and the SMS-C.

11.4.1.4.1 SMPP Driver Interoperability This section details interoperability features of the

SMPP Driver. The SMPP driver is compatible with these protocols: SMPP v3.4. IncomingMailIDs The e-mail addresses corresponding to the user names. Each e-mail address is separated by a comma and must reside in the same position in the list as their corresponding user name appears on the usernames list. Required only if e-mail receiving is supported on the driver instance. No NA IncomingUserIDs The list of user names of the mail accounts the driver instance is polling from. Each name must be separated by a comma, for example, foo,bar. Required only if e-mail receiving is supported on the driver instance No NA IncomingUserPasswords The list of passwords corresponding to the user names. Each password is separated by a comma and must reside in the same position in the list as their corresponding user name appears on the usernames list. Required only if e-mail receiving is supported on the driver instance. No NA IncomingProcessingChunkSize Max number of messages processed per message polling. No 100 Table 11–5 Client API MessageInfo Support Name Description Support Expiration Expiration means how long the message will exist until it expires. False Delay Delay means the amount of time that must elapse before the message is sent. False Note: The SMPP Driver implements Version 3.4 of the SMPP protocol and only supports connections to an SMS-C that supports this version. Table 11–4 Cont. Custom E-Mail Properties Name Description Mandatory? Default Value Configuring Oracle User Messaging Service 11-13 SMPP Driver features include: ■ Automatic connection retry ■ HTTP proxy for firewall traversal ■ Authentication configuration ■ Configurable chunk size ■ Bulk Sending ■ Encoding: UCS2, IA5, GSM_DEFAULT ■ Priority Setting ■ Configurable Window size ■ Plain text content only The Gateway Vendors in Table 11–6 have been verified.

11.4.1.4.2 Common Properties These are common driver properties that are indicative of

the capabilities of this driver for use by the engine when routing outbound messages. Some properties are set by the driver developer and do not normally require modification, while others can be modified by the administrator to change the routing behavior. Some properties such as SendingQueuesInfo are for advanced use and only require modification for advanced deployment topologies. For a complete description of these properties and available values refer to the javadoc of DriverConfigPropertyNames. Table 11–6 SMPP Driver Gateway Vendors Vendor Logica CMG Clickatell Verisign OpenSMPP simulator Table 11–7 Common SMPP Properties Name Description Mandatory Default Value InstanceName Instance Name for internal use only Yes SMPP-Driver Capability Message sending and receiving capability Yes Both SupportedDeliveryTypes Supported Delivery Types Yes SMS SupportedContentTypes Supported Content Types Yes textplain SupportedStatusTypes Supported Status Types No DELIVERY_TO_ GATEWAY_SUCCESS, DELIVERY_TO_ GATEWAY_FAILURE Cost Cost No NA Speed Speed No NA SupportedCarriers Supported Carriers No NA Supported Protocols Supported Protocols No NA