Is it the same create web service in netweaver CE7.1 and create in ECC6.0?

Hi.
I have some questions about ECC 6.0 and netweaver CE 7.1
1.  I want to test webservice in ECC6.0.
     At this time I have no this product, butI have downloaded netweaver CE 7.1 trial version (contains java edition).
     If I create web service in netweaver CE 7.1 trial version(contains java edition) environment, is it same as create
     web service in ECC6.0?
2.  If I call this web service in netweaver CE7.1 from third party(such as JSP on another machine), is it same as call webservice in
     ecc6.0 from http client?
3.  What relationship and difference between ECC6.0, netweaver 7.1 and netweaver CE 7.1?
Thanks.

answered on another place.

Similar Messages

  • How to publish an image and consume the same via web service?

    how to publish a soap web service which returns image and consume it via a client to display it properly?

    You could try to write a web service that returns a byte array and convert the image to bytes, and convert it back into an image again.

  • Errro while creating web service in NetWeaver 7.1

    I am working with EJB 2.1 project in Netweaver 7.1 . After creating session bean when i m trying to create webservice i m getting following error
    IWAB0234E An internal error occurred. Details: null
        java.lang.NullPointerException
        at org.eclipse.jst.ws.internal.consumption.ui.widgets.runtime.ClientRuntimeSelectionWidgetDefaultingCommand.getServerFromProject(ClientRuntimeSelectionWidgetDefaultingCommand.java:554)
        at org.eclipse.jst.ws.internal.creation.ui.widgets.runtime.ServerRuntimeSelectionWidgetDefaultingCommand.setServiceDefaultServer(ServerRuntimeSelectionWidgetDefaultingCommand.java:309)
        at org.eclipse.jst.ws.internal.creation.ui.widgets.runtime.ServerRuntimeSelectionWidgetDefaultingCommand.execute(ServerRuntimeSelectionWidgetDefaultingCommand.java:172)
        at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.runCommand(CommandFragmentEngine.java:418)
        at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.visitTop(CommandFragmentEngine.java:358)
        at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.moveForwardToNextStop(CommandFragmentEngine.java:253)
        at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager$5.run(SimpleCommandEngineManager.java:252)
        at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager.runForwardToNextStop(SimpleCommandEngineManager.java:216)
        at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.runForwardToNextStop(WizardPageManager.java:96)
        at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.getNextPage(WizardPageManager.java:147)
        at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.getStartingPage(WizardPageManager.java:78)
        at org.eclipse.wst.command.internal.env.ui.widgets.DynamicWizard.getStartingPage(DynamicWizard.java:362)
        at org.eclipse.jface.wizard.WizardDialog.showStartingPage(WizardDialog.java:1173)
        at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:545)
        at org.eclipse.jface.window.Window.create(Window.java:426)
        at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1081)
        at org.eclipse.wst.command.internal.env.ui.widgets.popup.DynamicPopupWizard.run(DynamicPopupWizard.java:126)
        at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:256)
        at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:545)
        at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:490)
        at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:402)
        at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
        at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
        at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682)
        at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293)
        at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
        at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
        at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
        at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
        at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
        at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
        at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
        at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
        at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:153)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
        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:585)
        at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:504)
        at org.eclipse.equinox.launcher.Main.basicRun(Main.java:443)
        at org.eclipse.equinox.launcher.Main.run(Main.java:1169)
        at org.eclipse.equinox.launcher.Main.main(Main.java:1144)
    How to resolve this issue???

    Hello
    You have to configure server for Web Service creation. In NWDS follow the path:  Window->Preferences-> Web Services-> Server and runtime
    and (the same path) Services registry.
    HTH
    Maciej Gottfried

  • How to create web service in netweaver 7.0?

    Dear sir.
    Firstly I'm new in sap product, and needs your help.
    I downloaded netweaver 7.0 vmware on the sap site.
    1. I want to create webservice on netweaver 7.0, and call this web service from other application.
    2. If I create webservice on the another system, how can I call this web service in the netweaver?
    Any guides or references appreciate.
    Thanks.

    Hi,
       SAP NetWeaver has different modules like PI,MDM,BI,EP....... Whic product are you using.??
    Suppose if you want to integrate two SAP Systems,if both System supports Webservice call then you cal it from one SAP Application without SAP Middleware SAP PI.
    elase you have to use SAP PI.
    What do you mean by How to create webservice.?? explain your req bit clearly.
    regards,
    Raj

  • Error while creating web service reference

    Hi,
    I have very limited knowledge of web services. we have a BPEL implementation and I have been handed location to 3 wsdl files for which I am trying to create a web service reference(under shared component->logic) in apex(3.1.1). I am successfully able to create for 1 wsdl but for other two i get the below error.
    "1 error has occurred
    The WSDL document contains multiple SOAP bindings. Application Express only supports WSDL's with one SOAP binding. Click Create Web Service Reference Manually to continue creating a reference for this service."
    looking at the working and not working wsdls, i see the following difference. i collapsed all the xml tags in the wsdl file and found that the one that is not working and giving above error has the below two tags twice with data in it.
    <wsdl:portType name=
    <wsdl:binding name=
    any help to parse this wsdl in APEX be greatly appreciated.
    thanks,
    khan

    I have just read that " APEX does not support multiple binding web services currently" at http://oraclebizint.wordpress.com/category/apex/
    ..still reading it. though the post is dated back in 2008, I wonder why this functionality wasn't added to Apex.

  • Error creating web service reference

    I am getting an error below when creating a web service reference from apex 4.2. Any idea on how to resolve it.
    •The WSDL document could not be understood by the rendering engine. Click Create Web Service Reference Manually to continue creating a reference for this service

    I have just read that " APEX does not support multiple binding web services currently" at http://oraclebizint.wordpress.com/category/apex/
    ..still reading it. though the post is dated back in 2008, I wonder why this functionality wasn't added to Apex.

  • Create a web service from java bean and map exceptions to SOAP faults

    Hi,
    We have to expose our Session stateless EJB3 as web services. I've tried to use annotations and jdev wizard "java bean to web service" and it works fine.
    Our problem now is that our methods can throw a business exception that contains a list of error message strings to be presented on the client.
    I did not find any way to use annotations to make it build a wsdl with soap fault mapped to our exception class. Neither I could to make the wizard to create wsdl with faults.
    As we are exposing already designed and implemented classes as web services, I think the bottom-top (java->wsdl) approach is better that top->botton (wsdl->java). Therefore, I'm looking for a possibility to generate the web services from the java beans and have the exception be mapped to a soap fault message.
    We are using jdev 10.1.3.1 and OAS 10.1.3.1., is there a way to map exceptions to soap faults using bottom->top approach?
    thank you

    A couple of links that may be of help:
    http://www.netbeans.org/servlets/ReadMsg?listName=nbj2ee&msgNo=1218
    My last question concerning web services:
    I have already written a session bean and I'd like to add some methods
    as a web service to it, how do I do that?
    Or I can only create another bean for a webservice and cannot modify the
    original one?You might create web service with existing sources and select you bean. New web services with appropriate lookup method will be generated.
    All web service method, that will be exposed in web service, you
    should add itself (Pop-up menu Web Service -> Add operation)
    http://usersguide.netbeans.org/files/documents/40/73/Chapter9-WebServices.pdf

  • My mom helped me to create my iTunes account and load it with a 50$ gift card and now I wanted to purchase a one month subscription at the AYI dating web service but apple never let them take money from my account and I was declined,don't know why?

    My mom helped me to create my iTunes account and load it with a 50$ gift card and now I wanted to purchase a one month subscription at the AYI dating web service but apple never let them take money from my account and I was declined,don't know why?

    You have posted to the iTunes Match forum, which your question is not related to. I suggest you contact the web site from whom you wish to purchase the subscription.

  • Delete / create the operations in Web services incoming

    Hi Experts,
    I have a situation, I begins in SIEBEL, and I have a question: I search the command that allows me to delete / create the operations in Web services incoming.
    Thanks;
    Hussam

    Help me please!!

  • How to create Web Service based on PI WSDL message

    Hi all,
    we have following scenario:
    Within PI (version 7.1) we set up a message type and inbound service interface. This service interface should send the PI message to a web service running on a SAP J2EE (version 7.01). As the PI message is sent as WSDL I thought it should be easy to build a web service on the SAP J2EE based on this WSDL from PI.
    Unfortunately, I have problems creating the Web Service.
    For my current project we integrated the NWDI to the SAP NetWeaver Developer Studio and I'm required to add the Web Service to an existing DC (Development Component) within the NWDI.
    What I tried so far is:
    - I created a Deployable Proxy Project and within this I created a Client Proxy Definition based on the WSDL from the PI. But I can't add this Proxy to the DCs of the NWDI and I don't know how to implement my own coding here in order execute specific functions.
    - I created a new class within the NWDI DC and a public method. Based on this I created a Virtual Interface and a Web Service Definition (WSD). Then I added this to a Web Service Deployment Descriptor. I uploaded this to the SAP J2EE. But I'm not able to access this and I don't know hoe to assign the WSDL here.
    I also tried here to create a client proxy based on this WSD as I thought I might assign the WSDL here. But I don't see the WSD in the list of Web Services uploaded to the SAP J2EE...
    Can you please advice me how to create a Web Service in such an environment?
    regards
    René Jurmann

    Hi Tahir,
    sorry that you needed to wait this long - but this is how I created the web service:
    The steps on how to create the web service in NetWeaver Developer studio are nearly the same as described in the blog http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/5838. [original link is broken] [original link is broken] [original link is broken]
    Some steps I just skipped and some others I added. Some of the steps I did the way I described it as I needed to connect the web service with the SAP PI.
    Prerequisites:
    Add Java Perspective and J2EE Development Perspective to the open perspectives.
    Within "Window - Preferences - Web Services" check "Soap extensions visible in the virtual interface editor"
    The SDM of the corresponding SAP J2EE is configured within "Window - Preferences"
    Create a Development Component (DC) with type "J2EE -> EJB Module"
    The business logic of the web service will be implemented in an Enterprise Java Bean (EJB). So first the EJB component must be created:
         Choose "File -> New -> Other"
         In opening PopUp choose "Development Component -> Development Component Project"
         Select the Software Component for which you want to add the DC (e.g. "Local Development -> MyComponents")
         Choose now vendor, name and type:
              vendor is an alpha-numeric string of 20 characters starting with a letter - all in lower case
              name is an alpha-numeric string starting with a letter - all in lower case
              vendor and name concatenated must not be longer then 40 characters
              the name can be separated into different part using "/" as separator
              each part of the name must not be longer than 8 characters
              the type is "J2EE - EJB Module"
              you can specify a Caption as general description for the web service
    Create new EJB
    To create the EJB itself:
         In J2EE DC Explorer of J2EE Development Perspective expand new DC and right-click on folder "ejbModule"
         Choose "New - EJB" with following details:
              EJB Name: <name as for PI service Interface to be created - starting in upper case>
              EJB Project: <pre selected>
              Bean Type: Stateless Session Bean
              Default EJB Package: <corresponds to namespace in PI>
              generate default interfaces: Checked
    Regarding the "Default EJB Package" this should be created according the namespace in PI for which all PI objects will be created. This only applies if you have some naming conventions here.
    Example:
    Namespace in PI is:  http://company.net/pi/SOFTWARE_COMP/Application
    The corresponding package then is: net.company.pi.software_comp.application
    Implement coding for web service
    As the web service will be called via PI some transfer variables will be submitted. Most likely, those variables will not be standard type (e.g. String) but a complex type. Those types must be generated as Java classes. Below an example of a complex type I needed:
    Data Type
    net.company.pi.software_comp.application.types.MessageProcessingInformation
    Structure:
         Element name          Element type
         sendingSystemID          String
         interfaceID               String
         businessProcessVariantCode     String
         testIndicator               Boolean
    For every element described a public "get", "set" and "has" method must be created in the corresponding Java class:
    package net.company.pi.software_comp.application.types;
    import java.io.Serializable;
    public class MessageProcessingInformation implements Serializable {
         protected String sendingSystemID;
         protected String interfaceID;
         protected String businessProcessVariantCode;
         protected Boolean testIndicator;
         public String getSendingSystemID() {
              return sendingSystemID;
         public void setSendingSystemID(String value) {
              this.sendingSystemID = value;
         public boolean hasSendingSystemID() {
              if(sendingSystemID != null && !sendingSystemID.equals("")){
                   return true;
              return false;
    All Java classes representing complex types and all classes referenced here (used for sub-types) must implement java.io.Serializable. Java standard types which do not implement this class must not be used as sub-types.
    As soon as all data types are declared the real business logic can be implemented:
         In J2EE DC Explorer of J2EE Development Perspective expand DC - "ejb-jar.xml" - <Name> and double click on "ejbCreate"
         In detail view select folder "Business Methods" and click "Add"
         choose name of business method - this should be the same as the PI message type used for the service interface - starting lower case
         return type should be "void"
         add needed parameters fully qualified - including package (as specified in PI and created previously in DC)
         you can mark certain parameters as array if necessary
    Remark:
    It might be that after saving you get an error. This might be as the package name of one component is copied to the corresponding Java class at the very beginning (before the package declaration within the Java class). Simply delete the string here.
    It also might be, that the new business method is only defined in the remote interface class but not in the bean class. Just create an according method in the bean class.
    Within the newly created business method within the bean class you can now implement the business logic.
    Create a DC with type "J2EE -> Enterprise Application"
    In order to create the "real" web service and deploy it to the J2EE an Enterprise Application project has to be created. So create a new DC as for the EJB Module but choose as type "J2EE -> Enterprise Application".
    After the DC is created right click on the EJB DC and choose "Add to EAR Project". Choose the new DC.
    Create web service for EJB
    As soon as you implemented the business logic you can create the "real" web service. Therefore:
         Right click on the EJB name below "ejb-jar.xml"
         Choose "New - Web Service"
         Choose proper "Web Service Name" and "Configuration Name" (probably oriented at the EJB name)
         Copy the URL of the web service - you'll need it later for PI configuration
         on the second next screen use the same name for "Virtual Interface" and "Web Service Definition" (the name should be the name of the "Endpoint")
         the "EAR Project" should be preselected
    Unfortunately, the web service can't be used in its current configuration to be accessed by PI. Therefore the Virtual Interface must be changed. To do so, expand folder "Virtual Interfaces" and double click the virtual interface created.
    Within the detail view expand in tabs "Mapping" and "Types" the complete folder structure. For any "SOAP Extension" where a namespace can be defined use as namespace the corresponding namespace in PI (e.g. http://corpintra.net/pi/CBFC_GLOBAL_SAP_APPL/BillerDirect) but do not change any "Soap Extension" of a standard Java type. (if you don't have any naming convetions for namespaces in PI you can leave the SOAP Extension here. But then the namespace in PI should be set accordingly.)
    Probably it can be necessary on top level "Soap Extensions" in tab "Mapping" to leave "Use Namespaces for Parameters" unchecked. For some of my web services this parameter must be checked for others not - just try.
    If you can define a "New Name", "Local Name" or "Item Label" for a Soap Extension then use a name with starting upper case letter. (For Java Naming conventions most of the data type names will start with lower case letters.) Especially the method name must be renamed this way in order to stick to the PI namings.
    As a last point to change here check in tab "Mapping" all "Incoming Parameters" which you specified as array. Use for those as "New Name" a different name - do not just simply change from lower case to upper case. This is necessary as on PI we need to create two levels although here only one is specified.
    For any own sub-type declared as array the name within the coding should also differ from the corresponding Java Class name the type refers to.
    If all this is done you can deploy the web service to the J2EE:
         right click on "Enterprise Application" DC and choose "Development Component - Build..." and build all corresponding components
         right click on "Enterprise Application" DC and choose "Development Component - Deploy"
    Test the new web service via <J2EE URL>/wsnavigator/enterwsdl.html
    Create PI interface
    After the web service is created successfully the PI integration can be started.
    Therefore, within the Enterprise Services Builder create a data type according to the web service definition. All components defined on top-level for this data type should be declared as incoming parameter for the web service business method. Therefore it could be necessary to create some sub data types on PI first and add those to the "master" data type.
    Ensure that the names of the components correspond to the names defined in the web service (see virtual interface here). Those names must exactly be the same - including lower/upper case. Also take care for the ordering of the components.
    In case you need to include arrays following applies:
    The upper level is of occurrence "1:1". This has only one sub-entry with occurrence "1:n". The names for upper and sub-level must not equal.
    Based on the data type a message type is created. The name of the message type must be exactly the same as the name of the web service business method. (Hint: the name of the web service business method was most likely changed in the virtual interface. Then this name must correspond to the message type name.) Based on the message type an asynchronous inbound interface is to be created (which will be referred in the Integration Directory). The operation name for this interface (left panel) should be the same as the name for the web service business method.
    Create PI mappings and routings
    How to map (message mapping and operation mapping) from source to the web service message I wont explain here as this depends on the source message. The only important things here are:
         When creating the SOAP communication channel within the Integration Builder the "Target URL" is:
              <J2EE URL>/<Access URL as specified in web service creation>?wsdl&style=document
         The soap action is the name of the web service business method.
         Most likely the web service needs authentication to be executed.

  • Error while creating web services proxy in Jdev. 10.1.3

    Hello,
    I created a web service using jdev.10.1.2 and created successfully a ws proxy with the the same version.
    However when I try to generate a ws proxy using 10.1.3, I am getting error:
    The WSDL document is invalid for the following reason:
    the wsdl contains a mixture of uses- "literal" and "encoded" Only literal OR encoded is supported in a wsdl, not both.
    What is the problem and how can I resolve this?
    Thanks in advance.

    I followed like what is mentioned in the document, however my return type is still object.
    Below is my message part. Pasted at the bottom is my complete wsdl.
    <message name="getEmpInfoXML0Response">
    <part name="result" type="xsd:anyType" />
    </message>
    ****************************** WSDL**************************************
    <?xml version="1.0" encoding="UTF-8" ?>
    - <!-- Generated by the Oracle JDeveloper 10g Web Services WSDL Generator
    -->
    - <!-- Date Created: Sun May 27 10:30:48 AST 2007
    -->
    - <definitions name="Portalws" targetNamespace="http://ws/bs/ew/EmpInfo.wsdl" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://ws/bs/ew/EmpInfo.wsdl" xmlns:ns1="http://ws.bs.ew/IPortalws.xsd">
    - <types>
    <schema targetNamespace="http://ws.bs.ew/IPortalws.xsd" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns="http://www.w3.org/2001/XMLSchema" />
    </types>
    - <message name="getEmpInfoXML0Request">
    <part name="empno" type="xsd:string" />
    </message>
    - <message name="getEmpInfoXML0Response">
    <part name="result" type="xsd:anyType" />
    </message>
    - <portType name="EmpInfoPortType">
    - <operation name="getEmpInfoXML">
    <input name="getEmpInfoXML0Request" message="tns:getEmpInfoXML0Request" />
    <output name="getEmpInfoXML0Response" message="tns:getEmpInfoXML0Response" />
    </operation>
    </portType>
    - <binding name="EmpInfoBinding" type="tns:EmpInfoPortType">
    <soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />
    - <operation name="getEmpInfoXML">
    <soap:operation soapAction="" style="rpc" />
    - <input name="getEmpInfoXML0Request">
    <soap:body use="encoded" namespace="Portalws" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
    </input>
    - <output name="getEmpInfoXML0Response">
    <soap:body use="encoded" namespace="Portalws" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
    </output>
    </operation>
    </binding>
    - <service name="Portalws">
    - <port name="EmpInfoPort" binding="tns:EmpInfoBinding">
    <soap:address location="http://host:portt/WebService-PortalWS-context-root/Portalws" />
    </port>
    </service>
    </definitions>

  • Error creating web service from WSDL in 11.1.2.0.0

    Hello,
    I have just installed JDeveloper 11.1.2.0.0. I tried to test a web service created (and successfully tested) in 11.1.1.5.0. The service is deployed to internal WebLogic server but when I call "Test Web Service" this is the error I get:
    The Web Service Tester cannot be invoked, because the WSDL document of the selected service cannot be read.
    java.lang.IllegalStateException: SSLContextImpl is not initialized
         at com.sun.net.ssl.internal.ssl.SSLContextImpl.engineGetSocketFactory(SSLContextImpl.java:145)
         at javax.net.ssl.SSLContext.getSocketFactory(SSLContext.java:260)
         at oracle.jdevimpl.credential.LazySSLContextSpi.engineGetSocketFactory(LazySSLContextSpi.java:67)
         at javax.net.ssl.SSLContext.getSocketFactory(SSLContext.java:260)
         at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader.getNewReaderInstance(CachedWSDLReader.java:398)
         at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader$1.initialValue(CachedWSDLReader.java:298)
         at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader$1.initialValue(CachedWSDLReader.java:294)
         at java.lang.ThreadLocal.setInitialValue(ThreadLocal.java:141)
         at java.lang.ThreadLocal.get(ThreadLocal.java:131)
         at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader.getReaderImpl(CachedWSDLReader.java:308)
         at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader.readWSDLInternal(CachedWSDLReader.java:531)
         at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader.readWSDLDirect(CachedWSDLReader.java:471)
         at oracle.jdevimpl.webservices.tcpmonitor.ServiceTester$3.run(ServiceTester.java:262)
         at java.lang.Thread.run(Thread.java:662)
    Then I tried to create a new project and Java web service from WSDL, but on the second step of the "Java Web Service from WSDL" wizard when I select WSDL file from the disk and click "Next" I get
    java.lang.IllegalStateException: SSLContextImpl is not initialized
    java.lang.IllegalStateException: SSLContextImpl is not initialized
         at com.sun.net.ssl.internal.ssl.SSLContextImpl.engineGetSocketFactory(SSLContextImpl.java:145)
         at javax.net.ssl.SSLContext.getSocketFactory(SSLContext.java:260)
         at oracle.jdevimpl.credential.LazySSLContextSpi.engineGetSocketFactory(LazySSLContextSpi.java:67)
         at javax.net.ssl.SSLContext.getSocketFactory(SSLContext.java:260)
         at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader.getNewReaderInstance(CachedWSDLReader.java:398)
         at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader$1.initialValue(CachedWSDLReader.java:298)
         at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader$1.initialValue(CachedWSDLReader.java:294)
         at java.lang.ThreadLocal.setInitialValue(ThreadLocal.java:141)
         at java.lang.ThreadLocal.get(ThreadLocal.java:131)
         at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader.getReaderImpl(CachedWSDLReader.java:308)
         at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader.readWSDLInternal(CachedWSDLReader.java:531)
         at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader.readWSDL(CachedWSDLReader.java:484)
         at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader.readWSDL(CachedWSDLReader.java:455)
         at oracle.jdevimpl.webservices.wizard.jaxrpc.common.SpecifyWsdlPanel.fetchWSDL(SpecifyWsdlPanel.java:1050)
         at oracle.jdevimpl.webservices.wizard.jaxrpc.common.SpecifyWsdlPanel$1.run(SpecifyWsdlPanel.java:364)
         at oracle.ide.dialogs.ProgressBar.run(ProgressBar.java:655)
         at java.lang.Thread.run(Thread.java:662)
    I performed fresh install of this new JDeveloper version in new Middleware home with all the default options and this is the first thing I tried.
    Any hints?
    Thanks,
    Bruno

    Hi Vishal,
    no, I don't see any HTTPS security settings defined. The thing is that this worked just fine in 11.1.1.5.0 version. I installed 11.1.2.0.0 and the first thing I tried was testing this web service. Right away I get this error. I also tried creating Web Service Client Proxy for this web service and I get the same exception. I looks to me that this happens when wizard tries parsing WSDL...
    But, I got another error when I opened "Java Web Service Editor" for this web service and selected "Methods":
    NPE in o.ji.webservices.wizard.jaxrpc.bottomup.SelectMethodsPanel:702
    Performing action (35) Project Properties... [ from ProjectNavigatorWindow ] [ for ( VegaService.jpr, VegaService.jpr, DMSVegaAdapter.jws ) ]
    oracle.jdevimpl.webservices.index:Jun 9, 2011 9:05:02 AM IndexFacade runQuery
    INFO: Having to guess workspace
    oracle.jdevimpl.webservices.index:Jun 9, 2011 9:05:28 AM IndexFacade runQuery
    INFO: Having to guess workspace
    Performing action (23) Find... [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (56) Properties... [ from ProjectNavigatorWindow ] [ for ( VegaService, VegaService.jpr, DMSVegaAdapter.jws ) ]
    oracle.jdevimpl.webservices.index:Jun 9, 2011 9:09:32 AM IndexFacade runQuery
    INFO: Having to guess workspace
    java.lang.NullPointerException
    java.lang.NullPointerException
    o.ji.webservices.wizard.jaxrpc.bottomup.SelectMethodsPanel.populateListImpl(SelectMethodsPanel.java:702)
    o.ji.webservices.wizard.jaxrpc.bottomup.SelectMethodsPanel.access$600(SelectMethodsPanel.java:82)
    o.ji.webservices.wizard.jaxrpc.bottomup.SelectMethodsPanel$4$1.run(SelectMethodsPanel.java:603)
    j.a.event.InvocationEvent.dispatch(InvocationEvent.java:209)
    j.a.EventQueue.dispatchEventImpl(EventQueue.java:642)
    j.a.EventQueue.access$000(EventQueue.java:85)
    j.a.EventQueue$1.run(EventQueue.java:603)
    j.a.EventQueue$1.run(EventQueue.java:601)
    j.security.AccessController.doPrivileged(Native Method)
    j.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
    j.a.EventQueue.dispatchEvent(EventQueue.java:612)
    o.javatools.internal.ui.EventQueueWrapper._dispatchEvent(EventQueueWrapper.java:169)
    o.javatools.internal.ui.EventQueueWrapper.dispatchEvent(EventQueueWrapper.java:151)
    j.a.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
    j.a.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
    j.a.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:178)
    j.a.Dialog$1.run(Dialog.java:1046)
    j.a.Dialog$3.run(Dialog.java:1098)
    j.security.AccessController.doPrivileged(Native Method)
    j.a.Dialog.show(Dialog.java:1096)
    j.a.Component.show(Component.java:1585)
    j.a.Component.setVisible(Component.java:1537)
    j.a.Window.setVisible(Window.java:842)
    j.a.Dialog.setVisible(Dialog.java:986)
    o.bali.ewt.dialog.JEWTDialog.runDialog(JEWTDialog.java:395)
    o.bali.ewt.dialog.JEWTDialog.runDialog(JEWTDialog.java:356)
    o.i.dialogs.WizardLauncher.runDialog(WizardLauncher.java:55)
    o.i.panels.TDialogLauncher.showDialog(TDialogLauncher.java:225)
    o.ji.webservices.wizard.jaxrpc.WebServicesEditor.showDialog(WebServicesEditor.java:313)
    o.ji.webservices.WebServicesAddin.findAndInvokeWizard(WebServicesAddin.java:1672)
    o.ji.webservices.WebServicesAddin.handleEvent(WebServicesAddin.java:870)
    o.i.controller.IdeAction$ControllerDelegatingController.handleEvent(IdeAction.java:1469)
    o.i.controller.IdeAction.performAction(IdeAction.java:662)
    o.i.controller.IdeAction.actionPerformedImpl(IdeAction.java:1140)
    o.i.controller.IdeAction.actionPerformed(IdeAction.java:617)
    jx.s.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
    jx.s.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318)
    jx.s.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
    jx.s.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
    jx.s.AbstractButton.doClick(AbstractButton.java:357)
    jx.s.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:809)
    jx.s.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:850)
    j.a.Component.processMouseEvent(Component.java:6289)
    jx.s.JComponent.processMouseEvent(JComponent.java:3267)
    j.a.Component.processEvent(Component.java:6054)
    j.a.Container.processEvent(Container.java:2041)
    j.a.Component.dispatchEventImpl(Component.java:4652)
    j.a.Container.dispatchEventImpl(Container.java:2099)
    j.a.Component.dispatchEvent(Component.java:4482)
    j.a.LightweightDispatcher.retargetMouseEvent(Container.java:4577)
    j.a.LightweightDispatcher.processMouseEvent(Container.java:4238)
    j.a.LightweightDispatcher.dispatchEvent(Container.java:4168)
    j.a.Container.dispatchEventImpl(Container.java:2085)
    j.a.Window.dispatchEventImpl(Window.java:2478)
    j.a.Component.dispatchEvent(Component.java:4482)
    j.a.EventQueue.dispatchEventImpl(EventQueue.java:644)
    j.a.EventQueue.access$000(EventQueue.java:85)
    j.a.EventQueue$1.run(EventQueue.java:603)
    j.a.EventQueue$1.run(EventQueue.java:601)
    j.security.AccessController.doPrivileged(Native Method)
    j.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
    j.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:98)
    j.a.EventQueue$2.run(EventQueue.java:617)
    j.a.EventQueue$2.run(EventQueue.java:615)
    j.security.AccessController.doPrivileged(Native Method)
    j.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
    j.a.EventQueue.dispatchEvent(EventQueue.java:614)
    o.javatools.internal.ui.EventQueueWrapper._dispatchEvent(EventQueueWrapper.java:169)
    o.javatools.internal.ui.EventQueueWrapper.dispatchEvent(EventQueueWrapper.java:151)
    j.a.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
    j.a.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
    j.a.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
    j.a.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
    j.a.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
    j.a.EventDispatchThread.run(EventDispatchThread.java:122)
    Regards,
    Bruno

  • SQL 2012 R2 - SSRS with the Report Server Web Service URL, can't access

    Hello:
    I am installing Dynamics CRM 2013.  When I am on RS Configuration manager; I am running into the SSRS (SQL 2012 on Server 2012)SQL issue, can't access the
    http://servername/:80/ReportsServer or
    http://servername/:Reports web pages
    The database server has SSRS native mode installed, it is using a domain account for the service credentials.  This account also has permission to log on a service in the GPO
    Account is a domain admin and is a local administrator
    SQL server is 2012 R2 on Windows Server 2012.  User base is less than 60 people and they have SharePoint 13 on the same SQL server.  Server more than enough resources.
    Any assistance would be appreciated.
    Thanks..Dan

    Hi DCas1,
    According to your description, you could not access
    http://servername/:80/ReportsServer or http://servername/:Reports web pages from Reporting Services configuration manager, SSRS in configured in native mode and the account you used is a local administrator.
    In Reporting Services, URLs are used to access the Report Server Web service and Report Manager. Before we can use either application, we need to configure at least one URL each for the Web service and Report Manager. If we are using the Reporting Services
    Configuration tool to create or modify the URLs, we can accept the default values for a URL or specify custom values. When we create a report server URL, we must specify the following parts: Host name, port and Virtual directory. In order to improve the efficiency
    of troubleshooting, I need to ask several questions:
    Since the default URL is http://<computername>/reportserver, did you type the URLs manually? or the URLs configured in Reporting Services configuration manager are
    http://servername/:80/ReportServer and
    http://servername/:Reports?
    Could you provide detailed information of error log(default location: %programfiles%\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\LogFiles)?
    For more information about Configuring a URL, please refer to the following documents:
    http://msdn.microsoft.com/en-us/library/ms159261(v=sql.110).aspx
    http://msdn.microsoft.com/en-us/library/bb630447(v=sql.110).aspx
    If you have any more questions, please feel free to ask.
    Thanks,
    Wendy Fu

  • Queries regarding creating Web Services in Oracle EBS 11i[Workaround found]

    Hi,
    We have an E-Business Suite 11i installation(11.5.10.2). In our implementation we are using some of the public APIs to insert & update data in EBS tables. Earlier this was done by calling the required PL/SQL procedures through dblinks.
    Now, we need to do the same by using Web Services. That is we need a Web Service which can be invoked from a different application(SAP) and the Web Service in turn will call the APIs.
    I am new to Web Services/SOA and as far as I could understand from reading the documentation, we need the following:
    1. Install Oracle 10g Application Server with BPEL Process Manager ONLY(Oracle AS Adapter will be installed as part of BPEL PM. The Oracle AS Adapter will connect 10gAS to EBS)
    2. JDeveloper to create and deploy the BPEL process.
    I have a few questions here:
    1. Are the above two points the only prerequisites for what I want to achieve? Do I need to install anything else?
    2. How do I expose the created Web Service? I mean how will the 3rd party application invoke this Web Service?
    Answers and/or links to helpful documents awaited.
    Regards,
    -Sujoy
    Found an alternate and more cost-effective solution. Turns out that the SAP PI/XI engine can use JDBC to connect to the Oracle DB. SAP PI/XI will host the Web Service and will internally access the API through a JDBC connection.
    Edited by: Sujoy on Feb 3, 2011 7:41 PM
    Edited by: Sujoy on May 16, 2012 6:49 PM

    Hi Helios,
    I had checked the note that you are referring to before posting here. It did provide me with a start but otherwise it wasn't a great help (also some of the links are broken) . Since I am quite new to this...I am not sure whether I am proceeding in the right direction. An example/tutorial is what would be pretty useful.
    Thanks anyway!
    -Regards,
    Sujoy

  • Error when creating web service client in netbeans

    i tried to create a web service client from a wsdl and an error pops up:
    web service client can not be created by jaxws:wsimport utility.
    reason: com.sun.tools.xjc.api.schemacompiler.resetschema()v
    There might be a problem during java artifacts creation: for example a name conflict in generated classes.
    To detect the problem see also the error messages in output window.
    You may be able to fix the problem in WSDL Customization dialog
    (Edit Web Service Attributes action)
    or by manual editing of the local wsdl or schema files, using the JAXB customization
    (local wsdl and schema files are located in xml-resources directory).
    end of error message
    I am using netbeans 6.0 RC 2 and the bundled tomcat 6.0.13. Please help me.

    Hi Yatan
    The error is mostly there may be some Duplicate variable/schema element decalared in the wsdl or the xsd referred in the wsdl. Like in WSDL for any Operations, most of the times, we use input and outputs as complex xsd element. We declare these xsd in the same file or in another file and import that in the .wsdl file. So check or validate your XSD file for any Duplicates.
    In JDeveloper itself, I think, you can open XSD or WSDL and validate it from right click menu options like that.
    Thanks
    Ravi Jegga

Maybe you are looking for