Job Management Partner 1/Automatic Job Management System 3 for Enterprise Applications Description, User's Guide and Reference

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 UNIX-based OSs:
/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 UNIX-based OSs

Figure 2-8 Model file for the environment setup file for InfoPackage control or process chain control (for UNIX)

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-11 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 1 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): 2.0 kilobytes
2 (detail level): 3.5 kilobytes + (InfoPackage or process chain execution time)/completion monitoring interval) x 0.2 kilobytes
3 (debug level): 24.0 kilobytes + (InfoPackage or process chain execution time)/completion monitoring interval) x 2.4 kilobytes

When not monitoring the completion of InfoPackage or process chains:
1 (standard level): 2.0 kilobytes
2 (detail level): 3.5 kilobytes
3 (debug level): 24.0 kilobytes

Normally, select standard level. The detail level or 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 65,535 (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 12,288 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

UNIX:

Character string beginning with /

Trace information about all applications will be collected in the specified file.
If you omit this key, a trace file is created for each application in the default directory.^#3

#1

If you specify 12,288 kilobytes as the trace file size, the trace file can record at least two days' worth of trace data when 100 jobs are executed per hour at trace level 1 (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.

#3

For details about the default directory that stores the trace file, see A. Directory List.

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 UNIX, specify whether to generate syslog messages.

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

Table 2-12 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 UNIX. 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 codepage 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-13 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

UNIX:

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^#1 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 type a setting of 0 or omit this key specification, the encountered error will be reported immediately and no attempt will be made to recover the connection.
If the RetryTime key is specified together with the RetryCount key, the RetryTime key is ignored. If neither the RetryTime key nor the RetryCount key is specified, the RetryCount key is valid^#2.
To specify the interval between reconnection retries, 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 retry is attempted and an error is reported immediately.
If you omit this key, 3 is assumed.
If the RetryCount key is specified together with the RetryTime key, the RetryTime key is ignored. If neither the RetryCount key nor the RetryTime key is specified, the RetryCount key is valid^#2.
To specify the interval between connection retries, use the RetryInterval key.

RetryInterval 1 to 65,535 (in seconds) Specify the interval at which attempts are made to restore connection with the SAP BW system if a communication error occurs during communication with the SAP BW system. The value specified here cannot exceed the value set for RetryTime. If you omit to specify this key, 180 seconds is set automatically. If you do not specify RetryTime or you set 0 for it, this RetryInterval setting is invalid.

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 codepage number to be used for character code conversion in the connected Unicode version SAP system.
When character data is sent or received in English, this key does not need to be specified.

#1

For details about the work path to use during execution of a JP1/AJS job, see the manual Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

#2

The RetryCount key and the RetryTime key are mutually exclusive. The valid key differs depending on the combination of the two keys as shown below:

Specified key Valid key

RetryCount key RetryTime key RetryCount key RetryTime key

Yes Yes Yes No

Yes No Yes No

No Yes No Yes

No No Yes No

Legend:

Yes: The key is specified or valid.

No: The key is not specified or not valid.

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 1 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): 2.0 kilobytes 2 (detail level): 3.5 kilobytes + (InfoPackage or process chain execution time)/completion monitoring interval) x 0.2 kilobytes 3 (debug level): 24.0 kilobytes + (InfoPackage or process chain execution time)/completion monitoring interval) x 2.4 kilobytes When not monitoring the completion of InfoPackage or process chains: 1 (standard level): 2.0 kilobytes 2 (detail level): 3.5 kilobytes 3 (debug level): 24.0 kilobytes Normally, select standard level. The detail level or 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 65,535 (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 12,288 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 UNIX: Character string beginning with /	Trace information about all applications will be collected in the specified file. If you omit this key, a trace file is created for each application in the default directory.^#3

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 UNIX. Specify whether or not to generate syslog messages. If this key specification is omitted, YES is used as the syslog message generation condition.

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 UNIX: 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^#1 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 type a setting of 0 or omit this key specification, the encountered error will be reported immediately and no attempt will be made to recover the connection. If the RetryTime key is specified together with the RetryCount key, the RetryTime key is ignored. If neither the RetryTime key nor the RetryCount key is specified, the RetryCount key is valid^#2. To specify the interval between reconnection retries, 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 retry is attempted and an error is reported immediately. If you omit this key, 3 is assumed. If the RetryCount key is specified together with the RetryTime key, the RetryTime key is ignored. If neither the RetryCount key nor the RetryTime key is specified, the RetryCount key is valid^#2. To specify the interval between connection retries, use the RetryInterval key.
RetryInterval	1 to 65,535 (in seconds)	Specify the interval at which attempts are made to restore connection with the SAP BW system if a communication error occurs during communication with the SAP BW system. The value specified here cannot exceed the value set for RetryTime. If you omit to specify this key, 180 seconds is set automatically. If you do not specify RetryTime or you set 0 for it, this RetryInterval setting is invalid.
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 codepage number to be used for character code conversion in the connected Unicode version SAP system. When character data is sent or received in English, this key does not need to be specified.

Specified key	Valid key
RetryCount key	RetryTime key	RetryCount key	RetryTime key
Yes	Yes	Yes	No
Yes	No	Yes	No
No	Yes	No	Yes
No	No	Yes	No

[Contents][Back][Next]

[Trademarks]