NOTE - It is highly recommended that backups be taken of the STS servers before following these steps.
Additionally, it is recommended to do the steps in a test environment first if at all possible.
These changes MUST be made on ALL STS hosts.
1. Open IIS manager on the STS host(s). Under Application Pool there should CAM entries. CloudAccessManager and CloudAccessManagerDatabase
2. If only CloudAccessManager exists Right click on 'Application Pool' and select 'Add Application Pool...'.
3. Enter CloudAccessManagerDatabase as the application name. Select .NET version 4 and Integrated mode.
4. Right click on the newly created Application Pool and select 'Advanced Settings...'.
5. Navigate to 'Process Model' - 'Identity' and click the button labelled '...'.
6. Select 'Custom Account' and click 'Set...' then enter the credentials of your configured Cloud Access Manager service account. This would be the one that was used during the initial setup. The application pool CloudAccessManager would already be using it. The username and password need to be the same for both.
7. Within IIS Manager navigate to Sites - Default Web Site - Cloud Access Manager - ODataPersistence
8. Click on 'Basic Settings' located on the right-hand side.
9. Click the 'Select...' button and select the application pool you created in Step 3.
10. Navigate to the Home section of IIS manager and restart IIS, located on the right-hand side.
STEPS TO REVERSE CHANGES.
1. Within IIS Manager navigate to Sites – Default Web Site – Cloud Access Manager – ODataPersistence.
2. Click on ‘Basic Settings’ located on the right-hand side.
3. Click the ‘Select…’ button and select the Cloud Access Manager Application pool from the menu.
4. Restart IIS.