Skip to Content

Different Ways for 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. Described below are all the different ways that you can activate the write-protect mode for PCD.

Procedure 1:

1.     Start the Visual Administrator.

2.     Choose Global Configuration ® Server ® Services ®

3.     The properties of the service are displayed:

a.     Pcd.Pl.WriteProtectActivated defines whether or not write-protect mode is

activated. By default it is set to false.

b.     Pcd.Pl.WriteProtectCause describes the reason that write-protect mode is 

activated. This information appears in the log files.

4.     Activate write-protect mode by entering true as the value for Pcd.Pl.WriteProtectActivated.

5.     Click Update and then click Save.

         A confirmation dialog box opens.

6.     To apply the changes to all cluster elements, click yes.

        The Reset dialog box opens.

7.     To restart the service, click yes.

8.     To reset the default values, click the Reset Default Global Properties icon


Procedure 2:

Use SAP NetWeaver Administrator to update the following properties:

1.   Pcd.Pl.WriteProtectActivated defines whether write-protect mode is activated. By default it is set to false. This has to set to true

2.    Pcd.Pl.WriteProtectCause specifies an explanation why write-protect mode was activated. This information appears in log files. This has to set to true

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 (


Components affected by the change




Object editors are either not available at all or 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 not available.


You cannot create new rooms, or edit or delete existing rooms.

User Management Engine

You cannot create portal roles, 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.

Further information:

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

2.    It is not necessary to switch on write-protect mode in order to create an online backup.

3.   You do not set write-protect mode from the PCD configuration file PCDStartup.Properties, rather you set it as shown above in the Procedure.

Reference links



You must be Logged on to comment or reply to a post.
    • Thanks for the updates Michael. As far as I know ther are only 2 ways of modifting the write protect mode for pcd and many folks dont know about the second eaier method. If you know of other method please add your 2 cents.
      • You miss the point. You grabbed a slab of text from and pretended it was your own! You didn't acknowldege that you had done this. That is wrong.
  • Definitely the original author should acknowledge
    the source of the first procedure.
    It is common courtesy, and also, one
    can see related topics if one so desires
    by clicking on the little [<-|->] icon
    on the SAP page.

    I liked the blog because otherwise I would not
    have known such a thing as PCD write
    protection. I know, I should spend time and sweat
    studying the voluminous docs.
    But who has time. And my memory is not as it
    used to be.

    The second procedure is nice to know too.
    Some people may like the web interface better.

    Also, personally I think SAP docs have too
    many "for more info, go here, here and there".
    My brain does not do "goto" too well.
    I like to read a linear doc.
    One linear doc, one procedure,
    I know, complex software has to have complex
    documentation, but still...

    Anyway thanks to both original author and
    the commentator pointing the official SAP doc