Deploying Branding Themes From a Production Environment
This chapter discusses how to:
Deploy branding themes from a production environment
Deploy branding themes from a development environments
Deploying Branding Themes From a Production Environment
To deploy themes from a production environment:
Make sure all images, styles, and HTML objects are in the production database. This may require entry through PeopleSoft Application Designer, use of the Upgrade Copy process, migrating remote objects to production servers, or a combination of these tasks.
Assign the new themes to the portal and specific roles, as desired. You stage them to appear on the proper date by using the Effective Date field on the Assign Themes page.
See Using Effective Dating to Create Versions of Branding Themes.
Test results and make adjustments as necessary.
Deploying Branding Themes From a Development Environment
This section discusses deploying branding themes from a development environment.
Understanding Data Mover Scripts Used in Deploying Branding Themes
Deploying branding themes from a development environment may require that you use PeopleSoft Data Mover scripts and the Upgrade Copy process. To use either, the same PeopleTools version must be running in both development and production environments.
Before you run a PeopleSoft Data Mover script, review the instructional text provided in each script.
The CLEAN script scrubs projects that you create in development environments, so that only branding-related objects are included. The other scripts come in pairs: an export version to pull the branding data out of development and an import version to push the data into production.
The Data Mover scripts used for deploying branding themes fall into three categories. Data Mover scripts that:
Apply to all themes, but do not apply to site overrides.
Apply to selected themes, but no not apply to site overrides.
Apply to selected sites and apply to site overrides.
The following PeopleSoft Data Mover scripts apply to all themes, but do not apply to site overrides.
|
Script Name |
Action |
Definitional Data |
PeopleSoft Application Designer Objects |
|
EPPBRALLCLEAN.DMS |
Cleans the PeopleSoft Application Designer project to include only branding objects, such as image, HTML, and style sheet objects. |
No |
Yes |
|
EPPBRALLEXP.DMS |
Extracts data from the source database and creates a .dat file. |
Yes |
No |
|
EPPBRALLIMP.DMS |
Loads the exported .dat file into the destination database. |
Yes |
No |
The following PeopleSoft Data Mover scripts apply to selected themes and do not apply to site overrides.
|
Script Name |
Action |
Definitional Data |
PeopleSoft Application Designer Objects |
|
EPPBRTHMCLEAN.DMS |
Cleans the PeopleSoft Application Designer project to include only branding objects, such as image, HTML, and style sheet objects. |
No |
Yes |
|
EPPBRTHMEXP.DMS |
Extracts data from the source database and creates a .dat file. |
Yes |
No |
|
EPPBRTHMIMP.DMS |
Loads the exported .dat file into the destination database. |
Yes |
No |
The following PeopleSoft Data Mover scripts apply to selected sites and all overrides.
|
Script Name |
Action |
Definitional Data |
PeopleSoft Application Designer Objects |
|
EPPSMBRCLEAN.DMS |
Cleans the PeopleSoft Application Designer project to include only branding objects, such as image, HTML, and style sheet objects. |
No |
Yes |
|
EPPSMBREXP.DMS |
Extracts data from the source database and creates a .dat file. |
Yes |
No |
|
EPPSMBRIMP.DMS |
Loads the exported .dat file into the destination database. |
Yes |
No |
Deploying Branding Themes From a Development Environment
To deploy branding themes from a development environment:
Verify that all theme definitions have effective dates as required for production use.
Move branding-related objects to production.
There are two options for moving branding-related objects to production. For either method, you can use the branding queries to identify all objects related to headers, footers and menus.
In addition, for either option, preparing the objects for migration to production may require the use of the Upgrade Copy process, migrating remote objects to production servers, or both.
Create a PeopleSoft Application Designer project and insert related image, HTML, style sheet, and application package/class objects manually. Then, copy the project to the target database.
Create a PeopleSoft Application Designer project and insert all image, HTML, style sheet objects and, if used in branding, the application package/class objects, and run CLEAN.dms to scrub the project.
Run the PeopleSoft Data Mover scripts to move the data comprising the theme, header, footer and menu override definitions.
Run the Copy Upgrade process to move branding objects.
Prior to executing the Copy Upgrade process, you may want to rerun the branding queries to double-check that you have identified all objects required for headers, footers and menus. Compare the list to the objects in the project after running the CLEAN PeopleSoft Data Mover script.
Check the results and make adjustments as necessary.