J2EE agents v2.2 on WebSphere

Has anyone been able to configure the policy agent 2.2 for WebSphere 5.1.1 in a Deployment Manager environment. Have not been able to find any documentation that would cover this. I managed to install the agent against the Deployment Manager and turn on global security. That seems to work, however, i am unable to get WAS Admin roles mapped to the Sun Access Manager Roles.
Any guidance is much appreciated.

Why do you have the TLD in the web.xml file? Why do you have the TLD under WEB-INF/classes?
There's a TLD already packaged inside the JAR file for the tag library. (Open it to see that it's true.)
If WSAD is like Tomcat, it should know how to go inside the JAR and find the TLD. All you need to do is make sure that the URI in your JSPs matches that specified in the packaged TLD.
%

Similar Messages

J2ee agent 2.2 configuration problem with Websphere Portal 5.1

Hi,
I am trying to configure j2ee agent 2.2 with Websphere Portal server.
I have followed the document "Sun Java SystemAccess Manager
PolicyAgent 2.2 Guide for IBM WebSphere Portal Server 5.1.0.2"
Please see the thread "Problem with Sun's SSO system and Websphere Portal Server integration" for environment related information.
Also the security on app server has been enabled and is talking to LDAP.
My aim here is to enable application server (portal server) to autheticate requests.
I am getting following error when I log into the portal application.
07/03/2007 06:32:16:062 PM IST: Thread[Servlet.Engine.Transports : 1,5,main]
AmFilter: now processing: SSO Task Handler
07/03/2007 06:32:16:062 PM IST: Thread[Servlet.Engine.Transports : 1,5,main]
SSOTaskHandler: SSO Validation failed for null
07/03/2007 06:32:16:062 PM IST: Thread[Servlet.Engine.Transports : 1,5,main]
URLFailoverHelper: Checking if https://apollo.maxnewyorklife.com:443/amserver/UI/Login is available
07/03/2007 06:32:16:078 PM IST: Thread[Servlet.Engine.Transports : 1,5,main]
WARNING: URLFailoverHelper: the url https://apollo.maxnewyorklife.com:443/amserver/UI/Login is not available
javax.net.ssl.SSLHandshakeException: unknown certificate
     at com.ibm.jsse.bs.a(Unknown Source)
     at com.ibm.jsse.bs.startHandshake(Unknown Source)
     at com.ibm.net.ssl.www.protocol.https.b.o(Unknown Source)
     at com.ibm.net.ssl.www.protocol.https.q.connect(Unknown Source)
     at com.ibm.net.ssl.internal.www.protocol.https.HttpsURLConnection.connect(Unknown Source)
     at com.sun.identity.agents.common.URLFailoverHelper.isAvailable(URLFailoverHelper.java:190)
     at com.sun.identity.agents.common.URLFailoverHelper.getAvailableURL(URLFailoverHelper.java:129)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getLoginURL(AmFilterRequestContext.java:757)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectURL(AmFilterRequestContext.java:285)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectURL(AmFilterRequestContext.java:258)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectResult(AmFilterRequestContext.java:363)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectResult(AmFilterRequestContext.java:345)
     at com.sun.identity.agents.filter.SSOTaskHandler.doSSOLogin(SSOTaskHandler.java:210)
     at com.sun.identity.agents.filter.SSOTaskHandler.process(SSOTaskHandler.java:98)
     at com.sun.identity.agents.filter.AmFilter.processTaskHandlers(AmFilter.java:189)
     at com.sun.identity.agents.filter.AmFilter.isAccessAllowed(AmFilter.java:152)
     at com.sun.identity.agents.websphere.AmIdentityAsserterBase.processRequest(AmIdentityAsserterBase.java:195)
     at com.sun.identity.agents.websphere.AmTrustAssociationInterceptor.negotiateValidateandEstablishTrust(AmTrustAssociationInterceptor.java:91)
     at com.ibm.ws.security.web.TAIWrapper.negotiateAndValidateEstablishedTrust(TAIWrapper.java:101)
     at com.ibm.ws.security.web.WebAuthenticator.handleTrustAssociation(WebAuthenticator.java:191)
     at com.ibm.ws.security.web.WebAuthenticator.authenticate(WebAuthenticator.java:928)
     at com.ibm.ws.security.web.WebCollaborator.authorize(WebCollaborator.java:531)
     at com.ibm.ws.security.web.EJSWebCollaborator.preInvoke(EJSWebCollaborator.java:262)
     at com.ibm.ws.webcontainer.webapp.WebAppSecurityCollaborator.preInvoke(WebAppSecurityCollaborator.java:132)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:506)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:208)
     at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:134)
     at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:321)
     at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
     at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:246)
     at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
     at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
     at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:652)
     at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:448)
     at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:936)
07/03/2007 06:32:16:078 PM IST: Thread[Servlet.Engine.Transports : 1,5,main]
URLFailoverHelper: disconnected the connection for availability check
07/03/2007 06:32:16:078 PM IST: Thread[Servlet.Engine.Transports : 1,5,main]
ERROR: URLFailoverHelper: No URL is available at this time
07/03/2007 06:32:16:078 PM IST: Thread[Servlet.Engine.Transports : 1,5,main]
ERROR: AmFilter: Error while delegating to inbound handler: SSO Task Handler, access will be denied
[AgentException Stack]
com.sun.identity.agents.arch.AgentException: No URL is available at this time
     at com.sun.identity.agents.common.URLFailoverHelper.getAvailableURL(URLFailoverHelper.java:133)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getLoginURL(AmFilterRequestContext.java:757)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectURL(AmFilterRequestContext.java:285)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectURL(AmFilterRequestContext.java:258)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectResult(AmFilterRequestContext.java:363)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectResult(AmFilterRequestContext.java:345)
     at com.sun.identity.agents.filter.SSOTaskHandler.doSSOLogin(SSOTaskHandler.java:210)
     at com.sun.identity.agents.filter.SSOTaskHandler.process(SSOTaskHandler.java:98)
     at com.sun.identity.agents.filter.AmFilter.processTaskHandlers(AmFilter.java:189)
     at com.sun.identity.agents.filter.AmFilter.isAccessAllowed(AmFilter.java:152)
     at com.sun.identity.agents.websphere.AmIdentityAsserterBase.processRequest(AmIdentityAsserterBase.java:195)
     at com.sun.identity.agents.websphere.AmTrustAssociationInterceptor.negotiateValidateandEstablishTrust(AmTrustAssociationInterceptor.java:91)
     at com.ibm.ws.security.web.TAIWrapper.negotiateAndValidateEstablishedTrust(TAIWrapper.java:101)
     at com.ibm.ws.security.web.WebAuthenticator.handleTrustAssociation(WebAuthenticator.java:191)
     at com.ibm.ws.security.web.WebAuthenticator.authenticate(WebAuthenticator.java:928)
     at com.ibm.ws.security.web.WebCollaborator.authorize(WebCollaborator.java:531)
     at com.ibm.ws.security.web.EJSWebCollaborator.preInvoke(EJSWebCollaborator.java:262)
     at com.ibm.ws.webcontainer.webapp.WebAppSecurityCollaborator.preInvoke(WebAppSecurityCollaborator.java:132)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:506)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:208)
     at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:134)
     at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:321)
     at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
     at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:246)
     at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
     at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
     at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:652)
     at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:448)
     at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:936)
07/03/2007 06:32:16:078 PM IST: Thread[Servlet.Engine.Transports : 1,5,main]
AmFilter: result =>
FilterResult:
     Status      : FORBIDDEN
     RedirectURL     : null
     RequestHelper:
          null
     Data:
          null
07/03/2007 06:32:16:078 PM IST: Thread[Servlet.Engine.Transports : 1,5,main]
AmIdentityAsserter: result => TAIResult: status: 403, principal: null, subject: null
From whatever analysis I have done so far, I believe this issue is related to the personal certificate for sun one webserver (on which access manager & LDAP are installed) not registered with the application server (portal server).
I am not sure about the way I go by solving the issue.
Please can anybody help me out.
Thanks,
Yaseer
Message was edited by:
yazee
Message was edited by:
yazee

Ankush,
I am getting error as follows in the webserver error log:-
Error receiving request from 172.23.213.75 (SSL_ERROR_CERTIFICATE_UNKNOWN_ALERT: SSL peer had some unspecified issue with the certificate it received)
Although I can get into am console but with https://apollo.maxnewyorklife.com/amconsole
Tried the same thing, but couldnt resolve it. I will give it another go.
Generally I am getting same error again and again.
In my amWebsphere log file of j2ee agent (under root\am_wps_agent\agent_001\logs\debug) error I get.....
07/15/2007 04:19:11:656 PM IST: Thread[Servlet.Engine.Transports : 0,5,main]
AmFilter: now processing: SSO Task Handler
07/15/2007 04:19:11:766 PM IST: Thread[Servlet.Engine.Transports : 0,5,main]
SSOTokenValidator.validate(): Exception caught
com.iplanet.sso.SSOException: Invalid sessionid formatjava.lang.IllegalArgumentException: Invalid server id in session id com.iplanet.services.naming.ServerEntryNotFoundException: Naming Service is not available.
     at com.iplanet.sso.providers.dpro.SSOProviderImpl.createSSOToken(SSOProviderImpl.java:205)
     at com.iplanet.sso.SSOTokenManager.createSSOToken(SSOTokenManager.java:325)
     at com.sun.identity.agents.common.SSOTokenValidator.validateInternal(SSOTokenValidator.java:252)
     at com.sun.identity.agents.common.SSOTokenValidator.validate(SSOTokenValidator.java:157)
     at com.sun.identity.agents.filter.SSOTaskHandler.process(SSOTaskHandler.java:88)
     at com.sun.identity.agents.filter.AmFilter.processTaskHandlers(AmFilter.java:189)
     at com.sun.identity.agents.filter.AmFilter.isAccessAllowed(AmFilter.java:152)
     at com.sun.identity.agents.websphere.AmIdentityAsserterBase.processRequest(AmIdentityAsserterBase.java:195)
     at com.sun.identity.agents.websphere.AmTrustAssociationInterceptor.negotiateValidateandEstablishTrust(AmTrustAssociationInterceptor.java:91)
     at com.ibm.ws.security.web.TAIWrapper.negotiateAndValidateEstablishedTrust(TAIWrapper.java:101)
     at com.ibm.ws.security.web.WebAuthenticator.handleTrustAssociation(WebAuthenticator.java:191)
     at com.ibm.ws.security.web.WebAuthenticator.authenticate(WebAuthenticator.java:928)
     at com.ibm.ws.security.web.WebCollaborator.authorize(WebCollaborator.java:531)
     at com.ibm.ws.security.web.EJSWebCollaborator.preInvoke(EJSWebCollaborator.java:262)
     at com.ibm.ws.webcontainer.webapp.WebAppSecurityCollaborator.preInvoke(WebAppSecurityCollaborator.java:132)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:506)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:208)
     at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:134)
     at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:321)
     at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
     at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:246)
     at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
     at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
     at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:652)
     at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:448)
     at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:936)
07/15/2007 04:19:11:766 PM IST: Thread[Servlet.Engine.Transports : 0,5,main]
SSOTaskHandler: SSO Validation failed for AQIC5wM2LY4SfcwoaNKFd01DvjYeNPbR3wXaa9sMVjcKtwo=@AAJTSQACMDE=#
07/15/2007 04:19:11:766 PM IST: Thread[Servlet.Engine.Transports : 0,5,main]
URLFailoverHelper: Checking if https://apollo.maxnewyorklife.com:443/amserver/UI/Login is available
07/15/2007 04:19:11:797 PM IST: Thread[Servlet.Engine.Transports : 0,5,main]
WARNING: URLFailoverHelper: the url https://apollo.maxnewyorklife.com:443/amserver/UI/Login is not available
javax.net.ssl.SSLHandshakeException: com.ibm.jsse2.util.g: No trusted certificate found
     at com.ibm.jsse2.bw.a(Unknown Source)
     at com.ibm.jsse2.bx.a(Unknown Source)
     at com.ibm.jsse2.bx.a(Unknown Source)
     at com.ibm.jsse2.v.a(Unknown Source)
     at com.ibm.jsse2.v.a(Unknown Source)
     at com.ibm.jsse2.u.a(Unknown Source)
     at com.ibm.jsse2.bx.a(Unknown Source)
     at com.ibm.jsse2.bx.l(Unknown Source)
     at com.ibm.jsse2.bx.startHandshake(Unknown Source)
     at com.ibm.net.ssl.www.protocol.https.b.o(Unknown Source)
     at com.ibm.net.ssl.www.protocol.https.q.connect(Unknown Source)
     at com.ibm.net.ssl.internal.www.protocol.https.HttpsURLConnection.connect(Unknown Source)
     at com.sun.identity.agents.common.URLFailoverHelper.isAvailable(URLFailoverHelper.java:190)
     at com.sun.identity.agents.common.URLFailoverHelper.getAvailableURL(URLFailoverHelper.java:129)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getLoginURL(AmFilterRequestContext.java:757)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectURL(AmFilterRequestContext.java:285)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectURL(AmFilterRequestContext.java:258)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectResult(AmFilterRequestContext.java:363)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectResult(AmFilterRequestContext.java:345)
     at com.sun.identity.agents.filter.SSOTaskHandler.doSSOLogin(SSOTaskHandler.java:210)
     at com.sun.identity.agents.filter.SSOTaskHandler.process(SSOTaskHandler.java:98)
     at com.sun.identity.agents.filter.AmFilter.processTaskHandlers(AmFilter.java:189)
     at com.sun.identity.agents.filter.AmFilter.isAccessAllowed(AmFilter.java:152)
     at com.sun.identity.agents.websphere.AmIdentityAsserterBase.processRequest(AmIdentityAsserterBase.java:195)
     at com.sun.identity.agents.websphere.AmTrustAssociationInterceptor.negotiateValidateandEstablishTrust(AmTrustAssociationInterceptor.java:91)
     at com.ibm.ws.security.web.TAIWrapper.negotiateAndValidateEstablishedTrust(TAIWrapper.java:101)
     at com.ibm.ws.security.web.WebAuthenticator.handleTrustAssociation(WebAuthenticator.java:191)
     at com.ibm.ws.security.web.WebAuthenticator.authenticate(WebAuthenticator.java:928)
     at com.ibm.ws.security.web.WebCollaborator.authorize(WebCollaborator.java:531)
     at com.ibm.ws.security.web.EJSWebCollaborator.preInvoke(EJSWebCollaborator.java:262)
     at com.ibm.ws.webcontainer.webapp.WebAppSecurityCollaborator.preInvoke(WebAppSecurityCollaborator.java:132)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:506)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:208)
     at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:134)
     at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:321)
     at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
     at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:246)
     at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
     at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
     at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:652)
     at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:448)
     at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:936)
Caused by: com.ibm.jsse2.util.g: No trusted certificate found
     at com.ibm.jsse2.util.f.b(Unknown Source)
     at com.ibm.jsse2.util.f.b(Unknown Source)
     at com.ibm.jsse2.util.d.a(Unknown Source)
     at com.ibm.jsse2.bn.checkServerTrusted(Unknown Source)
     at com.ibm.jsse2.z.checkServerTrusted(Unknown Source)
     ... 39 more
07/15/2007 04:19:11:797 PM IST: Thread[Servlet.Engine.Transports : 0,5,main]
URLFailoverHelper: disconnected the connection for availability check
07/15/2007 04:19:11:797 PM IST: Thread[Servlet.Engine.Transports : 0,5,main]
ERROR: URLFailoverHelper: No URL is available at this time
07/15/2007 04:19:11:797 PM IST: Thread[Servlet.Engine.Transports : 0,5,main]
ERROR: AmFilter: Error while delegating to inbound handler: SSO Task Handler, access will be denied
[AgentException Stack]
com.sun.identity.agents.arch.AgentException: No URL is available at this time
     at com.sun.identity.agents.common.URLFailoverHelper.getAvailableURL(URLFailoverHelper.java:133)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getLoginURL(AmFilterRequestContext.java:757)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectURL(AmFilterRequestContext.java:285)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectURL(AmFilterRequestContext.java:258)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectResult(AmFilterRequestContext.java:363)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectResult(AmFilterRequestContext.java:345)
     at com.sun.identity.agents.filter.SSOTaskHandler.doSSOLogin(SSOTaskHandler.java:210)
     at com.sun.identity.agents.filter.SSOTaskHandler.process(SSOTaskHandler.java:98)
     at com.sun.identity.agents.filter.AmFilter.processTaskHandlers(AmFilter.java:189)
     at com.sun.identity.agents.filter.AmFilter.isAccessAllowed(AmFilter.java:152)
     at com.sun.identity.agents.websphere.AmIdentityAsserterBase.processRequest(AmIdentityAsserterBase.java:195)
     at com.sun.identity.agents.websphere.AmTrustAssociationInterceptor.negotiateValidateandEstablishTrust(AmTrustAssociationInterceptor.java:91)
     at com.ibm.ws.security.web.TAIWrapper.negotiateAndValidateEstablishedTrust(TAIWrapper.java:101)
     at com.ibm.ws.security.web.WebAuthenticator.handleTrustAssociation(WebAuthenticator.java:191)
     at com.ibm.ws.security.web.WebAuthenticator.authenticate(WebAuthenticator.java:928)
     at com.ibm.ws.security.web.WebCollaborator.authorize(WebCollaborator.java:531)
     at com.ibm.ws.security.web.EJSWebCollaborator.preInvoke(EJSWebCollaborator.java:262)
     at com.ibm.ws.webcontainer.webapp.WebAppSecurityCollaborator.preInvoke(WebAppSecurityCollaborator.java:132)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:506)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:208)
     at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:134)
     at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:321)
     at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
     at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:246)
     at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
     at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
     at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:652)
     at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:448)
     at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:936)
Thanks,
Yaseer

Error while setting up J2ee agents

Hi,
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/odi_11g/setup_jee_agent/setup_jee_agent.htm
I am trying to set up J2EE agents for ODI using above link on lynux, in this process I am getting below error while giving createCred command
wls:/ODIDEV-Domain/serverConfig> createCred(map="oracle.odi.credmap",key="SUPERVISOR", user="SUPERVISOR", password="SUNOPSIS")
Traceback (innermost last):
File "<console>", line1, in ?
NameError: createCred
How to solve this issue. Please let me know.
Thanks.

You need to use the right wlst.sh, which is located at Oracle/Middleware/Oracle_ODI/common/bin/wlst.sh

FAM 8.0, Tomcat J2EE agent installation problem

Hello:
I was able to install FAM 8.0 in Tomcat 6.0.14 on Ubuntu (7.04) Linux. Everything seems fine. In the end, the applications I want to use with OpenSSO also make use of Tomcat 6.0.14. I noticed on the opensso users email list that the Tomcat 3.0 agent won't be available until early next year; but that the 2.2 agents should work with FAM 8.0. So, I got the the J2EE agent for Tomcat - SJS_Tomcat_Server_55_agent_2.2-01.tar.gz. The documentation makes no references to Tomcat 6, and I'm hoping this is due to the fact that Tomcat 6 was not available when the documentation was written.
Does this agent work with Tomcat 6? I have this problem when installing the agent (agentadmin --install):
$CATALINA_HOME environment variable is the root of the tomcat
installation.
[ ? : Help, < : Back, ! : Exit ]
Enter the $CATALINA_HOME environment variable: /Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14
Invalid directory specified for the $CATALINA_HOME environment variable
Invalid CATALINA_HOME directory :
/Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14I can see in debug/agentadmin.log the following:
[05/24/2008 13:06:37:684 PDT] FileSystemValidator : Is directory : /Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14 valid ? true
[05/24/2008 13:06:37:686 PDT] HomeDirValidator : Is $CATALINA_HOME directory /Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14 valid ? false
[05/24/2008 13:06:37:686 PDT] Invalid CATALINA_HOME directory : /Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14This directory does indeed exist, and is accessible by the user I'm logged in as. It appears FileSystemValidator agrees with me, but HomeDirValidator has a problem. I tried this on both Ubuntu 6.04 and Mac OS X 10.5.2. Does this indicate that Tomcat 6 is not supported? Or is it indicative that neither OS on which I've tried to install the agent is officially supported?
Thanks!
Jeff

Hi Denis:
Before being redirected to another short term task, I did indeed get the Tomcat 6 agent to work. I probably won't be able to look at OpenSSO again seriously for another couple of months. :(
I have the OpenSSO server running on Tomcat 6.0.14 on Ubuntu 6.x Linux running in a virtual machine on my Mac. I was not able to get the server to run directly on the Mac, and I cannot remember the reason at this time.
But, as far as the agent goes, I run it again using Tomcat 6.0.14 on my Mac (Mac OS X 10.5.2), using the 1.5 JRE. I do have the agentapp war deployed as well as the agentsample web application to play with. In my catalina.out file:
Jun 18, 2008 10:07:20 AM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.14
Jun 18, 2008 10:07:20 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive agentapp.war
Jun 18, 2008 10:07:21 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive agentsample.war
Jun 18, 2008 10:07:22 AM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8090
Jun 18, 2008 10:07:22 AM org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8011
Jun 18, 2008 10:07:22 AM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/16 config=nullI have no error messages is any Tomcat log file.
I checked out the source code for the Tomcat v6 agent (2.2) on May 27, so I don't know how that compares to yours or what's been checked into CVS since my build. I also don't know what the OpenSSO NamingService is.
I assume you used fully qualified domain names to specify the web application to be protected by agent as well as the OpenSSO server itself. The following is the output of the conversation when I run the agent installer script on my system. It has been redacted a bit (domain name and encryption key) to protect my client, but otherwise this is what I supplied to the installer:
Enter the complete path to the directory which is used by Tomcat Server to
store its configuration Files. This directory uniquely identifies the
Tomcat Server instance that is secured by this Agent.
[ ? : Help, ! : Exit ]
Enter the Tomcat Server Config Directory Path
[/opt/apache-tomcat-6.0.14/conf]: /Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14/conf
Enter the fully qualified host name of the server where Access Manager
Services are installed.
[ ? : Help, < : Back, ! : Exit ]
Access Manager Services Host: login.opensso.example.com
Enter the port number of the Server that runs Access Manager Services.
[ ? : Help, < : Back, ! : Exit ]
Access Manager Services port [80]: 8080
Enter http/https to specify the protocol used by the Server that runs Access
Manager services.
[ ? : Help, < : Back, ! : Exit ]
Access Manager Services Protocol [http]:
Enter the Deployment URI for Access Manager Services.
[ ? : Help, < : Back, ! : Exit ]
Access Manager Services Deployment URI [/amserver]: /opensso
Enter the fully qualified host name on which the Application Server
protected by the agent is installed.
[ ? : Help, < : Back, ! : Exit ]
Enter the Agent Host name: analysis.opensso.example.com
$CATALINA_HOME environment variable is the root of the tomcat
installation.
[ ? : Help, < : Back, ! : Exit ]
Enter the $CATALINA_HOME environment variable: /Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14
Choose yes to deploy the policy agent in the global web.xml file.
[ ? : Help, < : Back, ! : Exit ]
Install agent filter in global web.xml ? [true]:
Enter the preferred port number on which the application server provides its
services.
[ ? : Help, < : Back, ! : Exit ]
Enter the port number for Application Server instance [80]: 8090
Select http or https to specify the protocol used by the Application server
instance that will be protected by Access Manager Policy Agent.
[ ? : Help, < : Back, ! : Exit ]
Enter the Preferred Protocol for Application Server instance [http]:
Enter the deployment URI for the Agent Application. This Application is used
by the agent for internal housekeeping.
[ ? : Help, < : Back, ! : Exit ]
Enter the Deployment URI for the Agent Application [/agentapp]:
Enter a valid Encryption Key.
[ ? : Help, < : Back, ! : Exit ]
Enter the Encryption Key [XXmyencryptionkeyXX]:
Enter a valid Agent profile name. Before proceeding with the agent
installation, please ensure that a valid Agent profile exists in Access
Manager.
[ ? : Help, < : Back, ! : Exit ]
Enter the Agent Profile name: testagent1
Enter the path to a file that contains the password to be used for identifying
the Agent.
[ ? : Help, < : Back, ! : Exit ]
Enter the path to the password file: /Users/jas/Development/opensso/tryout/agent_password
SUMMARY OF YOUR RESPONSES
Tomcat Server Config Directory :
/Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14/conf
Access Manager Services Host : login.opensso.example.com
Access Manager Services Port : 8080
Access Manager Services Protocol : http
Access Manager Services Deployment URI : /opensso
Agent Host name : analysis.opensso.example.com
$CATALINA_HOME environment variable :
/Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14
Tomcat global web.xml filter install : true
Application Server Instance Port number : 8090
Protocol for Application Server instance : http
Deployment URI for the Agent Application : /agentapp
Encryption Key : XXmyencryptionkeyXX
Agent Profile name : testagent1
Agent Profile Password file name :
/Users/jas/Development/opensso/tryout/agent_password
Verify your settings above and decide from the choices below.
1. Continue with Installation
2. Back to the last interaction
3. Start Over
4. Exit
Please make your selection [1]: 1
Updating the
/Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14/bin/setclasspath.sh
script with the Agent classpath ...DONE.
Creating directory layout and configuring Agent file for Agent_001
instance ...DONE.
Reading data from file
/Users/jas/Development/opensso/tryout/agent_password and encrypting
it ...DONE.
Generating audit log file name ...DONE.
Creating tag swapped AMAgent.properties file for instance Agent_001 ...DONE.
Creating a backup for file
/Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14/conf/server.xml
...DONE.
Creating a backup for file
/Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14/conf/web.xml
...DONE.
Adding SJS Tomcat Agent Realm to Server XML file :
/Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14/conf/server.xml
...DONE.
Adding filter to Global deployment descriptor file :
/Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14/conf/web.xml
...DONE.
Adding SJS Tomcat Agent Filter and Form login authentication to selected Web
applications ...DONE.
SUMMARY OF AGENT INSTALLATION
Agent instance name: Agent_001
Agent Configuration file location:
/Users/jas/Development/opensso/tryout/tomcat_v6_agent/Agent_001/config/AMAgent.properties
Agent Audit directory location:
/Users/jas/Development/opensso/tryout/tomcat_v6_agent/Agent_001/logs/audit
Agent Debug directory location:
/Users/jas/Development/opensso/tryout/tomcat_v6_agent/Agent_001/logs/debug
Install log file location:
/Users/jas/Development/opensso/tryout/tomcat_v6_agent/logs/audit/install.log
Thank you for using Access Manager Policy Agent
[jaslap:tryout/tomcat_v6_agent/bin] jas% Can you post the exception details you're getting. That might help someone diagnose the problem.
Take it easy,
Jeff

Error when deploying JDBC file data source for J2EE agent in weblogic

Hi ODI experts!
we're using ODI 11g and we've installed J2EE agents on weblogic. We need to configure a connection pool within weblogic for a file data source. Thus, we've added snpsFile.jar (that was shipped with ODI 10g...) to the weblogic config so that we can configure a JDBC connection to file.
As we validate the config, an error occurs (see below):
Obviously, driver is found but cannot be deployed.
####<4 août 2011 09 h 39 CEST> <Error> <Deployer> <ppdlodi001> <SRVPPDODI_001> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <c53bfd6260db74bb:-485a441a:13193b42397:-7ffc-0000000000000027> <1312443551325> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1312443550020' for task 'weblogic.deploy.configChangeTask.6'. Error is: 'weblogic.application.ModuleException: '
weblogic.application.ModuleException:
at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:290)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:508)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:149)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:47)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1223)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:43)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:208)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:749)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:218)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:160)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.prepare(DeploymentReceiverCallbackDeliverer.java:41)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingContextUpdateCompletion.callDeploymentReceivers(AwaitingContextUpdateCompletion.java:164)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingContextUpdateCompletion.handleContextUpdateSuccess(AwaitingContextUpdateCompletion.java:66)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingContextUpdateCompletion.contextUpdated(AwaitingContextUpdateCompletion.java:32)
at weblogic.deploy.service.internal.targetserver.TargetDeploymentService.notifyContextUpdated(TargetDeploymentService.java:225)
at weblogic.deploy.service.internal.DeploymentService$1.run(DeploymentService.java:190)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused By: weblogic.common.ResourceException: com.sunopsis.jdbc.driver.file.a.i
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:263)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1193)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1117)
at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:244)
at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1110)
at weblogic.jdbc.common.internal.ConnectionPool.start(ConnectionPool.java:147)
at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:386)
at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:326)
at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:254)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:508)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:149)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:47)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1223)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:43)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:208)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:749)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:218)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:160)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.prepare(DeploymentReceiverCallbackDeliverer.java:41)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingContextUpdateCompletion.callDeploymentReceivers(AwaitingContextUpdateCompletion.java:164)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingContextUpdateCompletion.handleContextUpdateSuccess(AwaitingContextUpdateCompletion.java:66)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingContextUpdateCompletion.contextUpdated(AwaitingContextUpdateCompletion.java:32)
at weblogic.deploy.service.internal.targetserver.TargetDeploymentService.notifyContextUpdated(TargetDeploymentService.java:225)
at weblogic.deploy.service.internal.DeploymentService$1.run(DeploymentService.java:190)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Thanks in advance for your help.
Fredd.

Hi!
Some information: I found this website [http://gerardnico.com/doc/odi/webhelp/en/refmanual/connexion/jdbcdriversample.htm] explaining that the 'old' snpsFile.jar driver was deprecated and that a new one was existing... but I can't find it anywhere!
My questions are:
- Can the problem (original problem. See initial post) be due to driver version?
- Does someone know where to find this 'new' driver?
Thanks for your help.
Fredd.
Edited by: fredd2 on Aug 5, 2011 10:04 AM
Edited by: fredd2 on Aug 5, 2011 10:07 AM

New weblogic cookie gets created - app is protected by SAM J2EE agent

All
We have installed J2EE agent 2.2 on Weblogic App server (8.1 SP6) fine..
We get authenitcated against access manager while accessing a weblogic app, however it seems that
we are going in a loop and a new weblogic session id is getting created every time
We have the AMfilter as the 1st filter .. etc... We have deployed the SampleApp etc fine in the past
We have checked the AMAgent.properties file etc..
The weblogic app is in the same domain as our SAM server and the cookie domain is set fine...
We can see that SAM cookie is used fine.. but it seems like the weblogic thinks its a new session
and creates a new session cookie all the time
Any ideas
Thanks

We got some new jar files for the agent and now the agent with the tomcat container is working as expected.

Novell Access Manager J2EE Agent Installation

First post and first time attempting to install NETIQ unto my desktop. I'm a little confused as to the section of "Novell Access Manager J2EE Agent Installation" and what to enter for my Admin Console IP Address, username, password, & Application Server IP Address?... I'm not sure as to where to get this information from,..so if anyone could assist me, I'd greatly appreciate it very much, thanks in advance.

kpjones76,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://forums.novell.com/

ODI + J2EE agents

Hello,
I would like to know one info about odi. Whether J2EE agents can be exported and imported? Also can the manual steps involving weblogic for deploying J2EE agents be avoided?
Is there a way to automate this whole process?
Scenario is if i create a new setup (ODI + weblogic) i will have to do this manual steps to extend domain etc
Can this be avoided and automated ?
Thanks & Regards,
Prasad

As far as I am aware, you have to go through Manual process. (Not sure how it is with new ODI 12c).
But its really not that difficult, check here : ODI11g:Deploying and Configuring the ODI Agent as a Java EE Application
I think such feature will be surely expected in future.
Regards,
Santy.

J2EE WS call conflicts in Websphere

Hi!
I am trying to use J2EE webservices in a RAD / Websphere 6.1 environment. However, the libraries included by WS 6.1 create a conflict when performing the Message -> SOAP -> Message translation:
java.lang.ClassCastException: com.ibm.ws.webservices.engine.Message incompatible with com.sun.xml.messaging.saaj.soap.MessageImpl
     at com.sun.xml.rpc.client.StubBase._postSendingHook(StubBase.java:231)
Is there any way I can make sure that J2EE webservices does not cast its message as a com.ibm.ws.webservices.engine.Message?
The library that contains the package is necessary for WebSphere (i.e. I can't remove it) but I would like to somehow exclude it in the code for my J2EE WS calls.
Thank you for your time and help,
Michael

I'm getting a very similar type of exception which I posted about [here |http://www.coderanch.com/t/455258/Websphere/t-create-right-SOAPFactory-when#2028654] and here :
java.lang.ClassCastException: com.ibm.ws.webservices.engine.xmlsoap.Name incompatible with com.systinet.saaj.soap.NameImpl
   at com.systinet.saaj.soap.SOAPHeaderImpl.getSOAPElement(SOAPHeaderImpl.java:60)
   at com.systinet.saaj.soap.SOAPElementImpl.addChildElement(SOAPElementImpl.java:73)
   at com.systinet.saaj.soap.SOAPHeaderImpl.addHeaderElement(SOAPHeaderImpl.java:24)
   at com.filenet.apiimpl.wsi.ClientHeaderProcessor.handleOutput(ClientHeaderProcessor.java:90)   I'm able to resolve this in Glassfish by setting a JVM option to -Djavax.xml.soap.SOAPFactory=com.systinet.saaj.soap.SOAPFactoryImpl
However, a similar type of setting in WebSphere does not fix the problem. If I set this property, then query the SOAPFactory being used, it is still the wrong class.
Have you had any luck with a solution?

AM 7.1 patch1 + GlassFish 9.1_02 + J2EE Agent authentication problem

I've AM 7.1 running on SJS AS 9.1_02 on one host, and I want to protect a portal application also running on SJS AS 9.1_02, but on a different host.
I did have any problem/error when installing the J2EE agent
I can authenticate with any user to my user realm in AM, I think it's well configured but I try to connect to my portal, I get the following error in the browser:
javax.servlet.ServletException: PWC1243: Filter execution threw an exception
java.lang.NoClassDefFoundError
The agent log file doesn't have anything special
The application server server.log file contains the following error:
[#|2008-08-22T17:07:10.892+0200|SEVERE|sun-appserver9.1|javax.enterprise.system.container.web|_ThreadID=16;_ThreadName=httpSSLWorkerThread-8080-1;_RequestID=7
79200cb-b4d7-4e4a-a25b-c68f2c2253d4;|StandardWrapperValve[jsp]: PWC1406: Servlet.service() for servlet jsp threw exception
java.lang.NoClassDefFoundError
at com.sun.identity.agents.filter.URLPolicyTaskHandler.initialize(URLPolicyTaskHandler.java:63)
I've checked the application server CLASSPATH, and it looks fine since it contains, among others, the agent.jar file .
So, I don't understand where's the problem. Any idea ?

No direct solution found.
The ClassNotFound exception actually seemed to be a side effect rather than the real origin of the problem.
I found a workaround by uninstalling the whole J2EE agent software and using instead an embedded feature
of the application to protect, enabling some kind of OpenSSO client module.

Policy Agent 3.0 on Websphere Portal 6.1

Hello
I am looking into using policy agent 3.0 for Websphere Portal 6.1. Looking at the instructions of policy agent installation, it asks about OpenSSO Enterprise server as a requirement. We currently use Sun Access Manager to authenticate against our LDAP. I have a few follow-up questions
Do we need OpenSSO Enterprise server or can I use Sun AM urls while installing policy agent?
Do I need to install agent both on Websphere App server and portal server?
Any help is appreciated
thanks

Policy Agent 3.0.4 installed on Windows 2008 R2 IIS7.5, and the servers is NOT OpenSSO or OpenAM, but Sun Access Manager 7.1.
Turns out we were using the nightly build, version 3.0.5, not the stable 3.0.4. So we installed 3.0.4 instead. And now it works like a charm :-)

Weblogic J2EE agent 2.2 performance issue

Hi All,
Are these known performance issues with J2EE Agent 2.2 for Weblogic 8sp5?
Is there a document that tells about performance tuning of J2EE Agent 2.2 for Weblogic server?
We are doing the load testing with AM 7.0 and Weblogic J2EE Agent. We found that AM7.0 with Apache Policy agent works fine in our load test. Our Application's performance without the J2EE agent is good. The moment we add J2EE Agent for weblogic to the equation, it goes south...
Any help will be appreciated,
Thanks,
Vivek

Hi All,
Are these known performance issues with J2EE Agent 2.2 for Weblogic 8sp5?
Is there a document that tells about performance tuning of J2EE Agent 2.2 for Weblogic server?
We are doing the load testing with AM 7.0 and Weblogic J2EE Agent. We found that AM7.0 with Apache Policy agent works fine in our load test. Our Application's performance without the J2EE agent is good. The moment we add J2EE Agent for weblogic to the equation, it goes south...
Any help will be appreciated,
Thanks,
Vivek

Security Provider(JAAS chaine module)logging with SAP J2EE Agent Policy 2.2

Hello,
I have installed and configured a SAP J2EE Policy Agent 2.2 on a SAP J2EE Application Server 7.0 and installed an opensso 8.0.
I have configured and deployed a jsp application with the descriptor containing the agent filter on the SAP J2EE.
I have configured the security provider (based on JAAS) as follows:
EvaluateTicketModule
AmSAPWASLoginModule
CreateTicketLoginModule
I have then increased the severity check of logging on the SAP J2EE Application Server for:
com.sap.security.server.jaas
com.sap.engine.services.security
But since the installation of the agent, I am not able to see the logs of the different logon modules and be sure that the CreateLoginModule has been done.
I need to check that after the success of the agent login module, it goes through the CreateTicketLoginModule, how can I check that.
Thanks,
Tanguy Mezzano
amFilter log:
11/13/2008 06:02:39:810 PM CET: SAPEngine_Application_Thread[impl:3]_35
AmFilter: now processing: Notification Task Handler
11/13/2008 06:02:39:810 PM CET: SAPEngine_Application_Thread[impl:3]_35
AmFilter: now processing: Port Check Task Handler
11/13/2008 06:02:39:810 PM CET: SAPEngine_Application_Thread[impl:3]_35
PortCheckTaskHandler: request is on valid port
11/13/2008 06:02:39:810 PM CET: SAPEngine_Application_Thread[impl:3]_35
AmFilter: now processing: FQDN Task Handler
11/13/2008 06:02:39:810 PM CET: SAPEngine_Application_Thread[impl:3]_35
FQDNHelper: Incoming Server Name: [myserver] Result: null
11/13/2008 06:02:39:810 PM CET: SAPEngine_Application_Thread[impl:3]_35
AmFilter: now processing: Not Enforced List Task Handler
11/13/2008 06:02:39:810 PM CET: SAPEngine_Application_Thread[impl:3]_35
NotenforcedURIHelper.isNotEnforced(/myApp.jsp) found in enforced cache
11/13/2008 06:02:39:810 PM CET: SAPEngine_Application_Thread[impl:3]_35
NotenforcedURIHelper.isNotEnforced(/myApp.jsp) => false
11/13/2008 06:02:39:810 PM CET: SAPEngine_Application_Thread[impl:3]_35
AmFilter: now processing: SSO Task Handler
11/13/2008 06:02:40:122 PM CET: SAPEngine_Application_Thread[impl:3]_35
SSOTaskHandler: SSO Validation successful for id=myUser,ou=user,dc=myCompany,dc=com
11/13/2008 06:02:40:122 PM CET: SAPEngine_Application_Thread[impl:3]_35
AmFilter: now processing: URL Policy Task Handler
11/13/2008 06:02:40:310 PM CET: SAPEngine_Application_Thread[impl:3]_35
URLPolicyTaskHandler: access allowed by AmWebPolicy
11/13/2008 06:02:40:310 PM CET: SAPEngine_Application_Thread[impl:3]_35
AmFilter: now processing: Redirect Check Result Handler
11/13/2008 06:02:40:310 PM CET: SAPEngine_Application_Thread[impl:3]_35
RedirectCheckResultHandler: removing redirect counter cookie
11/13/2008 06:02:40:310 PM CET: SAPEngine_Application_Thread[impl:3]_35
AmFilter: result =>
FilterResult:
Status : CONTINUE
RedirectURL : null
RequestHelper:
null
Data:
null
-----------------------------------------------------------

I want to use my login page in BEA instead of Access Manager or Distributed Authentication Module. I think it is similar to the problem you have? Did you come up with a solution?
My problem is described in more detail on this thread:
http://forum.java.sun.com/thread.jspa?threadID=5197783

Error in integrating SAP J2EE agent with SAP EP7.0

hi
i got the following Error in logs while attempt for hitting SAP URL it redirects to SAM after giving credential it come back to sam SAP URL says internal server Error from logs i found following:-
SAPEngine_Application_Thread[impl:3]_37
ERROR: AmSAPEP70LoginModule.login(): An exception occured while processing login()
com.sap.engine.services.security.exceptions.BaseUnsupportedCallbackException: Unsupported type of callback.
     at com.sap.engine.services.security.remoteimpl.login.RemoteLoginContextHelperImpl.handle(RemoteLoginContextHelperImpl.java:126)
     at com.sun.identity.agents.sap.v70.AmSAPEP70LoginModule.login(AmSAPEP70LoginModule.java:81)
     at com.sap.engine.services.security.login.LoginModuleLoggingWrapperImpl.login(LoginModuleLoggingWrapperImpl.java:150)
     at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:69)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.services.security.login.FastLoginContext.login(FastLoginContext.java:172)
     at com.sap.engine.services.security.remoteimpl.login.RemoteLoginContextHelperImpl.login(RemoteLoginContextHelperImpl.java:72)
     at com.sap.engine.services.security.remoteimpl.login.RemoteLoginContextHelperImplp4_Skel.dispatch(RemoteLoginContextHelperImplp4_Skel.java:64)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
06/16/2008 05:05:11:780 PM GMT+05:30: SAPEngine_Application_Thread[impl:3]_37
AmSAPBaseLoginModule.abort(): abort result is: true

Where do I have to create the Agent Profile? in Agents>J2EE or in Agents>Agents 2.2?
Thanks,
Tanguy Mezzano

Using J2EE agent with Portal 7

Hello!
I'm trying to use a J2EE policy agent 2.2 for Application server 8.2 with portal, protecting /portal URL. However, after it prompts me to log in, the policies are not enforced. It works with the agentapp, but not with Portal when the AMagent filter is introduced.
Does anyone know why portal application ignores policies in access manager or where to get the documentation on how to properly troubleshoot this?
Thanks
-Max

Ok, its true.
My intention is to confirm if is possible install a Java instance in the same server that ECC is running with Abap instance.
My confusion is because note 1007341, in "deviations" part, says:
ECC 5.0 (ERP 2004 back-end system),
XSS 500 on a separate J2EE 6.40, EP NW04s
with business packages ESS and MSS (SAP ERP 2004).
The SAP system only supports this system landscape
if you have installed XSS 500 on a separate J2EE 6.40.
Then, would I install abap stack, and java stack as separate instances (not add-in!) ? and this landscape is supported acordding this note?
(in the example, A and C are in the same server)
thanks in advance!
regards,
Edited by: Leandro Balboni on Aug 12, 2008 5:28 PM

J2EE agents v2.2 on WebSphere

Similar Messages

Maybe you are looking for