SAP JAX-WS ?_?

Hello,
Does SAP Netweaver implement some kind of policy engine, in order to invoke WS-Security secured Web services? As I know from Metro (Sun), they have integrated this functionality directly. Anyway they use proprietary extensions of the WS-Policy, in order to describe security configuration data like the location of certificates. Beside of that, the license might be a problem for our project. So it would be nice to have some implementation of SAP, if there is one, please let me know.
Thankyou in advance
Konrad
Edited by: konrad.krentz on Oct 16, 2009 2:16 PM

Hi Guys,
I am getting the same error. Any resolution or updates on this.
Were you able to fix this error.
Thanks,
Yomesh

Similar Messages

How to create a JAX-WS dispatch client on top of the SAP JAX-WS runtime?

Hello,
We have created an ear file that calls a web service using the Metro toolkit. This code is throwing an exception when attempting to create a client to connect to the calculation service. The exception is coming out of the core JAX-WS classes that are part of NetWeaver. (see exception below)
Caused by: java.lang.NullPointerException
     at com.sap.engine.services.webservices.espbase.client.jaxws.core.SAPServiceDelegate.createDispatchContextExistingPort(SAPServiceDelegate.java:440)
     at com.sap.engine.services.webservices.espbase.client.jaxws.core.SAPServiceDelegate.createDispatchContext(SAPServiceDelegate.java:475)
     at com.sap.engine.services.webservices.espbase.client.jaxws.core.SAPServiceDelegate.createDispatch(SAPServiceDelegate.java:492)
     at com.sap.engine.services.webservices.espbase.client.jaxws.core.SAPServiceDelegate.createDispatch(SAPServiceDelegate.java:484)
     at javax.xml.ws.Service.createDispatch(Service.java:166)
We have done some research and it appears that as of NetWeaver 7.1 SP3 SAP stopped using the SUN JAX-WS runtime and implemented their own SAP JAX-WS runtime.
Included below is the code we use to create a client below. It works fine on all the platforms we support with the exception of NetWeaver 7.1 SP3 and higher (already checked SP5 as well)
      //Create URL for service WSDL
      URL serviceURL = new URL(null, tpsWSEndpointWSDL);
      //create service qname
      QName serviceQName = new QName(targetNamespace, "CalculateTaxWSService");
      //create port qname
      QName portQName = new QName(targetNamespace, "CalculateTax");
      //create service
      Service service = Service.create(serviceURL, serviceQName);
      //create dispatch on port
      serviceDispatch = service.createDispatch(portQName, Source.class, Service.Mode.PAYLOAD);
      //invoke dispatch with Source based request
      Source result = serviceDispatch.invoke(new StreamSource(documentToInputStream(request)));
Does anyone know what we need to change in order to create a JAX-WS dispatch client on top of the SAP JAX-WS runtime?
Thanksu2026
-Chris

Not that I have a definitive answer, but why should it matter? The web service should be developed independent of TLS. If you are trying to use SSL with then the web service is oblivious to it. If you are trying to use WS security thats a whole other ballgame.

JAX-WS Client throws NULL Pointer Exception in NW 7.1 SP3 and higher

All,
My JAX-WS client is throwing an exception when attempting to create a client to connect to the calculation service. The exception is coming out of the core JAX-WS classes that are part of NetWeaver. (see exception below)
Caused by: java.lang.NullPointerException
     at com.sap.engine.services.webservices.espbase.client.jaxws.core.SAPServiceDelegate.createDispatchContextExistingPort(SAPServiceDelegate.java:440)
     at com.sap.engine.services.webservices.espbase.client.jaxws.core.SAPServiceDelegate.createDispatchContext(SAPServiceDelegate.java:475)
     at com.sap.engine.services.webservices.espbase.client.jaxws.core.SAPServiceDelegate.createDispatch(SAPServiceDelegate.java:492)
     at com.sap.engine.services.webservices.espbase.client.jaxws.core.SAPServiceDelegate.createDispatch(SAPServiceDelegate.java:484)
     at javax.xml.ws.Service.createDispatch(Service.java:166)
I have done some research and it appears that as of NetWeaver 7.1 SP3 SAP stopped using the SUN JAX-WS runtime and implemented their own SAP JAX-WS runtime. I also took the time to decompile the jar file that contained the SAPServiceDelegate class which is throwing the null pointer exception. (see method from SAPServiceDelegate below)
    private ClientConfigurationContext createDispatchContextExistingPort(QName portName, JAXBContext jaxbContext)
        BindingData bindingData;
        InterfaceMapping interfaceMap;
        InterfaceData interfaceData;
        bindingData = clientServiceCtx.getServiceData().getBindingData(portName);
        if(bindingData == null)
            throw new WebServiceException((new StringBuilder()).append("Binding data '").append(portName.toString()).append("' is missing!").toString());
        QName bindingQName = new QName(bindingData.getBindingNamespace(), bindingData.getBindingName());
        interfaceMap = getInterfaceMapping(bindingQName, clientServiceCtx);
        interfaceData = getInterfaceData(interfaceMap.getPortType());
        ClientConfigurationContext result = DynamicServiceImpl.createClientConfiguration(bindingData, interfaceData, interfaceMap, null, jaxbContext, getClass().getClassLoader(), clientServiceCtx, new SOAPTransportBinding(), false, 1);
        return result;
        WebserviceClientException x;
        x;
        throw new WebServiceException(x);
The exception is being throw on the line where the interfaceMap.getPortType() is being passed into the getInterfaceData method. I checked the getInterfaceMapping method which returns the interfaceMap (line above the line throwing the exception). This method returns NULL if an interface cannot be found. (see getInterfaceMapping method below)
   public static InterfaceMapping getInterfaceMapping(QName bindingQName, ClientServiceContext context)
        InterfaceMapping interfaces[] = context.getMappingRules().getInterface();
        for(int i = 0; i < interfaces.length; i++)
            if(bindingQName.equals(interfaces<i>.getBindingQName()))
                return interfaces<i>;
        return null;
What appears to be happening is that the getInterfaceMapping method returns NULL then the next line in the createDispatchContextExistingPort method attempts to call the getPortType() method on a NULL and throws the Null Pointer Exception.
I have included the code we use to create a client below. It works fine on all the platforms we support with the exception of NetWeaver 7.1 SP3 and higher (I already checked SP5 as well)
      //Create URL for service WSDL
      URL serviceURL = new URL(null, wsEndpointWSDL);
      //create service qname
      QName serviceQName = new QName(targetNamespace, "WSService");
      //create port qname
      QName portQName = new QName(targetNamespace, "WSPortName");
      //create service
      Service service = Service.create(serviceURL, serviceQName);
      //create dispatch on port
      serviceDispatch = service.createDispatch(portQName, Source.class, Service.Mode.PAYLOAD);
What do I need to change in order to create a JAX-WS dispatch client on top of the SAP JAX-WS runtime?

Hi Guys,
I am getting the same error. Any resolution or updates on this.
Were you able to fix this error.
Thanks,
Yomesh

Error calling external web service over HTTPS

Hi everyone
I'm trying to call an external web service over HTTPS, and continually get the following error:
com.sap.engine.services.webservices.espbase.wsdl.exceptions.WSDLException: Peer sent alert: Alert Fatal: handshake failure
I haven't tried doing this before, so not quite sure where to start. I have a client certificate that must be used to access the remote web service, and I think the problem is associating the client cert with the web service call.
Has anyone else tried this before? Any suggestions of where to look?
I've had a brief look at Key Storage in NWA, but it's not something I'm familiar with - so not sure if it's even the right place to be looking.
Some help on this would be great!
Thanks
Stuart

Thanks Aleksandar
Here's the output from the trace. Unfortunately the SAP forums don't allow attachments, so it may be difficult to read. Please let me know if you see anything that may help.
Thanks
Stuart
Time Severity User Thread Location Message
09:18:23:687 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out About to get connection from DS
09:18:23:687 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out DS connection=com.sap.engine.services.dbpool.cci.CommonConnectionHandle@fa1b67
09:18:24:187 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out About to get connection from DS
09:18:24:187 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out DS connection=com.sap.engine.services.dbpool.cci.CommonConnectionHandle@4c8af
09:18:24:687 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out About to get connection from DS
09:18:24:687 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out DS connection=com.sap.engine.services.dbpool.cci.CommonConnectionHandle@b6981b
09:18:25:187 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out About to get connection from DS
09:18:25:187 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out DS connection=[email protected]
09:18:25:687 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out About to get connection from DS
09:18:25:687 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out DS connection=[email protected]
09:18:26:187 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out About to get connection from DS
09:18:26:187 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out DS connection=[email protected]
09:18:26:203 Debug Administrator HTTP Worker [0] ~es.espbase.client.jaxws.cts.CTSProvider [com.sap.engine.services.webservices.espbase.client.jaxws.cts.CTSProvider] 'nonProxyHosts' are configured '10.|127.|192.168.*'.
09:18:26:203 Debug Administrator HTTP Worker [0] ~es.espbase.client.jaxws.cts.CTSProvider [com.sap.engine.services.webservices.espbase.client.jaxws.cts.CTSProvider] 'nonProxyHosts' default value is '10.|127.|192.168.*'.
09:18:26:203 Debug Administrator HTTP Worker [0] ~es.espbase.client.jaxws.cts.CTSProvider Loadin mapping file from location :[c:/mapping.txt]
09:18:26:203 Debug Administrator HTTP Worker [0] ~es.espbase.client.jaxws.cts.CTSProvider Additional file for CTS configuration can not be found [c:\mapping.txt (The system cannot find the file specified)].
09:18:26:203 Debug Administrator HTTP Worker [0] ~es.espbase.client.jaxws.cts.CTSProvider >>>>>>>>> ERROR: Could not find mapping for service QName=vipSoapInterfaceService, class=class com.verisign._2006._08.vipservice.VipSoapInterfaceService
09:18:26:203 Debug Administrator HTTP Worker [0] ~es.espbase.client.jaxws.cts.CTSProvider com.sap.engine.services.webservices.espbase.client.jaxws.cts.CTSProvider: Creating client instance with WSDL URL [https://pilot-vipservices-auth.verisign.com:443/prov/soap/val/soap] (vipSoapInterfaceService) <com.verisign._2006._08.vipservice.VipSoapInterfaceService>
09:18:26:203 Debug Administrator HTTP Worker [0] ~es.espbase.client.jaxws.cts.CTSProvider com.sap.engine.services.webservices.espbase.client.jaxws.cts.CTSProvider: Using SAP JAX-WS Implemetation to create service delegate.
09:18:26:687 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out About to get connection from DS
09:18:26:687 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out DS connection=com.sap.engine.services.dbpool.cci.CommonConnectionHandle@5586b0
09:18:26:687 Path Administrator HTTP Worker [0] ~s.espbase.wsdl.exceptions.WSDLException Exception : Peer sent alert: Alert Fatal: handshake failure
java.lang.Exception
at com.sap.exception.BaseExceptionInfo.traceAutomatically(BaseExceptionInfo.java:1230)
at com.sap.exception.BaseExceptionInfo.<init>(BaseExceptionInfo.java:147)
at com.sap.exception.BaseException.<init>(BaseException.java:89)
at com.sap.engine.services.webservices.espbase.wsdl.exceptions.WSDLException.<init>(WSDLException.java:34)
at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.loadDOMDocument(WSDLLoader.java:140)
at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.load(WSDLLoader.java:91)
at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.load(WSDLLoader.java:80)
at com.sap.engine.services.webservices.espbase.client.jaxws.core.SAPServiceDelegate.loadWSDLDefinitions(SAPServiceDelegate.java:201)
at com.sap.engine.services.webservices.espbase.client.jaxws.core.SAPServiceDelegate.initWSDL(SAPServiceDelegate.java:159)
at com.sap.engine.services.webservices.espbase.client.jaxws.core.SAPServiceDelegate.<init>(SAPServiceDelegate.java:113)
at com.sap.engine.services.webservices.espbase.client.jaxws.cts.CTSProvider.createDelegate(CTSProvider.java:170)
at com.sap.engine.services.webservices.espbase.client.jaxws.cts.CTSProvider.createServiceDelegate(CTSProvider.java:151)
at javax.xml.ws.Service.<init>(Service.java:57)
at com.verisign._2006._08.vipservice.VipSoapInterfaceService.<init>(VipSoapInterfaceService.java:41)
at JEE_jsp_result_6740550_1225116575421_1225116585468._jspService(JEE_jsp_result_6740550_1225116575421_1225116585468.java:64)
at com.sap.engine.services.servlets_jsp.lib.jspruntime.JspBase.service(JspBase.java:102)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:66)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:433)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:240)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:66)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:32)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:431)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:289)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:309)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:222)
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:152)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
Caused by: org.w3c.www.protocol.http.HttpException: Peer sent alert: Alert Fatal: handshake failure
iaik.security.ssl.SSLException: Peer sent alert: Alert Fatal: handshake failure
at iaik.security.ssl.r.f(Unknown Source)
at iaik.security.ssl.x.b(Unknown Source)
at iaik.security.ssl.x.a(Unknown Source)
at iaik.security.ssl.r.d(Unknown Source)
at iaik.security.ssl.SSLTransport.startHandshake(Unknown Source)
at iaik.security.ssl.SSLTransport.getOutputStream(Unknown Source)
at iaik.security.ssl.SSLSocket.getOutputStream(Unknown Source)
at org.w3c.www.protocol.http.g.markUsed(Unknown Source)
at org.w3c.www.protocol.http.HttpBasicServer.getConnection(Unknown Source)
at org.w3c.www.protocol.http.HttpBasicServer.runRequest(Unknown Source)
at org.w3c.www.protocol.http.HttpManager.runRequest(Unknown Source)
at org.w3c.www.protocol.http.HttpURLConnection.connect(Unknown Source)
at org.w3c.www.protocol.http.HttpURLConnection.a(Unknown Source)
at org.w3c.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
at java.net.URL.openStream(URL.java:1007)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:201)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:263)
at com.sap.engine.lib.xml.parser.Parser.parse_DTDValidation(Parser.java:282)
at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:293)
at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:101)
at com.sap.engine.lib.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:127)
at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:146)
at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.loadDOMDocument(WSDLLoader.java:132)
at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.load(WSDLLoader.java:91)
at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.load(WSDLLoader.java:80)
at com.sap.engine.services.webservices.espbase.client.jaxws.core.SAPServiceDelegate.loadWSDLDefinitions(SAPServiceDelegate.java:201)
at com.sap.engine.services.webservices.espbase.client.jaxws.core.SAPServiceDelegate.initWSDL(SAPServiceDelegate.java:159)
at com.sap.engine.services.webservices.espbase.client.jaxws.core.SAPServiceDelegate.<init>(SAPServiceDelegate.java:113)
at com.sap.engine.services.webservices.espbase.client.jaxws.cts.CTSProvider.createDelegate(CTSProvider.java:170)
at com.sap.engine.services.webservices.espbase.client.jaxws.cts.CTSProvider.createServiceDelegate(CTSProvider.java:151)
at javax.xml.ws.Service.<init>(Service.java:57)
at com.verisign._2006._08.vipservice.VipSoapInterfaceService.<init>(VipSoapInterfaceService.java:41)
at JEE_jsp_result_6740550_1225116575421_1225116585468._jspService(JEE_jsp_result_6740550_1225116575421_1225116585468.java:64)
at com.sap.engine.services.servlets_jsp.lib.jspruntime.JspBase.service(JspBase.java:102)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:66)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:433)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:240)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:66)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:32)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:431)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:289)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:309)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:222)
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:152)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
09:18:27:187 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out About to get connection from DS
09:18:27:187 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out DS connection=com.sap.engine.services.dbpool.cci.CommonConnectionHandle@20ba3c
09:18:27:687 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out About to get connection from DS
09:18:27:687 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out DS connection=[email protected]
09:18:28:187 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out About to get connection from DS
09:18:28:187 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out DS connection=com.sap.engine.services.dbpool.cci.CommonConnectionHandle@26e3bf
09:18:28:687 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out About to get connection from DS
09:18:28:687 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out DS connection=[email protected]
09:18:29:187 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out About to get connection from DS
09:18:29:187 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out DS connection=com.sap.engine.services.dbpool.cci.CommonConnectionHandle@f827f6
09:18:29:687 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out About to get connection from DS
09:18:29:687 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out DS connection=com.sap.engine.services.dbpool.cci.CommonConnectionHandle@a8646a
09:18:30:187 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out About to get connection from DS
09:18:30:187 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out DS connection=[email protected]
09:18:30:687 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out About to get connection from DS
09:18:30:687 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out DS connection=com.sap.engine.services.dbpool.cci.CommonConnectionHandle@c449f1
09:18:31:187 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out About to get connection from DS
09:18:31:187 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out DS connection=[email protected]
09:18:31:593 Info Administrator HTTP Worker [3] System.out SessionImpl::getContext():[ B E G I N ].timerId=15
09:18:31:593 Info Administrator HTTP Worker [3] System.out SessionImpl::getContext():[ E N D ].timerId=[id:#15, elapsed: 0 ms.]

NWDS Java client creation

Hi Experts,
Could you provide the link/doc to create a Java client for the webservices(wsdl file) from NWDS?
Thanks & Regards
Sara

Hi Sara,
There is a difference in the way NWDI generated the service interface for web services client in SP3.
Until SP3 we used tha SUN RI JAX-WS runtime. In order to deliver the WSDL location packaged with the archive we used ClassLoader.getResource(..).
SP3 uses SAP JAX-WS Runtime which extracts the WSDL Location from annotations in case of deployable client and from static variable when the clients are standalone.
However we made a distinct difference and changed the generation so deployable clients could no be instantiated with "new" and the default constructor.
It should be clarified that deplyable clients should be instantiated using JNDI lookup or injection wuth @WebServiceRef annotation.
So if you need a standalone WS client generate a standalone proxy from the NWDI and it will contain the required code for initialization.
If you are making a java ee application please use the instantiation methods advised by the jave ee specification (lookup or injection).
Check these articles
http://pt.sun.com/sunnews/events/2006/javapt/pdf/SAP_JavaPT06_16102006.pdf
Web Services Development in Java
http://www.sapag.co.in/Portal-HOW-to/How%20to%20Configure%20the%20J2EE%20Engine%20Deployment%20Descriptor.pdf
https://admin.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/309c816e-7c51-2a10-05b6-9e0151d0ea2d
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/90d95d37-3f65-2a10-8fa9-a13738c93ea7
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6b5e9a90-0201-0010-39bd-ca7430d64c92
Hope this help.
Regards,
Suryanarayana

JAX-WS SAP libraries fail to add cookies

I am using the JAX-WS standard way of adding cookies in the web service call. However, it seems like the JAX-WS libraries of SAP (included in NWDS 7.1) does not support it. Does anyone know if there is a fix for this?
My code for adding the cookies follow:
javax.xml.ws.BindingProvider bp = (javax.xml.ws.BindingProvider) proxy;
Map<String, Object> ctxt = bp.getRequestContext();
ctxt.put(javax.xml.ws.BindingProvider.SESSION_MAINTAIN_PROPERTY, true );
Map<String, List<String>> headers = new HashMap<String, List<String>>();
String[] cookiesArray = new String[1];
cookiesArray[0] = "MYCOOKIE=cookieValue";
headers.put("Cookie",Arrays.asList(cookiesArray));
ctxt.put(MessageContext.HTTP_REQUEST_HEADERS, headers);

I am using the JAX-WS standard way of adding cookies in the web service call. However, it seems like the JAX-WS libraries of SAP (included in NWDS 7.1) does not support it. Does anyone know if there is a fix for this?
My code for adding the cookies follow:
javax.xml.ws.BindingProvider bp = (javax.xml.ws.BindingProvider) proxy;
Map<String, Object> ctxt = bp.getRequestContext();
ctxt.put(javax.xml.ws.BindingProvider.SESSION_MAINTAIN_PROPERTY, true );
Map<String, List<String>> headers = new HashMap<String, List<String>>();
String[] cookiesArray = new String[1];
cookiesArray[0] = "MYCOOKIE=cookieValue";
headers.put("Cookie",Arrays.asList(cookiesArray));
ctxt.put(MessageContext.HTTP_REQUEST_HEADERS, headers);

Jax jurisdictions using SAP software

Hello experts,
When I activate the tax jurisdiction determination using SAP software, the system assumes that I am using an external tax software and automatically changes the condition table (A053 to A003) accordingly. In FXTP, I no longer have jurisdiction code as part of my key.
Any ideas would be welcome!
Thanks in advance,
Robyn

Hello,
Any thoughts (even if it's not a solution) on this would be welcome!
Thanks in advance!
Update: OSS responded on a message that if the external system config point is maintained, standard system behaviour is to suppress the jurisdiction code in FTXP.
Edited by: Robyn Wilson on Mar 21, 2011 2:44 PM

J2EE/SAP Enterprise Portal - Developer Position

Our client is looking for Enterprise Application Developer with strong J2EE and SAP Portal knowledge.
Please submit your resume to [email protected] for an immediate consideration.
ENTERPRISE APPLIC. DEVELOPER
Description:
EDUCATION: B.Sc. Computer Science or equivalent Required Technologies: - Strong J2SE and J2EE experience - APIs knowledge - JSP, Java Serlvet, JMS, EJB (Session and CMP 2.x), JDBC, JNDI, JCA, J2EE Deployment, JAX-RPC, SOAP 1.2 - Web UI development framework such as Struts or SAP WebDynpro - Source Code Version control system such as CVS - Java Ant - Java Security and J2EE Security - Eclipse - LDAP JOB DUITES: - Develop plan and implement SAP EP into a large IT environment. This will include providing the technical expertise required to make this happen in a timely manner. - Work with internal clients to translate the defined business requirements into technical solutions, do feasibility assessments and identify the appropriate technical approach to meet those needs. - Technical architecture and design, and hands-on development of Portal solutions which are based on SAP best practices and J2EE standards. - Execute the software development life cycle, develop and carry out development best practices, and participate stress test and performance test. - Support and enhance existing applications.
EXPERIENCE: - Competency in the development of customized software and architecture processes - Java Application Server development, delivery and overall system optimization - Solid experience of software development life cycle (requirements, specifications, design & analysis, construction, testing, deployment). - Proven ability to meet deadlines - Demonstrate the ability to prioritize tasks and work effectively with minimal supervision in a collaborative environment -Must be details-oriented and have a strong commitment to client satisfaction - Strong analytical skills and ability to create innovative solutions to complex problems -Strong communication skills Required Experience: -Object Oriented analysis and design -Solid Java application development experience -Solid Web tier development experience -Solid XML and Web Services experience -Web application security such as Single Sign On architecture -Web application profiling -Experience design and document enterprise applications - Solid troubleshooting skills - Experience with source control system -Web application and enterprise application integration - Knowledge and/or exposure in SOA architecture - Relational database experience, knowledge of repository framework -Commercial Portal product experience is a bonus Desired Experience/Technologies: - Hands on experience in SAP Enterprise Portal 6 - Knowledge of SAP HR, R3, BW - Knowledge of ABAP - Hands on experience in webMethods product suite.

hi aditya,
u can also refer to this links to feel comfortable with portal.
New to EP..
Very new to EP with Little knowledge on JAVA....Help on this
http://help.sap.com/saphelp_nw04s/helpdata/en/10/4baa42cdccda11e10000000a155106/frameset.htm
Beginning EP Development
Oliver's favorite SDN link collection
Top Weblogs of All Time [19 to 14]
Installing and configuring the preview edition of EP
What is EP ??
About portal
e-Books on EP
Beginner to EP
Start with EP
Portal Development
regards
bhargava
note:reward points if useful

Configuring use of clinet certificates for jax web services configuring u

Hello dear people,
I have a very simple jax web service under glassfish v.2.1 and I want to secure it using mutual authentication. I could configure using server certificates but I have problems with configuring the server to ask client certificates. The problem is that the clients are not asked to provide a valid client certificate to use the service. The clients can easily use the service without having a certificate.
Can anyone tell me what should I do to have this?
I got the example code from http://java.net/projects/javaeetutorial/downloads and the sample code that I used is in the folder : javaeetutorial5/examples/jaxws/helloservice-clientcert
Best regards,
Arash.

Did you resolve your issue?
I´m posting some comments that maybe can help newer administrators facing similar doubts.
I´m using NW PI 7.1 EHP1 also and some interfaces were developed for using an external site providing web services through SSL (HTTPS) connection.
As in browser navigation, secure sites protected with SSL has a certificate emited by a international CA. We didn´t perceive the "handshake" in the most of cases because normally the web browser has a group of trusted CAs loaded on its certificate store.
With SAP PI and its WAS Java a similar procedure occurs with a small difference. The WAS Java didn´t have the trusted CAs loaded on KeyStorage. So, when the adapter tries to establishing a connection with an HTTPS site (it is a background process) a "handshake" is required to accepting the certificate and produces a error.
We completes the handshake importing the entire certificate chain (you can upload the site´s certificate to your browser and export it as file) on Keytore under the Trusted CAs view.
Hope this can help someone. It´s an "easy" part of SSL communication.
Now I´m trying to configure the inverse: Some third party consuming the PI web services using SSL. I have an additional component on inbound/ incoming connections that is the SAP Web Dispatcher.
The Help.sap.com is the reference but as always its a little difficult to find the (sequential) path following the links (go ahead, go ahead, go ahead, go back, go back, go ahead)...
Regards,
Rodrigo Aoki

JAX-WS client error when calling web method

My JAX-WS client is getting the following error when calling a web method:
Exception in thread "main" javax.xml.ws.WebServiceException:
No Content-type in the header!
I'm using Eclipse as my development environment. I use the CXF facet to generate a WSDL from Java code. I then use the New -> Web Service Client to generate client side code from the WSDL.
The following fully describes my environment:
Windows XP
JDK 1.6.0_22
Java EE 6
Eclipse Helios
Apache CXF 2.3.0 (runtime)
Tomcat 6.0
I have found several post on the net that describe this problem and a solution for JBoss, but I have been unable to find anything that addresses this error on Tomcat.
I can provide source code if needed. The app is a simple Hello World web service. I'm using it to try and get familiar with developing web services with all the components listed above.
Thanks

Hi Anders,
The resolution of the crossdomain problem is not to store an cross-domain-policy file at the [SAP] webservice side; but instead it needs to be done at the (every...) webservice client. In case the client is an IIS based webapplication (and thus the ultimate end-users are accessing it via their browser), this is not such an issue. It there is sufficient to put an crossdomain.xml policy file in the IIS main virtual root of your 'client' .net webapplication (c:\inetpub\wwwroot). It also can be required or at least helpful to put a clientaccesspolicy.xml file; both at the main virtual root and in the virtual root of the specific webapplication
In case of SharePoint application, the crossdomain.xml file must be stored in the WSS virtual root of that site; c:\inetpub\wwwroot\wss\virtualdirectories\<your SharePoint webapp>
Best regards, William.

SAP NetWeaver 7.1 and Web Services

Hi All,
Can I deploy Web Services(dswsbobje.war) on Sap Netweaver 7.1 ?
Where I can find documentation about that ?
Best Regards,

Hi Anne-Lise,
You going to struggle to get this working on the CE server side. SAP xml deserialization works in a similar fashion as JAXB deserialization & JAX-WS ref. implementation in that it's fault tolerant, so it will just log a warning message if the severity of your tracing location is set to 'Warning'
You could adopt the mediated SAP PI approach that Gourav has suggested OR increasing the severity of your tracing location & try to catch the warning message in you logic from the log OR (very dirty) just add aditional logic to try & catch it.
Ultimately, you would want the consumer to fix their problems first though
Regards, Trevor

SAAJ vs JAX-RPC

Hi Team,
Whats the differences implementing web service clients using SAAJ and JAX-RPC ?
Do we have any performance related differences between these two ?
If I am not worng, SAAJ dynamic way of calling web services which means that it will create SOAP message on fly for every request.
So SAAJ may take more time comapred to implementing the clients using JAX-RPC.
Please correct me if my assumption is wrong.
Thanks,Anil
Edited by: Anilkumar Vippagunta on Jan 29, 2008 1:50 AM
Edited by: Anilkumar Vippagunta on Jan 29, 2008 1:50 AM

Hi Anil
For more details have alook on these links
http://help.sap.com/saphelp_nw04/helpdata/en/d6/f9bc3d52f39d33e10000000a11405a/frameset.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c0bbd890-0201-0010-51bd-97029689f44b
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f98c731d-0e01-0010-dfa5-dfb8f49dac6e
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/ede71ec7-0701-0010-c08c-e284d530f384
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3b28e590-0201-0010-968f-e10ed5328191
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/90a5266f-f721-2a10-7fb1-cefceb106ecf
Regds
Abhishek

Java SE 1.4 client to call a web service JAX-WS

Hello,
I have an application running on Weblogic 8 (supports JAX-RPC) and jdk 1.4. This application has to call a web service running on another application which runs on Weblogic 10 (JAX-WS) and jdk1.5
Is there any JAX-WS implementation that help me generate a client that runs on jdk 1.4?
Thanks in advance,
Javi

Hi,
I think WS RM adapter can be used for the webservice proxy in SAP ECC.
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b00bbb77-75bc-2a10-6b9a-a6f8161515a6
Above link can you give some idea. Here it is point to point one with in SAP. In target side you can make it as file.
Regards,
Reyaz

Need versions of web service standards supported by SAP WAS

Hello Friends,
I need to know web service standards supported by SAP WAS with their versions.
   List of Web service specification needed is:
     Basic Profile
     Attachments Profile
     Simple SOAP Binding Profile
     WS-Addressing , SOAP Binding, WSDL Binding
       Simple Object Access Protocol (SOAP)
       Web Services Description Language (WSDL)
      JAX-WS
       JAX-R (For Registry integration)
Can anyone please provide me with these details?
Thanks and regards,
Mayuresh

I think you have to add the destination in Windows-Preferences-Destination Configuration-Web Service Configuration.
Then you can search it when selecting "web services" as provider
Edited by: Jan Nyfeler on Jun 11, 2010 8:52 AM

JNDI lookup for JAX-WS web services

Hi all,
When a JAX-Ws consumer proxy is deployed in its own EAR and is not consumed by means of an @WebServiceRef by an EE5 component, the proxy itself is not processed and not bound in the global JNDI context.
See:
A Java consumer proxy is not displayed in SAP NetWeaver Adm
SAP Note Number: 1396556
This means that in order to lookup the proxy via JNDI (InitialContext.lookup(...))from an arbitrary code location (i.e. a different EAR) you MUST create and deploy a dummy EJB whose only purpose is to have an instance variable with @WebServiceRef
This way JNDI proxy binding is performed at deploy time.
This seems a bit awkward.
Is there any plan to fix this and have the proxy processed and bound to JNDI at deploy time irrespective of whether it is used or not with @WebServiceRef?
thanks
regards
Vincenzo

appearently no way

SAP JAX-WS ?_?

Similar Messages

Maybe you are looking for