Prepare the system for multiple profile support on AIX
Overview
WebSphere Portal v7 ships a new configuration profile template called the portal profile template, which is registered with IBM WAS.
Before a new portal template can be created, the portal profile template must be primed with the baseline application server configuration to use as a basis for the new profile. This baseline configuration is provided in the form of a configuration archive (CAR) created from an existing portal profile.
The CAR is created by exporting the contents of an existing portal profile, which can be made at any time, such as immediately after initial installation, or after the original portal is fully configured with the baseline configuration, including security, basic application deployment, and server tuning.
Before creating new profiles, delete any existing search collections.
A wsadmin task is available to:
- Create the CAR
- Capture additional portal-specific files that need to be kept with the CAR
- Place the CAR and 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 use the Derby database after the initial installation. Any customizations made to the Derby database prior to running the enable-profiles task are included in the additional profiles created later. However, if you perform a database transfer to set up the release database on an external server prior to running the enable-profiles task, then any customizations made between the time the database transfer is performed and the time that the enable-profiles task is run will NOT be picked up by additional profiles created later. Therefore, you should perform all customizations that you want included on the additional profiles before transferring release database domain to an external database server.
Your environment MUST be a stand-alone profile. It can contain only one node. For example, 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. You can recreate the search collections after you run enable-profiles.
Complete the following steps to prepare the system for multiple profile support:
- If you installed WebSphere Portal as a non-root user, modify permissions for the Portal Server directory.
chmod -R u+rwx PORTAL_HOME/
- Within the configuration profile whose configuration will form the basis for the portal profile template, create the CAR.
WP_PROFILE/ConfigEngine
./ConfigEngine.sh enable-profiles -DWasPassword=fooThe Portal.car file is saved to:
PORTAL_HOME/profileTemplates/default.portal/configArchives
- Restore the non-root permissions to the Portal Server directory:
chmod -R u+rx PORTAL_HOME/After completing the initial profile template generation with required configuration, you should 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 AIX
Related tasks
Install WebSphere Portal on AIX on the primary node
Changed the g in the non-root user commands to a u. Added restriction for Search Collections Add a restriction. Fixed the chmod command. Added a note about changing non-root user permissions.