Web Services - General

I need to do a project about Web Services.
Could anyone tell me where to find, or just tell me:
1- What is a Web Service?
2- What a Web Service do?
3- Why I need one?
4- How can I build (a real SIMPLE) one? (in Java)
All I need is basic tutorials to explain it to my class.
Thanks.

Here are some links to get you started:
OTN Web Services Center - Learner's page
Web Services Overview
Regards,
-rh

Similar Messages

  • Web Services General Question

    Hi All,
    Does web services in Java mean to simply provide a SOAP container that wraps around an EJB (or even a web container)?
    If this is true, all of the work that's been done with the development of EJBs can be preserved, and other system will make calls to the SOAP container in order to get access to the web services provided.
    I'm trying to understand the big picture and slowly get into Web Services in Java.
    Thanks

    I don�t know if this answers your question, but I think that SOAP indeed can be used to expose existing EJB�s to non-Java-Systems.

  • (261936172) Q general Where are the Web Service source files?

    Q <general> Where are the source files for a Web Service created
    with WebLogic Workshop stored? How do I deploy the Web Service
    on a different WebLogic Server? Is there a way to bundle the
    Web Service project files manually to distribute them?
    Is there a way to configure the directory where Workshop stores
    the files?
    ANSWER: (by Adam Fitzgerald, [email protected]) The .jws files are stored
    in the project folder. This can be located on a local system, although by default
    they are in c:\bea\wlserver700b\sample\workshop\applications. The Web Service
    structure is understood by WLS 7.0 so by archiving the appropriate folder you
    can transfer the Web Service in its entirety from one deployment to another.

    Hi Dean,
    In SharePoint 2013 Designer, the help files are online. They provide tons of general information regarding SharePoint Designer 2013.  You can also find help files at:
    http://technet.microsoft.com/en-us/library/jj219638%28office.15%29.aspx .
    And find a great set of information on SPD 2013 and the new Workflow architecture here:
    http://msdn.microsoft.com/library/office/jj163986(v=office.15)
    More information, please refer to the link:
    http://blogs.msdn.com/b/sharepointdesigner/archive/2012/08/07/welcome-to-sharepoint-designer-2013-customer-preview.aspx
    I hope this helps.
    Thanks,
    Wendy
    Wendy Li
    TechNet Community Support

  • Q: General : When will you use Web Service as opposed to just Servlet and/or EJB?

    Hi,
    I don't know if this is an appropriate question to ask for this class as it's not
    workshop
    specific. I was wondering how will I decide when it is appropriate to use a web
    service as opposed to say servlet or an EJB for my application? What is a good
    rationale to use?
    Thanks,
    Sadhana

    Hi Adam,
    Thanks a lot for giving such a lucid explanation of my vague question!
    I understand now the difference between when to use EJBs/Servlets/Web Services.
    Thanks again!
    Sadhana
    "Adam FitzGerald" <[email protected]> wrote:
    >
    Hi Sadhana,
    Web service versus Servlet versus EJB. Which one to use? That is a very
    good question.
    EJBs should be the core desription and processing of your business rules.
    They generally
    have good performance, are easy to integrate into your security set up but
    they require
    access using the RMI-IIOP protocol. This means that generally EJBs are not
    accessible
    outside of your firewall and their clients have to be written in Java (other
    enterprise
    objects or applets or GUI applications).
    Servlets often form a web-based front end to EJBs. They also have good performance,
    integrate into security and only require HTTP access. This means they are
    accessible
    outside your firewall and any client with a HTTP or web API can call on
    them, however,
    there is no standard contract or rules for this type of interaction so you
    will need
    provide direct input into development of the client.
    Web services are also accessible via HTTP and so can be accessed from outside
    your
    firewall. In fact, Web services internally within Workshop and WebLogic
    actually
    operate by using servlets and EJBs but the main advantage is that the mechanism/contract
    for interacting with the web service is a well defined standard (WSDL) and
    can actually
    be registered or retreived dynamically (UDDI). Since web service standards
    are open,
    most popular programming languages already provide client APIs to interact
    with them
    thus freeing the web service developer from direct interaction with the
    client developer
    and letting the client be developed on any platform. The penalty for this
    openness
    is a small performance hit (XML translation) and a slowly maturing security
    model.
    So in summary, use EJBs for business operations that have Java clients within
    your
    enterprise, use servlets to provide web style access to your business operations
    (like web pages) and use web services to enable automated clients that can
    be written
    on any platform either inside or outside your enterprise (firewall). In
    fact, it
    is common to write the EJB first and then to expose some parts of it outside
    of your
    enterprise by writing a web service wrapper (maybe using the EJB controls
    that we
    saw in class).
    I hope this helps.
    Adam
    "Sadhana Jain" <[email protected]> wrote:
    Hi,
    I don't know if this is an appropriate question to ask for this class as
    it's not
    workshop
    specific. I was wondering how will I decide when it is appropriate to use
    a web
    service as opposed to say servlet or an EJB for my application? What is
    a good
    rationale to use?
    Thanks,
    Sadhana

  • (261936172) Q general Are there seperate logs for web services?

    Q<general> Are there seperate logs for web services?
    A<general> It does not appear that there are any separate logs for web services.
    There is knex.log file that records the errors that occur during deployment of
    your .jws files. There is also the standard server log that provides information
    about server status - you can write to this programmatically if you wish. There
    is also the access.log file which record all the HTTP requests so this might cover
    some of your web service requests that are transmitted over HTTP.

    Maybe the user has deniad Access to the Runbook, check in Runbook Designer.
    Seidl Michael | http://www.techguy.at |
    twitter.com/techguyat | facebook.com/techguyat

  • General queries related to implementing the web service

    Hi all,
    I am new to web services, so I would like to get some of the queries solved which I am facing as of now.
    - If in a function of web service, there are three parameters defined, in which one is input parameter while remaining others are output parameters, then from the client invoking that web service has to provide only the input parameter as an argument or all the three arguments should be provided?
    Please let me know.
    Thanks

    I really can't say about the input / output parameters. My guess is that you can't really have ByRef output variables, because the web method call is marshalled into XML and you only get a reply in XML based on the return type of the web method. What I'm trying to say is: only use the method's return value to receive output. Create complex Objects that can be mapped to XML to do that.
    The way to call the web service from java is to parse the WSDL document for the web service and see what kind of input messages the web service requires and what type of output messages it produces.
    As far as I know there are two ways to parse the WSDL.
    1) If you know the location of the WSDL during development you can use it as an input to tools like wsimport in order to create a Service Endpoint Interface.
    2) If you only know the WSDL location during runtime, you have to parse the document either by DOM/SAX etc either by using libraries such as wsdl4j
    http://sourceforge.net/projects/wsdl4j
    I hope I've helped.

  • How to consume a TIBCO web-service in SAP PI

    Dear All,
    I have a scenario to consume a webservice provided by TIBCO.
    A end to end scenario is configured in TIBCO (ws-TIBCO-ws). The WSDL file ganerated from TIBCO system is provided to me to consume in SAP PI.
    TIBCO generated WSDL will be in a format (Type, Service, Binding, Port, Message). For SAP system to consume a webservice, WSDL format should be (Type, Message, Binding, Port, Service). So i changed the format and imported into External Definitions in ESR and configured the SYNCHRONOUS end-to-end scenario(saop-PI-soap) in SAP PI. I have generated a wsdl from sender agreement and tested it using SOUP UI.
    In SOAP UI response it throws following error.
    <!--see the documentation-->
    <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
       <SOAP:Body>
          <SOAP:Fault>
             <faultcode>SOAP:Server</faultcode>
             <faultstring>Server Error</faultstring>
             <detail>
                <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
                   <context>XIAdapter</context>
                   <code>ADAPTER.JAVA_EXCEPTION</code>
                   <text>com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIAdapterFramework:GENERAL:com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: Response message contains an errorXIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server did not recognize the value of HTTP Header SOAPAction: .
      at com.sap.aii.adapter.soap.web.SOAPHandler.processSOAPtoXMB(SOAPHandler.java:746)
      at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:505)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
      at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:202)
      at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:103)
      at com.sap.engine.services.servlets_jsp.server.servlet.AuthenticationFilter.doFilter(AuthenticationFilter.java:126)
      at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)
      at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:432)
      at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
      at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
      at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
      at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
      at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
      at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:278)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
      at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
      at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
      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:78)
      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:78)
      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:78)
      at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
      at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
      at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
      at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
      at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
      at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
      at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
      at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
      at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
      at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
      at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
      at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)</text>
                </s:SystemError>
             </detail>
          </SOAP:Fault>
       </SOAP:Body>
    </SOAP:Envelope>
    Also let me know whether we can consume a TIBCO generated WSDL in SAP PI or not (because first we will hit TIBCO endpoint url which in turn internally hits the target system url from TIBCO )
    If this is possible, Please provide your valuable inputs
    Regards
    Koti Reddy

    Hi Koti - The soap action is case sensitive.
    What is the soap version of the wsdl?
    If you try to make a request to a SOAP 1.2 webservice with a SOAP 1.1 request then you may get this error too..
    to check the your webservice soap version - open the wsdl and check for the namespace
    SOAP 1.1 uses namespace http://schemas.xmlsoap.org/wsdl/soap/
    SOAP 1.2 uses namespace http://schemas.xmlsoap.org/wsdl/soap12/
    source - http://forum.spring.io/forum/spring-projects/web-services/45083-server-did-not-recognize-the-value-of-http-header-soapaction
    please share the wsdl as that may help in providing you more information.

  • Creating a new project with custom fields using web services

    I've been trying unsuccessfully for the last week or so to successfully create a new project from web services and I believe the main problem that I've been running into is that one of the required fields is a custom field. I've tried creating the Project
    in a couple of different ways and haven't had any success up to this point, so any help would be appreciated. I've tried creating it with both a REST call to /_api/ProjectServer/Projects and a SOAP call to /_vti_bin/PSI/Project.asmx. Below are the best shots
    I've made at the two different calls with the errors I received. If anyone has any leads on the best way to do this the help would be appreciated!
    REST POST /_api/ProjectServer/Projects
    'odata.type' : 'PS.PublishedProject',
    'Name' : 'OData Name',
    'Custom_9d77d62aa92e4d40adc8446c90eb7456' : "O&M"
    Response
    error: {
    code: "11713, Microsoft.ProjectServer.PJClientCallableException"
    message: {
    lang: "en-US"
    value: "PJClientCallableException: CustomFieldRequiredValueNotProvided CustomFieldRequiredValueNotProvided mdpropuid = 9d77d62a-a92e-4d40-adc8-446c90eb7456"
    SOAP POST /_vti_bin/PSI/Project.asmx
    <?xml version="1.0" encoding="UTF-8"?>
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:proj="http://schemas.microsoft.com/office/project/server/webservices/Project/" xmlns:projds="http://schemas.microsoft.com/office/project/server/webservices/ProjectDataSet/">
    <soapenv:Header />
    <soapenv:Body>
    <proj:QueueCreateProject>
    <proj:dataset>
    <ProjectDataSet xmlns="http://schemas.microsoft.com/office/project/server/webservices/ProjectDataSet/">
    <Project>
    <PROJ_UID>e1c2d38b-1529-4128-b707-42a94045e55b</PROJ_UID>
    <PROJ_NAME>Proj Dept Test 2</PROJ_NAME>
    <PROJ_TYPE>0</PROJ_TYPE>
    </Project>
    <ProjectCustomFields>
    <CUSTOM_FIELD_UID>4802a711-62a0-4f84-8e08-c7d22daadb5b</CUSTOM_FIELD_UID>
    <PROJ_UID>e1c2d38b-1529-4128-b707-42a94045e55b</PROJ_UID>
    <MD_PROP_UID>9d77d62a-a92e-4d40-adc8-446c90eb7456</MD_PROP_UID>
    <FIELD_TYPE_ENUM>21</FIELD_TYPE_ENUM>
    <CODE_VALUE>a47930d6-b89d-4f3a-b4e3-522015fe82a1</CODE_VALUE>
    </ProjectCustomFields>
    </ProjectDataSet>
    </proj:dataset>
    <proj:validateOnly>true</proj:validateOnly>
    </proj:QueueCreateProject>
    </soapenv:Body>
    </soapenv:Envelope>
    Response
    <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
    <s:Body>
    <s:Fault>
    <faultcode>s:Server</faultcode>
    <faultstring xml:lang="en-US">ProjectServerError(s) LastError=GeneralUnhandledException Instructions: Pass this into PSClientError constructor to access all error information</faultstring>
    <detail>
    <errinfo>
    <general>
    <class name="General Unhandled Exception in _Project.QueueCreateProject_">
    <error id="42" name="GeneralUnhandledException" uid="184feeaf-906a-e411-9b2a-00155d388b02" Exception="System.Data.StrongTypingException: The value for column 'PROJ_TYPE' in table 'Project' is DBNull. ---> System.InvalidCastException: Specified cast is not valid.
    at Microsoft.Office.Project.Server.Schema.ProjectDataSet.ProjectRow.get_PROJ_TYPE()
    --- End of inner exception stack trace ---
    at Microsoft.Office.Project.Server.Schema.ProjectDataSet.ProjectRow.get_PROJ_TYPE()
    at Microsoft.Office.Project.Server.BusinessLayer.Project.FixupProjectType(ProjectDataSet projDS)
    at Microsoft.Office.Project.Server.BusinessLayer.Project.QueueCreateProject(Guid jobUid, ProjectDataSet dataset, Boolean validateOnly)
    at Microsoft.Office.Project.Server.Wcf.Implementation.ProjectImpl.&lt;>c__DisplayClasse.&lt;QueueCreateProject>b__d()
    at Microsoft.Office.Project.Server.Wcf.Implementation.WcfMethodInvocation.InvokeBusinessObjectMethod(String businessObjectName, String methodName, IEnumerable`1 actions)"/>
    </class>
    </general>
    </errinfo>
    </detail>
    </s:Fault>
    </s:Body>
    </s:Envelope>

    Julie,
    You can create the fields that are project specifc & you can create fields that apply to all projects but have specific options for projects. Your goal is to create fields that are specific to each project, but right now you get all fields from you old project - is this correct?
    From your description below it appears that the fields in your original project are marked as applied to all projects & hence when you create a new project they are inherited. If you mark those fields as applied to certain project & then create a new project those fields will not be inherited.
    But you are right in the sense that it is limiting that there is no multi-select for "applies to" field.

  • Web Service Access to a extension field

    Hello All:
       Scoping against solution capability, how easy, or at all possible, is to access a extension fields to a native ByD business Objects via web services? In my specific case, the E-Commerce Sales Order Creation Web Service.
       But the question is pretty general, This can be a data retrieve web services as well? Any limitations? does it needed to be rebuild by SAP? or can we generate them by ourselves?
       Also, if in future new extension required on web services, can this process be done after implementation and go live? Without too much trouble?
       Any documentation will be greatly appreciated! Thank You!

    This is doubtful as it is a Standard service (we use it for several different solutions).. and is the same across all tenants and I do not think it can be applied as a custom one off..
    asking your dev coach would probally be your best bet.
    Another solution for you would be to have a simple Read,Update Service you write that just deals with your extension fields... so after an order is created you can update your field on the sales order, or read the value given a specific sales order. 
    Unless this has changed it is my understanding that you have to add the Extension field via the Development studio not the Key user tools if you wish to have access to it in the Studio for releasing a webservice like I described above.(Most my work so far has involved integrations and the standard  webservices)

  • What's a lightweight method to call a web service from an applet?

    So, writing web service clients in java is pretty easy these days using the JAX-RPC library. Problem is in an applet you want it to load fast. I need my applet to call a web service, but don't want to include all the 'baggage' that comes along with JAX-RPC. It looks like you need XML libraries for JAX-RPC stuff to run, and those are huge jar files (many megabytes). I want a lightweight way to call web services. They are my own web services, so I don't need a general solution. There's got to be a way to just form a soap message and use http to send it. It seems like that has been done already.
    On a related note. I will be passing byte arrays as parameters, so if I do try and form my own SOAP XML message, how are byte typically encoded into these messages?
    Thanks a bunch for any suggestions.
    Mike

    The scripting prompt is due to locally installed WebHelp. If you put it on a server, it should work fine. (Or try to enable Mark of the Web for your output.)
    The problem with CSH not working is probably because the CSH is not enabled in the output. In the single source layout settings, make sure that all your map files are selected:
    The easiest way I see it to create a simple API yourself. (We did it for Delphi and C# and it took about ten minutes.) You can just create a URL and feed it to the default browser. If you want to be able to load new help calls in the same tab, you will have to hook into the browser somehow.
    The URL's are really easy to create. See http://www.wvanweelden.eu/article-category/context-sensitivity for a complete overview of all your options in HTML and WebHelp. If you want to call a CHM context sensitive look at the following article: http://msdn.microsoft.com/en-us/library/2bk8zwb3(v=vs.90).aspx
    Greet,
    Willam

  • SOAP, Web Service Interaction using Flex 2

    A Web Service exists on the local computer. It is a .NET
    Framework web service (SOAP) running under IIS. It commences with a
    demand for three parameters. One fills in the form and presses a
    button on the form and is returned an XML file with vital data
    necessary for future web service transactions that will involve
    SQL-form queries and XML responses. Actions that Flex 2 is required
    to perform: 1) submit a URI and receive a form, 2) POST a response
    to the form and receive an XML file, 3) submit a query, 4) reformat
    an XML file to remove irrelevant data and to make a Flex 2 data
    provider happy so that a chart can be displayed. I assume Flex 2
    can do all these things and it is just a matter of knowing how.

    Your description is a bit confusing. The webservice in
    question has a single method that takes three parameters, and
    returns a FORM? What are the three parameters, and what, exactly,
    do you mean by "form".
    When I hear "form", I usually think of an HTML form with text
    input fields, comboboxes, radio buttons, etc. But, in general,
    properly developed webservices do not return UI elements (such as
    text input fields, comboboxes, and radio buttons). They are
    typically only used as a communication method in the model layer,
    where they return datasets or process responses. And the view layer
    (in this case, Flex) is responsible for building any UI elements
    that collect data for the interaction with the webservice.
    But, okay, let's say, for some odd reason, this webservice
    returns a form (as I am thinking of the term). What format is this
    form in? I personally can't think of a readily available method
    that could display this form with a Flex app, but maybe I'm missing
    something. Or is it that, by "form", you mean something completely
    different, like a second method in the webservice that receives
    posted data? What is actually returned in your step #1?
    Step #2 is a cinch. Simply create an HTTPService tag (or in
    script, create URLLoader and URLRequest objects) in your app that
    posts the appropriate data to the appropriate webservice URL with
    the appropriate method. In the callback handler function for that
    webservice call, a (properly formatted) XML response will be
    converted automatically to a "Flex-friendly" data object, which you
    can easily parse apart to build your SQL as necessary.
    Step #3, again, where do you submit the query to? A third
    method in the webservice? If so, it would be just like #2 above.
    And the response data would, again, be automatically converted into
    a Flex data object.
    Step #4 would probably be accomplished more by manipulating
    the Flex data object rather than any reformatting of the XML.
    Simply loop through the object and remove irrelevant children/data.
    Then set a bindable variable to the cleaned data object, and have
    your chart bound to that variable.
    There are many many examples on the web. Just search for
    'flex "mx:HTTPService"' or similar. And take a look through
    LiveDocs for [Bindable] for step #4.

  • Using WebCenter Spaces Web Service API through JDeveloper's Data Control

    Hi,
    I'm trying to access WebCenter Spaces Web Service API (located at http://host:port/webcenter/SpacesWebService)
    using JDeveloper's Web Center Data Control.
    I created a data control in my portal project using JDeveloper's Web Service Data Control wizard.
    I also created and configured key stores (jps-config.xml) at both sides (spaces server and my portal client).
    How I created a data control:
    * First I entered the name and the URL (http://host:port/webcenter/SpacesWebService?WSDL)
    * Then I entered HTTP basic authentication details (user name and password)
    * After that I drag-and-drop the getGroupSpaces() method from the data control to a .jspx page as a ADF read-only table.
    * Then ran my portal project and navigated to this .jspx page and it worked. List of group spaces appeared well on that page.
    The problem is that I got only public group spaces and group spaces created by the user I entered on HTTP basic authentication details.
    I makes no sense to enter some static user details in a web service client (or a data control).
    So the question is; can I use identity propagation to get only group spaces created by the same user which I logged in my portal?
    Edited by: 832886 on Feb 18, 2011 3:09 AM

    Hi,
    You generally get NameError when you are executing the createCred/updateCred from a incorrect location. Are you using the wlst from oracle_common\common\bin?
    Also, In your steps I don't see what you did to populate the walllet at JDeveloper end after your updateCred failed. This is a required step. Use the wlst from the location emntioned above and you should be able to proceed.
    Thanks,
    Vishal

  • 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.

  • Ejbmodule error while building the external service app using web service

    Hi,
    I am new to SOA. I have developed an external service application using web service. While buiding the project i am getting the ejb module error which is mentioned below and the remaining five internal projects are getting deployed successfully. Can anyone help me out in resolving this issue.
    Apr 17, 2008 3:51:45 PM /userOut/Development Component (com.sap.ide.eclipse.component.provider.listener.DevConfListener) [Thread[ModalContext,5,main]] ERROR: user_example/ejbmodule: Build failed for sap.com/user_example/ejbmodule(MyComponents) in variant "default": Compile failed; see the compiler error output for details.
    Build log -
    Development Component Build (2008-04-17 15:51:39)
      Component name: user_example/ejbmodule
      Component vendor: sap.com
      SC compartment: MyComponents
      Configuration: LocalDevelopment
      Location: local
      Source code location: mzwrxw@w2mzwrxw01
      DC root folder: D:\Documents and Settings\mzwrxw\.dtc\LocalDevelopment\DCs\sap.com\user_example\ejbmodule\_comp\
      DC type: J2EE
      DC subtype: EJBModule
      Host: w2mzwrxw01
    DC Model check:
       All used DCs are available locally
       validating dependency to build plugin "sap.com/tc/bi/bp/ejbmodule"
       validating dependency to  public part "default" of DC "sap.com/ejb20"
       validating dependency to  public part "default" of DC "sap.com/jdbc20"
       validating dependency to  public part "default" of DC "sap.com/jms"
       validating dependency to  public part "default" of DC "sap.com/tc/ddic/metamodel/content"
       validating dependency to  public part "CAFRuntimeAPI" of DC "sap.com/caf/runtime/impl"
       validating dependency to  public part "compilation" of DC "sap.com/caf/runtime/api"
       validating dependency to  public part "default" of DC "sap.com/bi/mmr/core"
       validating dependency to  public part "compilation" of DC "sap.com/caf/metamodel"
       validating dependency to  public part "default" of DC "sap.com/com.sap.security.api.sda"
       validating dependency to  public part "default" of DC "sap.com/tc/logging"
       validating dependency to  public part "default" of DC "sap.com/com.sap.exception"
       validating dependency to  public part "default" of DC "sap.com/com.sap.jdo"
       validating dependency to  public part "compilation" of DC "sap.com/bi/mmr/cwm_1.0_source"
       validating dependency to  public part "jmi" of DC "sap.com/bi/mmr/jmi"
       validating dependency to  public part "ClientApi" of DC "sap.com/caf/km.proxyjava"
       validating dependency to  public part "default" of DC "sap.com/bi/mmr/db"
       validating dependency to  public part "ClientAPI" of DC "sap.com/caf/runtime/security"
       validating dependency to  public part "ClientAPI" of DC "sap.com/caf/core/services"
       validating dependency to used DC "sap.com/caf/runtime/connectivity/base"
       validating dependency to used DC "sap.com/caf/runtime/connectivity"
       validating dependency to used DC "sap.com/applocking"
       validating dependency to  public part "default" of DC "sap.com/com.sap.engine.client.lib"
       validating dependency to  public part "default" of DC "sap.com/jta"
       DC model check OK
    Start build plugin:
       using build plugin: sap.com/tc/bi/bp/ejbmodule
       starting build plugin from : C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP_BUILDT\DCs\sap.com\tc\bi\bp\ejbmodule\_comp\gen\default\public\ejb\
    Build Plugin 'EJBModulePlugin', Version 7.00 SP 9 (NW04S_09_REL, built on 2006-10-25 22:26:50 CEST)
       development component:  user_example/ejbmodule (sap.com)
          software component:  MyComponents (demo.sap.com)
                    location:  local
                        type:  J2EE, subtype EJBModule
               build variant:  default
             source location:  mzwrxw@w2mzwrxw01
           plugin start time:  2008-04-17 15:51:39 GMT+05:30 (IST)
                     Java VM:  Java HotSpot(TM) Client VM, 1.4.2_09-b05 (Sun Microsystems Inc.)
    General options:
      convert *.xlf to *.properties: yes
      include sources for debugging: yes
    Source folder src exists but is empty.
    Plugin initialized in 0.187 seconds
    Preparing data context..
    No 'default' JDK defined, will use running VM.
    Data context prepared in 0.078 seconds
    Executing macro file..
      Using macro file:     C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP_BUILDT\DCs\sap.com\tc\bi\bp\ejbmodule\_comp\gen\default\public\ejb\macros\build.vm
      Creating output file: D:\Documents and Settings\mzwrxw\.dtc\LocalDevelopment\DCs\sap.com\user_example\ejbmodule\_comp\gen\default\logs\build.xml
    Macro file executed in 0.141 seconds
    Starting Ant..
      Using build file:     D:\Documents and Settings\mzwrxw\.dtc\LocalDevelopment\DCs\sap.com\user_example\ejbmodule\_comp\gen\default\logs\build.xml
      Using build target:   build
      Generation folder:    D:\Documents and Settings\mzwrxw\.dtc\LocalDevelopment\t\0C4E7D6DF04F4534176A82AEB939F6DA
      Using Ant version:    1.6.2
    compile:
          [echo] Starting Java compiler
          [echo] Settings:
          [echo]   debug:       on
          [echo]   optimize:    off
          [echo]   deprecation: off
          [echo]   verbose:     default
          [echo]   encoding:    UTF8
          [echo]   source:      default
          [echo]   target:      default
          [echo]   source path: D:\Documents and Settings\mzwrxw\.dtc\LocalDevelopment\DCs\sap.com\user_example\ejbmodule\_comp\ejbModule
          [echo]   class path:
          [echo]     C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP-JEE\DCs\sap.com\tc\logging\_comp\gen\default\public\default\lib\java\logging.jar
          [echo]     C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP-JEE\DCs\sap.com\tc\logging\_comp\gen\default\public\default\lib\java\logging.perf.jar
          [echo]     C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP_JTECHS\DCs\sap.com\tc\ddic\metamodel\content\_comp\gen\default\public\default\lib\java\SapMetamodelDictionaryContent.zip
          [echo]     C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP_JTECHS\DCs\sap.com\com.sap.jdo\_comp\gen\default\public\default\lib\java\jdo.jar
          [echo]     C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP_JTECHS\DCs\sap.com\com.sap.jdo\_comp\gen\default\public\default\lib\java\sapjdoapi.jar
          [echo]     C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\BI_UDI\DCs\sap.com\bi\mmr\jmi\_comp\gen\default\public\jmi\lib\java\sap.combimmrjmijmi.jar
          [echo]     C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\BI_UDI\DCs\sap.com\bi\mmr\core\_comp\gen\default\public\default\lib\java\sap.combimmrcoredefault.jar
          [echo]     C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\CAF\DCs\sap.com\caf\km.proxyjava\_comp\gen\default\public\ClientApi\lib\java\sap.comcafkm.proxyjava~ClientApi.jar
          [echo]     C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP-JEE\DCs\sap.com\applocking\_comp\gen\default\public\default\lib\java\applocking.jar
          [echo]     C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP-JEE\DCs\sap.com\applocking\_comp\gen\default\public\default\lib\java\frame.jar
          [echo]     C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP-JEE\DCs\sap.com\applocking\_comp\gen\default\public\default\lib\java\jdbc.jar
          [echo]     C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\CAF\DCs\sap.com\caf\metamodel\_comp\gen\default\public\compilation\lib\java\sap.comcafmetamodel.jar
          [echo]     C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\CAF\DCs\sap.com\caf\metamodel\_comp\gen\default\public\compilation\lib\java\sap.comcafmetamodel_JMI.jar
          [echo]     C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\CAF\DCs\sap.com\caf\metamodel\_comp\gen\default\public\compilation\lib\java\sap.comcafmetamodel_JMI_src.jar
          [echo]     C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP-JEE\DCs\sap.com\com.sap.engine.client.lib\_comp\gen\default\public\default\lib\java\sapj2eeclient.jar
          [echo]     C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\CAF\DCs\sap.com\caf\runtime\connectivity\base\_comp\gen\default\public\com.sap.caf.mp.base\lib\java\sap.comcafruntimeconnectivitybase~com.sap.caf.mp.base.jar
          [echo]     C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\CAF\DCs\sap.com\caf\runtime\security\_comp\gen\default\public\ClientAPI\lib\java\sap.comcafruntimesecurityClientAPI.jar
          [echo]     C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\CAF\DCs\sap.com\caf\runtime\api\_comp\gen\default\public\compilation\lib\java\sap.comcafruntimeapicompilation.jar
          [echo]     C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP-JEE\DCs\sap.com\jdbc20\_comp\gen\default\public\default\lib\java\jdbc.jar
          [echo]     C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\BI_UDI\DCs\sap.com\bi\mmr\cwm_1.0_source\_comp\gen\default\public\compilation\lib\java\sap.combimmr~cwm_1.0_source.jar
          [echo]     C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\BI_UDI\DCs\sap.com\bi\mmr\cwm_1.0_source\_comp\gen\default\public\compilation\lib\java\sap.combimmr~cwm_1.0_source_JMI.jar
          [echo]     C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\BI_UDI\DCs\sap.com\bi\mmr\cwm_1.0_source\_comp\gen\default\public\compilation\lib\java\sap.combimmr~cwm_1.0_source_JMI_src.jar
          [echo]     C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\CAF\DCs\sap.com\caf\runtime\impl\_comp\gen\default\public\CAFRuntimeAPI\lib\java\sap.comcafruntimeimplCAFRuntimeAPI.jar
          [echo]     C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP-JEE\DCs\sap.com\ejb20\_comp\gen\default\public\default\lib\java\ejb20.jar
          [echo]     C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP-JEE\DCs\sap.com\jms\_comp\gen\default\public\default\lib\java\jms.jar
          [echo]     C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP-JEE\DCs\sap.com\com.sap.security.api.sda\_comp\gen\default\public\default\lib\java\com.sap.security.api.jar
          [echo]     C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP-JEE\DCs\sap.com\com.sap.security.api.sda\_comp\gen\default\public\default\lib\java\com.sap.security.api.perm.jar
          [echo]     C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP-JEE\DCs\sap.com\jta\_comp\gen\default\public\default\lib\java\jta.jar
          [echo]     C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\CAF\DCs\sap.com\caf\core\services\_comp\gen\default\public\ClientAPI\lib\java\sap.comcafcoreservicesClientAPI.jar
          [echo]     C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP-JEE\DCs\sap.com\com.sap.exception\_comp\gen\default\public\default\lib\java\exception.jar
          [echo]     C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\CAF\DCs\sap.com\caf\runtime\connectivity\_comp\gen\default\public\com.sap.caf.mp.core.api\lib\java\sap.comcafruntimeconnectivitycom.sap.caf.mp.core.api.jar
          [echo]     C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\BI_UDI\DCs\sap.com\bi\mmr\db\_comp\gen\default\public\default\lib\java\sap.combimmrdbdefault.jar
          [echo]   output dir:  D:\Documents and Settings\mzwrxw\.dtc\LocalDevelopment\t\0C4E7D6DF04F4534176A82AEB939F6DA\classes
         [javac] Compiling 23 source files to D:\Documents and Settings\mzwrxw\.dtc\LocalDevelopment\t\0C4E7D6DF04F4534176A82AEB939F6DA\classes
         [javac] D:\Documents and Settings\mzwrxw\.dtc\LocalDevelopment\DCs\sap.com\user_example\ejbmodule\_comp\ejbModule\com\sap\user_example\besrv\user\userServiceBean.java:51: cannot resolve symbol
         [javac] symbol  : variable JARM_REQUEST
         [javac] location: class java.lang.String
         [javac]         com.sap.caf.rt.util.CAFPublicLogger.entering(user, user.JARM_REQUEST, method, userServiceBean.location, new java.lang.Object[] , com.sap.caf.rt.util.CAFPublicLogger.LEVEL_MEDIUM);
         [javac]                                                                ^
         [javac] D:\Documents and Settings\mzwrxw\.dtc\LocalDevelopment\DCs\sap.com\user_example\ejbmodule\_comp\ejbModule\com\sap\user_example\besrv\user\userServiceBean.java:81: cannot resolve symbol
         [javac] symbol  : variable JARM_REQUEST
         [javac] location: class java.lang.String
         [javac]             com.sap.caf.rt.util.CAFPublicLogger.exiting(user, user.JARM_REQUEST, method, userServiceBean.location, com.sap.caf.rt.util.CAFPublicLogger.LEVEL_MEDIUM);
         [javac]                                                                   ^
         [javac] D:\Documents and Settings\mzwrxw\.dtc\LocalDevelopment\DCs\sap.com\user_example\ejbmodule\_comp\ejbModule\com\sap\user_example\besrv\user\userServiceBean.java:92: cannot resolve symbol
         [javac] symbol  : variable JARM_REQUEST
         [javac] location: class java.lang.String
         [javac]             com.sap.caf.rt.util.CAFPublicLogger.exiting(user, user.JARM_REQUEST, method, userServiceBean.location, com.sap.caf.rt.util.CAFPublicLogger.LEVEL_MEDIUM);
         [javac]                                                                   ^
         [javac] D:\Documents and Settings\mzwrxw\.dtc\LocalDevelopment\DCs\sap.com\user_example\ejbmodule\_comp\ejbModule\com\sap\user_example\besrv\user\userServiceBean.java:96: cannot resolve symbol
         [javac] symbol  : variable JARM_REQUEST
         [javac] location: class java.lang.String
         [javac]         com.sap.caf.rt.util.CAFPublicLogger.exiting(user, user.JARM_REQUEST, method, userServiceBean.location, new java.lang.Object[] , com.sap.caf.rt.util.CAFPublicLogger.LEVEL_MEDIUM);
         [javac]                                                               ^
         [javac] D:\Documents and Settings\mzwrxw\.dtc\LocalDevelopment\DCs\sap.com\user_example\ejbmodule\_comp\ejbModule\com\sap\user_example\besrv\user\userServiceBean.java:105: cannot resolve symbol
         [javac] symbol  : variable JARM_REQUEST
         [javac] location: class java.lang.String
         [javac]           com.sap.caf.rt.util.CAFPublicLogger.entering(user, user.JARM_REQUEST, method, userServiceBean.location, new java.lang.Object[] , com.sap.caf.rt.util.CAFPublicLogger.LEVEL_MEDIUM);
         [javac]                                                                        ^
         [javac] D:\Documents and Settings\mzwrxw\.dtc\LocalDevelopment\DCs\sap.com\user_example\ejbmodule\_comp\ejbModule\com\sap\user_example\besrv\user\userServiceBean.java:115: cannot resolve symbol
         [javac] symbol  : variable JARM_REQUEST
         [javac] location: class java.lang.String
         [javac]                com.sap.caf.rt.util.CAFPublicLogger.exiting(user, user.JARM_REQUEST, method, userServiceBean.location, com.sap.caf.rt.util.CAFPublicLogger.LEVEL_MEDIUM);
         [javac]                                                                               ^
         [javac] D:\Documents and Settings\mzwrxw\.dtc\LocalDevelopment\DCs\sap.com\user_example\ejbmodule\_comp\ejbModule\com\sap\user_example\besrv\user\userServiceBean.java:126: cannot resolve symbol
         [javac] symbol  : variable JARM_REQUEST
         [javac] location: class java.lang.String
         [javac]                com.sap.caf.rt.util.CAFPublicLogger.exiting(user, user.JARM_REQUEST, method, userServiceBean.location, com.sap.caf.rt.util.CAFPublicLogger.LEVEL_MEDIUM);
         [javac]                                                                               ^
         [javac] D:\Documents and Settings\mzwrxw\.dtc\LocalDevelopment\DCs\sap.com\user_example\ejbmodule\_comp\ejbModule\com\sap\user_example\besrv\user\userServiceBean.java:131: cannot resolve symbol
         [javac] symbol  : variable JARM_REQUEST
         [javac] location: class java.lang.String
         [javac]           com.sap.caf.rt.util.CAFPublicLogger.exiting(user, user.JARM_REQUEST, method, userServiceBean.location, new java.lang.Object[] , com.sap.caf.rt.util.CAFPublicLogger.LEVEL_MEDIUM);
         [javac]                                                                       ^
         [javac] D:\Documents and Settings\mzwrxw\.dtc\LocalDevelopment\DCs\sap.com\user_example\ejbmodule\_comp\ejbModule\com\sap\user_example\besrv\user\userServiceBean.java:139: cannot resolve symbol
         [javac] symbol  : variable JARM_REQUEST
         [javac] location: class java.lang.String
         [javac]           com.sap.caf.rt.util.CAFPublicLogger.entering(user, user.JARM_REQUEST, method, userServiceBean.location, new java.lang.Object[] , com.sap.caf.rt.util.CAFPublicLogger.LEVEL_MEDIUM);
         [javac]                                                                        ^
         [javac] D:\Documents and Settings\mzwrxw\.dtc\LocalDevelopment\DCs\sap.com\user_example\ejbmodule\_comp\ejbModule\com\sap\user_example\besrv\user\userServiceBean.java:154: cannot resolve symbol
         [javac] symbol  : variable JARM_REQUEST
         [javac] location: class java.lang.String
         [javac]                com.sap.caf.rt.util.CAFPublicLogger.exiting(user, user.JARM_REQUEST, method, userServiceBean.location, com.sap.caf.rt.util.CAFPublicLogger.LEVEL_MEDIUM);
         [javac]                                                                               ^
         [javac] D:\Documents and Settings\mzwrxw\.dtc\LocalDevelopment\DCs\sap.com\user_example\ejbmodule\_comp\ejbModule\com\sap\user_example\besrv\user\userServiceBean.java:159: cannot resolve symbol
         [javac] symbol  : variable JARM_REQUEST
         [javac] location: class java.lang.String
         [javac]           com.sap.caf.rt.util.CAFPublicLogger.exiting(user, user.JARM_REQUEST, method, userServiceBean.location, com.sap.caf.rt.util.CAFPublicLogger.LEVEL_MEDIUM);
         [javac]                                                                       ^
         [javac] D:\Documents and Settings\mzwrxw\.dtc\LocalDevelopment\DCs\sap.com\user_example\ejbmodule\_comp\ejbModule\com\sap\user_example\besrv\user\userServiceBean.java:165: cannot resolve symbol
         [javac] symbol  : variable JARM_REQUEST
         [javac] location: class java.lang.String
         [javac]           com.sap.caf.rt.util.CAFPublicLogger.entering(user, user.JARM_REQUEST, method, userServiceBean.location, new java.lang.Object[] , com.sap.caf.rt.util.CAFPublicLogger.LEVEL_MEDIUM);
         [javac]                                                                        ^
         [javac] D:\Documents and Settings\mzwrxw\.dtc\LocalDevelopment\DCs\sap.com\user_example\ejbmodule\_comp\ejbModule\com\sap\user_example\besrv\user\userServiceBean.java:186: cannot resolve symbol
         [javac] symbol  : variable JARM_REQUEST
         [javac] location: class java.lang.String
         [javac]                    com.sap.caf.rt.util.CAFPublicLogger.exiting(user, user.JARM_REQUEST, method, userServiceBean.location, com.sap.caf.rt.util.CAFPublicLogger.LEVEL_MEDIUM);
         [javac]                                                                                ^
         [javac] D:\Documents and Settings\mzwrxw\.dtc\LocalDevelopment\DCs\sap.com\user_example\ejbmodule\_comp\ejbModule\com\sap\user_example\besrv\user\userServiceBean.java:200: cannot resolve symbol
         [javac] symbol  : variable JARM_REQUEST
         [javac] location: class java.lang.String
         [javac]                    com.sap.caf.rt.util.CAFPublicLogger.exiting(user, user.JARM_REQUEST, method, userServiceBean.location, com.sap.caf.rt.util.CAFPublicLogger.LEVEL_MEDIUM);
         [javac]                                                                                ^
         [javac] D:\Documents and Settings\mzwrxw\.dtc\LocalDevelopment\DCs\sap.com\user_example\ejbmodule\_comp\ejbModule\com\sap\user_example\besrv\user\userServiceBean.java:206: cannot resolve symbol
         [javac] symbol  : variable JARM_REQUEST
         [javac] location: class java.lang.String
         [javac]           com.sap.caf.rt.util.CAFPublicLogger.exiting(user, user.JARM_REQUEST, method, userServiceBean.location, com.sap.caf.rt.util.CAFPublicLogger.LEVEL_MEDIUM);
         [javac]                                                                       ^
         [javac] D:\Documents and Settings\mzwrxw\.dtc\LocalDevelopment\DCs\sap.com\user_example\ejbmodule\_comp\ejbModule\com\sap\user_example\besrv\user\userServiceBean.java:213: cannot resolve symbol
         [javac] symbol  : variable JARM_REQUEST
         [javac] location: class java.lang.String
         [javac]           com.sap.caf.rt.util.CAFPublicLogger.entering(user, user.JARM_REQUEST, method, userServiceBean.location, new java.lang.Object[] , com.sap.caf.rt.util.CAFPublicLogger.LEVEL_MEDIUM);
         [javac]                                                                        ^
         [javac] D:\Documents and Settings\mzwrxw\.dtc\LocalDevelopment\DCs\sap.com\user_example\ejbmodule\_comp\ejbModule\com\sap\user_example\besrv\user\userServiceBean.java:233: cannot resolve symbol
         [javac] symbol  : variable JARM_REQUEST
         [javac] location: class java.lang.String
         [javac]             com.sap.caf.rt.util.CAFPublicLogger.exiting(user, user.JARM_REQUEST, method, userServiceBean.location, com.sap.caf.rt.util.CAFPublicLogger.LEVEL_MEDIUM);
         [javac]                                                                   ^
         [javac] D:\Documents and Settings\mzwrxw\.dtc\LocalDevelopment\DCs\sap.com\user_example\ejbmodule\_comp\ejbModule\com\sap\user_example\besrv\user\userServiceBean.java:244: cannot resolve symbol
         [javac] symbol  : variable JARM_REQUEST
         [javac] location: class java.lang.String
         [javac]             com.sap.caf.rt.util.CAFPublicLogger.exiting(user, user.JARM_REQUEST, method, userServiceBean.location, com.sap.caf.rt.util.CAFPublicLogger.LEVEL_MEDIUM);
         [javac]                                                                   ^
         [javac] D:\Documents and Settings\mzwrxw\.dtc\LocalDevelopment\DCs\sap.com\user_example\ejbmodule\_comp\ejbModule\com\sap\user_example\besrv\user\userServiceBean.java:254: cannot resolve symbol
         [javac] symbol  : variable JARM_REQUEST
         [javac] location: class java.lang.String
         [javac]         com.sap.caf.rt.util.CAFPublicLogger.exiting(user, user.JARM_REQUEST, method, userServiceBean.location, com.sap.caf.rt.util.CAFPublicLogger.LEVEL_MEDIUM);
         [javac]                                                               ^
         [javac] D:\Documents and Settings\mzwrxw\.dtc\LocalDevelopment\DCs\sap.com\user_example\ejbmodule\_comp\ejbModule\com\sap\user_example\besrv\user\userServiceBean.java:261: cannot resolve symbol
         [javac] symbol  : variable JARM_REQUEST
         [javac] location: class java.lang.String
         [javac]         com.sap.caf.rt.util.CAFPublicLogger.entering(user, user.JARM_REQUEST, method, userServiceBean.location, new java.lang.Object[] , com.sap.caf.rt.util.CAFPublicLogger.LEVEL_MEDIUM);
         [javac]                                                                ^
         [javac] D:\Documents and Settings\mzwrxw\.dtc\LocalDevelopment\DCs\sap.com\user_example\ejbmodule\_comp\ejbModule\com\sap\user_example\besrv\user\userServiceBean.java:270: cannot resolve symbol
         [javac] symbol  : variable JARM_REQUEST
         [javac] location: class java.lang.String
         [javac]                com.sap.caf.rt.util.CAFPublicLogger.exiting(user, user.JARM_REQUEST, method, userServiceBean.location, com.sap.caf.rt.util.CAFPublicLogger.LEVEL_MEDIUM);
         [javac]                                                                       ^
         [javac] D:\Documents and Settings\mzwrxw\.dtc\LocalDevelopment\DCs\sap.com\user_example\ejbmodule\_comp\ejbModule\com\sap\user_example\besrv\user\userServiceBean.java:281: cannot resolve symbol
         [javac] symbol  : variable JARM_REQUEST
         [javac] location: class java.lang.String
         [javac]                  com.sap.caf.rt.util.CAFPublicLogger.exiting(user, user.JARM_REQUEST, method, userServiceBean.location, com.sap.caf.rt.util.CAFPublicLogger.LEVEL_MEDIUM);
         [javac]                                                                               ^
         [javac] D:\Documents and Settings\mzwrxw\.dtc\LocalDevelopment\DCs\sap.com\user_example\ejbmodule\_comp\ejbModule\com\sap\user_example\besrv\user\userServiceBean.java:288: cannot resolve symbol
         [javac] symbol  : variable JARM_REQUEST
         [javac] location: class java.lang.String
         [javac]          com.sap.caf.rt.util.CAFPublicLogger.exiting(user, user.JARM_REQUEST, method, userServiceBean.location, new java.lang.Object[] , com.sap.caf.rt.util.CAFPublicLogger.LEVEL_MEDIUM);
         [javac]                                                               ^
         [javac] D:\Documents and Settings\mzwrxw\.dtc\LocalDevelopment\DCs\sap.com\user_example\ejbmodule\_comp\ejbModule\com\sap\user_example\besrv\user\userServiceBean.java:295: cannot resolve symbol
         [javac] symbol  : variable JARM_REQUEST
         [javac] location: class java.lang.String
         [javac]         com.sap.caf.rt.util.CAFPublicLogger.entering(user, user.JARM_REQUEST, method, userServiceBean.location, com.sap.caf.rt.util.CAFPublicLogger.LEVEL_MEDIUM);
         [javac]                                                                ^
         [javac] D:\Documents and Settings\mzwrxw\.dtc\LocalDevelopment\DCs\sap.com\user_example\ejbmodule\_comp\ejbModule\com\sap\user_example\besrv\user\userServiceBean.java:300: cannot resolve symbol
         [javac] symbol  : variable JARM_REQUEST
         [javac] location: class java.lang.String
         [javac]           com.sap.caf.rt.util.CAFPublicLogger.exiting(user, user.JARM_REQUEST, method, userServiceBean.location, com.sap.caf.rt.util.CAFPublicLogger.LEVEL_MEDIUM);
         [javac]                                                                       ^
         [javac] D:\Documents and Settings\mzwrxw\.dtc\LocalDevelopment\DCs\sap.com\user_example\ejbmodule\_comp\ejbModule\com\sap\user_example\besrv\user\userServiceBean.java:308: cannot resolve symbol
         [javac] symbol  : variable JARM_REQUEST
         [javac] location: class java.lang.String
         [javac]           com.sap.caf.rt.util.CAFPublicLogger.entering(user, user.JARM_REQUEST, method, userServiceBean.location, new java.lang.Object[] , com.sap.caf.rt.util.CAFPublicLogger.LEVEL_MEDIUM);
         [javac]                                                                        ^
         [javac] D:\Documents and Settings\mzwrxw\.dtc\LocalDevelopment\DCs\sap.com\user_example\ejbmodule\_comp\ejbModule\com\sap\user_example\besrv\user\userServiceBean.java:370: cannot resolve symbol
         [javac] symbol  : variable JARM_REQUEST
         [javac] location: class java.lang.String
         [javac]                com.sap.caf.rt.util.CAFPublicLogger.exiting(user, user.JARM_REQUEST, method, userServiceBean.location, com.sap.caf.rt.util.CAFPublicLogger.LEVEL_MEDIUM);
         [javac]                                                                               ^
         [javac] D:\Documents and Settings\mzwrxw\.dtc\LocalDevelopment\DCs\sap.com\user_example\ejbmodule\_comp\ejbModule\com\sap\user_example\besrv\user\userServiceBean.java:462: cannot resolve symbol
         [javac] symbol  : variable JARM_REQUEST
         [javac] location: class java.lang.String
         [javac]           com.sap.caf.rt.util.CAFPublicLogger.entering(user, user.JARM_REQUEST, method, userServiceBean.location, com.sap.caf.rt.util.CAFPublicLogger.LEVEL_MEDIUM);
         [javac]                                                                        ^
         [javac] D:\Documents and Settings\mzwrxw\.dtc\LocalDevelopment\DCs\sap.com\user_example\ejbmodule\_comp\ejbModule\com\sap\user_example\besrv\user\userServiceBean.java:477: cannot resolve symbol
         [javac] symbol  : variable JARM_REQUEST
         [javac] location: class java.lang.String
         [javac]                com.sap.caf.rt.util.CAFPublicLogger.exiting(user, user.JARM_REQUEST, method, userServiceBean.location, com.sap.caf.rt.util.CAFPublicLogger.LEVEL_MEDIUM);
         [javac]                                                                               ^
         [javac] D:\Documents and Settings\mzwrxw\.dtc\LocalDevelopment\DCs\sap.com\user_example\ejbmodule\_comp\ejbModule\com\sap\user_example\besrv\user\userServiceBean.java:482: cannot resolve symbol
         [javac] symbol  : variable JARM_REQUEST
         [javac] location: class java.lang.String
         [javac]           com.sap.caf.rt.util.CAFPublicLogger.exiting(user, user.JARM_REQUEST, method, userServiceBean.location, com.sap.caf.rt.util.CAFPublicLogger.LEVEL_MEDIUM);
         [javac]                                                                       ^
         [javac] 30 errors
    Ant runtime 4.984 seconds
    Ant build finished with ERRORS
    Compile failed; see the compiler error output for details.
    Error: Build stopped due to an error: Compile failed; see the compiler error output for details.
    Build plugin finished at 2008-04-17 15:51:45 GMT+05:30 (IST)
    Total build plugin runtime: 5.515 seconds
    Build finished with ERROR
    Thanks,
    Madhavi

    HI
    i used the below line of code to log the info
    com.sap.caf.rt.util.CAFPublicLogger.entering(CAF_user, WTCServiceBean.JARM_REQUEST, CAF_methodHeader, WTCServiceBean.location, CAF_parameters);
    But , can anyone suggest ,where can i seee this log msg.
    Any pointers would be highly appreciated.
    Thanks

  • Calling a web service in ABAP

    Hello Experts!
    After I am assuming the SOAP Experts at the SOAP Forum
    are being already on christmas vacation
    I saw no other possiblitiy to post my question right here.
    I have created a web service through:
    Open the affected  function Module  .
    Choose Utilities  -> More Utilities  -> Creating a Web Service  -> From Function Module.
    Later you can test it with SOAMANAGER etc.
    The goal is now (requirement)
    Calling a web service in ABAP.
    How can I generally call a (eg .above created by me ) webservice with abap which is existing on the sap system (Web Services which are generated from Function Modules)
    Has really nobody such a problem ever before ?
    Regards
    ertas ilhan

    Michael thank you very much.
    You are saying:
    The easiest way to do it is with the WSDL file that you'll get from the existing Web Service. In your proxy class it will generate a method which you can then call within your program to consume that web service.
    I understand the first part with the WSDL file but the second part it is unclear to me with
    In your proxy class it will generate a method which you can then call within your program to consume that web service
    Can you please explain me this more detailed.
    Thanks
    ertas

Maybe you are looking for