Knowledge Document, kb000111027
, is basically answering the question if XCOM r12 is compatible with AT-TLS. The answer is that we don't see it having a problem, but XCOM r12 has not been tested/certified with AT-TLS. Because XCOM r12 has not been tested/certified with AT-TLS, we don't know of any or what problems may be encountered.
If a non secured port, which is identified by parameter SERVPORT, can be implemented to use AT-TLS with XCOM r12. The encryption of the data will occur at the AT-TLS level. If you have implemented a secured port, which is identified by parameter SSLPORT, and use SSL certificates, then the encryption of the data will occur at the SSL level. AT-TLS can be implemented for a secured port being used by XCOM, but it will encrypt the data twice. Once by SSL and then with AT-TLS. Implementing this will cause more overhead to the transfer performance and a user would need to keep that in mind when questioning such performance because that would be out of XCOM scope.
XCOM also allows you to implement IPV6 ports, which can be identified with parameters SERVPORTV6 and SSLPORTV6. Please refer to the XCOM r12
manuals for details on the parameters.