Packaging themes for deployment

We can deploy theme static resources together with dynamic resources in an EAR file. This eliminates the needs to leverage WebDAV.

Repackage the static content as a WAR file, or an EAR file containing the WAR file when it is not possible to exchange the static content with the Operations Team as a separate compressed file.
Create a custom theme before starting this process.

Create and collect the required code artifacts, the scripts to register the theme and skins, and the list of required runtime configuration changes. Create an EAR file containing one WAR file containing the dynamic content of the theme and one WAR file containing the static content.

Theme is created based on the modularized portal theme.

Create a custom version of the dynamic content as a new EAR file and a custom version of the static content by creating a folder in the file store. For more information about copying a theme for customization, see Create a copy of the theme. No further customization was performed so far. Also an XML Access script is used to register the themes and skins that are part of the EAR file.

If we performed additional changes, like deleting files or changing file names, then we need to map the following steps accordingly.

Cache headers are not automatically set for static files served from a war file. External means, such as overwriting headers in the HTTP Server, must be used in this case. When we use this approach, complete the Base Portal Tuning - Web Server tuning chapter of the Performance Tuning Guide for optimal performance.

See

• Developing IBM WebSphere Portal 8.5 EAR Themes: A Step-by-Step Guide
• Add static content to the custom theme
• Adapt the scripts that register the custom theme and skins
• Adapting the list of required runtime configuration changes for the theme
• Test the custom EAR file
  

Parent Develop themes for a production portal

Related concepts:
Development and operations overview
Create a copy of the theme