Import a Site Builder template from a file using Solution Installer

If we have exported a Site Builder template file, use the Solution Installer to make the Site Builder template available to administrators and website creators.

Before we can import a Site Builder template, the target server must have WebSphere Portal, Web Content Manager, Content Template Catalog, and the Site Builder page and library installed and visible.

Do not import a Site Builder template that uses embedded page templates stored in the Portal Site library. Conflicts between duplicate page templates will cause the imported Site Builder template to break on the destination server.

The Site Builder template can be installed via the Solution Installer by invoking the normal install-paa, update-paa-components and deploy-paa commands.

If the Site Builder template or page templates already exist on the server, they are overwritten. If a required library named in the Site Builder template file already exists on the server, we will not be able to 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: Installing add-ons.

1. Run...

   cd WP_PROFILE/ConfigEngine
   ./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 created when we exported the Site Builder template.
   • site_template is the name of the component inside the application.

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

   Where:

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

Parent Export a Site Builder template to a file