Kontakt

Ansicht
Dokumentation

EHS_MD_135_02 - Set Up Windows Registry

EHS_MD_135_02 - Set Up Windows Registry

rdisp/max_wprun_time - Maximum work process run time   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.
SAP E-Book

If you are not using service administration, you must process this Customizing activity to enter the configuration of Expert in the Windows registry. If you have service administration, you configure the relevant settings directly in service administration (see the Customizing activity Set Up Server Using EH&S Service Administration).

Using the Expert Admin icon, open the Expert Administration dialog box.

The following settings are generated automatically during installation and if possible, you should not change them:

  • Global Settings
  • Server Polling Intervall..milliseconds field

Typical value: 100
Value in [ms] after which the program checks whether a request from the SAP system to determine data is present.
  • Maximum Number of Requests before Restart field

Typical value: 100
Number of requests that the Expert server processes. For performance reasons, the Expert server then starts a new Expert server and terminates itself.
  • Product Safety Version: Value that was specified during installation

  • Reconnect Wait field

Typical value: 500
Value in [sec] after which Expert attempts to reconnect to the SAP system after an interruption. This means Expert is not interrupted if the SAP system is not available for a brief period of time.
  • CheckGateway field

Typical value: 300
Expert works as a registered RFC server that registers itself in an SAP system when it is started and waits for jobs. The RFC connection may be lost at any time, for example, if the network is interrupted or the SAP system is restarted. The RFC registration may be lost without the Expert server being aware of this. Other jobs do not then arrive at the Expert server. To prevent this, the Expert server can be set up so that it checks its own registration independently at specified time intervals. If the registration has been lost, the Expert server attempts to reestablish the connection after the intervals defined in the Reconnect Wait field. You can use the CheckGateway setting to define an interval in seconds for the active check of the RFC connection. If you enter the value 0 or the setting is missing, no check is carried out. Note that when the check for registration is active, it slows down the network and may create log entries for routers and gateways.
  • ReOrderBytes

This value is obsolete since Expert 2.7B SP03.
  • ShowBapiTime field

Value: oder Yes
Enter Yes if you want to display in the DOS console or the Windows event display how long the respective calls to the Business Application Programming Interface (BAPI) modules took to read and write the input and output data for Expert data determination.
  • CacheRoot field

Directory for the Expert cache
  • Instances
  • IgnoreWarnings

Value: A list, seperated by commas, that covers the numbers of those warnings that should no longer been issued by the corresponding rule set instances.
  • Nur für OCC: HeaderCachingActivated

Depending on performance reasons, you can define whether the caching of header XML files should be used or not.
Value: Yes or No.
  • Systems (settings for the Expert entry)
  • Core Module (DLL) field

Value: ExpCore.dll
Defines the *.DLL file for the Expert server.
  • Working Directory field

Value: for example, C:\Program Files\EHS Expert\Rules
Working directory
  • Logging Directory field

Value: for example, C:\Program Files\EHS Expert\Log
Log directory
  • Additional Settings list, name RfcLog

Value: Yes or No
Here you can activate a log of the data exchange for all sets of rules. For more information, see Activities.
  • Additional Settings list, name LogLevel

Value: for example, 0
Here you can activate a log of the rule execution for all sets of rules. For more information, see Activities.
  • Additional Settings list, name Install Dir field

Value: for example, C:\Program Files\EHS Expert\BIN
Installation directory
  • InTy

This value is obsolete with EHS Expert 2.7B SP3.
  • WildcardMap

This value is obsolete with EHS Expert 2.7B SP3.
  • Valid only for OCC: LanguageFile

Gibt den Pfad zur Sprachdatei für die Dialogfelder an.
  • Valid only for OCC: SubNameDisplayLength

Specifies the number of digits of a substance name that are displayed.
If the name of the substance is longer, the remaining digits are cut.
The standard value is 50.
  • Valid only for OCC: FactRecID

The specifies the mapping of the clear OCC unique ID for freetext
categories. The standard value is: /DEF=TEXTCAT:OCCUNQID
  • Valid only for OCC: ColumnsRequired

Specified the number of columns that are displayed in the OCC dialog. The standard value is 3.
  • SAP Destinations
You can also make the settings described in the Customizing activity Set Up SAPRFC.INI on the SAP Destinations tab page. To do this, choose Add and configure the required settings.
In addition, you can adapt the settings described here under Global Settings specifically for a particular SAP system and thus run Expert with Product Safety systems or SAP systems of different versions on the same PC.

You register sets of rules for Expert under Instances. Demo sets of rules are delivered with the standard system (Demo1, Demo2, Demo3). To register a new set of rules, proceed as follows:

  1. Choose Add.
The New Instance dialog box appears.
  1. Enter the key for the new set of rules and choose OK. The set of rules is identified by means of this key in parameter EXPERT_RULE_SET (see Extend Entry in Secondary Data Determination).
The key is transferred.
  1. Under Rule File, enter the name and path of the rule file: \.RUL
  2. Under Map File, enter the name and path of the file that contains the mapping tables: \.MDB
  3. Under LogLevel enter a number between 0 and 15 for the log type of the Expert server. The higher the number, the more detailed the log that the Expert server generates. The file name of the log is EXP.LOG. No log is generated for the value 0. The following log types exist:
  • ERROR: displays the errors in rule processing

The message text is relayed to the calling system as follows: ERROR("","","",""," ")
Expert contains an error message table in the calling interface that includes internal errors (for example, errors reading and writing the data, errors in the mapping tables, and so on) as well as errors created by the person who created the set of rules using the ERROR command.
The message number indicates a message code in the following form:
- The first character indicates the message type (E for error, W for warning, I for information).
- The next two characters indicate the message class (typically a customer message class specially created for the set of rules).
- The next three characters indicate the message number.
The message text specified is output if no text is specified in the SAP system. The three further optional parameters are inserted in place of placeholders in the message text.
Example:
ERROR("EZM502","Identifier & & with error", "NAM", "PROD")
  • FACTS AFTER APPLY: Displays the facts with the data that is returned as the result after the rules are applied

  • FACTS WITH DATA: Displays the facts with the data before the rules are applied

  • APPLY COND: Displays the condition of the respective rules while they are being applied

  • APPLY TODO: Displays the respective TODOs being applied while the rules are being applied

  • APPLY NAME: Displays the respective names of the rules being applied while the rules are being applied

  • APPLY RULE: Displays the complete rule text of the respective rule being applied while the rules are being applied

  • ISFREE: Displays the status of the rules with respect to their preconditions (for example, whether a rule cannot be applied for specific reasons)

  • DEPEND PATH: Displays the rules that are dependent and on which the rule itself depends

  • EVALUABLES: Displays the result of the check, or in other words, whether or not a fact is empty

  • EVAL: Displays the result of an arithmetic expression (for example, A + B < C - D => result: A + B = 5, C - D = 6, 5 < 6 = -1)

  • RULES AFTER PARSE: Displays the rules that result after parsing after the rule file has been loaded. The sequence corresponds to that of the rule file. Parsing is the process of loading a set of rules. The syntax is checked, syntax errors are identified, and memory structures are generated in Expert in accordance with the rules.

  • REDUCE: Not currently used.

  • STATISTIC: Not currently used.

LogLevel Log Type Executed
0 No log
1 ERROR, FACTS AFTER APPLY
2 ERROR, FACTS AFTER APPLY, FACTS WITH DATA
3 ERROR, FACTS AFTER APPLY, FACTS WITH DATA,
APPLY COND
4 ERROR, FACTS AFTER APPLY, FACTS WITH DATA,
APPLY COND, APPLY TODO, APPLY NAME
5 ERROR, FACTS AFTER APPLY, FACTS WITH DATA,
APPLY COND, APPLY TODO, APPLY RULE
6 ERROR, FACTS AFTER APPLY, FACTS WITH DATA,
APPLY COND, APPLY TODO, APPLY NAME, ISFREE, EVAL
7 ERROR, FACTS AFTER APPLY, FACTS WITH DATA,
APPLY COND, APPLY TODO, APPLY RULE, ISFREE, EVAL
8 ERROR, FACTS AFTER APPLY, FACTS WITH DATA,
APPLY COND, APPLY TODO, APPLY NAME, DEPEND PATH
9 ERROR, FACTS AFTER APPLY, FACTS WITH DATA,
APPLY COND, APPLY TODO, APPLY RULE, DEPEND PATH
10 ERROR, FACTS AFTER APPLY, FACTS WITH DATA,
APPLY COND, APPLY TODO, APPLY NAME, ISFREE, DEPEND
PATH, EVALUABLES
11 ERROR, FACTS AFTER APPLY, FACTS WITH DATA,
APPLY COND, APPLY TODO, APPLY RULE, ISFREE, DEPEND
PATH, EVALUABLES
12 ERROR, FACTS AFTER APPLY, FACTS WITH DATA,
APPLY COND, APPLY TODO, APPLY RULE, ISFREE, DEPEND
PATH, EVALUABLES, RULES AFTER PARSE
13 ERROR, FACTS AFTER APPLY, FACTS WITH DATA,
APPLY COND, APPLY TODO, APPLY RULE, ISFREE, DEPEND
PATH, EVALUABLES, EVAL, RULES AFTER PARSE
14, 15 ERROR, FACTS AFTER APPLY, FACTS WITH DATA,
APPLY COND, APPLY TODO, APPLY NAME, APPLY RULE,
ISFREE, DEPEND PATH, EVALUABLES, EVAL, RULES AFTER
PARSE, EXPANDED RULES, REDUCE, STATISTIC

  1. Enter Yes under RFC Log if you want the system to create a log that displays the parameter tables that are transferred between the BAPIs and Expert. In this way you can analyze problems that may occur when reading and writing the specification data. The file name of the RFC log is RFC.LOG.
  2. Enter EHSExpert under System. If you want to create a link to other expert systems, you can enter the name of the set of rules engine here. The alternative set of rules engine must be configured under Systems and be sufficient for the Expert interface.
  3. Configure any additional settings required. In the Additional Settings list, you can add entries with Add and delete them with Delete. Possible additional settings are:
Name: IgnoreWarnings, value Yes to ignore all warnings, or a list of warning numbers in the message class CM_EXPERT that Expert is to ignore, separated by commas, for example, "332,355,341,301,356". Errors cannot be ignored.
  1. Choose Save.

Sets of rules that are stored in the SAP system database must not be registered here. The instance DefaultEasyExpert that was created during installation is used automatically here. You can change its standard settings if you wish.






CL_GUI_FRONTEND_SERVICES - Frontend Services   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Length: 19588 Date: 20240417 Time: 014052     sap01-206 ( 203 ms )