Setting Write-Protect Mode for the
PCD
You can prevent data from being written to the Portal Content Directory (PCD) by activating write-protect mode. For example, you can activate write-protect mode when migrating data from an old portal system to a new one in order to prevent data from being written to the old system during this time.
The following components are affected by write-protect mode:
Component |
Effect |
Portal |
Object editors are either not available at all or only have limited functionality. For example, portal administrators cannot import or export packages using the Package Transport Editor. They also cannot create new objects, delete objects, or edit objects using the object editors. Personalization of the portal themes is not available. When the portal is in write-protect mode, error messages appear when you attempt to call functions that are currently not available. |
Collaboration |
You cannot create new rooms, or edit or delete existing rooms. |
User Management Engine |
You cannot create portal roles cannot be created, but you can create and change UME roles since they are not stored in the PCD. You cannot assign portal roles to actions, neither in the user management administration console nor in the Role Editor. |

You do not set write-protect mode from the PCD configuration file PCDStartup.Properties; rather you set it with NetWeaver Administrator.
Use SAP NetWeaver Administrator to update the following properties:
● Pcd.Pl.WriteProtectActivated defines whether write-protect mode is activated. By default it is set to false.
● Pcd.Pl.WriteProtectCause specifies an explanation why write-protect mode was activated. This information appears in log files.
To change a setting, open the Java System Properties of the NetWeaver Administrator, select the Services tab, and modify the settings for PCD Generic Layer (com.sap.portal.tc.pcd.gl.srv).

It is not necessary to switch on write-protect mode in order to create an online backup. For more information about online backup, see SAP note 779708.

Write-protect mode can only be configured for the entire cluster, and the properties should be set for all the cluster instances.