Access Manager does not update the Application Server domain.xml properly with JVM options and server classpath . This is known to occur in the following scenario:
You install and configure Application Server and Directory Server.
You create a node agent.
You create a non-default Application Server instance.
You install Access Manager in "Configure Later" mode.
You edit the amsamplesilent file and then run it using amconfig.
When you try to log in to Access Manager with a browser, an error message is displayed.
Solution Before installing Access Manager, edit the amsamplesilent file so that the container block includes the following information:
AS81_HOME=/opt/SUNWappserver/appserver AS81_PROTOCOL=$SERVER_PROTOCOL AS81_HOST=$SERVER_HOST #AS81_HOST=$DISTAUTH_HOST AS81_PORT=$SERVER_PORT AS81_ADMINPORT=$ADMIN_PORT AS81_ADMIN=admin AS81_ADMINPASSWD="$ADMINPASSWD" AS81_INSTANCE=server1 AS81_DOMAIN=domain1 AS81_INSTANCE_DIR=/var/opt/SUNWappserver/nodeagents/nodename/server-instance AS81_DOCS_DIR=/var/opt/SUNWappserver/nodeagents/nodename/server-instance/docroot AS81_ADMIN_IS_SECURE=true |
After the edits are completed, run the amconfig command:
./amconfig -s amsamplesilent |