Consider the following rules for a shared-resource system: • There are n shared
ID: 3857679 • Letter: C
Question
Consider the following rules for a shared-resource system:
• There are n shared data resources and m clients where n and m are positive integers.
• The resources are accessed via a network connection.
• The clients may read and write to the shared resources and may only execute one operation at a time.
• Clients’ read and write requests are served sequentially as they are received.
Propose rule changes and possible additional operations on resources besides read or write that would ensure the following:
• No client’s modifications can be overwritten by another client’s out-of-date revisions.
It may help to add new operations in addition to read and write, as well as enforce rules on the order in which a client can execute operations. Please provide a scenario, incorporating the operations and rules, on how the system works.
Explanation / Answer
A scenario, incorporating the operations and rules, on how the system works if we have a client.
So lets go with the SAP level and SAP standard of securing the different clients in the Business.
In SAP there are special settings for securing the business data in it.
The settings like:
- Changes w/o automatic recording:- client dependent objects may be changed without being recorded in change
requests. Used for tests or training clients.
- Automatic recording of changes: attempts to make client dependent changes will result in a prompt for a
change request in which to record the changes. Used for customizing clients
- No changes allowed:- client dependent objects cannot be changed. Used for production, SAP reference clients
or test clients in QA.
- No transports allowed: changes are allowed but cannot be transported out of the system.
Used for sandbox, pre-config. clients or training clients.
There are Cross-client change options also there:
- Changes to repository and client-ind. Customizing allowed:- no restrictions. Used in development clients.
- No changes to client-ind. Customizing objects:- Repository objects (programs, table definitions, etc.)
can be changed but some customizing which are client independent cannot be.
Used in ABAP only development clients.
- No changes to repository: Repository objects (programs, table definitions, etc.) cannot be changed
but some customizing which are client independent can be. Used in customizing only development clients.
- No changes to repository and client-independent custom. Obj.: no client independent changes allowed.
Used in QA and production clients.
There are protection like level 0, level 1 and level 2
- level o is for No restrictions
- level 1 is for No overwriting
- level 2 is for No overwriting, no external availability.
So in this way the Protection is taken care in the client side. This is how the Client Copier and
Comparison Tool' settings used.