The SNPP Component adds paging send functionality to your BizTalk Server.
The SNPP Adapter implements a Simple Network Paging Protocol transmission client that can be used to send pages from your BizTalk Server to any paging-enabled device.
SNPP Send Adapter
The SNPP Send Adapter requires that you set a ServerName and ServerPort to connect to. You must also specify the recipient's PagerId. There is an optional CallerId property that will identify a number for the recipient to call.
The adapter also supports Secure Socket Layer (SSL) transport security. This may be enabled by selecting an SSLCert and a valid SSLAcceptServerCert, and then setting the SSLStartMode to an appropriate value.
Once the send port is set up, it will connect to the SMPP server whenever it has a message to send. By default, it will send the contents of the message body as the text of the short message. This behavior can be overridden by setting the MessageText property at design time or at runtime by writing the property to the message context.
Please refer to the section on adapter configuration for a description of how to configure receive locations and send ports for this adapter.
Sender Property List
The following is the full list of the properties of the sender adapter with short descriptions. Click on the links for further details.
|CallerId||The id of the caller.|
|ConnectionLifetime||Instructs the component whether or not to leave the connection to the server open.|
|Firewall||A set of properties related to firewall access.|
|MaxPersistentConnections||The maximum number of simultaneous persistent connections when sending.|
|MaxThreads||The maximum number of threads that the component may consume.|
|MaxTransmissionBatchSize||The maximum number of messages that can be sent in a single batch.|
|MessageText||The message being sent (alphanumeric).|
|Other||Defines a set of configuration settings to be used by the component.|
|PagerId||The id number of the pager which will receive the current page message.|
|RuntimeLicense||Specifies the component runtime license key.|
|ServerName||The name or address of the SNPP server.|
|ServerPort||The server port for SNPP (default 444).|
|SSLAcceptServerCert||Instructs the component to unconditionally accept the server certificate that matches the supplied certificate.|
|SSLCert||The certificate to use for client authentication during the SSL handshake.|
|SSLStartMode||Determines how the component starts the SSL negotiation.|
|Timeout||A timeout for the component.|
|TransmitBatchMode||How the transmitter processes batches.|
|TransportLog||Tells the component where and how to report information about its operations.|
|URI||The Uniform Resource Identifier (URI) of the send port or receive location.|
The following is a list of configuration settings for the adapter with short descriptions. Click on the links for further details.
|ReuseSSLSession||Determines if the SSL session is reused.|
|SSLCipherStrength||The minimum cipher strength used for bulk encryption.|
|SSLEnabledCipherSuites||The cipher suite to be used in an SSL negotiation.|
|SSLEnabledProtocols||Used to enable/disable the supported security protocols.|
|SSLIncludeCertChain||Whether the entire certificate chain is included in the SSLServerAuthentication event.|
|SSLSecurityFlags||Flags that control certificate verification.|
|TLS12SignatureAlgorithms||Defines the allowed TLS 1.2 signature algorithms when UseInternalSecurityAPI is True.|
|TLS12SupportedGroups||The supported groups for ECC.|
|TLS13KeyShareGroups||The groups for which to pregenerate key shares.|
|TLS13SignatureAlgorithms||The allowed certificate signature algorithms.|
|TLS13SupportedGroups||The supported groups for (EC)DHE key exchange.|
|AbsoluteTimeout||Determines whether timeouts are inactivity timeouts or absolute timeouts.|
|LocalHost||The name of the local host or user-assigned IP interface through which connections are initiated or accepted.|
|TcpNoDelay||Whether or not to delay when sending packets.|
|UseInternalSecurityAPI||Tells the component whether or not to use the system security libraries or an internal implementation.|