The PCD Standalone implementation.

There are actually three "runtime flavors" of the PCD:

1. The normal "Engine" scenario
2. The "OfflineEngine" scenario
3. The "Standalone" scenario

In both the "OfflineEngine" and "Standalone" scenarios, the Init class initializes the PCD. Other than in the "Engine" scenario (where the initialization is done by the PcdService), though, the PersistenceLayer (PL) can be initialized without the need to initialize the other PCD layers (since some tools only use the PL), so Init offers some specific methods for initialization.

In general, Init requires some Properties which are either provided programmatically or by specifying the file name of a .properties file in a dedicated System parameter (see the Init javadocs).

PcdAccess (in the com.sapportals.portal.pcd.gl package) is the class that abstracts from Standalone vs. Engine scenarios. Applications that are supposed to run in both Engine and Standalone must only use PcdAccess methods.

All other classes in this and the com.sapportals.portal.pcd.gl.transport package are standalone proxy implementations.