Application Trace Level 0 = Errors (error messages cannot be suppressed), 1 = plus Warnings, 2 = plus Infos, 3 = plus Debug, 4 = plus Fine Debug, If this parameter is set to 'true', the SLD is automatically started with the AS Java if the nominal state is 'started'. If this parameter is set to 'false', SLD startup is done during the first incoming request. Note: the START / STOP buttons on the Administration page define the nominal state of the application. Thus, the application does not start if it has been explicitly stopped on the Administration page. The SLD Working Directory by default points to the sub-directory 'sld' of the AS Java 'global' directory. The AS Java 'global' path is defined in the profile parameter 'DIR_GLOBAL' and can be read also from the Java System property 'sys.global.dir'. If you set the SLD Working Directory here, file upload, download, and SLD tracing features are re-directed. The parameter is used on all instances of the cluster after SLD restart. Caution: set this parameter for temporary purposes only!

If true, show technical CIM class names (SAP_BCSystem) instead of user friendly names (BC System) in instance and class browser. Refresh interval in seconds for views with auto-refresh functionality. Format used for displaying and entering dates. Use MM for month, dd for day, yy or yyyy for year. Format used for displaying and entering times. Use HH for hours, mm for minutes, ss for seconds. Check new software component and software component version names against rules of NetWeaver Development Infrastructure (NWDI). Number of instances or items that is considered large. The UI will react differently if a list has more than that many items. For example, the Technical System list will not display instances at startup, and the log will not display more lines without filtering. Set to 0 to disable this feature. Number of change log entries that is considered large. If a change log search has more hits than specified by this parameter, a warning dialog will be displayed requesting user confirmation before continuing with a possible long-running change log search. Specifying zero or a negative value will disable this warning dialog.

If 'true' the object manager uses a memory cache for CIM instances. Maximum number of CIM instances held in the SLD instance cache. Eviction is based on an LRU strategy (LRU = Least Recently Used). Defines a time-to-live (TTL) for entries in the SLD instance cache. If a cache entry is older than the TTL it will be evicted regardless of any other considerations. This TTL ensures that potential mismatches in the instance cache are not conserved indefinitely, e.g. if a cache invalidation message is lost. Specifying zero or a negative value disables TTL handling entirely. If 'true' modifications of CIM classes are checked in a strict manner. This means that any incompatible change to a class is rejected no matter if there are any instances present that can not be updated consistently. However, if this parameter is set to 'false' incompatible changes to CIM classes will be allowed if there are no instances present or if all instances can be updated consistently. If 'true' modifications of CIM qualifiers are checked in a strict manner. This means that any incompatible change to a qualifier is rejected no matter if the qualifier is used by any class or instance. However, if this parameter is set to 'false' incompatible changes to CIM qualifiers will be allowed if the qualifier is not used anywhere.

Maximum error count for soft errors (default: 100). Soft errors in an SLD import are those related to the content, that is, the data to be imported does not fit to the current SLD content. The most prominent examples are cardinality violations and missing association ends. The import aborts when the number of soft errors exceeds the limit set here. Set a negative value for an unlimited count.

If set to true, the RFC server part of the SLD bridge is started. The RFC server part accepts SAP Application Server ABAP system data. Host name of the SAP gateway where RFC (ABAP) data suppliers send data to. This can be either a standalone gateway, the central service instance gateway (7.10), or the gateway of the ABAP system. Service name (sapgwXX) or port number (33XX) of the SAP gateway on the host specified by parameter 'GatewayHost' where the SLD bridge registers itself. If set to true, write all incoming data packets as files into sub directory 'trace/Bridge' of the SLD working directory (see Server Settings). Program ID of the SLD data supplier bridge at the SAP gateway for Unicode RFC partner systems. Important Note: Do not change this value without changing the program ID in the RFC destinations of all (!) SAP Application Servers ABAP registering in this SLD. All these systems have to be on release 7.10 or higher. Program ID of the SLD data supplier bridge at the SAP gateway for NONE Unicode RFC partner systems. Important Note: Do not change this value without changing the program ID in the RFC destinations of all (!) SAP Application Servers ABAP registering in this SLD. All these systems have to be on release 7.10 or higher. Defines the timeout that is used to check the availability of unresponsive remote data supplier targets. If data suppliers are forwarded to an unrepsonsive SLD system, forwarding to other SLD systems could be hindered. To avoid such a situation an unresponsive system is pinged using this (typically short) timeout to skip forwarding if the system is not yet available again. Decreasing this value may speed up forwarding if there is an unrepsonsive system but can lead to failures in detecting that a previously unresponsive system is available again. Increasing this value may slow down forwarding if there is an unrepsonsive system. Specifying zero or a negative value disables the ping mechanism. In this case each forwarding target will be used when a data supplier package is received without checking its responsiveness first. Time interval (in seconds) during which complete processing of supplied data is enforced. This means, data that is reported multiple times within this interval will be processed like new or changed data, even if it does not contain any changes compared to previous data. For example, by manually triggering a data supplier twice you can enforce complete processing. Specifying zero or a negative value disables this feature. Time interval (in hours) during which complete processing of supplied data is omitted for unchanged data to improve bridge throughput. This means, unchanged data that is reported multiple times within this interval will not be processed. Only the sync time stamp will be updated. Specifying zero or a negative value enforces complete processing of all supplied data. The SNC (Secure Network Communications) component provides extra security by encrypting data and guaranteeing more secure authentication by both partners in a communication. If you have SNC installed, you can choose whether to use the extra security functions by setting the SNC mode. SNC name of the RCF server program. Example: p:CN=testuser, OU=TEST01, O=SAP, C=DE Quality of protection of data transfer for connections that are initiated by the SAP system. The following values are available: 1 = Secure authentification only 2 = Data integrity 3 = Data confidentiality External security product's library. Path and file name of the library. Example: c:\usr\sap\SAPCryptolib\sapcrypto.dll Defines a lifetime for technical instance data, e.g. SAP_J2EEEngineInstance (SAP AS Java Instance) or SAP_BCApplicationServer (BC Application Server). The corresponding time unit is specified by the TechnicalInstancesLifeTimeUnit parameter. When a system registers itself in SLD, a technical instance will be deleted together with all data that depends on it if the technical instance has not been supplied for a time period exceeding this lifetime. If this parameter is set to 0, technical instances will be deleted immediately in case of absence. A negative value means the lifetime is infinite, and the technical instances will never be deleted automatically. Once this parameter is activated, the last synchronization time of old technical instances, which are not supplied anymore, is updated to a value 12 hours in the past. That means SLD assumes that such technical instances have been reported by the previous registration. Defines the time unit for the TechnicalInstancesLifeTime parameter. Possible values are: 0 = seconds 1 = hours 2 = days Any other value is interpreted as the default value. Controls the behavior of the automatic AS Java or AS ABAP system move that is initiated by a host name change while processing data in the SLD bridge. The automatic move can prevent system duplicates in SLD. You can select from the values: 0 = No system move is initiated by host name change even if SID and the Installation Number (10-digit) of the system are the same. A new system is created in SLD. 1 = Recommended: The system is moved to a new host name, but only if SID, Installation Number (10-digit) and System Number (18-digit) are the same as in the previous system. 2 = Restricted: The system is moved if SID and Installation Number (10-digit) are the same. This is a special method that must only be used if system landscape must not contain the same SID twice. Using this value is not recommended, use only on explicit advice. Any other value is interpreted as the default value.

Maximum lifetime in seconds for user objects cached internally (default: 0). Zero or a negative value will disable the user cache. Enabling the user cache may be required in certain scenarios to improve performance.

This interval defines the minimum rate (in seconds) at which SLD content sync sources will be queried for changes. If no content sync notification has been received in the polling interval, the target SLD actively polls for changes in source systems. Usually the polling interval is longer than the notification interval to rely on notifications rather than regular polling. Specifying a lower value results in more synchronous behavior of content synchronization (if no notifications are used) but increases network traffic due to frequent polling. Specifying a higher value results in more asynchronous behavior (if no notifications are used) and reduced network traffic. If zero or a negative value is specified, polling will be disabled. This interval defines the maximum rate (in seconds) at which remote SLD systems will be notified about content changes. When a content change occurs in the notification interval after the last change, the notification will be delayed to the end of this interval. Otherwise, a notification will be sent immediately. If you specify a lower value, this will result in more synchronous behavior of content synchronization but increases network traffic due to notifications. If you specify a higher value, this will result in more asynchronous behavior and reduced network traffic. If zero or a negative value is specified, notifications are disabled. For example, disabling notifications is necessary if a firewall prevents access from the content synchronization source in direction of the target SLD. This parameter defines the maximum number of threads used for content synchronization. Increasing this value will consume more resources, but may increase throughput because background processing may be executed in a parallel manner. Please note that parallelization is only possible for different target namespaces. Synchronizing content from multiple sources into the same target namespace can not be executed in parallel. If zero or a negative value is specified, "1" will be used instead. This interval defines the timeout in seconds used for remote requests to content synchronization source systems. This value defines the time interval used for querying change log entries from the source system that occurred since the last processed entry. Zero or a negative value means that no time interval is used. Setting a time interval incurs additional overhead but may become necessary if timeouts occur due to a large number of pending changes (millions). For example, this can happen if the source SLD is affected by an endless circular bridge forwarding of generic data suppliers for an extended period of time. For details on this issue refer to SAP note 1721707. This parameter determines behavior of the prerequisite model version check that is performed at the beginning of a full sync. If 'true' is selected, the target namespace is allowed to have a higher model version than the source (the default is that both models must be identical). Note that in such a case the full sync may take more time, because fingerprint comparison of instances may detect differences simply because classes differ. Switch for the conflict resolution enabling the update of individual, non conflicting properties. In general, a change message is conflicting with the target namespace, if the original state of the change differs from the current target state. In default resolution mode, the content synchronization rejects the complete instance change in case of a conflict and a message rank lower than the target namespace rank. If this switch is set to TRUE, every property of the instance is checked individually for conflicting with the target state. In this mode only the conflicting properties are rejected, the non conflicting properties are updated in the target namespace. In case of a bi-directional content synchronization it is recommended to run both sides in the same conflict resolution mode.