2.7.5 About setting to acquire investigation material prepared for abnormal termination
JP1/AJS3 for EAP might be required RFC trace file (dev_rfc.trc) which is generated by the SAP NetWeaver RFC Library for failure analysis purposes. The character code of the RFC trace file has defined in configuration file (sapnwfc.ini) of SAP NetWeaver RFC Library. Therefore, if the encoding is not configured in sapnwrfc.ini, the trace information will not properly be generated. In that case, it is difficult to do failure analysis and we ask you to reproduce the issue after you set the configuration file.
Thus, we recommend that you configure the encoding setting in sapnwrfc.ini file before you run command of JP1/AJS3 for EAP for preparing he failure analysis. See below for the path to be placed and settings of sapnwrfc.ini.
Path to place the sapnwrfc.ini
-
In the case that you use command to control job Set sapnwrfc.ini to either or both paths depending on your operating style.
-
The working directory of the JP1/AJS3 for EAP where is specified by WorkDir key under the command (command section) in the environmental configuration file (conf file) to control job (If the WorkDir key is not set, current directory is set when command is run)
-
The folder where is specified an environment variable RFC_INI
-
-
In the case that you use the command to control InfoPackage or process chain
Set sapnwrfc.ini to either or both paths depending on your operating style.
-
The working directory of the JP1/AJS3 for EAP where is specified by WorkDir key under the command (command section) in the environmental configuration file (conf file) to control InfoPackage or process chain (If the WorkDir key is not set, current directory is set when command is run)
-
The folder where is specified an environmental valuable RFC_INI
-
Settings
Set the beginning of the sapnwrfc.ini below
-
In Windows
-
DEFAULT
-
RFC_TRACE_ENCODING=UTF-16
See also the sample of sapnwrfc.ini (installation-folder\Sample\apnwrfc.ini).
-
-
In Linux
-
DEFAULT
-
RFC_TRACE_ENCODING=UTF-16
See also the sample of sapnwrfc.ini (/opt/jp1_am_r3/sample/sapnwrfc.ini).
-
- Organization of this subsection
(1) In Windows
A user mode process dump may be required as investigation material when the command of JP1/AJS3 for EAP terminates abnormally. By setting the following registry, you can immediately obtain a user mode process dump for a problem investigation report when terminates command of JP1/AJS3 for EAP abnormally. It is recommended to set it beforehand in case of failure occurrence. Take sufficient care when setting registry values, because registry values influence the entire system.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps
Set the following registry value for the registry key above:
-
DumpFolder: REG_EXPAND_SZ folder-name-of-dump-destination
The folder requires access authorization.
-
DumpCount: REG_DWORD number-of-dumps-saved
-
DumpType: REG_DWORD 2
If the above is not set, no user mode process dump is output in case of failure occurrenceby JP1/AJS3 for EAP, so you might not be able to investigate the cause of error. In this case, it may be necessary to reproduce the symptom after setting the above.
(2) In Linux
-
Core dump may be required as investigation material when the command of JP1/AJS3 for EAP terminates abnormally. The maximum size of a core dump file depends on the command-executing user's core dump file size setting (ulimit -c). It is recommended to set the size of the core dump file to unrestricted (ulimit -c unlimited) beforehand in preparation for a failure occurrence.
If the above is not set, no core dump is output in case of failure occurrenceby JP1/AJS3 for EAP, so you might not be able to investigate the cause of error. In this case, it may be necessary to reproduce the symptom after setting the above.
-
For Linux environments in which the Automatic Bug Reporting Tool (ABRT) is installed, if you specify the ABRT settings to limit core dump file generation by users or user groups of the OS accounts or processes that use JP1/AJS3 for EAP, no core dump file will be output and you will not be able to investigate the failure in situations such as when a segmentation fault or a bus failure occurs in a JP1/AJS3 for EAP process. In accordance with the operations you are performing, revise the ABRT settings so they do not limit generation of core dump files by users or user groups of the OS accounts or processe.
-
These settings apply to Linux environments where the settings file for core dump file names (/proc/sys/kernel/core_pattern) begins with the character string "|/usr/lib/systemd/systemd-coredump". If the operation settings file for core dump files (/etc/systemd/coredump.conf) includes a setting that specifies that no core dump files are to be created, no core dump file will be output and users will not be able to investigate the failure in situations such as when a segmentation fault or a bus failure occurs in a JP1/AJS3 for EAP process. Based on operations to be performed, revise the settings in /etc/systemd/coredump.conf so that core dump files are created. For details, see the Linux documentation.
-
If the standard trace level (trace level 1) is set, detailed investigation is not possible at the time of failure occurrence, and it may be necessary to reproduce the symptom after setting the trace level to 2. It is recommended to set the trace level to 2 before executing the JP1/AJS3 for EAP command in preparation for a failure occurrence.