Configure SAP Java Connector (JCo) connection properties.
For a comprehensive list of SAP JCo properties you can use to create an instance of a client connection to a remote SAP system, see http://help.sap.com/javadocs/NW04/current/jc/com/sap/mw/jco/JCO.html#createClient(java.util.Properties).
| Name | Description | Supported values |
|---|---|---|
| endpointName | Specifies the endpoint name. | Endpoint name |
| jco.client.alias_user | Specifies the alias user name. | Alias user name. |
| jco.client.client | Specifies the SAP client. | Three-digit client number; preserve leading zeros if they appear in the number |
| jco.client.user | Specifies the login user ID. | User name for logging in to the SAP system If using X.509 certificate authentication, remove the JCo properties jco.client.passwd and jco.client.user defined for the SAP connection profile in Sybase Control Center (SCC). |
| jco.client.passwd | Specifies the login password. | Password for logging in to the SAP system |
| jco.client.lang | Specifies a login language. |
ISO two-character language code (for example, EN, DE, FR), or SAP-specific single-character language code. As a result, only the first two characters are ever used, even if a longer string is entered. The default is EN. |
| jco.client.sysnr | Indicates the SAP system number. | SAP system number |
| jco.client.ashost | Identifies the SAP application server. | Host name of a specific SAP application server |
| jco.client.mshost | Identifies the SAP message server. | Host name of the message server |
| jco.client.gwhost | Identifies the SAP gateway host. |
Host name of the SAP gateway Example: GWHOST=hs0311 |
| jco.client.gwserv | Identifies the SAP gateway service. |
Service name of the SAP gateway Example: GWSERV=sapgw53 |
| jco.client.idle_timeout | Specifies the idle timeout, in seconds, for the connection after which it will be closed by R/3. Only positive values are allowed. | Idle timeout, in seconds. |
| jco.client.r3name | Specifies R/3 name. | Name of the SAP system |
| jco.client.group | Identifies the group of SAP application servers. | Group name of the application servers |
| jco.client.tpname | Identifies the program ID of the external server program. |
Path and name of the external RFC server program, or program ID of a registered RFC server program Example: TPNAME=/sap/srfcserv |
| jco.client.tphost | Identifies the host of the external server program. This information determines whether the RFC client connects to an RFC server started by the SAP gateway or to an already registered RFC server. Note: If the gateway host and external server program host are different, make sure that the SAP gateway
has access to start the server program through a remote shell.
|
Host name of the external RFC server program Example: TPHOST=hs0311 |
| jco.client.type | Identifies the type of remote host. |
2: R/2 3: R/3 E: external |
| jco.client.trace | Specifies whether or not to enable RFC trace. |
0: disable 1: enable |
| jco.client.codepage |
Identifies the initial code page in SAP notation. A code page is used whenever character data is processed on the application server, appears on the front end, or is rendered by a printer. |
Four-digit SAP code page number |
| jco.client.abap_debug |
Enables or disables ABAP debugging. If enabled, the connection is opened in debug mode and the invoked function module can be stepped through in the debugger. For debugging, an SAP graphical user interface (SAPGUI) must be installed on the same machine the client program is running on. This can be either a normal Windows SAPGUI or a Java GUI on Linux/UNIX systems. |
0: no debugging 1: attach a visible SAPGUI and break at the first ABAP statement of the invoked function module |
| jco.client.use_sapgui | Specifies whether a remote SAP graphical user interface (SAPGUI) should be attached to the connection. Some older BAPIs need an SAPGUI because they try to send screen output to the client while executing. |
0: no SAPGUI 1: attach an "invisible" SAPGUI, which receives and ignores the screen output 2: attach a visible SAPGUI For values other than 0 a SAPGUI needs to be installed on the machine, where the client program is running. This can be either a Windows SAPGUI or a Java GUI on Linux/Unix systems. |
| jco.client.getsso2 | Generates an SSO2 ticket for the user after login to allow single sign-on. If RfcOpenConnection() succeeds, you can retrieve the ticket with RfcGetPartnerSSOTicket() and use it for additional logins to systems supporting the same user base. |
0: do not generate SSO2 ticket 1: generate SSO2 ticket |
| jco.client.mysapsso2 | Indicates whether or not to use the specified SAP Cookie Version 2 (SSO2) as the login ticket instead of user ID and password. |
User: $MYSAPSSO2$ Password: Base64-encoded ticket Login with single sign-on is based on secure network connection (SNC) encryption and can only be used in combination with an SNC. |
| jco.client.x509cert | Indicates whether or not to use the specified X509 certificate as the login certificate instead of user ID and password. |
User: $X509CERT$ Password: Base64-encoded ticket Login with X509 is based on secure network connection (SNC) encryption and can only be used in combination with an SNC. |
| jco.client.lcheck | Enables or disables login check at open time. |
0: disable 1: enable If you set this to 0, RfcOpenConnection() opens a network connection, but does not perform the login procedure. Therefore, no user session is created inside the back-end system. This parameter is intended only for executing the function module RFC_PING. |
| jco.client.grt_data | Provides additional data for graphical user interface (GUI) to specify the SAProuter connection data for the SAPGUI when it is used with RFC. |
/H/ router string : the entire router string for the SAPGUI /P/ password : specify this value if the password for the SAPGUI connection is not the same as the password for the RFC connection. |
| jco.client.use_guihost | Identifies which host to redirect the remote graphical user interface to. | Host name |
| jco.client.use_guiserv | Identifies which service to redirect the remote graphical user interface to. | Name of the service |
| jco.client.use_guiprogid | Indicates the program ID of the server that starts the remote graphical user interface. | Program ID of the server |
| jco.client.snc_mode | Enables or disables secure network connection mode. |
0: off 1: on |
| jco.client.snc_partnername | Identifies the secure network connection partner. | Secure network connection name of the application server (for example, p:CN=R3, O=XYZ-INC, C=EN) |
| jco.client.snc_qop | Specifies the secure network connection security level. |
1: digital signature 2: digital signature and encryption 3: digital signature, encryption, and user authentication 8: default value defined by backend system 9: maximum value that the current security product supports |
| jco.client.snc_myname | Indicates the secure network connection name. This property overrides the default secure network connection partner. | Token or identifier representing the external RFC program |
| jco.client.snc_lib | Identifies the path to the SAP crytpographic library that provides secure network connection service. | Full path and name of third-party security library. You must download and install the library from the SAP Service Marketplace. |
| jco.client.dest | Identifies a configured R/2 system defined in the sideinfo configuration. | |
| jco.client.dsr | Enables or disables jDSR monitoring. | 0: off 1: on |
| jco.client.saplogon_id | Defines the string for SAPLOGON on 32-bit Windows. | String key to read parameters from the saplogon.ini file created by the SAPLogon GUI program on Windows |
| jco.client.extiddata | Provides data for external authentication (PAS). This is an old login mechanism similar to SSO; Sybase recommends that you do not use this approach. | |
| jco.client.extidtype | Specifies type of external authentication (PAS). See External Authentication Data property. |