Accessing wsdl to build a web svcs client app

We are users of WebLogic 8.1 but have hit an embarrassing impasse. We were demonstrating
how good it was using web services by deploying a service and using each of the
leading market tools to build a client app dynamically by just pointing the tool
at the published wsdl doc.
We hit a brick wall trying to do this with WLW.
For example in 3 mins in both JBuilderX & WebSphereAD5.1 we could tell the tool
we wanted to build a Web Service THEN WE SELECT 'CLIENT', provide a URL to where
the *.wsdl for the service is, then generate the code and test the functions published.
Three experts at work (self included) just can't figure out how to even get started
when attempting this with WLW. The help in WLW is as below ...
Creating a Web Service Control from a WSDL File
This procedure describes how to create a Web Service control if you have a WSDL
file for the target web service.
Ensure that the WSDL file for the web service is in your project.
Browse to the WSDL file in the Application pane.
Right-click on the WSDL file in the Application pane and select Generate JCX.
None of us could achieve this.
Any pointers to if this (dynamic build by pointing to wsdl URL) can be done at
all will be much appreciated. If not we know which tools to adopt.
Cheers
Doug Marker

Not a problem, I hope you have success with it. There's nothing like
popping up workshop and dropping in a control to talk with a web service in
like two minutes flat, I've found that has a nice profound affect when doing
demos. I also personally try to find a web service written in dot net or
perl or something totally opposite of J2EE which shows not only speed and
ease of creation but complete interoperability as well :)
"Doug Marker" <[email protected]> wrote in message
news:[email protected]...
>
Ryan,
Many thanks for your post. Will be trying this today. I have sommitted todo
a live demo within a couple of weeks & want to be 100% sure that myself &other
demonstrators can show how easy this process is.
As a demo, it sure gets peoples attention.
Cheers
Doug Marker
"ryan upton" <ryanjupton at learningvoyage dot com> wrote:
Doug,
You're thinking is correct in that it should be easy to do this in
Workshop
and in fact it is. Grab a WSDL file from somewhere like xmethods.com
if you
don't have an internal repository containing your own services. I assume
you want to incorporate the service into a page flow? Open the .jpf,
under
data palette->controls->add select web service. In the wizard that pops
up
select a reference variable name in step one. In step two decidewhether
you want to use an existing .jcx or create a new one (it sounds like
you're
going to want to create a new one) In step three enter the uri for the
WSDL, click create and you're almost done. The only thing left is to
call
the methods of the web service and incorporate the results somewhere
in you
control or presentation. One cool thing that Workshop does is to provide
the ability to automagically create a pageflow from the .jcx control,
simply
right click the control you've created, select generate pageflow and
follow
the wizard. Of course this is good for demos and you'll probably want
to
tweak it for real development work :)
~RU
"Doug Marker" <[email protected]> wrote in message
news:[email protected]...
We are users of WebLogic 8.1 but have hit an embarrassing impasse.We
were demonstrating
how good it was using web services by deploying a service and usingeach
of the
leading market tools to build a client app dynamically by just pointingthe tool
at the published wsdl doc.
We hit a brick wall trying to do this with WLW.
For example in 3 mins in both JBuilderX & WebSphereAD5.1 we could tellthe
tool
we wanted to build a Web Service THEN WE SELECT 'CLIENT', provide aURL to
where
the *.wsdl for the service is, then generate the code and test thefunctions published.
Three experts at work (self included) just can't figure out how toeven
get started
when attempting this with WLW. The help in WLW is as below ...
Creating a Web Service Control from a WSDL File
This procedure describes how to create a Web Service control if youhave a
WSDL
file for the target web service.
Ensure that the WSDL file for the web service is in your project.
Browse to the WSDL file in the Application pane.
Right-click on the WSDL file in the Application pane and select
Generate
JCX.
None of us could achieve this.
Any pointers to if this (dynamic build by pointing to wsdl URL) canbe
done at
all will be much appreciated. If not we know which tools to adopt.
Cheers
Doug Marker

Similar Messages

  • Accessing Local Interface EJB from Web Container Oracle App Server 9.0.4

    Hi,
    I am developing a struts based small application, which calls a EJB which uses Local Interface from Struts ActionClass.
    I am getting NameNotFoundException. The exact exception is s mentioned below.
    05/03/29 16:15:49 javax.naming.NameNotFoundException: LoginRSL not found
    The deployment descriptors are as mentioned below.
    =============
    ejb-jar.xml
    <?xml version = '1.0' encoding = 'windows-1252'?>
    <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
    <ejb-jar>
    <enterprise-beans>
    <session>
    <description>Session Bean ( Stateless )</description>
    <display-name>LoginRSL</display-name>
    <ejb-name>LoginRSL</ejb-name>
    <local-home>loginApp.model.LoginRHome</local-home>
    <local>loginApp.model.LoginL</local>
    <ejb-class>loginApp.model.LoginRSL</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    </session>
    </enterprise-beans>
    <relationships/>
    <assembly-descriptor>
    <container-transaction>
    <method>
    <ejb-name>LoginRSL</ejb-name>
    <method-name>*</method-name>
    </method>
    <trans-attribute>Required</trans-attribute>
    </container-transaction>
    </assembly-descriptor>
    </ejb-jar>
    orion-ejb-jar.xml
    <?xml version = '1.0' encoding = 'windows-1252'?>
    <!DOCTYPE orion-ejb-jar PUBLIC "-//Evermind//DTD Enterprise JavaBeans 1.1 runtime//EN" "http://xmlns.oracle.com/ias/dtds/orion-ejb-jar.dtd">
    <orion-ejb-jar>
    <enterprise-beans>
    <session-deployment name="LoginRSL"/>
    </enterprise-beans>
    </orion-ejb-jar>
    I also tried adding following code to web.xml
    web.xml
    <ejb-local-ref>
    <ejb-ref-name>LoginRSL</ejb-ref-name>
    <ejb-ref-type>Session</ejb-ref-type>
    <local-home>LoginRHome</local-home>
    <local>LoginL</local>
    <ejb-link>LoginRSL</ejb-link>
    </ejb-local-ref>
    It is quite evident that it is not able to lookup the JNDI name.
    Can someone throw light on this? If someone has working sample of this, can you mail it to [email protected]?

    Nipun,
    WebLogic and OC4J are not the same thing. That's like saying Oracle and SQL Server are the same thing -- or C++ and Java are the same thing.
    I recall a posting to a forum (don't remember if it was this one), where the poster was complaining that some feature of the application server he had previously used, was not supported by OC4J. Turned out that the feature he was referring to, contradicted the J2EE specification -- which is why it wasn't available in OC4J. In other words, he didn't like the fact that OC4J was more compliant with the J2EE specification than his "other" application server. Go figure!
    So, if you haven't already done so, I suggest you verify that this feature of WebLogic is something that complies with the J2EE specifications -- before expecting OC4J to support the same feature.
    And if it's not clear, from the specifications, then every vendor is free to implement this feature (or not).
    So if it turns out that WebLogic is a more appropriate application server for you -- then why not just stick with it (and forget the others)?
    Good Luck,
    Avi.

  • Problems with Web services client

    Hi all,
    I'm trying to build a Web Service Client with netbeans 6.5. I add the Web Service Refefrences by clicking right on my project/new/Web Service Client and giving it the url of the wsdl or the wsdl file itself. All work well, I use the web service without problems but then, after several successful try I don't know why, I get this kind of exception:
    Exception in thread "main" javax.xml.ws.WebServiceException: class net.stuff.webservice.webservices.Upload do not have a property of the name {www.stuff.net/WebService/WebServices}uploadReq
    I precise I don't modify the code that call the web service.
    To make it work again, I have to Clean & Build several time the project and/or Refresh tjh WebClient Reference, gain, without modifying the code.
    The Web Service producer runs on .net and doesn't seems to "move".
    Have you ever see this issue?
    Maybe this could help: I'm using JDK 5 with JAXB-WB
    Thanks

    Hello Eric:
    I have the same problem... but he Clean & Build thing didn't work :(...
    To make it work I call the Web Service from a java application and include the java application's jar in the libraries of the java web application.

  • SAAJ (Web Service Client) and Integrated windows Authentication

    Hello
    I have build a web service client using SAAJ, the Web services is deployed on MS IIS. Every thing seems to work fine, The problem appears when I apply directory security on the Web Service Directory. When I apply Basic authentication SAAJ manages to send the user name and password and it goes fine, but when I apply Integrated Windows Authentication, I always get a response Access is Denied.
    I know we can authenticate the user credentials from NTLM from JAAS but here I am using a web services client.
    My Question is How can we pass the user credentials through a web service client to the IIS when the directory security is Windows Integrated Authentication?
    Any work around or the solution will be appreciated.
    Thanks :-)
    Syed Saulat

    Hi Gilles,
    Thank you very much for your answer. Actually, I think the problem is a little bit different. The kerberos server is not delivering a "grant" ticket to the client for the service provided by the VIP, because the CSS didn't register to the Active Directory, as a normal W2K web server would. The first thing the client does when he wants to access a web server behind the CSS is to ask the kerberos server for a "gtanting" ticket for that service. So the problem arise before the client sends any packet to the CSS (therefore I think it is more a Microsoft problem rather than a CSS problem).
    But for sure, other people have this environment I suppose...
    What is your opinion on this ?
    Yves

  • HTTP Analyzer help for web service client in 11g

    I am using jDev 11.1.1.3.0 to build a web service client (proxy) to a potential vendor's web service. I've used the Http Analyzer before but I'm having trouble configuring it for a WS proxy. I just want to see the SOAP stream between my client and the web service. I used the Web Service Proxy wizard to create the Java code, but the web service provider has kept some of the contract in the WSDL private so that I had to manually generate the meat and potatoes of the Java code. I need to be able to see the SOAP my Java code is sending.
    I have tried to configure the Http Analyzer to listen on it's own localhost and port with a forward rule to forward the request to the real WS, but I cannot figure out how to get the client to send it's requests to localhost instead of the actual WS.
    Actually, I did figure it out, but then the request fails as it apparently tries to connect to the real WSDL before actually sending the request and cannot find a WSDL at the localhost URL. Here's the error:
    Exception in thread "main" javax.xml.ws.WebServiceException: {http://localhost:8099}CatalogRequest is not a valid service. Valid services are: {http://[actual URL here]}CatalogRequest
         at com.sun.xml.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:249)
    I have also tried to configure the Http Analyzer to somehow 'sniff' the actual URL by listening on the actual URL and port, but either I cannot get the Analyzer to see the request or it fails because the Analyzer is using the same port the request is trying to use.
    Can someone explain how to configure the Http Analyzer to see the SOAP stream for a Web Client Proxy?

    Hi, I'm just using the default setup for HTTP Analyzer and having no problem using it.
    Just make sure to run the HTTP Analyzer first before running or starting your app server (Integrated weblogic Server).

  • Problem creating J2ME web service client

    Hi,
    I am using netbeans (5 and 5.5 beta 2). I have created a web service which works fine. I also created a regular web service client as a standalone application which also works fine and connects to my web service with no problem.
    BUT, when I want to create a J2ME web service client (under a J2ME application) I have to locate my WSDL file. but the wizard shows me the error "WSDL file does not contain port information".
    By looking at the WSDL file I can see that port is created - or maybe I'm wrong.
    piece from WSDL file:
    <service name="myServiceName">
    <port name="myServiceSPort" binding="tns:TranslatorWSPortBinding">
    <soap:address location="myURLLocation"/>
    </port>
    </service>
    Please note that I have replaced the actual values in above piece
    I tried to use wsgen manually but it didn't help.
    Can anyone help me in generating the correct WSDL format as J2ME web service client expects?
    Thanks a lot,
    S.

    well stubs are generated separately using WTK 2.5 stub generator but the problem is with the WSDL at this point.
    S.

  • How to prevent downloading wsdl in weblogic web service client

    Hi,
    I get a problem regarding weblogic web service client. My working environment:
    weblogic server 8.1
    Windows XP SP2
    JDK 1.4
    I use the weblogic tool to generate the client jar file from the wsdl file.
         <target name="generate-client">
              <clientgen wsdl="ACCESS.wsdl"
                   packageName="xxxxxx.client"
                   clientJar="${client}/${AccessClient_jar_file}"
                   keepGenerated="true"
                   saveWSDL="true"
              />
              <javac srcdir="${source}"
              destdir="${client}"
              includes="**/AccessClient.java">
              <classpath>
              <pathelement path="${client}/${AccessClient_jar_file}"/>
              </classpath>
              </javac>
         </target>
    After that, I create a client java file to invoke the service deploy in the server.
    public static void main(String[] argv)
    throws Exception
         int transactionId = 100;
         int id = 1000;
    // Setup the global JAXM message factory
    System.setProperty("javax.xml.soap.MessageFactory", "weblogic.webservice.core.soap.MessageFactoryImpl");
    // Setup the global JAX-RPC service factory
    System.setProperty( "javax.xml.rpc.ServiceFactory", "weblogic.webservice.core.rpc.ServiceFactoryImpl");
    AccessServicePorts ws = new AccessServicePorts_Impl(argv[0]);
    AccessService port = ws.getAccessService();
    // Resource - create
    Resource resource = new Resource();
    resource.setRES_CD("Create ResCo");
    resource.setCODE_CODE("code_cod");
    resource.setRES_TYPE("Resource typ");
    resource.setCOMMON_FIELD(common);
    AccessDefaultResult resultItems = port.createResource(resource);
    System.out.println("createResource : " + resultItems);
    I find that this web service client always issue 2 http requests to invoke an web service method deployed in server.
    1st http reqeust:
    GET /AccessEpol/EpolServiceSoap?WSDL HTTP/1.1
    User-Agent: Java/1.4.2_08
    Host: 127.0.0.1:8001
    Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
    Connection: keep-alive
    the return result is the wsdl downloaded from the server.
    2nd http request is the real web service request.
    The question is how could I eliminate the 1st http request because it's really unnecessary. I use other web service client like Axis 1.x, Axis client never has the http request to download the wsdl from the server.
    I read through weblogic web service document. It do mentions that put saveWSDL="true" in the clientgen ant task. the default value for saveWSDL is true already. I did try saveWSDL="false" also. None of them can eliminate the 1st http request.
    appreciate for any answer my question?

    Hi David,
    thanks for the reply.
    More or less I agree some points you mentioned above.
    I did use Axis 1.x to test the inter-operability. The web service was developed in Weblogic 8.1 and is a part of an existing web application. It will be merged to existing application deployed in weblogic 8.1.
    I also program the web service client to test the web service.
    The implementation of the server and client will be handed over the project team and training for supporting or continuous development have to be conducted by me. So I don't like to use two types of technologies which will make thing complex.
    I found this issue when I tried to protected the web service endpoint, eg http://localhost:7001/epol/service, using the web application Basic mechanism. The wsdl URL http://localhost:7001/epol/service?WSDL is also protected in this case. Unfortunately the username/password pair is not sent to the server when the weblogic client download the WSDL from the server. In this case, the client failed and throw exception.

  • Web Service Client Generation on 7.10 SP3 - No WSDL URL is specified....

    We have a mysterious problem here.
    In out ABAP system we had a WebService created. With "New - Web Service Client" we created a web service client on the java side for that one and we were able to invoke it.
    We had to recreate this Web service due to wrong naming conventions. And now the problem starts.
    In the Main service class we had before something generated by NWDS:
    private static java.net.URL SERVICES_SERVICE_WSDL_LOCATION = null;
    static {
        java.net.URL url = null;
        try {
              java.net.URL tmpUrl = Thread.currentThread().getContextClassLoader().getResource("wsdl/com/sap/document/sap/soap/functions/mc_style/sap/bc/srt/wsdl/bndg_001279D063121DECA58AC5F7200DC55D/wsdl11/allinone/ws_policy/document/rootwsdl_SERVICES.wsdl");
              url = new java.net.URL(tmpUrl.getProtocol(), tmpUrl.getHost(), tmpUrl.getPort(), tmpUrl.getFile());
        } catch (java.net.MalformedURLException e) {
          e.printStackTrace();
        SERVICES_SERVICE_WSDL_LOCATION = url;
    After the new creation with the new Web Service this static initializer is gone an we see:
    private final static java.net.URL SERVICE_WSDL_LOCATION = null;
    This code is ridiculous, to make something static final and set it to Null. And as expected at runtime it results in WebServioceException telling us:
    No WSDL URL is specified for service [class com.sap.document.sap.soap.functions.mc_style.Service] on service creation.
    Anyone knows what is going wrong here??
    Best regards,
    Frank

    Same problem here.
    From Netweaver dev studio, I'm generating a deployable proxy for a Session Bean that is supposed to access a webservice but I keep getting the exception:
    "Caused by: javax.xml.ws.WebServiceException: No WSDL URL is specified for service [class eu.socrades.sap.ServiceMonitorBeanTESTService] on service creation.
    at com.sap.engine.services.webservices.espbase.client.jaxws.core.SAPServiceDelegate.<init>(SAPServiceDelegate.java:108)
    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 eu.socrades.sap.ServiceMonitorBeanTESTService.<init>(ServiceMonitorBeanTESTService.java:14)"
    I'm injecting the reference to the service with:
    @WebServiceRef(wsdlLocation = "rootwsdl_ServiceMonitorBeanTESTService.wsdl")
    private ServiceMonitorBeanTESTService service;
    I tried changing the location to a URL (where the wsdl can be downloaded from) or to "META-INF/wsdl/eu/socrades/sap/rootwsdl_ServiceMonitorBeanTESTService/rootwsdl_ServiceMonitorBeanTESTService.wsdl" but that did not help.
    Any clue?
    Thanks a lot,
    Dom

  • Client access to Server application using Web Server

    Hi there.
    I'm working on a LabView application that controls several devices, read data from them and show their measures on the front panel, using different graphs and indicators. All the items defined in the project and the collected data is stored in a SQL Server database. The application includes another module ("Reports Module"), which consists of several windows (VIs Front Panels) where queries to the SQL Server database are made and displays lists of the selected data. This module can be accessed by the main menu of the software.
    Our intention is to deploy the application in a PC placed in the working site (server), and access the registered data using remote PCs (clients). The idea is to access the "Reports Module" via web.
    For this purpose, we are using the Web Server feature of LabView. The main VI of the "Reports Module" is defined with "Reentrant execution" (so that it can be accessed by multiple clients), and we create an HTML document of it using the Web Publishing Tool. We make an executable of the application (using the Application Builder) and, to create a Web Server in the deploy machine, we make use of what is stated in the following link:
    http://digital.ni.com/public.nsf/allkb/7F95D43D3F50FCAC8625710E000068E1?OpenDocument
    The problem we find is that when the main application is running in the server computer, if we access the "Reports Module" and begin selecting the queries options through its different windows, the same windows are opened in the server computer screen, so that it's difficult for an operator to control the main application on the server side if someone its accessing simultaneously through a remote client.
    Is there a way to do prevent this behaviour?
    Could you suggest me a different method to accomplish what we intend to do?
    Thanks in advance.
    Regards,
    Francisco

    I played with remote front panels a really long time ago snd it was nothing but problems. I hear they have improved but what I did was abandon them for an extJS application to do what you are doing. It is now called Sencha. Sorry but I can't help with a pure LabVIEW solution.
    =====================
    LabVIEW 2012

  • J2EE web service client using WSDL

    Hi,
    We are required to develop client program in Java for the
    web services developed in SAP XI 2.0.
    We will be getting the WSDL files for corresponding web
    services.
    We have tried doing it with J2EE JAX-RPC...
    We studied the sample program of HelloService...
    While calling the service from command line..it takes .jar file..
    But we have to make use of only WSDL....
    Is there any alternative way?? or jax-rpc is the best one???
    wat will be the best way to do so??

    Hi,
    thanx for your reply!
    We have written web services in SAP XI 2.0....
    we has generated corresponding WSDL..which is little
    incomplete..but we can modify and update it according to
    requirements...so we have complete WSDL....for corresponding web
    services.
    My colleagues have developed web dynpro application which
    makes use of those services. Now for demostration purpsoe we need
    to write java/jsp which will access those services...
    can u help???

  • Not able to access the Oracle I/PM web client.

    I have started the Administration server and the Oracle I/PM Managed Server. Now I'm trying to access the Oracle I/PM web client at this URL: http://hostname:16000/imaging. But when I hit this URL, the following error comes up:
    Error 404--Not Found
    From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
    10.4.5 404 Not Found
    The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
    If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
    I'm also posting a part of the logs from the IPM_server log file:
    ####<May 20, 2013 10:32:52 AM IST> <Notice> <WebLogicServer> <01hw311161> <IPM_server1> <main> <<WLS Kernel>> <> <> <1369026172860> <BEA-000360> <Server started in RUNNING mode>
    ####<May 20, 2013 10:32:53 AM IST> <Info> <J2EE> <01hw311161> <IPM_server1> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1369026173516> <BEA-160151> <Registered library Extension-Name: bea_wls_async_response (JAR).>
    ####<May 20, 2013 10:32:53 AM IST> <Info> <WebService> <01hw311161> <IPM_server1> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1369026173641> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceHttps for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
    ####<May 20, 2013 10:32:53 AM IST> <Info> <WebService> <01hw311161> <IPM_server1> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1369026173735> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceJms for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
    ####<May 20, 2013 10:32:53 AM IST> <Info> <WebService> <01hw311161> <IPM_server1> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1369026173735> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseService for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
    ####<May 20, 2013 10:32:53 AM IST> <Info> <WebService> <01hw311161> <IPM_server1> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1369026173750> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceSoap12Jms for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
    ####<May 20, 2013 10:32:53 AM IST> <Info> <WebService> <01hw311161> <IPM_server1> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1369026173766> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceSoap12 for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
    ####<May 20, 2013 10:32:53 AM IST> <Info> <WebService> <01hw311161> <IPM_server1> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1369026173782> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceSoap12Https for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
    ####<May 20, 2013 10:33:51 AM IST> <Info> <Health> <01hw311161> <IPM_server1> <weblogic.GCMonitor> <<anonymous>> <> <> <1369026231604> <BEA-310002> <85% of the total memory in the server is free>
    What configuration am I missing?
    Thanks in advance
    Pradeep

    Hi Srinath,
    I have checked that as well, it is showing the IPM_server in running mode.
    Also it doesn't show any deployment failure in the command line. Here is what it shows:
    <May 20, 2013 10:32:51 AM IST> <Notice> <WebLogicServer> <BEA-000332> <Started W
    ebLogic Managed Server "IPM_server1" for domain "base_domain123" running in Deve
    lopment Mode>
    <May 20, 2013 10:32:52 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server st
    ate changed to RUNNING>
    <May 20, 2013 10:32:52 AM IST> <Notice> <WebLogicServer> <BEA-000360> <Server st
    arted in RUNNING mode>
    I feel there is some issue as this log is suggesting:
    ####<May 20, 2013 10:32:53 AM IST> <Info> <WebService> <01hw311161> <IPM_server1> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1369026173782> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceSoap12Https for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
    But I don't know how to resolve it.
    Thanks
    Pradeep

  • Different display on client report builder and web reports

    Hi all, I have build a report in report 6i version Report Builder 6.0.8.13.1.And I set the page to 8.5*11 ,and it runs well in the client ,but when I put it on the UNIX SERVER,and run it from web URL,It displayed different from the client report builder.The web report is "smaller" than the client report ,but the font size is as same as the client .
    My HPUX is 11x,and display the Chinese report .
    Any body know why ?give me some advice ,thank u very much.

    Hi
    If you had built the report definition on Windows and then moved this to Unix server, you may find different fonts in use. This is becuase your Unix setup does not have the same fonts install. At design time, You need to use fonts which are available on Unix also. The same fonts shaould also be installed for printer in Unix i.e. the AFM/PFM font files should be kept under $ORACLE_HOME/guicommonX/tkXX/admin/AFM or PFM directory. This would give you the same output and would lessen the porting affect.
    Thanks
    Rohit

  • Error creating a web service client from th WSDL document (soamanager)

    Hello everyone,
    we have generate with the wizard a web-service using the function module BAPI_CONTROL_RECIPE_GET_LIST. Then we have generated with SOAMANAGER the end point. As test, we have used a web-service explorer of Eclispe and we can retrieve without problems the data.
    Then we wanted to generate the web-servcie client with Eclipse Galileo (3.5.0) wiith the server GlassFish v2.1 Java EE 5 we first installed the WSIT jars, in order to support WS-RM protocol
    We have started the generation based on the document obtainend within the soamanager under the "Open WSDL document for selected binding" link.
    We have tried it several times and we always got the following error is:
    IWAB0399E Error in generating Java from WSDL: WSDLException (at /wsdl:definitions/wsdl:portType/wsp:Policy):
    faultCode=INVALID_WSDL: Encountered unexpected element 'Policy'.: <br>
        WSDLException (at /wsdl:definitions/wsdl:portType/wsp:Policy): faultCode=INVALID_WSDL: Encountered unexpected element 'Policy'.:
    at com.ibm.wsdl.util.xml.DOMUtils.throwWSDLException(Unknown Source)
    at com.ibm.wsdl.xml.WSDLReaderImpl.parsePortType(Unknown Source)
    at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown Source)
    at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
    at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
    at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
    at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:516)
    at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:495)
    at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361)
    at java.lang.Thread.run(Unknown Source)
    Do you know if we took the right document in order to generate the web-service client? Do we need to have some specifics settings in the configurations of th endpoint? (provider security, transport settings, etc...?)
    If needed, or if someone would be nice enough to try to generate it on its side, I can post here the whole wsdl document, but due to its length, I first wait your comments.
    Thanks a lot in advance for your feed-back
    best regards
    Pierre-André
    addtions:
    maybe this should have been better posted within the forum Service-Oriented Architecture than standards?
    I forgot to mention the following threads, which seems to me to be somehow in this direction. But I do not get really how I could use them, or how is is releated.
    Edited by: Pierre-andre Jacquod on Sep 23, 2009 4:02 PM

    Hi,
    I am facing the same issue while generating the client java class from IBM RAD 6.0.
    Here is the error I am getting.
    WSDLException (at /wsdl:definitions/wsdl:portType/wsp:Policy): faultCode=INVALID_WSDL: Encountered unexpected element 'Policy'.:
         [java] at com.ibm.wsdl.util.xml.DOMUtils.throwWSDLException(Unknown Source)
         [java] at com.ibm.wsdl.xml.WSDLReaderImpl.parsePortType(Unknown Source)
         [java] at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown Source)
         [java] at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
         [java] at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
         [java] at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
         [java] at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:516)
         [java] at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:495)
         [java] at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361)
         [java] at java.lang.Thread.run(Thread.java:571)
    Please guide me to resolve this issue.
    Thanks & Regards,
    Vijay

  • How to create Web Service Client from wsdl with digital signature?

    Please, help me to create Web Service Client from wsdl with digital signature. I know create Web Service client from wsdl file and I know how to add digital signature to XML with jwsdp, but I don't know how to do it together.
    Thanks.

    I'm handling security wit JAX-WS handler. So I insert "manually" ws-security tag and I encrypt (and sign) message parts.
    On client side, all works fine, but on server side I obtain:
    ---Server Inbound SOAP message---|#]
    Decrypting message and rebuilding Valuees... |#]
    Starting decrypt|#]
    . dectypted.!
    --found following string: <ns1:addiziona><num1>80</num1><num2>22222</num2></ns1:addiziona>|#]
    ...MESSAGE Restored.|#]
    <?xml version="1.0" ?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:ns1="http://calculator.me.org/" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"><soapenv:Body><ns1:addiziona><num1>80</num1><num2>22222</num2></ns1:addiziona></soapenv:Body></soapenv:Envelope>|#]
    Error in decoding SOAP Message
    Error in decoding SOAP Message
            at com.sun.xml.ws.encoding.soap.server.SOAPXMLDecoder.toInternalMessage(SOAPXMLDecoder.java:89)
            at com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher.toMessageInfo(SOAPMessageDispatcher.java:187)
            at com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher$SoapInvoker.invoke(SOAPMessageDispatcher.java:571)
            at com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher.receive(SOAPMessageDispatcher.java:145)
            at com.sun.xml.ws.server.Tie.handle(Tie.java:88)
            at com.sun.enterprise.webservice.Ejb3MessageDispatcher.handlePost(Ejb3MessageDispatcher.java:160)
            at com.sun.enterprise.webservice.Ejb3MessageDispatcher.invoke(Ejb3MessageDispatcher.java:89)
            at com.sun.enterprise.webservice.EjbWebServiceServlet.dispatchToEjbEndpoint(EjbWebServiceServlet.java:178)
            at com.sun.enterprise.webservice.EjbWebServiceServlet.service(EjbWebServiceServlet.java:109)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
            at com.sun.enterprise.web.AdHocContextValve.invoke(AdHocContextValve.java:100)
            at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
            at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
            at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:71)
            at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:182)
            at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
            at com.sun.enterprise.web.VirtualServerPipeline.invoke(VirtualServerPipeline.java:120)
            at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
            at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137)
            at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
            at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
            at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
            at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:231)
            at com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:667)
            at com.sun.enterprise.web.connector.grizzly.ProcessorTask.processNonBlocked(ProcessorTask.java:574)
            at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:844)
            at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:287)
            at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:212)
            at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252)
            at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:75)
    Caused by: javax.xml.ws.soap.SOAPFaultException: Cannot find the dispatch method
            at com.sun.xml.ws.encoding.soap.SOAPDecoder.raiseFault(SOAPDecoder.java:674)
            at com.sun.xml.ws.encoding.soap.server.SOAPXMLDecoder.decodeDispatchMethod(SOAPXMLDecoder.java:152)
            at com.sun.xml.ws.encoding.soap.SOAPDecoder.decodeBodyContent(SOAPDecoder.java:337)
            at com.sun.xml.ws.encoding.soap.SOAPDecoder.decodeBody(SOAPDecoder.java:327)
            at com.sun.xml.ws.encoding.soap.SOAPDecoder.decodeEnvelope(SOAPDecoder.java:250)
            at com.sun.xml.ws.encoding.soap.server.SOAPXMLDecoder.toInternalMessage(SOAPXMLDecoder.java:81)
            ... 29 more
    |#]
    --->handleFault O_o<---|#]If you have any idea for solving my problem, then I can post my simple example :(
    Bye!

  • Problem using WSDL from SAP in IBM's RAD for generating web service client

    When importing a WSDL from the ABAP stack on a SAP 6.40 system into IBM's RAD tool for generating a web service client there are errors with the soap fault classes that get generated.  The WSDL declares the types for the faults with WebServiceName.RfcException and these have elements of name, text, and message.  When the tools see this in the WSDL they generate classes that extend the Java exeception class and this causes an error because the "message" name conflicts with the standard java exception message.  Has anyone else ran into this problem?  It seems like a basic problem many java tools for generating web service client proxies would have because the soap faults get turned into java exceptions.  This name conflict of the java exception with the WSDL fault definition means that code always needs to be adjusted and cannot simply use the classes that are generated from the WSDL.  Anyone run across this or a similar problem in the java environment using the SAP WSDL?
    Aaron

    Hi,
    Hello again .
    Have you tried your service using soapui ?
    You can use your WSDL as input .
    In order to eliminate eclipse problem try this service:(I just did)
    http://www.oorsprong.org/websamples.countryinfo/CountryInfoService.wso?WSDL
    Regards.
    package main;
    import java.io.FileInputStream;
    import java.rmi.RemoteException;
    import java.util.Properties;
    import org.oorsprong.www.websamples_countryinfo.CountryInfoServiceSoapType;
    import org.oorsprong.www.websamples_countryinfo.CountryInfoServiceSoapTypeProxy;
    import org.oorsprong.www.websamples_countryinfo.TCountryCodeAndName;
    public class Main {
    public static void main(String[] args) {
      try {
       final Properties properties = new Properties();
       properties.load(new FileInputStream("properties.ini"));
       System.getProperties().putAll(properties);
      } catch (final Exception exception) {
       exception.printStackTrace();
      new Main();
    public Main() {
      try {
       final CountryInfoServiceSoapType infoServiceSoapType = new CountryInfoServiceSoapTypeProxy();
       final TCountryCodeAndName[] tCountryCodeAndNames = infoServiceSoapType.listOfCountryNamesByName();
       for (final TCountryCodeAndName tCountryCodeAndName : tCountryCodeAndNames) {
        System.out.println(tCountryCodeAndName.getSName());
      } catch (final RemoteException exception) {
       exception.printStackTrace();

Maybe you are looking for