Appendix G Known Issues and Limitations

6462076 

Single WAR Configurator fails against Directory Server

Access Manager, when deployed as a single WAR, will not configure Directory Server 6 with a single component root suffix (as in dc=example) although it works as expected with multi-component root suffixes (as in dc=example,dc=com).

Workaround: Use multi-component root suffixes.

6472662 

When SSL terminates at the Access Manager load balancer, the console application changes protocol from HTTPS to HTTP.

When you try to access the Access Manager load balancer with a URL such as https://loadbalancer:port/amserver/console or https://loadbalancer:port/amserver/UI/Login, you cannot access the login page because the console application changes the protocol from HTTPS to HTTP.

Workaround: Add <property name="relativeRedirectAllowed" value="true"/> to the sun-web.xml file for the individual instances of Access Manager and restart them.

After applying the workaround, the only supported URL is https://loadbalancer:port/amserver/UI/Login. It is highly recommended that you access the Access Manager instances directly to perform any administrative tasks rather than accessing them through a load balancer. This workaround was tested on Sun Java Systems Web Server 7.

6476271 

BEA servers do not start up when startup script is not configured properly.

The BEA administration server and managed server instances will not start up if the start up script is not configured properly. When using J2EE Policy Agent 2.2 on BEA Application Server 9.2, you must append the following to the end of the setDomainEnv.sh file:

• . /usr/local/bea/user_projects/domains/ProtectedResource-1/bin/setAgentEnv_ApplicationServer-1.sh for Protected Resource 1.

• . /usr/local/bea/user_projects/domains/ProtectedResource-2/bin/setAgentEnv_ApplicationServer-2.sh for Protected Resource 1.

The setDomainEnv.sh file contains the call to commEnv.sh.

6477741 

Exception is thrown when you run the agentadmin utility..

The following exception is thrown when you run the agentadmin utility from the J2EE Policy Agent 2.2 server (BEA Appserver 9.2).

# ./agentadmin --getUuid amadmin user example

Failed to create debug directory 
Failed to create debug directory 
Failed to create debug directory 
Failed to create debug directory 
Failed to create debug directory