Application Server 8.1 server.policy file must be edited when using non-default URIs (6309759)

If you are deploying Access Manager 7 2005Q4 on Application Server 8.1 and you are using non-default URIs for the services, console, and password web applications, which have default URI values of amserver, amconsole, and ampassword, respectively, you must edit the application server domain's server.policy file before attempting to access Access Manager via a web browser.

Workaround: Edit the server.policy file as follows:

1. Stop the Application Server instance on which Access Manager is deployed.

2. Change to the /config directory. For example:

   cd /var/opt/SUNWappserver/domains/domain1/config

3. Make a backup copy of the server.policy file. For example:

   cp server.policy server.policy.orig 

4. In the server.policy file, look for the following policies:

   grant codeBase "file:\${com.sun.aas.instanceRoot}/
   applications/j2ee-modules/amserver/-" { ... 
   };
   grant codeBase "file:\${com.sun.aas.instanceRoot}/
   applications/j2ee-modules/amconsole/-" { ...
   };
   grant codeBase "file:\${com.sun.aas.instanceRoot}/
   applications/j2ee-modules/ampassword/-" { ...
   };  

5. Replace amserver with the non-default URI used for the services web application in the following line:

   grant codeBase "file:\${com.sun.aas.instanceRoot}/
   applications/j2ee-modules/amserver/-" {  

6. For legacy mode installations, replace amconsole with the non-default URI used for the console web application in the following line:

   grant codeBase "file:\${com.sun.aas.instanceRoot}/
   applications/j2ee-modules/amconsole/-" {  

7. Replace ampassword with the non-default URI used for the password web application in the following line:

   grant codeBase "file:\${com.sun.aas.instanceRoot}/
   applications/j2ee-modules/ampassword/-" {  

8. Start the Application Server instance on which Access Manager is deployed.