2.2.1 Setting the operating environment for JP1/AJS3 for EAP (job control)
You can modify the operating environment for JP1/AJS3 for EAP (job control) by creating a job control environment setup file.
The environment setup file for job control (conf file) is located in the following directory. If the environment setup file does not exist at installation, the model file in the same directory is automatically copied as the environment setup file at installation.
-
Windows: (installation-path)\conf\conf
-
Linux: /etc/opt/jp1_am_r3/conf/conf
The following figure shows the contents of the model file on which the environment setup file to be created at installation is based.
-
For Windows
Figure 2‒1: Model file for the environment setup file for job control (for Windows) -
For Linux
Figure 2‒2: Model file for the environment setup file for job control (for Linux)
In situations where Windows is used with an NTFS type file system, we recommend that you prevent tampering of the environment setup file information by defining the access permission so that only personnel with Administrators permission can edit the environment setup file.
Before reediting the environment setup file, make sure that no command has been executed for JP1/AJS3 for EAP.
The environment setup file syntax is as follows:
[section] key=string
-
As the separator between section and key and between key and key, specify one or more new-line codes.
-
The character strings specified for section and key are case-insensitive.
-
The key specifications within the same section can be in any order.
-
If a semicolon (;) is placed at the beginning of a line, the line is handled as a comment statement.
-
When there are two or more section or key specifications having the same name, the value of the first specification is used.
In the following situations, JP1/AJS3 for EAP operates using the defaults.
-
An environment setup file is not created.
-
An illegal value is specified for the environment setup file (includes a syntax error).
-
The environment setup file cannot be read.
The keys that can be specified for the environment setup file are explained below for each section.
For trace (trace section), specify the name of the trace file that stores the trace level, trace file size, and trace information. The following table describes the keys that can be specified in the trace section.
- #1
-
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 at trace level 2 (default).
- #2
-
The remote resource name expressed in UNC format is \\computer-name\sharename, which is provided by Microsoft for networked folder/file name specification purposes. The folder and files must be kept accessible at all times.
- #3
-
For details about the default directory that stores the trace file, see A. Directory List.
- Important
-
A temporary directory is used when outputting trace files.
Under Windows, the folder specified by the TMP environment variable is used. In the TMP environment variable, specify a folder that can be accessed using the permissions of the user executing the command (if the default JP1/AJS service account is used when a JP1/AJS job is executed, the folder specified in the TMP system environment variable is used).
For event (event section), specify whether or not to generate events that are used in Windows application logs.
For Linux, make an event (event section) entry to specify whether to generate syslog messages. The following table describes the keys that can be specified in the event section.
For command (command section), specify whether or not to check the work directory for JP1/AJS3 for EAP, the job completion monitoring interval, the appropriateness of a specified R/3 object, the time and interval for attempting to retry connection in the event of a communication error, and whether to output the R/3 job log to the standard error output file. Also, specify the code page number used when replacing the character code in the connected Unicode version SAP system. The following table describes the keys that can be specified in the command section.
- #1
-
The remote resource name expressed in UNC format is \\computer-name\sharename, which is provided by Microsoft for networked folder/file name specification purposes. This folder must be kept accessible at all times.
- #2
-
For details about the work directory used when a JP1/AJS job is executed, see the manual JP1/Automatic Job Management System 3 System Design (Configuration) Guide.
- #3
-
Network load will be greater than if a checklevel of 0 has been specified. The required time for command execution will also be longer.
- #4
-
The valid key differs depending on whether you specify the RetryCount key, the RetryTime key, or both.
Key specification |
RetryCount |
||||
---|---|---|---|---|---|
Not specified |
Specified |
||||
0 |
N (> 0) |
||||
RetryTime |
Not specified |
(1) Retry three times |
(4) Immediate error |
(5) Retry N times |
|
Specified |
0 |
(2) Immediate error |
(4) Immediate error |
(5) Retry N times |
|
T (> 0) |
(3) Retry for T minutes |
(4) Immediate error |
(5) Retry N times |
(1) If neither the RetryTime key nor the RetryCount key is specified, retry is set to three times, which is the default value of the RetryCount key.
(2) An error occurs because 0 is specified for the RetryTime key and the RetryCount key is not specified.
(3) The specification of the RetryTime key takes effect. Retry for T minutes is set.
(4) An error occurs immediately because 0 is specified for the RetryCount key.
(5) Because the specification of the RetryCount key has priority, retry is set to N times.
- #5
-
The following shows the operation when the RetryCount and RetryTime keys are specified:
For XMI (XMI section), specify the XMI interface session audit level. The following table describes the keys that can be specified in the XMI section.