Swinging profiles between product installations
You can configure your environment to use a common set of profiles that you associate with multiple installations. Customers who provision many servers might use this method to keep their environments at equivalent service levels, especially for the underlying WebSphere environment and Java security patches.
About this task
A profile defines the runtime environment. When you change the service level of the installation, the service level of the profile also changes. You can configure your environment to use a common set of profiles. Because the profiles are decoupled from any specific installation, you can associate the profiles with different application server installations, or swing the profiles.
- This process applies to Linux only.
- This process applies to updating binary code and configuration properties but not database metadata, which limits some of the benefits for rolling back Business Automation Workflow. Any service that is applied to Business Automation Workflow also requires manual steps to be performed for each profile.
Business Automation Workflow follows a V.R.M.F naming scheme, where the letters stand for version, release, modification, and fix pack. You can swing profiles only within a release, such as between product installations at different fix packs or interim fix levels. You cannot swing profiles between different product versions.
An environment that is configured for swinging profiles relies on one or more master installations, which are the installations to which you apply service from fix packs or interim fixes. The master installation is used to create application server copies for production use, and application server profiles are created in a way that enables their service levels to be changed with a symbolic link.
