Redpeaks V6.8
Trouble shooting
Monitors Guide
Sidebar
products:promonitor:6.8:monitorsguide:netweaver:sapchangesettings
Book Creator
Add this page to your book
Add this page to your book Book Creator
Remove this page from your book
Remove this page from your book 
Manage book (
Help Table of Contents
SAP change settings
Clients correct configuration is important to guaranty system integrity against changes. This monitor will check that system and clients change modes are matching the expected configuration.
Configuration hints
- You can define the expected global change mode of the SAP system and make sure to be notified as soon as the mode changes.
- This can be used primarily to make sure that your production system cannot be modified.
- For each client or for each type of client role, you can define the expected customization options.
- You can also check that each client has the correct logical name.
- Use the surveillance table to adjust the monitoring settings: Thresholds, severity, filters, etc…
Client settings configuration
- The monitor allows some degrees of flexibility on what the client configuration is expected to be.
- The below settings allow to define if some client changes must be completely disabled, or if any other settings are accepted.
- Client change:
- Must be set to false if the expected configuration is No Changes Allowed
- If set to true, any other setting will be accepted
- Cross client custo change
- Must be set to false if the expected configuration is either No changes to cross-client Customizing objects or No changes to Repository and cross-client Customizing objects
- If set to true, any other setting will be accepted
- Cross client repository change
- Must be set to false if the expected configuration is either No changes to Repository objects or No changes to Repository and cross-client Customizing objects
- If set to true, any other setting will be accepted
Atomic fields
| Check missmatch between system change mode and the monitoring configuration | If checked, the probe will check that system change mode is matching the monitoring configuration |
|---|---|
| Severity if missmatch found | The level of severity of the alarm generated if a missmatch is found |
| Expected mode “Modifiable” | If checked, the expected mode will be “Modifiable” |
Surveillance table
SAP clients change mode
| Parameter | Description |
|---|---|
| Active | Use this field to activate or deactivate a line of configuration. |
| Client | Define the client for which to set the rule, or * for a role based surveillance. |
| Logical name | The expected logical name for a given client (Client has to be specified in client field) |
| Role | If Client field contains *, this rule will define the customization settings for all clients associated to the given role. If a specific client is set in client field, it will also check that the client is associated to the given role. |
| Client change | Defines if the client configuration changes are completely disabled or not. |
| Cross client custo change | Defines if cross client customization is completely disabled or not. |
| Cross client repository change | Defines if cross client repository change is completely disabled or not. |
| Changes and transport configuration | Defines the expected configuration for changes and transports. Use NO_CHECK if this should be checked |
| Cross client configuration | Defines the expected cross client configuration. Use NO_CHECK if this should be checked |
| Client copy | Defines the expected client copy configuration. Use NO_CHECK if this should be checked |
| CATT configuration | Defines the expected CATT and eCATT configuration. Use NO_CHECK if this should be checked |
| Severity | The level of severity of the alarm generated by this line of surveillance. |
| Auto clear | If checked, the alarm will be cleared as soon as the alarm condition is not met anymore. |
| Alarm tag | This field allows to add custom text within the alarm message. %MSG% variable will contain the actual generated message and can be used such as: “my_prefix %MSG% my_suffix”. By default, tag will be used as prefix. |
| Alarm | If checked, this line of surveillance will be used for alarm generation. |
| Metric | |
| Report | If checked, this line of surveillance will used for showing threshold and severity in the daily report |
Examples
| Active | Client | Logical name | Role | Client change | Cross client custo change | Cross client repository change | Severity | Auto clear | Alarm tag | Alarm | Metric |
|---|---|---|---|---|---|---|---|---|---|---|---|
| true | * | * | Production | false | false | false | MAJOR | true | true | false |
Effect : Checks that all clients with Production role cannot be changed and that cross client custo. and repository changes are not allowed.
Examples
| Active | Client | Logical name | Role | Client change | Cross client custo change | Cross client repository change | Severity | Auto clear | Alarm tag | Alarm | Metric |
|---|---|---|---|---|---|---|---|---|---|---|---|
| true | 066 | ID2CLNT066 | Customizing | true | true | true | MAJOR | true | true | false |
Effect : Sends an alarm if client 066 has not the correct logical name, if it is not associated to Customizing role and if the expected change and customization settings are not respected.
Generated metrics
| metricId | metricUnit | metricTarget | metricDescription |
|---|---|---|---|
| SYSTEM_GLOBAL_CHANGE_LOCKED | Status | SID | Sends TRUE if the system change mode is authorized, FALSE instead |
/home/clients/8c48b436badcd3a0bdaaba8c59a54bf1/wiki-web/data/pages/products/promonitor/6.8/monitorsguide/netweaver/sapchangesettings.txt · Last modified: 2024/09/13 15:03 by rbariou
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
