There is a known issue with the single WAR deployed on Weblogic 8.1, with JAX-RPC initialization. In order for Access Manager to communicate with the client SDK, you need to replace the JAX-RCP 1.1 jar files with JAX-RPC 1.0 jar files.
There are two ways to obtain the WAR file. One is through the Java Enterprise System 5 installer with Access Manager set to the Configure Later option, the other is from Sun's download site.
If you have generated the WAR file through the Java Enterprise System 5 installer with the Configure Later option:
Remove the following JAXRPC 1.1 .jar files from AccessManager-base/SUNWam/web-src/WEB-INF/lib:
Copy the following .jar files from their respective locations to AccessManager-base/SUNWam/web-src/WEB-INF/lib:
jaxrpc-api.jar from /opt/SUNWam/lib/jaxrpc 1.0
jaxrpc_ri.jar from /opt/SUNWam/lib/jaxrpc 1.0
commons-logging.jar from /opt/SUNWmfwk/lib
Goto AccessManager-base/SUNWam/bin/ and run the following command:
amconfig —s samplesilent
For more information on configuring Access Manager using the amconfig script, see Running the Access Manager amconfig Script in the Access Manager Post Installation Guide.
If you have obtained the WAR file through the Oracle download site (http://www.oracle.com/technetwork/indexes/downloads/index.html):
Acquire the ZIP_ROOT/applications/jdk14/amserver.war file and explode it into a staging area, such as /tmp/am-staging.
Remove the following JAXRPC 1.1 .jar files from /tmp/am-staging/WEB-INF/lib:
Copy the following JAXRPC 1.0 .jar files and the commons logging .jar file, located in the ZIP_ROOT/applications/jdk14/jarFix directory to /tmp/am-staging/WEB-INF/lib:
Recreate and deploy the Access Manager WAR. For more information, see Deploying Access Manager as a Single WAR File in the Access Manager Post Installation Guide.