SAP JCo properties

Each of the configuration objects can contain a list of properties which are optional and can be taken from the JCo documentation for the DestinationDataProvider. The SAP tenant specific properties precede the SAP system specific properties. If different optional properties have been set in the objects they are treated as union.

Additional properties set in the configuration are overridden by the more specific ones in the SAPTenant. The following JCo properties will not be overridden because they depend on the configured connection parameters:

• jco.client.client

• jco.client.user

• jco.client.passwd

• jco.client.sysnr

• jco.client.ashost

• jco.client.mshost

• jco.client.r3name

• jco.client.group

• jco.destination.repository_destination

• jco.destination.auth_type

• jco.client.destination

ImageMaster supports SAP Java Connector (SAP JCo) properties, which can be configured using the AdminClient:

Properties must be provided as plain JCo properties like “jco.client.gwhost value” in the configuration panel. What entries you have to provide depends on the SAP infrastructure. Below you find a list of the supported JCo properties:

Property	Description
Destination authentication information
jco.destination.auth_type	Authentication type – configured user or current user
jco.destination.user_id	Logon ID that helps to identify the user or system (when user / password logon is not used). The parameter is mandatory if neither user nor user alias is provided.
User logon properties
jco.client.client	SAP client
jco.client.user	Logon user
jco.client.alias_user	Logon user alias
jco.client.passwd	Logon password
jco.client.lang	Logon language
jco.client.mysapsso2	Uses the specified SAP Cookie Version 2 as logon ticket
jco.client.x509cert	Uses the specified X509 certificate as logon ticket
Connection configuration
jco.client.saprouter	SAP router string to be used for a system protected by a firewall
jco.client.sysnr	SAP system number
jco.client.ashost	SAP application server
jco.client.mshost	SAP message server
jco.client.msserv	Optional: SAP message server port to use instead of the default sapms<sysid>
jco.client.gwhost	Gateway host
jco.client.gwserv	Gateway service
jco.client.r3name	System ID of the SAP system
jco.client.group	Group of SAP application servers
Trace configuration
jco.client.trace	Enables/disables RFC trace (0 or 1)
jco.client.cpic_trace	Enables/disables CPIC trace (-1 [take over environment value <CPIC_TRACE>], 0 [no trace], 1,2,3 [different trace levels])
Special parameters
jco.client.lcheck	Enables/disables logon check at open time, 1 (enable) or 0 (disable)
jco.client.use_sapgui	Starts an SAP GUI and associates with the connection (0 – do not start [default], 1 – start GUI, 2 – start GUI and hide if not used)
jco.client.codepage	Initial codepage in SAP notation
jco.client.getsso2	Requests/suppresses an SSO ticket after logon (1 or 0)
jco.client.deny_initial_password	Denies usage of initial passwords (0 [default] or 1)
Destination pool configuration
jco.destination.peak_limit	Maximum number of active connections that can be created for a destination simultaneously
jco.destination.pool_capacity	Maximum number of idle connections kept open by the destination A value of 0 has the effect that there is no connection pooling, i.e. connections will be closed after each request.
jco.destination.expiration_time	Time in milliseconds after which the connections held by the internal pool can be closed
jco.destination.expiration_check_period	Interval in milliseconds at which the timeout checker thread checks the pool connections for expiration
jco.destination.max_get_client_time	Maximum time in milliseconds to wait for a connection when the application has allocated the maximum allowed number of connections
SNC configuration
jco.client.snc_mode	Secure network connection (SNC) mode, 0 (off) or 1 (on)
jco.client.snc_partnername	SNC partner, e.g. p:CN=R3, O=XYZ-INC, C=EN
jco.client.snc_qop	SNC level of security, 1 to 9
jco.client.snc_myname	SNC name, overrides the default SNC partner
jco.client.snc_lib	Path to the library which provides the SNC service
Repository configuration
jco.destination.repository_destination	Specifies which destination should be used for repository queries
jco.destination.repository.user	Optional: If repository_destination is not set and this property is configured, it will be used as the user for repository queries. This allows the use of a different user for repository lookups, enabling more restricted permissions.
jco.destination.repository.passwd	The password for a repository user, which is mandatory if a repository user is to be employed
jco.destination.repository.snc_mode	Optional: If SNC is used for this destination, it can be disabled for repository connections by setting this property to 0. By default, it uses the value of jco.client.snc_mode.
jco.destination.one_roundtrip_repository	Setting this to 1 forces the use of RFC_METADATA_GET in the ABAP system, while 0 deactivates it. If this property is not set, the destination will perform a remote call to check whether RFC_METADATA_GET is available. If it is, the destination will use it.

Table 252: JCo properties

SAP system usage

The “SAPSystem” configuration object contains basic connection information for all SAP tenants which will be accessed. The configuration attributes for direct and load balanced connections are mutually exclusive. For valid values see the documentation above.

Direct connections – direct access to an SAP system by providing instance number and host name or IP address of the connection.

Example:

Load Balanced connections – access to an SAP system via an SAP load balancer.

Example:

SAP tenant usage

The “SAPTenant” configuration object contains connection specific information. One SAP tenant identifies one connection.

The repository destination identifies a dedicated connection to an SAP system only used for access to the SAP repository (see SAP Secure Custom Destination). It is configured in an additional SAP tenant.

Example:

Optional JCo properties can be set for an SAP tenant. You can get an overview of all supported properties from the SAP JCo documentation. These properties are valid for this tenant and replace properties with the same name in the SAP system configuration. Properties with different names from the SAP system are added. The passwords for the password alias have to be configured in the ImageMaster password store.