PMF components extend WebFOCUS capabilities to accommodate PMF, as other WebFOCUS applications do. As a result, PMF components are placed in many parts of the WebFOCUS installation footprint.
Note: When upgrading, moving, or reinstalling a WebFOCUS environment, it is important to make sure the PMF components are backed up prior to the change and restored to their proper locations afterward. Deleting these files can cause issues with PMF capabilities.
The following is a list of the PMF components installed or configured on the WebFOCUS Server Application root (/ibi/apps).
Note: In multi-tier instances, the application directories are installed both on the server and client.
The core code repository for PMF. You do not need to backup this folder.
Location for PMF gadget procedures and components. You should back up any custom gadgets in this folder.
Translated string files to support multiple languages in PMF, such as English, French, German, Arabic, Chinese, Dutch, Japanese, Spanish, and Catalan. You do not need to back up this folder, unless you have a special case involving string customization.
Standard location where any developed customized PMF components should be stored. Make sure to backup this component.
DBMS-specific folders. These folders contain common MFD and ACX files used by PMF. All are always present to facilitate RDBMS switching without reinstalling PMF. There is no need to back up these folders.
Root application folder where PMF looks for configuration and files for each tenant in a single or multi-tenant installation. The standard template tenant folder is pmf_tenants/pmf_base. The root folder structure of this should be backed up, but the contents will be updated on any upgrade/migration.
Folder where modified MFD and ACX files are stored for a particular PMF tenant. In single-tenant installations, [tenant] is pmf_base. No need to back up this folder.
Root storage folder for configuration files modified during PMF installation; also standard PMF fonts for installation on Windows client machines (to allow display of indicators in PowerPoint output). No need to back up this folder.
Folder where modified configuration and settings files are stored and retrieved looked for. In single-tenant installations, [tenant] is pmf_base. No need to back up the contents of these folders.
Database file backups for demonstrations, new DB and upgrade DDL (SQL) scripts. There is no need to back up this folder.
Demonstration data and PMF source database snapshots. There is no need to back up this folder.
There are currently 24 PostScript font files (pmf01 to pmf08) added to enable icons in PDF reports in the Font Storage area (/ibi/srvxx/home/etc). Make sure to backup these components.
There are modifications made during PMF installation to the DHTML.FMP and PDF.FMP files to map the fonts needed for PMF PDF and PPT reports in the Font Map Area (/ibi/srvxx/home/nls). Make sure to backup these components.
The following is a list of the edited Server configuration files.
The PMF application paths are added to a separate server profile for each PMF tenant. A single tenant installation would use pmf_base.prf.
In the client basedir folder a PMF domain is added that contains all the tab launch pages for the WebFOCUS BID templates.
Contains three text files that control color pallets for graphing.
Contains three PMF jsp files.
Note: These additions to the reportcaster webapps directory require decompressing/recompressing the ReportCaster WAR file after installation is complete. If these files are modified for a hotfix, they will also need to be decompressed/recompressed.
Adds changes to a customized WebFOCUS BID login page, mainly used for PMF demonstrations. This file is distributed with WebFOCUS.
Make sure to backup these components.
Default Group View templates with tab sets for each Functional Role in PMF are added to this folder.
A set of default BID skins is added to this folder to enable matching formats for the distributed PMF skins.
Sample default BID Group Views are configured for the bootstrap PMF users configured in the WebFOCUS MR environment, to enable quick display of the proper Group View tabs.
These are WebFOCUS BID templates that configure group views for PMF.
There is a database component that will be stored in the DBMS of your choosing (DB2, MS SQL Server 2000 / 2005 / 2008, Oracle) which will need a database adapter configured for it, as well as connectors for any data source that PMF information will be loaded from.
Make sure to backup these files.
The PMF MR Domain is added to this file to enable quick use of PMF in the customer environment.
The Group Views needed for use of PMF in WebFOCUS BID are configured here.
Needed variable pass-throughs (security tokens, protocol and port) and use of global filtering file for the PMF Domain is configured.
PMF installer inserts install key for PMF.
Make sure to backup these files.