Import a Site Builder template from a file using Solution Installer

If you export a Site Builder template file, use the Solution Installer to make the template available to HCL WebSphere Portal administrators and website creators.

Before importing a Site Builder template, the target server must have HCL WebSphere Portal, Web Content Manager, Content Template, and the Site Builder page and library installed and visible.

Note: Do not import a Site Builder template that uses embedded page templates stored in the Portal Site library. Conflicts between duplicate page templates cause the imported Site Builder template to break on the destination server. The Site Builder template can be installed using the Solution Installer by running the normal install-paa, update-paa-components, and deploy-paa commands. If the Site Builder template or page templates exist on the server, they are overwritten. If a required library named in the Site Builder template file exists on the server, we cannot import the Site Builder template.Site Builder prevents custom libraries from being overwritten accidentally.

Further information on using the Solution Installer can be found here: Install add-ons.

1. Go to the wp_profile_root directory.

2. Run the ConfigEngine batch or script file with the install-paa parameter. For example:
   ./ConfigEngine.sh install-paa update-paa-components -DPAALocation=site_template.paa -DappName=site_template -Dcomponents/site_template.unique=true

   Where:

   • site_template.paa is the name of the paa file that is created when we exported the Site Builder template.
   • site_template is the name of the component inside the application.

3. Run the ConfigEngine batch or script file with the deploy-paa parameter. For example:

   ./ConfigEngine.sh -DappName=site_template -Dcomponents/site_template.unique=true

   Where:

   • site_template is the name of the component inside the application.

Parent topic: Export a Site Builder template to a file