Prepare the system for multiple profile support on Windows
WebSphere Portal provides the enable-profiles configuration task for creating configuration archive (CAR) files.
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.
The 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.
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 collections after running enable-profiles.
From a configuration profile directory, whose configuration will form the basis for the portal profile template, run...
cd WP_PROFILE\ConfigEngine
ConfigEngine.bat enable-profiles -DWasPassword=fooThis creates...
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 created when running enable-profiles.
After generating the initial profile template, 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 Windows
Related: Install WebSphere Portal on Windows on the primary node