Configuring Operation Settings

You use this procedure to specify the general operation settings.

Prerequisites

When using an ABAP system or LDAP as the backend for user management, use a local user of the SAP NetWeaver Java engine to perform the configuration. Otherwise, the jobs stop working if the user backend is unavailable.
You have the authorization to configure engine settings.

For more information, see Standard Permissions.

Procedure

Choose Setup Settings.
Choose Expert Mode.
On the Engine tab, choose Edit.

Specify your general operation settings.

Field	Default Value	Possible Values	Description
Allow Multiple Instances on same Host	Checkbox deselected	Checkbox selected Checkbox deselected	To prepare and run one instance on a host, keep this checkbox deselected. Example You allow one application server or a single system database, or a single custom instance to run on one host at a time. To prepare and run multiple instances on the same host, select this checkbox. Example You run an application server instance installed traditionally together with an adaptive-enabled application server instance on one host. You run multiple adaptive-enabled application server instances on one host. You run a system database together with a central instance on one host. You run an application server instance together with a custom instance on one host. You can configure but you cannot prepare and run multiple instances with common exclusively consumed operating system (OS) resources such as network ports, OS instance names, or custom resources on the same host. Example Two instances that both use the port 50100 cannot run together on the same host. You cannot prepare and run multiple instances using the same local mount points with different export paths or different mount options on the same host.
Allow Multiple Database Instances on Same Host	Checkbox deselected	Checkbox selected Checkbox deselected	To prepare and run multiple database instances which were installed traditionally or are adaptive-enabled on the same host, select this checkbox. Note This can increase the risk of data loss. You can configure but you cannot prepare and run multiple database instances with common exclusively consumed OS resources such as network ports, OS instance names, or custom resources on the same host. Example Two database instances that both use the port 50100 cannot run together on the same host. You cannot prepare and run multiple database instances using the same local mount points with different export paths or different mount options on the same host. For more information, see SAP Note 919135 .
Automatic Mountpoint Creation	Checkbox deselected	Checkbox selected Checkbox deselected	To create mount points automatically during prepare operations, select this checkbox.
Automatic Mountpoint Deletion	Checkbox deselected	Checkbox selected Checkbox deselected	To delete mount points automatically during unprepare operations, select this checkbox.
Enable User Exit Scripts	Checkbox deselected	Checkbox selected Checkbox deselected	To call configured pre- and/or post-operation user exits, select this checkbox. Note To individually decide whether to call configured user exits scripts for an operation, you can additionally select the Enable User Exit Scripts Individually per Operation checkbox in the Advanced Operation Settings.
Default Timeout for Soft Shutdown of Non-Database Instances [seconds]	300	0 - 3600	Specify a timeout for the soft shutdown of instances that do not represent a database. After the timeout specified is reached, SAP Landscape Management performs a hard shutdown.
Perform Hard Shutdown as Default Stop Operation for Database Instances	Checkbox deselected	Checkbox selected Checkbox deselected	To perform a soft shutdown as default stop operation for database instances, keep this checkbox deselected. To perform a hard shutdown as default stop operation for database instances, select this checkbox. Note To individually choose the shutdown option before stop operations, you can select the Show advanced shutdown options during stop operations checkbox in the Advanced Operation Settings.
Perform Hard Shutdown for Other Database Instances [DB types semicolon separated]	<empty>	Database types separated by `;`: `ORA` `MSS` `ADA` `DB6` `DB2` `DB4`	To perform a hard shutdown as default stop operation for other database instances, enter the database types. For more information, see SAP Note 1663409 .
Perform Hard Shutdown as Default Stop Operation for Non-Database Instances	Checkbox selected	Checkbox selected Checkbox deselected	To perform a soft shutdown as default stop operation for instances not representing a database, deselect this checkbox . To perform a hard shutdown as default stop operation for instances not representing a database, keep this checkbox selected. Note To individually choose the shutdown option before stop operations, you can select the Show advanced shutdown options during stop operations checkbox in the Advanced Operation Settings.
Ignore User for SAP HANA shutdown	<empty>	Java regular expressions separated by `;` To ignore all users starting with USR_, enter `USR_.*`	Enter users which can be ignored during a soft shutdown. Example Monitoring users, XS Advanced Controller users. Recommendation Ignore only users with read-only permissions.
Ignore Hosts for SAP HANA shutdown	<empty>	Java regular expressions separated by `;`	Enter host connections, you want to be ignored during a soft-shutdown. Example Central Monitoring Hosts
Timeout for all Operations Related to: DB Instances [min]	0	0 - 120	Specify a timeout for operations on database instances. If the time specified is exceeded, SAP Landscape Management cancels the requests. By default, SAP Landscape Management waits indefinitely for an operation response.
Timeout for all Operations Related to: AS Instances and Central Instances [min]	0	0 - 120	Specify a timeout for operations on application server instances and central instances. If the time specified is exceeded, SAP Landscape Management cancels the requests. By default, SAP Landscape Management waits indefinitely for an operation response.
Timeout for all Operations Related to: Central Services, ERS, Web Dispatcher, and TREX [min]	0	0 - 120	Specify a timeout for operations on central services, enqueue replication servers, Web dispatchers, and TREX. If the time specified is exceeded, SAP Landscape Management cancels the requests. By default, SAP Landscape Management waits indefinitely for an operation response.
Socket Timeout for all: Single Custom Operations of Type "HTTP POST" and "Web Service" [seconds]	100	0 - 3600	Specify a timeout for a single custom operation of type HTTP POST or Web Service. If the time specified is exceeded, SAP Landscape Management cancels the requests.
Socket Timeout for all: Mass Custom Operations/Hooks of Type "HTTP POST" and "Web Service" [seconds]	30	0 - 3600	Specify a timeout for a custom mass operation or a custom hook of type HTTP POST or Web Service. If the time specified is exceeded, SAP Landscape Management cancels the requests.
Timeout for synchronous operations [seconds]	20	5 - 120	Specify a timeout for synchronous operations such as RFC operations or synchronous custom operations. You specify the maximum time during which the UI is blocked waiting for synchronous operations to be executed. If the operation is completed within this time, the result is displayed in a dialog box. Otherwise, you can check the result in the logs of the operation.

Save your entries.

Results

The following SAP Landscape Management jobs are rescheduled using the current user:

LVM_Job_ProcessExecutor
LVM_Job_ProcessCleaner

You can review the status of the jobs and the scheduling user in the SAP NetWeaver Administrator tool Java Scheduler.