Changing product service levels by swinging profiles

You can update or roll back the product service level by applying service to the master installation and swinging profiles to an updated application server copy.

Before you begin

To associate a profile with a different installation by following this procedure, your environment must be configured for swinging profiles. For more information, see Installing and configuring a swinging profile environment.

Procedure

Update the service level of the master installation, or roll back the master installation to a previously installed service level.

For more information, see Installing and uninstalling interim fixes and fix packs on distributed operating systems.

Avoid trouble: If the master installation is on the same host as the application server copies, you must set the symbolic link back to the master installation directory when you apply fix packs or interim fixes. Changing the symbolic link renders all copies unusable during the maintenance window. To avoid this behavior, you can install separate master installations for each service level.
Copy the contents of the master installation AppServer directory to a new product installation directory for the updated service level, such as sp_install_dir/V85510/AppServer.
```
cp -R /opt/SPInstalls/MASTER/AppServer/* /opt/SPInstalls/V85510/AppServer/
```
Update the symbolic link to point to the AppServer directory of the updated copy of the application server.
The following example removes the existing symbolic link and creates a new one for the updated application server copy.
```
rm /opt/SPCommonArea/SPLink
ln -s /opt/SPInstalls/V85510/AppServer /opt/SPCommonArea/SPLink
```
This action swings all existing application server profiles to the updated service level.
Run script setupProfileSDK.sh from the product installation directory for the updated service level to switch the existing profile(s) using the embedded Java SE 6 to use the new embedded Java SE 8. For more information, see Swinging profiles between product installations.
```
cd sp_install_dir/V85514/AppServer/bin
./setupProfileSDK full_path_to_profileRegistry.xml
```
Using the symbolic link, start the application server by running the server start command.
```
/opt/SPCommonArea/SPLink/bin/startServer -profileName AppSrv01 server1
```
The application server runs at the updated service level.

What to do next

You can continue to install new application server service levels in the sp_install_dir directory, create and update application server profiles, and swing between profiles as required.