2.3.1 Setting the operating environment for JP1/AJS3 for EAP (InfoPackage control or process chain control)

You can modify the operating environment for JP1/AJS3 for EAP (InfoPackage control or process chain control) by creating an environment setup file for InfoPackage control or process chain control.

The environment setup file for InfoPackage control or process chain 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.

For Windows:
```
installation-folder\bwsta\conf\conf
```
For Linux:
```
/etc/opt/jp1_am_r3/bwsta/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‒7: Model file for the environment setup file for InfoPackage control or process chain control (for Windows)

For Linux

Figure 2‒8: Model file for the environment setup file for InfoPackage control or process chain 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.

trace (trace 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.

Table 2‒10: Keys that can be specified for trace
Key	Value selectable as a string	Explanation
`Level`	`0` No trace `1` Standard level `2` Detail level `3` Debug level	Specify the trace level. If this key specification is omitted, a trace level of `2` is used. The trace volume per command for each trace level is as follows: When monitoring the completion of InfoPackage or process chains: `1` (standard level): 5.7 kilobytes `2` (detail level): 7.2 kilobytes + (InfoPackage or process chain execution time)/completion monitoring interval) x 0.3 kilobytes `3` (debug level): 27.7 kilobytes + (InfoPackage or process chain execution time)/completion monitoring interval) x 2.5 kilobytes When not monitoring the completion of InfoPackage or process chains: `1` (standard level): 2.0 kilobytes `2` (detail level): 7.2 kilobytes `3` (debug level): 27.7 kilobytes Normally, select Detail level. The debug level should be specified only if a failure occurs. If you select no trace, no information about the use of JP1/AJS3 for EAP will be collected.
`Size`	0 or 1 to 1,280,000 (in kilobytes)	Specify the trace file size. If you specify `0`, the trace file size is 2 gigabytes. If this key specification is omitted, the trace file size is 307,200 kilobytes.^#1 To reduce the trace file size, delete the created trace file and then change the size.
`TargetFile`	Windows: Character string beginning with (`drive-name`)`:\` or remote resource name coded in Universal Naming Convention (UNC) format^#2 Linux: Character string beginning with `/`	Trace information about all applications will be collected in the stored file. If you omit this key, a trace file is created for each application in the default directory.^#3

#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).

event (event section)

For event (event section) in Windows, specify whether or not to generate events that are used in Windows application logs.

For event (event section) in Linux, specify whether to generate syslog messages.

The following table describes the keys that can be specified in the event section.

Table 2‒11: Keys that can be specified for an event
Key	Value selectable as a string	Explanation
`ntevent`	`YES` or `NO`	This entry can be made when you are using Windows. Specify whether to generate Windows events. If this key specification is omitted, `YES` is used as the event generation condition.
`Syslog`	`YES` or `NO`	This entry can be made when you are using Linux. Specify whether or not to generate `syslog` messages. If this `key` specification is omitted, `YES` is used as the `syslog` message generation condition.

command (command section)

For command (command section), specify the work directory for JP1/AJS3 for EAP, the InfoPackage or process chain completion monitoring interval, and the time and interval for attempting to retry connection in the event of a communication error. Also, specify the code page number to be used for character code conversion in the connected Unicode version SAP system. The following table describes the keys that can be specified in the command section.

Table 2‒12: Keys that can be specified for command
Key	Value selectable as a string	Explanation
`WorkDir`	Windows: Character string beginning with (`drive-name`)`:\` or remote resource name coded in Universal Naming Convention (UNC) format^#1 Linux: Character string beginning with `/`	Enter a full pathname to specify the work directory for InfoPackage control function commands. The work directory is set when you execute an InfoPackage control function command. If this `key` specification is omitted, the current directory at the time the command is executed is used. (When JP1/AJS is used, the work directory to be used for execution of a JP1/AJS job^#2 is used.)
`MonitorInterval`	1 to 65,535 (in seconds)	Specify the interval for monitoring the completion of InfoPackage or a process chain. This value is used if you do not specify the interval for monitoring the completion of InfoPackage or a process chain on the `jbwipsta` command line of JP1/AJS3 for EAP. If this `key` specification is omitted, the InfoPackage completion monitoring interval value is 5 seconds.
`RetryTime`	0 to 65,535 (in minutes)	Specify a period of time during which attempts are made to restore connection with the SAP BW system if a communication error occurs during communication with the SAP BW system. Repeated attempts to recover the connection will be made until the duration specified here elapses. If you specify `0`, no attempt is made to restore the connection and an error is reported immediately. Specification of this key is ignored if you specify this key together with the `RetryCount` key. If neither the `RetryTime` key nor the `RetryCount` key is specified, the default value of the `RetryCount` key (`3` times) takes effect.^#3 To specify the interval between retries to restore connection, use the `RetryInterval` key.
`RetryCount`	0 to 65,535 (times)	Specify the number of retries to restore connection with the SAP BW system if a communication error occurs during communication with the SAP BW system. If you specify `0`, no attempt is made to restore the connection and an error is reported immediately. If you omit this key, the default value of `3` is assumed. The `RetryCount` key has priority over the `RetryTime` key if they are specified together. If neither the `RetryCount` key nor the `RetryTime` key is specified, the default value of the `RetryCount` key (`3` times) takes effect.^#3 To specify the interval between retries to restore connection, use the `RetryInterval` key.
`RetryInterval`	1 to 65,535 (in seconds)	If you specify the `RetryTime` or `RetryCount` key, specify the time interval between retries to restore connection with the SAP BW system if a communication error occurs during communication with the SAP BW system.^#4 If you specify the `RetryTime` key, a time longer than the time specified for the `RetryTime` key cannot be specified for the `RetryInterval` key. If you omit this key, the time interval is set to 180 seconds. The value of the `RetryInterval` key is invalid in the following cases: You specify `0` for the `RetryCount` key. You specify `0` for the `RetryTime` key without specifying the `RetryCount` key.
`RequestMonitorTime`	-1 or 0 to 65,535 (in minutes)	Specify a period of time during which InfoPackage request registrations are monitored (request registration monitoring time). If a request registration does not complete within the time specified by this value, the InfoPackage completion monitoring process ends abnormally. If you specify `-1`, the request registration monitoring time is the same as the `-time` option (length of time during which the completion is monitored) of the `jbwipsta` command. If you specify `0`, the completion monitoring for InfoPackage immediately ends abnormally if the request is not registered for the first status query. If you omit this key, `-1` is assumed.
`QMActionWaitTime`	0 to 65,535 (in seconds)	Specify a time period (wait time) during which InfoPackage ends normally and then the job that executes InfoPackage ends. In JP1/AJS3 for EAP, the completion of QM action (enabling processing of loaded data that is executed after InfoPackage data loading) or subsequent processing (such as deletion of duplicated requests) of InfoPackage cannot be monitored. If you wish to execute a subsequent job by waiting for the end of that processing, set this wait time. This value is used when you omit wait time specification`(-qmwait_time` option) in the `jbwipsta` command line of JP1/AJS3 for EAP. If this `key` specification is omitted, the wait time is `0` seconds.
`Codepage`	0 to 9999 (unit: Codepage number)	Specify the code page number to be used for character code conversion in the connected Unicode version SAP system. To exchange Japanese character data with a Unicode version SAP system, specify `8000` as the Shift JIS code page number. To use Japanese UTF-8 code as the character code in Linux, specify the same code page number. When character data is sent or received in English, this `key` does not need to be specified.

#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 path to use during execution of a JP1/AJS job, see the manual JP1/Automatic Job Management System 3 System Design (Configuration) Guide.
#3: The valid key differs depending on whether you specify the RetryCount key, the RetryTime key, or both.

Key specification			`RetryCount`
			Not specified	Specified
			Not 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
	Specified	`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.

#4: The following shows the operation when the RetryCount and RetryTime keys are specified:

[Figure]

To Page Top