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

Similar Messages

PP module integration with SAP-OER & SAP-AII

Dear All,
What is SAP-OER & SAP-AII module?
How this module integrated with SAP PP?
Maulik

Please go to
http://help.sap.com/erp2005_ehp_05/helpdata/en/52/16a979543311d1891c0000e8322f96/frameset.htm

Issue in Communication of SAP R/3 6.4C with SAP J2EE Engine 6.40.

Hello,
We have an application deployed in SAP J2EE engine 6.20. From SAP R3 (SAP R/3 version is 6.4C), We are communicating to the application deployed in SAP J2EE Engine 6.20 using RFC protocol. EJB module (Deployed in SAP J2EE Engine 6.20) which is being invoked from a Function Module using RFC protocol has the same name as the Function Module name. We were able to communicate to SAP J2EE Engine 6.20 this way.
Currently, I have deployed the same application in SAP J2EE Engine 6.40. I have followed the same procedure which i have used while depolying and working with SAP J2EE Engine 6.20. But, it is not working, and i was not able to communicate to SAP J2EE 6.40, the same way i did in SAP J2EE Engine 6.20.
Please let me know whether the procedure for communicating to SAP J2EE Engine 6.40 has changed in comparison with SAP J2EE Engine 6.20.
Also,Any pointers regarding RFC and JCO implementation in SAP J2EE Engine 6.40 willl be helpful.
Thank you.
Regards,
-Shabir Rahim.

Hi,
compare to 4.7
1.New ABAP editor added like if u write code in abap editor ,using if coditions and select statments it automatically shows the link endif, like if .. endif,select ...endselect.
2.New abap debugger compare to the classic debugger.
3.DBACOCKPIT
Missing indexes of various database tablesu2019 and the transaction to reactivate all the missing indexes is u2018DBACOCKPITu2019. Below is the screenshot of the transaction DBACOCKPIT.
Regards,
Madhu

Security Provider for a web dynpro with tool Visual Administrator

Hello all,
after deploying successfully my web dynpro on the J2EE 7.0 WAS, I'm trying to set up authentication to it but I cannot find my applicaiton in the list of policy configurations of the Security Provider entry. When I try to add the path to my local web dynpro, the engine doesn't find it.
I have noticed that all other policy configurations reference a servlet_jsp application. Should I transform my web dynpro into a servlet_jsp? How do I do that?
Thanks for your input,
Tanguy Mezzano

Hello Marcel,
in fact, I don't succeed to redeploy with another provider name... I have undeployed my webdynpro with SDM on the Java stack, but from NWDS, when I change the application-j2ee-engine.xml and application.xml files, and that I rebuild the webdynpro, when I run and deploy, it always redeploys under the former provider: local.
When I create the application, I tell to use the existing component, should I select create a new one, but that means that I have to rebuild the whole application.
Will then the webdynpro be in the Security Provider list, so that I can configure it with http header?
Thx for your help,
Tanguy

Log In issue with SAP J2EE 6.20 Administrator

After a successful installation I am attempting to Log into the SAP J2EE 6.20 Instance Administrator and am not successful.
Is their a default password for user:Administrator?
If not is there a place where I can reset it?
thanx,
raj.

RJ -
The default password is blank "". Also, you usually need to change the port to 50004 (or calculate depending on the number of J2EE instances on the server).
If you changed the default J2EE password during install, you'll need to use whatever you changed it to.
Also, J2EE needs to be running to log into the Admin console.
Regards,
Kyle

Sender Mail Adapter with SAP Conversion agent

have some1 used SAP conversion agent on attchment from XI Sender Mail adapter?
it seems to ignore the attchment of the e-mail
the sender configuration module tab is as follows :
1.localejbs/AF_Modules/PayloadSwapBean transform
2.localejbs/sap.com/com.sap.nw.cm.xi/CMTransformBean CM
3.sap.com/com.sap.aii.adapter.mail.app/XIMailAdapterBean mail
The paramters are
transform swap.keyName Content-Disposition
transform swap.keyName Content-Description
transform swap.keyValue attachment
transform swap.keyValue codeco
CM TransformationName ZIM_CODECO_VALIDATIONS
The Convesion Agnet runs prefectly when using the Conversion Agent engine
thx,Shai Rosenzweig

check with tis may helpful for you
http://help.sap.com/saphelp_nw04/helpdata/en/43/4c38c4cf105f85e10000000a1553f6/frameset.htm
Regds
Abhishek

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

SAPOSCOL does not start with SAP Host Agent processes

Dear all,
on one of our servers the SAPOSCOL process is not running. The latest SAP Host Agent is in place - automatic updating has been finished sucessfully but after the restart of the host agent processes SAPOSCOL returned the following entry in log dev_saphostexec:
[Thr 01] Fri Nov 25 11:23:30 2011
[Thr 01] *** WARNING => /usr/sap/hostctrl/exe/saposcol -l -w60 pf=/usr/sap/hostctrl/exe/host_profile exit with status 4 [OsCollectorW 171]
It is only a warning but as a consequence no SAPOSCOL process is running.
Any ideas? Your quick response will be very much appreciated
Regards,
Mattias Umlauf

Hi
if
/usr/sap/hostctrl/exe/saposcol -status
shows no PID but shared memory attached either cleanipc
or try to force start saposcol
/usr/sap/hostctrl/exe/saposcol -f
Regards
Stanislav

Urgent: IDOC to EDI with SAP Conversion Agent

Hi,
I have a requiremetn like IDOC to EDI ( Gentran ) scenario.
We have decided to use SAP Conversion Agent to deal the same.
Can anybody share their experiences on this kind of scenario.
Needed step by step information to complete would be appreciated with the full of points.
Cheers.,
E

check with tis may helpful for you
http://help.sap.com/saphelp_nw04/helpdata/en/43/4c38c4cf105f85e10000000a1553f6/frameset.htm
Regds
Abhishek

JAAS Login Module in EP ?

Hi everyone,
I need to do a JAAS proof-of-concept with SAP EP. I have reviewed the necesary steps, but I need some help with the java code.
Somebody has an example of this code ?
Thanks and regards from Mexico !!!
Diego

Hi Diego,
I checked the steps for creating the library and it did not work with me either. The problem was that the tutorial says (at this step: http://help.sap.com/saphelp_nw04/helpdata/en/d8/22d240caeb752ae10000000a155106/frameset.htm) to export the login module class into a JAR file that is saved to an arbitrary directory on your PC. However, on the step where you add the JAR file to the library project, the Developer Studio searches for JAR files under the Dev. Studio's workspace - hence, it cannot find the JAR. The workaround is to export the login module to a JAR that resides under the workspace. And the Studio finds it that way.
Hope that helps!

Regarding RFC Communication from SAP R/3 to SAP J2EE Engine 6.40

Hello,
     We have an application deployed in SAP J2EE engine 6.20. From SAP R3 (SAP R/3 version is 6.4C), We are communicating to the application deployed in SAP J2EE Engine 6.20 using RFC protocol. EJB module (Deployed in SAP J2EE Engine 6.20) which is being invoked from a Function Module using RFC protocol has the same name as the Function Module name. We were able to communicate to SAP J2EE Engine 6.20 this way.
     Currently, I have deployed the same application in SAP J2EE Engine 6.40. I have followed the same procedure which i have used while depolying and working with SAP J2EE Engine 6.20. But, it is not working, and i was not able to communicate to SAP J2EE 6.40, the same way i did in SAP J2EE Engine 6.20.
   Please let me know whether the procedure for communicating to SAP J2EE Engine 6.40 has changed in comparison with SAP J2EE Engine 6.20.
Also,Any pointers regarding RFC and JCO implementation in SAP J2EE Engine 6.40 willl be helpful.
Thank you.
Regards,
-Shabir Rahim.

Hello ,
      The Connection in sm59 is established successfully> there were no Error thorwn in SAP when testing the connnection. But when i am making background call using a Function Module in SAP R3, the calls reaches Application deployed in SAP J2EE Engine 6.40, But it is failing with the error as,
#1.5#005056A24413003C000000240000126000042853BD899290#1170240034258#/System/Server##com.sap.engine.services.dsr####sstra902_IPC_2629150#Guest#6813e650a93f11dba9f5005056a24413#Thread[JCO.ServerThread-1,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/System/Server#Plain####
#1.5#005056A244130042000000000000126000042853CFDB80F8#1170240341655#/System/Server##com.sap.engine.services.dsr#Guest#2####322aaa71b11811db85e1005056a24413#SAPEngine_Application_Thread[impl:3]_36##0#0#Error#1#com.sap.engine.services.dsr#Java#DSR_36#com.sap.engine.services.dsr.res.DSRResourceBundle#Error while taking over external passport null#1#null#
#1.5#005056A244130042000000030000126000042853CFDB86BD#1170240341671#/System/Server##com.sap.engine.services.jndi#Guest#2####322aaa71b11811db85e1005056a24413#SAPEngine_Application_Thread[impl:3]_36##0#0#Info#1#com.sap.engine.services.jndi#Plain###Incorrect name parameter rfcaccessejb//DCEUR/Z_AIS_IPC_CFG_PRICE in naming operation.#
#1.5#005056A244130042000000040000126000042853CFDB8745#1170240341671#/System/Server##com.sap.engine.services.jndi#Guest#2####322aaa71b11811db85e1005056a24413#SAPEngine_Application_Thread[impl:3]_36##0#0#Info#1#com.sap.engine.services.jndi#Plain###Incorrect name parameter java:rfcaccessejb//DCEUR/Z_AIS_IPC_CFG_PRICE in naming operation.#
#1.5#005056A24413003C000000280000126000042853CFDBC4AA#1170240341686#/System/Server##com.sap.engine.services.dsr####sstra902_IPC_2629150#Guest#6813e650a93f11dba9f5005056a24413#Thread[JCO.ServerThread-1,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/System/Server#Plain####
Here, //DCEUR/Z_AIS_IPC_CFG_PRICE is the Funcrtion module name in SAP R/3 6.4C.
Also Please let me know whether is there any Operating Differences between WAS 6.20 and WAS 6.40, for JCO/RFC based Communication( ie Comunicating with WAS 6.40 from SAP r/3 using RFC Protocol). Any materials and Information on how to work on SAP J2EE Engine 6.4 will also be very helpful.
Thank you.

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

SAP Conversion Agent - Performance Tuning

Hi Experts,
We are working with SAP Conversion agent..we have developed several scenarios on that...
But, Now we are worried about the performance issues on the same.
Can anybody share their experience on SAP Conversion Agent and any performance tuning guide on SAP Conversion Agent.
-S

Hi,
/people/bla.suranyi/blog/2006/09/29/conversion-agent--handling-edi-termination-characters
Conversion Agent
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/da1e7c16-0c01-0010-278a-eaed5eae5a5f - conversion agent
Thanks,
Madhu

SAP J2EE version

Hi all
I am in the process of installing EP 6.0 from Netweaver04 DVDs. As prerequisite I installed SAP Web Application Server Java 6.40 on Windows. But when launched J2ee server it shows it as SAP J2EE Engine 6.30 . As per my guess I should see SAP J2EE 6.40. I thought Netweaver 04 comes with SAP J2EE 6.40. Correct me if I am wrong.
2. How to check SP level for J2EE. As per the administrator tool parameter SAP_J2EE_Engine_Version shows 6.30 Patch Level 66061.37. What does it mean? How to interpret this? I need to upgrade from Sp3 to Sp4 before installing portal.
Thanks

Hi RG,
About the Java part of the SAP NetWeaver there is no fundamental difference between 6.30 and 6.40 (in contrast to the APAP part).
So, SAP J2EE Engine up to SP3 is version 6.30 and from SP4 becomes 6.40.
There is a note where you can find what SP is your engine knowing the patch level the note number is 701385.
You can read the information about the version from this file:
"...j2ee/cluster/server0/version.txt" which is located into the J2EE Engine installation directory.
If you cannot see the note 701385, here is a snipped:
The SP number on the market place is just a counter assigned at publication time, i.e. later. That's why the patch number is not written into version.txt.
SP____BuildNumber___TimeStamp________ReleaseDate
00.........48385...........16.04.03 20:43/GMT.....06.10.2003
02.........56692.32......24.07.03 13:16/GMT.....08.10.2003
02-PL1..67206.39......12.01.04 02:21/GMT.....23.01.2004
03.........66061.37......11.01.04 21:06 GMT.....11.01.2004
04.........71379.311.....25.02.04 23:16 GMT.....26.02.2004
05.........75145.313.....19.04.04 19:49 GMT.....19.04.2004
06.........77737.313.....03.06.04 19:38 GMT.....09.06.2004
06-PL1..80393.311.....17.06.04 19:34 GMT.....18.06.2004
07.........83087.313.....29.07.04 19:46 GMT.....05.08.2004
08.........84589.313.....06.09.04 19:48 GMT.....09.09.2004
09.........87037.313.....19.10.04 19:52 GMT.....22.10.2004
(The notation "xx-PLx" in the column "SP" stands for SPxx Patch Level x)
I hope this helps
Best regards,
Lyubomir

JDEV deployment of web app with custom JAAS login module fails

For the first time, I am trying to implement a custom JAAS login module.
JDEV deployment to standalone OC4J only fails when my orion-application.xml is included. The deployment fails with a java.lang.InstantiationException.
This what I have done:
1) Wrote a custom LoginModule called com.whirlpoool.sjtc.jaas.gpa.LDAPLoginModule.
2) Put it and its dependent classes in a jar named sjtcjaas.jar.
3) Put the jar in $ORACLE_HOME\j2ee\home\lib
4) Changed library_path in $ORACLE_HOME\j2ee\home\config\application.xml to
<library path="../../home/lib/scheduler.jar;../../home/lib/sjtcjaas.jar" />
5) Added an orion-application.xml to the JDEV project. (I used an Oracle How-to as a pattern, see below.)
I think I'm close but no cigar, yet. Any help would be appreciated.
Regards,
Al Malin
=============== orion-application.xml ========================================
<?xml version="1.0"?>
<orion-application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://xmlns.oracle.com/oracleas/schema/orion-application-10_0.xsd" deployment-version="10.1.3.0.0" default-data-source="jdbc/OracleDS" schema-major-version="10" schema-minor-version="0" >
<security-role-mapping name="sr_manager">
<group name="managers" />
</security-role-mapping>
<security-role-mapping name="sr_developer">
<group name="developers" />
</security-role-mapping>
<log>
<file path="application.log" />
</log>

<jazn-loginconfig>
<application>
<name>customjaas</name>
<login-modules>
<login-module>
<class>com.whirlpoool.sjtc.jaas.gpa.LDAPLoginModule</class>
<control-flag>required</control-flag>
<options>
<option>
<name>debug</name>
<value>true</value>
</option>
</options>
</login-module>
</login-modules>
</application>
</jazn-loginconfig>
</orion-application>

Starting OC4J from c:\oc4j\j2ee\home ...
2006-09-07 13:45:28.484 NOTIFICATION JMS Router is initiating ...
06/09/07 13:45:29 Oracle Containers for J2EE 10g (10.1.3.0.0) initialized
2006-09-07 13:45:58.609 NOTIFICATION Application Deployer for aam STARTS.
2006-09-07 13:45:58.640 NOTIFICATION Copy the archive to C:\oc4j\j2ee\home\applications\aam.ear
2006-09-07 13:45:58.656 NOTIFICATION Initialize C:\oc4j\j2ee\home\applications\aam.ear begins...
2006-09-07 13:45:58.656 NOTIFICATION Auto-unpacking C:\oc4j\j2ee\home\applications\aam.ear...
2006-09-07 13:45:58.687 NOTIFICATION Unpacking aam.ear
2006-09-07 13:45:58.687 NOTIFICATION Unjar C:\oc4j\j2ee\home\applications\aam.ear in C:\oc4j\j2ee\home\applications\aam
2006-09-07 13:45:58.750 NOTIFICATION Done unpacking aam.ear
2006-09-07 13:45:58.750 NOTIFICATION Finished auto-unpacking C:\oc4j\j2ee\home\applications\aam.ear
2006-09-07 13:45:58.750 NOTIFICATION Auto-unpacking C:\oc4j\j2ee\home\applications\aam\aam.war...
2006-09-07 13:45:58.750 NOTIFICATION Unpacking aam.war
2006-09-07 13:45:58.765 NOTIFICATION Unjar C:\oc4j\j2ee\home\applications\aam\aam.war in C:\oc4j\j2ee\home\applications\aam\aam
2006-09-07 13:45:58.765 NOTIFICATION Done unpacking aam.war
2006-09-07 13:45:58.765 NOTIFICATION Finished auto-unpacking C:\oc4j\j2ee\home\applications\aam\aam.war
2006-09-07 13:45:58.812 NOTIFICATION Initialize C:\oc4j\j2ee\home\applications\aam.ear ends...
2006-09-07 13:45:58.828 NOTIFICATION Starting application : aam
2006-09-07 13:45:58.828 NOTIFICATION Initializing ClassLoader(s)
2006-09-07 13:45:58.828 NOTIFICATION Initializing EJB container
2006-09-07 13:45:58.828 NOTIFICATION Loading connector(s)
2006-09-07 13:45:58.843 NOTIFICATION application : aam is in failed state
06/09/07 13:45:58 WARNING: Application.setConfig Application: aam is in failed state as initialization failedjava.lang.InstantiationException
Sep 7, 2006 1:45:58 PM com.evermind.server.Application setConfig
WARNING: Application: aam is in failed state as initialization failedjava.lang.InstantiationException
06/09/07 13:45:58 oracle.oc4j.admin.internal.DeployerException: java.lang.InstantiationException
06/09/07 13:45:58 at oracle.oc4j.admin.internal.ApplicationDeployer.addApplication(ApplicationDeployer.java:510)
06/09/07 13:45:58 at oracle.oc4j.admin.internal.ApplicationDeployer.doDeploy(ApplicationDeployer.java:191)
06/09/07 13:45:58 at oracle.oc4j.admin.internal.DeployerBase.execute(DeployerBase.java:93)
06/09/07 13:45:58 at oracle.oc4j.admin.jmx.server.mbeans.deploy.OC4JDeployerRunnable.doRun(OC4JDeployerRunnable.java:52)
06/09/07 13:45:58 at oracle.oc4j.admin.jmx.server.mbeans.deploy.DeployerRunnable.run(DeployerRunnable.java:81)
06/09/07 13:45:58 at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:814)
06/09/07 13:45:58 at java.lang.Thread.run(Thread.java:595)
06/09/07 13:45:58 Caused by: java.lang.InstantiationException
06/09/07 13:45:58 at com.evermind.server.ApplicationStateRunning.initDataSources(ApplicationStateRunning.java:1424)
06/09/07 13:45:58 at com.evermind.server.ApplicationStateRunning.initializeApplication(ApplicationStateRunning.java:195)
06/09/07 13:45:58 at com.evermind.server.Application.setConfig(Application.java:391)
06/09/07 13:45:58 at com.evermind.server.Application.setConfig(Application.java:308)
06/09/07 13:45:58 at com.evermind.server.ApplicationServer.addApplication(ApplicationServer.java:1771)
06/09/07 13:45:58 at oracle.oc4j.admin.internal.ApplicationDeployer.addApplication(ApplicationDeployer.java:507)
06/09/07 13:45:58 ... 6 more
2006-09-07 13:45:58.890 NOTIFICATION Application Deployer for aam FAILED.
2006-09-07 13:45:58.890 NOTIFICATION Application UnDeployer for aam STARTS.
2006-09-07 13:45:58.906 NOTIFICATION Removing all web binding(s) for application aam from all web site(s)
2006-09-07 13:45:59.015 NOTIFICATION Application UnDeployer for aam COMPLETES.
06/09/07 13:45:59 WARNING: DeployerRunnable.run java.lang.InstantiationExceptionoracle.oc4j.admin.internal.DeployerException: java.lang.InstantiationException
at oracle.oc4j.admin.internal.DeployerBase.execute(DeployerBase.java:126)
at oracle.oc4j.admin.jmx.server.mbeans.deploy.OC4JDeployerRunnable.doRun(OC4JDeployerRunnable.java:52)
at oracle.oc4j.admin.jmx.server.mbeans.deploy.DeployerRunnable.run(DeployerRunnable.java:81)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:814)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.InstantiationException
at com.evermind.server.ApplicationStateRunning.initDataSources(ApplicationStateRunning.java:1424)
at com.evermind.server.ApplicationStateRunning.initializeApplication(ApplicationStateRunning.java:195)
at com.evermind.server.Application.setConfig(Application.java:391)
at com.evermind.server.Application.setConfig(Application.java:308)
at com.evermind.server.ApplicationServer.addApplication(ApplicationServer.java:1771)
at oracle.oc4j.admin.internal.ApplicationDeployer.addApplication(ApplicationDeployer.java:507)
at oracle.oc4j.admin.internal.ApplicationDeployer.doDeploy(ApplicationDeployer.java:191)
at oracle.oc4j.admin.internal.DeployerBase.execute(DeployerBase.java:93)
... 4 more
2006-09-07 13:45:59.031 WARNING java.lang.InstantiationException

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

Similar Messages

Maybe you are looking for