EHS_MD_135_07 - Set Up Expert Server As a Windows ServiceVendor Master (General Section) BAL_S_LOG - Application Log: Log header data
This documentation is copyright by SAP AG.
In this IMG activity, you set up the Expertserver as a Windows NT or Windows 2000 service.
- Your PC runs on the Windows NT or Windows 2000 operating system.
- You have installed the Expertserver on your PC.
- You have configured the Expertserver for a certain destination. (In the following, the destination EHS_EXPERT is used as an example).
The Expertserver as a Windows service consists of the file EHSEXPSV.EXE that is automatically copied to the corresponding bin directory for Expertinstallation when installing the Expert2.7B (for example, c:\program files\ehs expert\bin). The bin directory should also contain the following three files:
- The administration program SVCADMIN.EXE, which can be used to install, configure, and check services
- The program library WIN32SVC.DLL
- The EHSSTART.EXE file to automatically start and monitor the WWI generation server or Expertserver as a Windows service
- Log on as local administrator to the PC.
- Start the MS-DOS prompt and change to the bin directory for Expertinstallation.
- Install the service by calling the EHSEXPSV file together with command line parameters as follows:
EHSEXPSV.EXE -I -N
- EHSEXPSV.EXE -I -NTest -DEHS_EXPERT installs the Windows service ExpertServer (Test). The destination EHS_EXPERT is used.
- Make the settings that are specific to the application for the Expertserver as a Windows NT service.
During the installation, for each service, a key is created with the name EhsExpertSvc(
) under the main key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services.
- Start REGEDIT.EXE via Start\Run\regedit.exe.
Choose the key EhsExpertSvc(
- Change the parameters if required.
- Destination: name of logical SAP system destination
- Idle Time:
- (default value = 1000 ms)
- InitialServerCount: Number of Expertserver threads that are created directly after the service is started.
- (Default value = 1)
- MaximumServerCount: Maximum number of Expertserver threads. As soon as the maximum is reached, a warning is logged. The service main thread then only functions as a database server.
- (Default value = 20)
- LogDirOptions: (Default value = 1 /F /P /E /L=clean.log)
Syntax: n [/F] [/P] [/E /L=
- The number n deletes all files whose creation date or change date is more than n days ago (with 1 <= n <= 365)
- /F If the parameter is set, the reference point for deleting is the creation date. If the parameter is not set, the reference point for deleting is the date of the last access or last change.
- /P If the parameter is set, subdirectory structures are retained and only files are deleted. If the parameter is not set, everything below the current directory is deleted.
- /E Logs the names of all files and directories that cannot be deleted owing to restricted access rights. /L=
Name of log file if parameter /E is set.
- 1 /F /P /E /L=clean.log deletes all files whose creation date is more than a day ago and log messages are created in the CLEAN.LOG file in the Expertdirectory.
- 1 /P deletes all files whose change date is more than a day ago.
- Configure the application log for Windows NT or Windows 2000.
- Start the Windows event viewer (EVENTVWR.EXE).
- Change the setting for the application log via Log -> Log settings to the option Overwrite Events as Needed to prevent an overflow in the event viewer.
- Test the service.
- Start and stop the ExpertServer (Test) service using the SVCADMIN.EXE program from the bin directory of the Expert installation or the Services control in Windows.
- Call the ExpertServer (Test) from the SAP System.
- Use the event viewer to check whether the respective commands in the application log file have been logged and whether the language-dependent texts for the events are displayed in the detail view.
- Check whether the service was started automatically on system startup by rebooting the PC and calling the ExpertServer (Test) from the SAP System.
To remove an installed service, proceed as follows:
- Log on to the PC with administrator rights.
- Start the service administration program SVCADMIN.EXE from the bin directory for the Expert installation.
- If necessary, close the current service using the Control and configure services function.
- Remove the service using the Uninstall services function.
Monitoring an ExpertServer
To monitor a service-based ExpertServer using EHSSTART.EXE, proceed as follows (prerequisite: you have configured EHSSTART.EXE as a service).
- Start the service administration program SVCADMIN.EXE from the bin directory of the Expert installation.
- Choose the Control and configure services function.
- Select the respective ExpertServer service or WWI generation server service.
- By pressing the Options button, an option dialog box is opened.
- Choose the Service Attributes tab.
- Set the Start type parameter to the option Manually.
- Add the internal service name (for example, EHSStart) to the Service Dependency dialog box using the Add Dependency button.
- Confirm the changes with OK.
- Close the EHSStart service and the service you just configured if necessary.
- Start the EHSStart service. After a short delay, this should start the service you just configured and monitor it. The principle here is that EHSStart starts and monitors all services that are dependent on it.
Addresses (Business Address Services) rdisp/max_wprun_time - Maximum work process run time
This documentation is copyright by SAP AG.
Length: 8921 Date: 20200606 Time: 062222 sap01-206 ( 36 ms )
Looking for Support? Questions?
Leave us your contact details and we will call you back. Panels marked with * are mandatory.