Servlet + deployable proxy (401 error)

hi,
i'm trying to get my adaptive webservice running inside a servlet. so i created an deployable proxy etc.
error -> Service call exception; nested exception is:
com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (401) Unauthorized.
InitialContext ctx = new InitialContext();
RunSQLWS obj = (RunSQLWS) ctx.lookup("java:comp/env/DPRunSQL");
RunSQLWSViDocument port = (RunSQLWSViDocument) obj.getLogicalPort("Config1Port_Document", RunSQLWSViDocument.class);
port.runSQL("runsql", "select * from ws_runsql");
RunSQLResponse result = new RunSQLResponse();
ArrayList res = result.getResponse();
but i cant find any property to set the username and password (i use basic authentication in my webservices)
pleas help..
regards,
constantin

solved it!
in the visual administrator under services / web services security / web service clients / ...
the dynamic proxy created a new definition and i needed to fill in the basic-authentication stuff

Similar Messages

ABAP client proxy 401 error

Hi i have generated a ABAP client proxy in my ECC system and sending an outbound message to XI. i get the following error.
HTTP response contains status code 401 with the description Unauthorized Error while sending by HTTP (error code: 401, error text: Unauthorized)
I have tested the following.
1) My sld and ECC system have the integration engine and pipeline settings for the XI Server: http://server:8000/sap/xi/engine?type=entry
2) logon to the URL http://server:8000/sap/xi/engine with user XIAPPLUSER and pwd in the browser because of the error 'Der Aufruf der URL http://server:8000/sap/xi/engine wurde aufgrund fehlerhafter Anmeldedaten abgebrochen'
any sugestions ? using a proxy as target works fine

Hi ,
You seem to have a problem with the XIAPPLUSER logon. Can you check that the user has the appropriate authorizations? Maybe the user is locked? Maybe the password has been incorrectly entered?
XIAPPLUSER should have the role SAP_XI_APPL_SERV_USER.
Also, check that the XI engine service has been activated.
Transaction SICF. Default_host->sap->xi Activate the entire node with all subtrees.
Cheers
Manish

Deployable Proxy ClassCast Error

Hi,
I have created a Deployable Webservices Proxy. When I try to use it, I get a ClassCastException on the last line. Can someone please help me to figure out why? Thanks
Object obj = ctx.lookup("/wsclients/proxies/sap.com/analytics~perws/com.sap.analytics.GetObjectList");
// obj.getClass().getName() -> RS_BCT_XA_X_OBJECT_GETLISTServiceImpl.
RS_BCT_XA_X_OBJECT_GETLISTService x = (RS_BCT_XA_X_OBJECT_GETLISTService) obj;

Yes, it is solved.
You need to create a Hard reference to the library sapxmltoolkit.
This must be done in your deployable prpxy project/application.
Using Navigation view of your proxy project, you should find the application-j2ee-engine.xml file. Use NWDI, u can add a hard reference to the library.
Remember, this must be done on the deployable proxy project. After you finished, your file shold look as follow:. Good luck.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE application-j2ee-engine SYSTEM "application-j2ee-engine.dtd">
<application-j2ee-engine>
 <reference
 reference-type="hard">
 <reference-target
 provider-name="sap.com"
 target-type="library">sapxmltoolkit</reference-target>
 </reference>
 <provider-name>sap.com</provider-name>
 <fail-over-enable
 mode="disable"/>
</application-j2ee-engine>

Invoke Web Service error: WS Client ---Deployable Proxy --WS-https

hi all:
I use Deployable Proxy in NWDS to call Web Service(https-SSL)
working on PI7.0 platform
Scenario is :
WSClient(Stateless EJB) -
>Deployable Proxy ---> WS-https
Deployable Proxy setting:
SSL Service Certification : Ignore Service Certification
Run Result is :
Sometimes it works(Really amazing)
Sometimes it doesn't work.
When it doesn't work:
The http response is : HTTP/1.1 500 Internal Server Error
J2EE engine exception log is : pay attention the Strong msg
[EXCEPTION]
com.sap.engine.services.ejb.exceptions.BaseEJBException: Exception in method getVersion.
     at com.sap.ejb.VersionLocalLocalObjectImpl0_0.getVersion(VersionLocalLocalObjectImpl0_0.java:119)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.engine.services.webservices.runtime.EJBImplementationContainer.invokeMethod(EJBImplementationContainer.java:126)
     at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:157)
     at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:79)
     at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:92)
     at SoapServlet.doPost(SoapServlet.java:51)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     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:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: javax.xml.rpc.soap.SOAPFaultException: java.lang.NullPointerException
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.buildFaultException(MimeHttpBinding.java:737)
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.processRpcFault(MimeHttpBinding.java:771)
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1470)
     at com.sap.ws.VersionSoapBindingStub.getVersion(VersionSoapBindingStub.java:74)
     at com.sap.ejb.VersionBean.getVersion(VersionBean.java:44)
     at com.sap.ejb.VersionLocalLocalObjectImpl0_0.getVersion(VersionLocalLocalObjectImpl0_0.java:103)
     ... 25 more
javax.xml.rpc.soap.SOAPFaultException: java.lang.NullPointerException
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.buildFaultException(MimeHttpBinding.java:737)
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.processRpcFault(MimeHttpBinding.java:771)
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1470)
     at com.sap.ws.VersionSoapBindingStub.getVersion(VersionSoapBindingStub.java:74)
     at com.sap.ejb.VersionBean.getVersion(VersionBean.java:44)
     at com.sap.ejb.VersionLocalLocalObjectImpl0_0.getVersion(VersionLocalLocalObjectImpl0_0.java:103)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.engine.services.webservices.runtime.EJBImplementationContainer.invokeMethod(EJBImplementationContainer.java:126)
     at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:157)
     at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:79)
     at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:92)
     at SoapServlet.doPost(SoapServlet.java:51)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     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:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Edited by: paul yang on Mar 9, 2009 8:41 AM

Hi Paul,
As it sometimes works & throws error in some cases, I would recommend you to try restarting the application server.
Also, as there is some version related issue, you can also try to re-deploy the webservice (I think you are exposing the EJB as webservice), restart the server, deploy new archive & run the application.
Hope this helps you.
Kind Regards,
Nitin

Error while creating a deployable proxy for a URL in NWDS

Hi ,
There is a requirement for calling a webservice in the .NET platform from JAVA using NWDS. The webservice of the server is pinged using the URL of the webservice. when the URL is passed in the WS navigator of CRD ( that is Development Server) , the response is retreived successfully . The version of NWDS is 7.0.23.
we are facing problem when we are trying to create a Deployable proxy in NWDS by using the following steps :
1) Create a Development Component
2) Select the Deployable Proxy
3) Create the Client Proxy Defintion of the created DC
At step 3 , when we giving the url or WSDL link like "http:// www3.authoring.syngenta/newswebservice.asmx?WSDL" (this is just for example) , it is showing as "Invalid wsdl or wsdl not found " . so that we are not able to procees further.
When we are trying to create proxy the for the WSDL link like " http:// www.authoring.syngenta/newswebservice.asmx?WSDL" , we are able to create successfully.
can anyone suggest why we are able to create the proxy for the URL "http:// www.authoring.syngenta/newswebservice.asmx?WSDL" and not for the other URL.
Any pointers or suggestions are very helpful.
Thanks and Regards,
Sreedevi

Late response I know, but I have solved a similar problem recently and thought I would share.
Firstly, the problem is not with the namespace. The "Namespace ..." part is just stating the namespace the "Incorrect Value" has. So this error is complaining about the value "Unknown" - which isn't very helpful.
It appears the SAP SE80 importer does not like elements like the following because it can't understand <s:element ref="s:schema" />. It appears this is a common thing to be included in .NET generated WSDLs.
<s:element minOccurs="0" maxOccurs="1" name="GetCursDynamicResult"> <s:complexType> <s:sequence> <s:element ref="s:schema" /> <s:any /> </s:sequence> </s:complexType></s:element>
SAP will also not like this example as it does not support mixed content (see: http://www.w3schools.com/schema/schema_complex_mixed.asp)
<s:element minOccurs="0" maxOccurs="1" name="SaldoXMLResult">
 <s:complexType mixed="true">
 <s:sequence>
 <s:any />
 </s:sequence>
 </s:complexType>
</s:element>
You can "Fix" the problem in both cases by removing the offending text in a local copy of the WSDL file so remove line 4 in the first example and change line 2 in the second to <s:complexType> the proxy can then be generated. No idea if the resulting service will be fully operational though!

ABAP Client Proxy error code: 401, error text: Unauthorized

Hi,
I have Client proxy in ECC for oubound interface in PI 7.0, when i look into SXMB_MONI of ECC i can see my message with Error "HTTP response contains status code 401 with the description Unauthorized Authorization error while sending by HTTP (error code: 401, error text: Unauthorized)".
As per few thread i already assign SAP_XI_APPL_SERV_USER role to PIAPPLUSER in ECC, still i am getting same eror.
I do not understand how this Proxy communication work, which ECC user will be use in communication and how this communcation link to RFC destination "SAP_PROXY_ESR" type G. Even i can not see type H in ECC so i created RFC destination of type G.
With Regards
Sunil

We were able to get it working by making a change in the Integration Engine Configuration (in sxmb_adm).
Changed "Corresponding Integ. Server" from "http://<server>:<port>/sap/xi/engine?type=entry"
to "dest://RFCdestinationName"

Error when deploy a deployable proxy

Hi all
    I'm using SP15.
    I follow step by step the wizard to create a deployable proxy to implemente a client web services.
    I select Local File System or URL, and I can import the wsdl file, build the project, but when I try to deploy.....
06/03/10 16:44:05 - ERROR: Not deployed. Deploy Service returned ERROR:
                     java.rmi.RemoteException: Cannot deploy application ..
                     Reason: Webservices common deployment exception! The reason is: Error occured, trying to generate ws clients deploy files for applicaiton . . Additional info: ; nested exception is:
                          java.lang.Exception: com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices common deployment exception! The reason is: Error occured, trying to generate ws clients deploy files for applicaiton Additional info:
Any idea ?
Regards
Martin

Hi Martin,
I have found the same problem that you... did you finally solve it?
Could you please tell me what it was wrong?
Muchísimas gracias.
Isidro Lopez

Failed creation of deployable proxy upon wsdl containing "soapenc" types

Hello all,
I've tried to create deployable proxy upon wsdl file
Creation process has failed and following exception was logged:
com.sap.engine.services.webservices.jaxrpc.exceptions.ProxyGeneratorException: Proxy Generator Error. Proxy generation problem. See nested exception.
Caused by: java.lang.Exception: WSDL part <in0> points to unavailable type with qname: <string>
wsdl is created by Apache Axis version: 1.4. It contains "soapenc" types, e.g.:
 <wsdl:message name="getPageObjectListRequest">
 <wsdl:part name="in0" type="soapenc:string"/>
 <wsdl:part name="in1" type="soapenc:string"/>
 <wsdl:part name="in2" type="soapenc:string"/>
 <wsdl:part name="in3" type="soapenc:string"/>
 </wsdl:message>
Could you give me any advice? What should I do to create deploable proxy upon such wsdl file?

I am getting this error by generating a web service from pl/sql procedure. Just one package, just one procedure. Error stack:
java.lang.NullPointerException
 at oracle.jdevimpl.webservices.generator.WrapperClassGenerator.generate(WrapperClassGenerator.java:262)
 at oracle.jdevimpl.webservices.generator.SPWebServiceGenerator$1.run(SPWebServiceGenerator.java:285)
 at oracle.ide.dialogs.ProgressBar.run(ProgressBar.java:551)
 at java.lang.Thread.run(Thread.java:595)
The pl/sql package header looks like this:
CREATE OR REPLACE package ADMIN.etis_autent as
procedure autent(
 ps_kasutajatunnus in varchar2,
 ps_parool in varchar2,
 ps_isikukood out varchar2,
 ps_eesnimi out varchar2,
 ps_perekonnanimi out varchar2
end etis_autent;
/

HTTP 401 error while connecting SAP PI 7.1 with SOAPAdapter

Hello,
I am trying to call webservice on R/3 system using SAP PI 7.1 but I am getting HTTP 401 error.
Following is the error for more detail:
Message: Server returned error code = 401 for URI : http://sapxx03x:50000/XISOAPAdapter/MessageServlet?channel=:BS_xxxxxxxxxxx_50:CC_xxxxxxxxxxxxx_WSDL_Sender.
same url when I use with SAP XI 3.0 it works fine. It is only giving problem with PI 7.1
I know this issue is related to authentication but what problem I am facing is how to pass the credentical with the url to
resolve this authentication issue? Are there any settings I am missing? or Any other way of doing it?
I have already tried following things to resolve this issue:
1. tried giving user id & password in URL but still having same error HTTP 401.
2. tried one of the SAP note (891877) regarding Netweaver Administration to change ROLE settings but problme still persist.
3. Checked SAP Help settings
4. Did changes to web.xml file to comment the security part and restarted the system
But, Problem still exist.
Please let me know what will be the solution for this issue.
Thanks,
Anand

Hello Abhishek,
Fine I will try using new URL but user id & password are working fine with PI 7.1.
I tried running URL directly and it is working fine and giving following message:
Message Servlet is in Status OK
Status information:
Servlet com.sap.aii.adapter.soap.web.MessageServlet (Version $Id: //tc/xpi.adapters/NWxx_xx_xxx/src/_soap_application_web_module/webm/api/com/sap/aii/adapter/soap/web/MessageServlet.java#1 $) bound to /MessageServlet
Classname ModuleProcessor: null
Lookupname for localModuleProcessorLookupName: localejbs/ModuleProcessorBean
Lookupname for remoteModuleProcessorLookupName: null
ModuleProcessorClass not instantiated
ModuleProcessorLocal is Instance of $Proxy45_10002
ModuleProcessorRemote not instantiated
Any other pointers,
Thanks,
Anand

Problem in JNDI Lookup of Deployable Proxy from the logon par file

Hi,
I have customized the Logon par file and have a functionality to call a webservice when the Password Reset happens.
from the ResetPassword.jsp , SAPMLogonLogic.java is getting called ,and there is a method called performResetPassword().
I am calling a Deployable Proxy in that method by using the below code,
Gateway objGateway=(SMSGateway)ctx.lookup("java:comp/env/MailProxy");
MailGatewayViDocument objSMSGatewayViDocument=(MailGatewayViDocument )objGateway.getLogicalPort("wsPort_Document",MailGatewayViDocument.class);
objMailGatewayViDocument.sendMail(...);
I am getting the Exception,
com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at java:comp, the whole lookup name is java:comp/env/MailProxy.
I have deployed the Deployable Proxy in the J2EE Engine and add this API Jar as the External Library (Project >Properties>Java Build Path ---> Add External jars...Added the .jar file generated in the Proxy Project).
Please let me know the possible solutions where i can call a deployable proxy inside the logon par file.
Thanks and Regards,
Sekar

Hi,
I have fixed this error by changing the lookup as follows.
InitialContext ctx=new InitialContext();
Gateway objGateway=(Gateway)ctx.lookup("wsclients/proxies/sap.com/GatewayProxy/com.ms.sap..GatewayProxy");
Just open Visual Administrator and look for the path under wsclients for proper naming.
Thanks and Regards,
Sekar
Edited by: Sekar M on Jan 16, 2008 6:10 PM

Wls 10.0 - intermittent 401 errors

I have a simple HelloWorld servlet that is configured to use CLIENT-CERT as the authentication mechanism.
I am attempting to deploy this to a WLS 10.0 instance (though the problem I'm seeing also occurs under 9.2)
When I access the servlet once from my web browser everything works fine, the 2-way SSL handshake takes place and I get the output from my servlet.
However, if I attempt to access the servlet from multiple tabs concurrently, I get 401 errors intermittently. I can pick any one of the tabs that has a 401 error, hit 'reload' and get the correct output from the servlet.
I'm concluding that this problem shows up when too many concurrent authentication attempts are made I get the 401 errors.
This problem disappears if I remove the <security-contraint> section from the web.xml. This leads to the following questions:
1) If the <security-constraint> configures the servlet to allow any authenticated user (i.e the role specified maps to <principal-name>users</principal-name> in weblogic.xml) AND my WebLogic server is configured to require client certificates (and only listen on the SSL port), is the <security-constraint> serving any purpose?
2) How do I go about debugging this? Is this some sort of thread/resource issue that can be tweaked through WebLogic server settings somewhere?
Thanks in advance,
Bruce

Probably too late for an answer but I try,
We are not able to build our J2EE 1.4 application with weblo 10, we have to build them with weblo 8 which contains the xdoclet. then we deploy it in WL10. then sometimes we have to fix some build constraints that WL10 doesn't allow anymore.

[ADF-11.1.2] Security 401 error ONLY while navigating from 1 BTF to another

Hi,
I have 2 BTF in my Security-Enabled ADF application. First BTF has a Task Flow Call to another BTF.
I then created 2 web pages for each BTF. Page A for first BTF and B for second BTF.
If I open any page, it ask for Authentication and display the page with BTF content on web browser.
The only Problem is, if I click on the button on first BTF which has a navigation to second BTF, it throws me following error.
Note: All Task Flows and web page has 'View' permission for 'authenticated-role' Rule. Can someone please explain if I can open 2 BTF separately, then why it is throwing 401 error while navigating from 1 BTF to another. Am I missing assigning any permission ?
javax.servlet.ServletException: ADF_FACES-60101:HTTP Error Status Code: 401."
     at oracle.adfinternal.view.faces.config.rich.XmlHttpServletResponse._logException(XmlHttpServletResponse.java:140)
     at oracle.adfinternal.view.faces.config.rich.XmlHttpServletResponse.sendError(XmlHttpServletResponse.java:106)
     at oracle.adfinternal.view.faces.config.rich.XmlHttpServletResponse.sendError(XmlHttpServletResponse.java:100)
     at oracle.adfinternal.controller.util.JsfInterfaceImpl.sendResponseError(JsfInterfaceImpl.java:477)
     at oracle.adfinternal.controller.engine.ControlFlowEngine.handleException(ControlFlowEngine.java:725)
     at oracle.adfinternal.controller.engine.ControlFlowEngine.doRouting(ControlFlowEngine.java:934)
     at oracle.adfinternal.controller.engine.ControlFlowEngine.doRouting(ControlFlowEngine.java:824)
     at oracle.adfinternal.controller.engine.ControlFlowEngine.routeFromActivity(ControlFlowEngine.java:554)
     at oracle.adfinternal.controller.engine.ControlFlowEngine.performControlFlow(ControlFlowEngine.java:158)
     at oracle.adfinternal.controller.application.NavigationHandlerImpl.handleAdfcNavigation(NavigationHandlerImpl.java:115)
     at oracle.adfinternal.controller.application.NavigationHandlerImpl.handleNavigation(NavigationHandlerImpl.java:84)
     at org.apache.myfaces.trinidadinternal.application.NavigationHandlerImpl.handleNavigation(NavigationHandlerImpl.java:50)
     at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:130)
     at org.apache.myfaces.trinidad.component.UIXCommand.broadcast(UIXCommand.java:190)
     at oracle.adf.view.rich.component.fragment.UIXRegion.broadcast(UIXRegion.java:159)
     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.broadcastEvents(LifecycleImpl.java:1129)
     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:353)
     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:204)
     at javax.faces.webapp.FacesServlet.service(FacesServlet.java:312)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:173)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:121)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:468)
     at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:468)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:293)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:199)
     at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:180)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
     at java.security.AccessController.doPrivileged(Native Method)
     at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
     at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
     at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
     at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161)
     at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:136)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)

I upgraded to 11.1.2.2... and the good news is.. it throws me more appropriate error message:-
ADFC-0619: Authorization check failed: '/WEB-INF/task-flow-name' 'VIEW'.
ADF_FACES-60097:For more information, please see the server's error log for an entry beginning with: ADF_FACES-60096:Server Exception during PPR, #2I was using template taskflow from another adf application, but I failed to give permission to that task flow template because I didn't check "Show task flows imported from ADF libraries".
I gave permission to task template and is working fine now.. :)

HTTP_RESP_STATUS_CODE_NOT_OK 401 error

Hi,
I am doing sender ABAp proxy and receiver Webservice , Proxy is running sucessfully till yesterday but while executing the ABAp proxy 2day i am getting following error
HTTP_RESP_STATUS_CODE_NOT_OK 401 error
HTTP response contains status code 401 with the description Unauthorized Authorization error while sending by HTTP (error code: 401, error text: Unauthorized

Check the RFC Dest of type H in ECC which is connect to XI system is working or not if it not working check the credentials
Below are some tgreads which may help u to solve u r problem
How do you activate ABAP Proxies?
Re: HTTP_RESP_STATUS_CODE_NOT_OK 401 Unauthorized
Re: Regarding HTTP_RESP_STATUS_CODE_NOT_OK error.

Deployable proxy does not provide needed types

Hi everybody,
i have created a deployable proxy with NWDS using this <a href="http://www.webservicex.net/WeatherForecast.asmx?WSDL">WSDL</a>. Now i would love to have a client bean that calls the service via the proxy. I tried to do it like <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/45/029840cf43495195da923f32262911/frameset.htm">this</a>.
Now the problem i have is that when i do the lookup on the initial context i get an object of class WeatherForecastImpl. The deployable proxy, however, does not create this class in design time. Only after deploying it is available on the j2ee. I thus cannot cast to this type, because the NWDS does not recognize the type.... The standalone proxy on the other hand offers this class and allows me to cast to this type in design time. i still get a run time error though. plus it seems wrong to create a standalone proxy for this purpose, right?
I am really new to this java world, so maybe i am missing something really simple. Any help will be much appreciated.
Cheers, Michael.

hey everyone.
Well, it seems, the point is something else. From what i've read throughout the day, the class WeatherForecastImpl is not supposed to be included in the deployable proxy but it should be downcasted to the interface, in this case WeatherForecast. The is, though, that the cast throws an ClassCastEcxeption. Is it possible that the proxy or the implementation were created incorrectly?
this is what the interface looks like:
package de.sap;
* Service Interface (generated by SAP WSDL to Java generator).
public interface WeatherForecast extends javax.xml.rpc.Service {
public java.rmi.Remote getLogicalPort(String portName, Class seiClass) throws javax.xml.rpc.ServiceException;
public java.rmi.Remote getLogicalPort(Class seiClass) throws javax.xml.rpc.ServiceException;
public String[] getLogicalPortNames();
public com.sap.engine.services.webservices.jaxrpc.wsdl2java.lpapi.LogicalPortType getLogicalPortConfiguration(String lpName);
thank for helping.
cheers, michael

A Servlet as Proxy

Hello,
I want to use a servlet as proxy (MyProxy) on Apache Jserv
My HTTPD server (Apache) is located at 10.11.12.13 and my clients
are configurate to use its IP address as proxy...
I have mounted my servlet zone in jserv.conf as:
ApJServMount / /myproxy
-> myproxy : zone in which the servlet used as proxy is located
-> in the myproxy zone properties file, the alias '/' is used for
MyProxy servlet (servlet./.code=MyProxy)
If I try 10.11.12.13/hi (hi is the alias for Hello.class servlet),
It works very well ... It works too if I send request at
10.11.12.13/MyProxy .... but I'm getting a 'BAD Request' HTTP
500 error code when I'm sending a HTTP request to http://10.11.12.13/
Please help me !!!!
Best regards,
Thanks in advance,
Ludovic, from France

Use mod_webapp instead of jServ... Apache is going to deprecate jserv.

Servlet + deployable proxy (401 error)

Similar Messages

Maybe you are looking for