Multiple profile support
IBM WebSphere Portal uses profiles to represent the application server configuration, including...
- datasource definitions
- web application and portlet deployments
- Java virtual machine
Multiple profiles allow multiple independent portal instances running from the same installation binaries.
Profile types...
portal.default Standalone portal server, or after federation, used to create base of portal cluster. managed.portal Portal run time environment. No servers. After federation, used to create cluster members. management.portal.augment Profile contains a dmgr prepared for use with portal. Used to federate the other portal profiles.
Search Collection with multiple profiles
We cannot share search collections between multiple profiles.
Before federating, delete all search collections, including the default search collections. We can back up and restore the collections on the original profile, or we can use export and import steps...
- Export the existing search collections.
- Remove the existing search collections.
- If you installed portal as a non-root user, to set permissions...
chmod -R g+rwx /portal_server_root
- Capture the portal configuration using either of the following configuration tasks...
- enable-profiles
- replace-profiles
- Import the saved search collections on the original profile.
- Create new profiles using the profile templates; default search collections will be automatically created in the new profile.
- Restore permissions....
chmod -R g+rx /portal_server_root
To share search collections between multiple Portal server instances, such as in a clustered or farm environments, configure a remote search server.
Maintenance with multiple clusters
During maintenance application to a cluster, the entire cluster should be taken out of service, so that cluster-wide changes can take effect without affecting user traffic or potentially causing synchronization conflicts between cell managed resources, like enterprise applications and portlets, and the product binary files in the local file system.
For a continuous availability environment, multiple clusters might be necessary, to allow traffic to continue to one cluster while another is being serviced.
Apply maintenance to product binaries and to each profile instance. Update both at the same time to keep them in sync and avoid conflicts. IBM recommends that if profiles share the same binary files, they should belong to the same cluster.
Parent: Plan
Related:
Support multiple profiles
Create multiple profiles on AIX
Create multiple profiles on IBM i
Create multiple profiles on Linux
Create multiple profiles on Solaris
Create multiple profiles on Windows
Related:
Portal farm considerations