To use SNC with CPIC calls from AS ABAP, you must configure the SNC options for each CPIC destination individually. You can either use transaction SM54 or SM30 (table TXCOMSECU). In this section, we describe how to configure the SNC options using transaction SM54.
Transaction SM54 distinguishes the following types of CPIC destinations (depending on the communication partner):
● TYPE = C: R/2 connections (Does not support SNC.)
● TYPE = I: R/3 connections
● TYPE = E: Connections to external programs that are started over a gateway
● TYPE = R: Connections to registered external programs
SNC for CPIC connections to R/2 (type = C) is not supported. There are no security products available for mainframes that support the GSS-API or that are implemented in R/2.
Therefore, you cannot activate SNC for connections defined as protocol type = C! Currently, you receive no error message when you activate SNC in the SNC options; however, you receive an error when you attempt to establish such a CPIC connection.
Maintaining SNC options for the initiator (AS ABAP) is similar for all of the categories and is described in Maintaining CPIC Destinations and Their SNC Options Using Transaction SM54.
No comments:
Post a Comment