SAP JCo properties

The ImageMaster Client supports SAP Java Connector (SAP JCo) properties. These properties have to be provided as plain JCo properties like “jco.client.gwhost value” in the configuration panel. The list of all supported JCo destination properties is displayed in the table below:

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

Logons user

jco.client.alias_user

Logons user alias

jco.client.passwd

Logons password

jco.client.lang

Logons 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

Gets / does not get 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 ms after that the connections hold by the internal pool can be closed

jco.destination.expiration_check_period

Interval in ms with which the timeout checker thread checks the connections in the pool for expiration

jco.destination.max_get_client_time

Maximum time in ms to wait for a connection if the maximum allowed number of connections is allocated by the application

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 default SNC partner

jco.client.snc_lib

Path to library which provides 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 set, it will be used as user for repository queries. This allows using a different user for repository lookups and restricting the permissions.

jco.destination.repository.passwd

The password for a repository user, which is mandatory, if a repository user should be employed.

jco.destination.repository.snc_mode

Optional: If SNC is used for this destination, it is possible to turn it off for repository connections, if this property is set to 0. Defaults to the value of jco.client.snc_mode

jco.destination.one_roundtrip_repository

 

1 forces the usage of RFC_METADATA_GET in ABAP System, 0 deactivates it.

If the property is not set, the destination will initially do a remote call to check whether RFC_METADATA_GET is available. In case it is available, it will use it.