To Change the Host Machine Name in an Access Manager Deployment

The following procedure explains what you need to modify in an Access Manager deployment when the name of the machine on which Access Manager is hosted changes.

1. Stop Access Manager.

2. Delete the bootstrap file.

   # rm user_home/AccessManager/*

   where user_home is the home directory of the UNIX user under which the Access Manager web container is running.

3. Copy the value of the am.encryption.pwd property from AMConfig.properties.

   am.encryption.pwd=eza2p5sYo+19hlzeZPynfOk+g89JUbRS

4. Delete the sample identities created by the Identity Repository Service when Access Manager is deployed.

   By default, context-root is amserver.

   1. Change to the agent directory.

      # cd AM-Config-Dir/context-root/idRepo/agent/

   2. Remove the following.

      # rm LibertyBearerTokenWSP LibertySAMLTokenWSP LibertyX509TokenWSP LocalDiscoDiscovery SAML-HolderOfKeyWSP SAML-SenderVouchesWSP UserNameTokenWSP wscWSC wspWSP X509TokenWSP

   3. Change to the realm directory.

      cd AM-Config-Dir/context-root/idRepo/realm/

   4. Remove the following.

      # rm ContainerDefaultTemplateRole

   5. Change to the user directory.

      cd AM-Config-Dir/context-root/idRepo/user/

   6. Remove the following.

      # rm jondoe jsmith

5. Start Access Manager.

6. Using a browser, go to the Access Manager URL using the new host machine name: http://new_FQDN_AM_host:port/amserver.

   You will be redirected to the Access Manager configuration page. After redirection, verify that the URL in the Location bar reflects the new host name.

7. Fill in the details on the configuration page displayed.

   Be sure of the following:

   • Verify that the value of the Server URL correctly reflects the new host name.

   • Paste the encryption password you previously copied as the value of the Encryption Key.

8. Click Configure to submit the form.

   A message confirming a successful configuration will be displayed and you will be redirected to the Access Manager console to login.

9. Login to the Access Manager console as amadmin.

   If configuration has failed or you are unable to login, troubleshoot the issue by looking at the logs from the web container that hosts Access Manager and the debug logs from Access Manager itself.

10. Make the following changes to the Access Manager Platform Service.

    1. Click the Configuration tab.

    2. Click System Properties.

    3. Click Platform.

    4. Delete the Instance Name entry referring to the old host name.

    5. Update the Site Name to include the instance-ID pertaining to the new host name.

    6. Click Save to save the changes.

11. Make the following changes to the top-level realm.

    1. From the console home page, click the Access Control tab.

    2. Click the name of the top-level realm.

    3. Click Realm Attributes.

    4. Under Realm/DNS Aliases, delete the entry referring to the old host name.

    5. Click Save to save the changes.

12. Follow the instructions in To Change the Domain in an Access Manager Deployment, if applicable.

13. Log out of the Access Manager console.