Prepare the system for multiple profile support on Solaris

several profile templates used to create a new WebSphere Portal profile or to augment an existing profile with WebSphere Portal. To use these profile templates, first run enable-profiles to configure the profile templates, register these templates with IBM WAS, and save the current WebSphere Portal baseline configuration. The baseline configuration is provided in the form of a configuration archive created by exporting the contents of an existing profile. We can create the CAR any time, such as immediately after the initial installation or after the original portal is fully configured with security, database, basic application deployment, and server tuning.

Before creating new profiles, delete any existing search collections.

WAS uses the wsadmin scripting interface to support the CAR creation. WebSphere Portal provides a configuration task that creates the CAR and also captures additional portal-specific file that must be kept with the CAR. The task also places the CAR and any associated files in the correct directory.

Many portal customizations, such as new pages, blogs, and wikis, are stored in the WebSphere Portal release database, which uses the Derby database after the initial installation. Any customizations made to the Derby database prior to running enable-profiles are included in the additional profiles created later. However, if you complete a database transfer to set up the release database on an external server before running enable-profiles, then any customizations made between the transfer and when enable-profiles is run are NOT picked up by additional profiles. Therefore, complete all customizations you want included on the additional profiles before transferring the release database domain to an external database server.

Restriction: Your environment MUST be a stand-alone profile. If you have a node federated to a dmgr, remove the node from the cell. If you have a web server node, remove the node before running enable-profiles.

Restriction: Search Collections cannot be shared between multiple profiles. Before running enable-profiles, remove existing search collections from the default profile. We can re-create the search collections after running enable-profiles.

To prepare the system for multiple profile support:

1. If you installed portal as a non-root user, modify permissions for the Portal Server directory...
   chmod -R u+rwx PORTAL_HOME/

2. ./ConfigEngine.sh enable-profiles -DWasPassword=foo task, from the WP_PROFILE/ConfigEngine of the configuration profile whose configuration will form the basis for the portal profile template, to create the CAR. The Portal.car file is saved to

   PORTAL_HOME/profileTemplates/default.portal/configArchives/Portal.car

   If we configured a remote database with Type 4 drivers under...

   WP_PROFILE/PortalServer

   ...they are included in the CAR file created when running enable-profiles.

3. Restore the non-root permissions...

   chmod -R u+rx PORTAL_HOME/

   
   

After completing the initial profile template generation with the required configuration, only make further customization changes to the wp_profile directory that are intended to be included in all additional Portal profiles. This approach allows the portal profile template configuration to be immediately updated after applying maintenance, because it will already contain the required configuration to be saved with the Portal profile templates.

Parent: Create multiple profiles on Solaris
Related:
Install WebSphere Portal on Solaris on the primary node