virtual file interface

In many cases, a Java EE application cannot directly access the file system on the application server. To allow customers to prepare for this capability, the PublicAPI contains Java classes that mimic many features of java.io facilities. Together, these are known as the Virtual File Interface.

The com.pega.pegarules.pub.util Package contains these classes:

PRFile class — Mimics a subset of methods in java.io.File
PRInputStream — Emulates java.io.InputStream
PROutputStream class — Emulates java.io.OutputStream
PRReader class — Emulates java.io.Reader
PRWriter class — Emulates java.io.Writer

Consult the PublicAPI JavaDocs for details on these Java classes.

In Web tier deployments of Pega 7 Platform, these facilities operate the same as the corresponding java.io facilities.

In e-tier deployments, operation of file access depends on the following Dynamic System Setting:

Dynamic System Setting: prconfig/storage/class/default
The prconfig/storage/class/default setting provides the configuration for the storage mechanisms, as well as the mapping between the resource types and those mechanisms. The following values are valid for this Dynamic System Setting:
Value	Description
`filesystem`	The regular, physical file system (Default)
`resadaptor`	A Java EE resource adapter
`embedded`	(Reserved)
`datasource`	A database accessed through a JDBC Datasource
Caution: The prconfig setting can have broad impact on the operation of your system. Update with caution.

Related terms

Open topic with navigation

virtual file interface

Dynamic System Setting: prconfig/storage/class/default

Value

Description