Appendix: Migrating BIP Definitions

This appendix provides an overview of BIP definitions and discusses how to:

• Migrate BIP definitions

• Migrate BI Publisher translated languages

• Clean Up BI Publisher Metadata

BIP Definitions Overview

To facilitate the movement of reports and templates from development to test and then to production, BI Publisher (BIP) objects are available as managed objects that can be placed into projects for migration from database to database. To facilitate the location of report-related objects, these items can be identified based on object owner ID.

Migrating BIP Definitions

The following definition types can be added to projects in Application Designer:

• BIP Data Source Definitions

• BIP File Definitions

• BIP Report Definitions

• BIP Template Definitions

If the data source for the BIP report is PS Query or Connected Query, then the query or connected query definition should also be included in the project.

Note. Because BI Publisher is based on managed objects, all updates to your data need to be performed using the PeopleSoft BI Publisher Pure Internet Architecture pages, PeopleSoft Application Designer, or BI Publisher PeopleCode APIs.

Note. As with other PeopleTools-delivered features, BI Publisher for PeopleSoft Enterprise uses managed object functionality, and you cannot use the switching feature of multilanguage data entry. You can populate Related Language tables by signing in and establishing a different session language. Then you can populate the Related Language table for that session.

See Working With PeopleSoft Applications in Multiple Languages, Understanding PeopleSoft Pure Internet Architecture.

Migrating BI Publisher-Translated Languages

BIP template translation uses related XLIFF files (one for each language) that contain not only specific translation pairs but the whole template definition. This is a standard for using XLIFF translation methodology.

Because the translation is tied to the template definition, the translation file (BIP Template Definition) as well as the specific XLIFF files (BIP File Definition) should be included in the project.

Note. If the template file is not copied with the language files, the correct translation file cannot be used when you run the report. Run a SYSAUDIT for Audit BI Publisher Integrity and delete any orphaned definitions.

See BI Publisher Integrity.

Cleaning Up BI Publisher Metadata

To ensure the integrity of the BI Publisher files, run the application engine program PSXPCLEAN.

This application engine program finds:

• Unreferenced objects in PSFILEDEFN.

• Template definitions and template translations for which file objects are missing.

• Inconsistencies between PSFILEDEFN and PSFILEDATA.

This application engine program is delivered in Report and Delete mode. To run the program in Report Only mode, open the application engine program PSXPCLEAN in Application Designer and remove the comment in the following statement in PSXPCLEAN:Main:Start PeopleCode action:

rem PSXPFILECLN_AET.REPORT_ONLY_FLAG = "Y"

You can schedule and run PSXPCLEAN using the PeopleTools, Process Scheduler, System Process Request page. You should run this program on a regular basis to keep template metadata consistent.