2.6.1 Notes on version upgrading
In version 11-00, the RFC library, which is used to communicate with the SAP system, has been changed from the classic RFC library to SAP NetWeaver RFC Library. In SAP NetWeaver RFC Library, the name of the saprfc.ini file and the parameter specifications have been changed from those provided by the classic RFC library. If you were using the saprfc.ini file in version 10-00 or earlier, you need to perform migration operations by noting the specification changes described below.
- Organization of this subsection
(1) Changing file names
The name of the saprfc.ini file, which has been used so far, has been changed to sapnwrfc.ini. Change the name of the saprfc.ini file for version 10-00 or earlier to sapnwrfc.ini.
In addition, the file name sapnwrfc.ini is now fixed for SAP NetWeaver RFC Library. If multiple saprfc.ini files with a name of your choice were stored in the same folder in version 10-00 or earlier, you need to take action such as storing those files in separate folders.
(2) Changing parameter definitions
The parameter definitions in the file have been changed. The SAP connection type parameter (TYPE) was removed from the range supported by JP1. If the TYPE parameter was set in the saprfc.ini file, remove the parameter from the sapnwrfc.ini file.
The following table lists the parameters supported by JP1 version 11-00 and later.
Parameter |
Description |
---|---|
DEST |
Specifies destinations. |
ASHOST |
Specifies the host name for the SAP system. |
SYSNR |
Specifies the system number that is used to identify the SAP system. |
MSHOST |
Specifies the host name for the message server. |
R3NAME |
Specifies the system ID of the SAP system. |
GROUP |
Specifies the logon group. |
CLIENT |
Specifies the client number that is valid in the logon destination SAP system. |
USER |
Specifies the user name that is valid in the logon destination SAP system. |
PASSWD |
Specifies a password for the SAP user specified in the USER parameter. |
LANG |
Specifies the language type to be used for logon. |
CODEPAGE |
Specifies the code page number. |
DEFAULT |
Items that indicates common section of sapnwrfc.ini. |
RFC_TRACE_ENCODING |
The encoding of the trace file that the RFC library output. Set the followings for encoding.
If you do not set above, the RFC library cannot output information properly when the communication error occurs. Also, do not comment out the line. |
The following table lists the parameters supported by JP1 version 13-00 and later.
Parameter |
Description |
---|---|
TLS_SAPCRYPTOLIB |
Specifies the absolute path of the cryptography library. |
WSHOST |
Specifies the host name of the SAP system connected using WebSocket RFC. |
WSPORT |
Specifies the port number of the SAP system connected using WebSocket RFC. |
USE_TLS |
Specifies whether to enable or disable SSL/TLS encryption. |
TLS_CLIENT_PSE |
Specifies the PSE file containing the certificates required for TLS encrypted communications. |
TLS_CLIENT_CERTIFICATE_LOGON |
Specifies whether to use client certificates for server logins. |
(3) Changing the definition of the environment parameter RFC_INI
If the path for the saprfc.ini file has been specified for the environment parameter RFC_INI, in line with the definition change made in (1), change the file path to that of the sapnwrfc.ini file.
The following compatibility function is available to make it easy for you to change the definition of the environment parameter RFC_INI:
- Compatibility function:
-
If a file name that does not end with "sapnwrfc.ini" is specified for the environment parameter RFC_INI, the function regards the path up until the folder name as valid, and then references the sapnwrfc.ini file in that folder.
By using this function, you can reference the sapnwrfc.ini file without changing the value of the environment parameter RFC_INI, even if the sapnwrfc.ini file and saprfc.ini file are created in the same folder.
(4) Other notes
-
When you perform an overwrite installation or an upgrade installation over this product, select the product of the same model name for the installation.
-
In version 11-00-01 of JP1/AJS3 for EAP, the default value of trace level has changed from 1 to 2 and the size of trace size has changed from 12,288(KB) to 307,200(KB). For JP1/AJS3 for EAP, the changed trace level value and trace size value will not applied,in case of performing an overwrite installation or an upgrade installation , from version 11-00 or later versions.
Change the trace level value and trace size value refering the following procedure.
Files to be changed:
-
In case of using job control function:
Environment file for job control
In Windows: Installation folder/conf/conf
In Linux: /etc/opt/jp1_am_r3/conf/conf
-
In case of using info package or process chain control:
Environment file for info package or process chain control
In Windows: Installation folder/bwsta/conf/conf
In Linux: /etc/opt/jp1_am_r3/bwsta/conf/conf
Change the Level and Size of trace (trace section). Change example follows:
-
Old
[Trace]
Level=1
Size=12288
-
New
[Trace]
Level=2 #1
Size=307200 #2
#1: Specify the trace level. It is recommended to specify 2 (detail level).
#2: Specify the size of the trace file. Default value is 307200(KB).
Specify the size of the trace file based on the execution frequency
of the command in the your operational environment and the period you want to keep the trace.
Trace file size (KB)= Trace volume per command (KB/times) *
Frequency of command execution (times/day) *
period to leave the trace(day)
For details on the trace volume per command and the environment setting file, see 2.3.1 Setting the operating environment for JP1/AJS3 for EAP (job control) or 2.4.1 Setting the operating environment for JP1/AJS3 for EAP (InfoPackage control or process chain control). If you specify 307,200 kilobytes as the trace file size, the trace file can record at least seven days' worth of trace data when 100 jobs are executed per hour (2,400 times / day) at trace level 2.
-