Appendix: Migrating XMLP Definitions

To facilitate the movement of reports and templates from development to test and then to production, XML Publisher 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.

XMLP Definition Types

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

• XMLP Data Src Defn.

• XMLP File Defn.

• XMLP Report Defn.

• XMLP Template Defn.

Note. Since XML Publisher is based on managed objects, it is important to understand that direct SQL updates to your data are not recommended because of the complexity of the various report objects and their relationships. Instead, update your data using the PeopleSoft XML Publisher Pure Internet Architecture pages and PeopleSoft Application Designer.

Note. As with other PeopleTools delivered features, XML Publisher for PeopleSoft Enterprise utilizes managed object functionality, and you do not have the ability to use the switching feature of multilanguage data entry. Related Language tables can be populated by logging in and establishing a different session language. The Related Language table for that session can then be populated.

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

Migrating XML Publisher Translated Languages

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

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

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

See XML Publisher for PeopleSoft Integrity.

Cleaning Up XML Publisher Metadata

To insure the integrity of the XML Publisher files run the application engine program PSXPCLEAN.

This application engine program will:

• Find unreferenced objects in PSFILEDEFN.

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

• Find 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 PSXPCLEAN in Application Designer and uncomment the following statement in PSXPCLEAN:Main:Start PeopleCode action:

rem PSXPFILECLN_AET.REPORT_ONLY_FLAG = "Y"

PSXPCLEAN could be scheduled and run via PeopleTools, Process Scheduler, System Process Request page. This program should be run on a regular basis to keep template metadata consistent.