Which BAPI is implemented in a given Web Service?

If I have a WSDL for an SAP web service, how can I determine what BAPI is being exectued on the back end?
For example, given the Web Service name EmployeeBasicDataByEmployeeQueryResponse_In, how can I tell what BAPI(s) are used?
Please be specific in your answer. This is pretty new technology to me.

Hi,
Goto transaction SPROXY:
- Search for your service.
- Double click and see "provider class" : CL_PAD_EMPBASICDATA_EMPQR
- You will find class and implementation method
- Usually you can find actual bapi etc in "BUSINESS_LOGIC" method.
Do few times and you will be expert in this
Regards,
Gourav
Edited by: Gourav Khare on Jul 29, 2009 12:37 AM

Similar Messages

Which metadata fields can be modified via web services?

I have searched the discussions and the documentation, but have not seen this answered comprehensively. What I would like to know is which fields can be modified using MergeTrack? The following are the ones I've gotten to work so far (entity name on left, iTunes field on right):
Title = Name
Comment = Comment
ArtistName = Artist
AlbumName = Album
TrackNumber = Track #
DiscNumber = Disc #
CategoryCode = Category (but this will not appear in the Category column in iTunes)
Can Genre be set? Or Show, Year, Season, Composer, etc.? Thanks.

For the definitive answer, I always turn to the request XSD.
Categories are only significant if you're in the process of expanding from a private/public site to "iTunes U in the iTunes Store". Otherwise applying category info has no real effect. In fact, applying category info is one of the things you do when you are "staging" for admission to the iTunes Store.
The web service does not allow you to change genre, show, year, season, composer, etc. The only way to change that info is to modify it from within the iTunes application (or a similar tool).

How to implement the security in web service with Weblogic 9.2

I've generated web service by Web Logic 9.2 using existing WSDL (as per client requirement) and want to add security policy for authentications.
I have used following annotation in service class.
@Policies({
@Policy(uri="policy:Auth.xml" , direction=Policy.Direction.inbound)
But it gives compilation time error with following message.
The Policy and Policies annotations are not allowed on jws file when compiledWsdl option is specified
I've also tried to modify the WSDL to accommodate policy configuration and again generate the web service but problem is being as it is.
If anybody has solution of this issue then please let me know ASAP.

Did you get an answer to your question? I have the same problem with WebLogic 10.0.

Implementing authentication for web services

Hi all,
I'm struggling trying to guess how to implement basic HTTP authentication as well as using certificates in order to apply HTTPS, for some web services we've created, running on the Oracle Application Server 10.1.12. The web services were implemented using JDeveloper 9.0.4. Any help would be very appreciated.
Thanks in advanced and regards,
Luis

Hi,
But, I need to develop the web services logon method using WSDL which generated the LogonBindingImpl.java, instead of web services using EJB bean.
Besides, the Web Service logon method (LogonBindingImpl.java) need to accept the input user name and password to check with the user name and password that stored in database table through the EJB bean. If checking successful, client program is allowed to invoke other WebServices method, else login failed exception need to be thrown when client calling other web services methods.
Appreciate the advice here on how to achieve that. Thanks.

Create BAPI as Web Service

Hi,
I have expose a BAPI as a web service.
Application : PA
BAPI : EmployeePersonalData
Method : Create
When i try to test the web serive with the following test data:
Employeenumber (String) = 12345678
Validitybegin (String) = 2001-01-01
Validityend (String) = 2003-01-01
It give me the following error:
=============================================
HTTP/1.1 500 Internal Server Error
Set-Cookie: <value is hidden>
content-type: text/xml; charset=utf-8
content-length: 803
sap-srt_id: 20080128/122539/v1.00_final_6.40/DCCD591434D56BF19BA300145E6770F3
server: SAP Web Application Server (1.0;700)
<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/"><soap-env:Body><soap-env:Fault><faultcode>soap-env:Client</faultcode><faultstring xml:lang="en">Deserialisation failed</faultstring><detail><n0:SimpleTransformationFault xmlns:n0="http://www.sap.com/transformation-templates"><MainName>/1BCDWB/WSS0080123034217187000</MainName><ProgName>/1BCDWB/WSS0080123034217187000</ProgName><Line>128 </Line><Valid>X</Valid><ReferenceFault><DescriptionText>Error accessing the ref. node 'EMPLOYEENUMBER'</DescriptionText><RefName>EMPLOYEENUMBER</RefName></ReferenceFault><Caller><Class>CL_SRG_RFC_PROXY_CONTEXT</Class><Method>IF_SXML_PART~DECODE</Method><Positions>1 </Positions></Caller></n0:SimpleTransformationFault></detail></soap-env:Fault></soap-env:Body></soap-env:Envelope>
============================================
What wrong with it? Any idea how to resolve this problem?
Regards,
Rayden

Hi Rayden
It will surely help you.
Please reward pts if help.
Deepanker
Expose BAPI as a Web Service
1. Go to transaction SE80.Select Function Group from drop down menu; enter the function group in which the BAPI (which is to be exposed as Web Service) comes. You can find this Function Group from function module (BAPI) itself. Go to transaction SE37 and enter function module name (BAPI name) and click on display. You can see the function group here under attribute tab .
2. Then from Function Modules list choose the BAPI to which you want to expose as a
Web Service .
3. On right clicking on the BAPI a context menu appears. Click on create and Web Service option .
4. New window will pop up. Click on Continue.
5. Give the name for Enterprise service and short description. Click on continue.
6. New window will pop up.Click on Continue
7. New window pop up. Click on 'Release service for runtime'. Click on Continue.
8. This window pops up. Click on Complete.
9. New pop up window come up asking for Package. Give the package name and click on SAVE button.
10. New window pop up asking for Request . Give request and click on OK.
11. New window comes displaying service definition.
12. Now go to transaction WSADMIN and choose your web service. Go to Web Service menu and choose WSDL option.
13. New pop up window come.Check on Include SAP Feature in WSDL and click on OK.
14. Internet browser will be opened and asking for User Name and Password .
15. After giving values for user name and password, you will get WSDL file opened in internet explorer. SAVE this locally on your computer for further use.

Accessing XI Web Service in Web DynPro

Hi Experts,
I have a scenario wherein, I will have to access a Web Service that created in XI.
My Finding still now,
1. I have a web service which is created in XI System.
2. Created a Logical Destination in the Visual Administrator. We have given the wsdl URL, system ID, Client and Basic Authentication Information.
3. When we test the Web Service in the Visual Admin, we get a Message Reponse 200, but the content type says Unknown
4. When we test the Web Service in the SOAP Sonar Web Service Testing Tool, we are getting the correct solution
5. After that, we tried creating an Adaptive Web Service Model, using the WSDL URL.
6. When we deploy the application, we get the following error
Exception on creation of service metadata for WS metadata destination 'POItems' and WS interface 'POitem_WS_OUT'. One possible reason is that the metadata destination 'POItems' has not been properly configured; check configuration
When I tried to access a BAPI that is exposed as a Web Service by default, I end up in the following error
Exception on execution of web service with WSDL URL 'http://mycomp01:1001/sap/bc/soap/wsdl11?services=ZBAPI_POITEM_GETLIST&sap-client=800' with operation 'ZBAPI_POITEM_GETLIST' in interface '{urn ap-com ocument ap:rfc:functions}ZBAPI_POITEM_GETLISTPortType'
I have also tried to create a Deployable Web Service using the WSDL file in the Web Service Perspective. Once I deploy the ear file, it appears in the Visual Admin, but when I try testing it I get an error with Response Code 500
Note: I have tried to create an Adaptive Web Service model for the following Link : http://www.webservicex.net/WeatherForecast.asmx?wsdl that is availbale in the net using a logical destination that refers to the same WSDL URL, the application is working fine.
Server/Studio Config details
J2EE - 7.0
NWDS 2004s SP 12
JDK - 1.4.2_09
Please suggest a solution for the above problem or it would be helpful if you can give links that helps in creating a Web DynPro Application to access the XI Web Service. We have followed as per this Link :
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b2bc0932-0d01-0010-6d8e-cff1b2f22bc7
Regards,
Mathan MP

Vaishali,
never did this before, but some general ideas:
Do you have an WSDL for that web service? Then simply use your NWDS and select New --> Portal Service --> From WSDL (or similar). What I mean is the following: NWDS can read WSDL files and will automatically generate a proxy for you that actually generates an ordinary portal service. This portal service then can be called by standard means in SAP EP.
Regards,
Dominik

About web service

hi, all
i call the web service in abap report.
there is a runtime error that is "Method 'nr1:put-messagesRequest' not implemented: method name or namespace not recognized".

Hi Ken
Hope it will help you.
Pls reward if help.
Expose BAPI as a Web Service
1. Go to transaction SE80.Select Function Group from drop down menu; enter the function group in which the BAPI (which is to be exposed as Web Service) comes. You can find this Function Group from function module (BAPI) itself. Go to transaction SE37 and enter function module name (BAPI name) and click on display. You can see the function group here under attribute tab .
2. Then from Function Modules list choose the BAPI to which you want to expose as a
Web Service .
3. On right clicking on the BAPI a context menu appears. Click on create and Web Service option .
4. New window will pop up. Click on Continue.
5. Give the name for Enterprise service and short description. Click on continue.
6. New window will pop up.Click on Continue
7. New window pop up. Click on 'Release service for runtime'. Click on Continue.
8. This window pops up. Click on Complete.
9. New pop up window come up asking for Package. Give the package name and click on SAVE button.
10. New window pop up asking for Request . Give request and click on OK.
11. New window comes displaying service definition.
12. Now go to transaction WSADMIN and choose your web service. Go to Web Service menu and choose WSDL option.
13. New pop up window come.Check on Include SAP Feature in WSDL and click on OK.
14. Internet browser will be opened and asking for User Name and Password .
15. After giving values for user name and password, you will get WSDL file opened in internet explorer. SAVE this locally on your computer for further use.
NOw u need to import this wsdl to NW-XI-IntegrationBuilder-IntegrationRepository and use this in your scenario.

ABAP web services

HIII..
I want to know about a ABAP web service . How this can be created????
Thanks in advance.
Regards
Mayank Saxena

Hi,
Web Services
Business processes consist of individual process steps that can vary in how extensive they are. One or more functions are then assigned to these steps; an executing software component is then assigned to each function. Clearly, the heterogeneous nature of system landscapes in enterprises makes it impossible to implement all the necessary functions associated with a complete process using the same technology on the same component. A modern software infrastructure must be in the position to integrate functions, implemented on widely differing software components, in one effective complete process. Until now, the combination of different applications has largely been based on manually declared interfaces, message formats, and agreements between business partners.
Web services simplify this process. They are based on open, generally accepted standards. They enable you to combine functions in a single process, even if they are implemented in widely differing software components. Web services are standalone, executable entities that can be published, searched for, and called, across a network.
Introduction
The SAP Web Application Server implements the following basic Web services standards: eXtensible Markup Language (XML); Simple Object Access Protocol (SOAP); Web Service Definition Language (WSDL); and Universal Description, Discovery, and Integration (UDDI).
In the documentation that follows, we assume that the reader is familiar with Web service standards and techniques. You will find a general introduction to the Web Services topic under Sun Microsystems, in the pages of W3C, and in the general explanations for standardization organization OASIS under the topic UDDI.
Integration
ABAP and Java Web Services
Enterprises can extend their solutions by using Java or ABAP Web services, or both. If your priority in programming an application is the selection of data, the integration of an ABAP Web Service could be appropriate. Conversely, if you are implementing processes that involve different business partners and systems, it may be beneficial to program in Java and integrate Java Web Services.
The Web Service Framework consists of:
·        The development environment for the ABAP Engine
·        The development environment for the J2EE Engine
·        Tools that support UDDI registration
·        A distributed, interoperable SOAP runtime (ABAP and J2EE Engine)
Processing of SOAP requests using the Internet Communication Framework
Web Services and the SAP Exchange Infrastructure
The SAP Exchange Infrastructure is a key area in SAP NetWeaver. The Exchange Infrastructure provides an open, process-oriented integration infrastructure for the unhindered flow of information and for XML-based message exchanges. Systems integrated using SAP XI exchange messages over the Integration Server.
The programming model for XI ABAP proxies and Web services has been unified. The advantage of this is that both technologies can be implemented so that they complement one another. Messages can be sent and received either using the XI runtime or the Web service runtime.
Additional proxy runtime services can be controlled using protocols that you request using a proxy method. The features you have available depend on whether you are using the Web Service Framework or the Exchange Infrastructure for communication.
Features
The ABAP Workbench offers an environment where you can publish, search for, and call Web services. It enables the SAP Web Application Server to act both as a server and client for Web services.
The Web service infrastructure enables developers to:
·    Publish independent function that were implemented as RFC-enabled function modules, function groups, BAPIs, or XI message interfaces. This includes functions available as part of mySAP.com solutions, or functions developed by customers or partners. The Web service can be used across the entire Internet using standard protocols and can easily be added to any development environment. (See also Creating a Web Service).
·    Consume Web services, regardless of where they are stored or how they are implemented. Business processes can be implemented across several systems, either within an enterprise or across several enterprises. (See also Consuming Web Services.)
The following triangle shows the basic architecture of the Web Service Framework:
Service Provider
After the functions have been implemented, a Web service interface must be created that provides a representation of the Web service for the user. This interface offers an abstraction layer and thus independence from the specific implementation used. Based on this interface, the Web service is configured and can be called at runtime. Publishing Web services in a UDDI Registry is supported by the UDDI client functions in the SAP Web AS.
Service Directory
You can store Web service definitions and released Web Services in a UDDI Registry. WSDL documents provide the basis of the Web service client, which can then be searched for in the UDDI using either a browser or the standard UDDI APIs. Web services can be published and searched for in all registries that conform to the standard. SAP also offers a public UDDI Business Registry under uddi.sap.com.
Service Requestor
The SAP Web AS allows you to integrate Web services. It can generate Web service clients from WSDL files.
Standardization and Extensibility
Web services and Web service standards develop quickly; new standards are being presented continually at standardization committees. However, these extended standards such as security standards or additional protocols can easily be integrated in the Web Service Framework using SAP.
See also:
Web Services Toolset
For more information see the following link.
http://help.sap.com/saphelp_nw04/helpdata/en/9b/dad1ae3908ee44a5caf57e10918be9/frameset.htm
Please Reward If Helpful
Jagadish

'Payload not Serializable' with custom WSDL data types in message-style web service

I'm implementing a message-style web service which publishes to a JMS Queue.
I had the web service built and deployed, but noticed that the "sendRequest" message's
part was of type "xsd:anyType." This is not specific enough for our interface,
since it is externally facing and needs to describe the object we're expecting
on the back end.
So I replaced xsd:anyType with mynamespace:MyType, which is defined as a complex
type in the same WSDL document.
My problem is that when I test the web service with the new WSDL (using the client.jar),
I get a server-side exception from the DestinationSendAdapter.doPost() method.
The exception reads:
javax.servlet.ServletException: Payload not Serializable
at weblogic.soap.server.servlet.DestinationSendAdapter.doPost(DestinationSendAdapter.java:129)
The domain object ('classic' JavaBean) that it should map to on the server side
extends a class that implements Serializable, so it should inherit the trait.
So my questions are:
1) Did I properly go about trying to restrict the object type that gets sent to
my Destination?
2) If no, what is the correct way? If yes, why am I receiving the Payload not
Serializable error if the domain object implements Serializable?
Thanks in advance.

Resolved:
Apparently this is the right approach, as it boiled down to a classpath issue
on the client-side. Thanks anyway.

Simple web services and XA

WSI-15 indicates non-transactional WS, But WSI-16 indicates WS "use short-running,
XA transactions"

A<WSI-15>Let me clear up any possible confusion. There is no inherent support for
transactions within the web service framework and in particular there is no way for
a web service client to demarcate a transaction. There are some emerging standards
(BTP,SOAP-CTX) that hope to address these issues but they really are in their infancy.
On the implementation side of the web service (with your stateless session EJB for
instance) there is however nothing to stop you using transaction. The actual business
process that you are invoking can and should have complete XA transaction support
which is what slide 16 eludes to.
"Elie Dagher" <[email protected]> wrote:
>
WSI-15 indicates non-transactional WS, But WSI-16 indicates WS "use short-running,
XA transactions"

Error while creating web service reference

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

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

How to use WS-RM web Service from Session Bean?

Hi all.
Could you tell me the way how to call WS-RM web service(Staring BPM Process) from SessionBean?
Our environment: SAP NetWeaver CE 7.2 SP3
I do the following.
I have created a BPM Process starting with Message Start Event.
This Message Start Event was created by Service Interface(stateless and asynchronous) which was imported from ESR.
I deployed this into my server and it worked fine in webservice navigator as a WS-RM WebService.
But I can't call this webservice from SessionBean in EJBExplorer.
I get the following error message:
Caused by: This exception is wrapper of javax.xml.ws.soap.SOAPFaultException. com.sap.engine.services.webservices.espba
se.client.bindings.exceptions.SOAPFaultException: Invalid WS-RM message. There are no WS-RM headers within SOAP message.
at com.sap.engine.services.webservices.espbase.client.bindings.impl.JAXWSUtil.processFault(JAXWSUtil.java:412)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1366)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:960)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:915)
at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:168)
at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEISyncMethod(WSInvocationHandler.java:121)
at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEIMethod(WSInvocationHandler.java:84)
at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invoke(WSInvocationHandler.java:65)
at $Proxy2753.zwsvCheckOrderdataMainprocessStart(Unknown Source)
at jp.co.ogis_ri.WSTestSessionBean.exeWS(WSTestSessionBean.java:81)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
I created this SessionBean as follows:
I created DCs for EJB and created SessionBean in EJB DC.
I imported a WSDL file(WS-RM web service) from Service Registory and
I created service clients and Service References.
After that I implemented SessionBean to call web service checking with this help.
http://help.sap.com/saphelp_nwce72/helpdata/en/44/4d2bb1c6b00597e10000000a155369/frameset.htm
After deploying this EJB,I configured properties in nwa.
Thanks
Yuichi

Yuichi
Did you manage to solve this? I'm doing something similar and seeing the same problem, although they're up to 7.3 SP7.
Any help greatly appreciated.
Lewis

Exception (org.apache.axis2.AxisFault: Server) when accessing Web-Service

Hi all,
I have read already some interesting posts on Java implementation for Oracle CoD Web Services.
Somehow I am stuck and can't find a way out.
I try to access the LeadQuery command via the following code:
          String sessionCookie = logon(
                    "https://secure-ausomxapa.crmondemand.com/Services/Integration",
                    username, password);
          LeadStub stub;
          try {
               stub = new LeadStub(
                         "https://secure-ausomxapa.crmondemand.com/Services/Integration;jsessionid="
                                   + sessionCookie);
               // ServiceClient client = stub._getServiceClient();
               // client.getOptions().setManageSession(true);
               // client.getOptions().setProperty("jsessionid", sessionCookie);
               // client.getOptions().setUserName(username);
               // client.getOptions().setPassword(password);
               LeadQueryPage_Input leadQueryPage_Input = new LeadQueryPage_Input();
               ListOfLeadQuery listOfLeadQuery = new ListOfLeadQuery();
               QueryType queryType = new QueryType();
               queryType.setString("LIKE 'A*'");
               LeadQuery leadQuery = new LeadQuery();
               leadQuery.setCompany(queryType);
               listOfLeadQuery.setLead(leadQuery);
               leadQueryPage_Input.setListOfLead(listOfLeadQuery);
               LeadQueryPage_Output leadQueryPage_Output = stub
                         .LeadQueryPage(leadQueryPage_Input);
          } catch (AxisFault e) {
               e.printStackTrace();
          } catch (RemoteException e) {
               e.printStackTrace();
          } catch (Exception e) {
               e.printStackTrace();
               System.err.println("\n\n\n");
          logoff("https://secure-ausomxapa.crmondemand.com/Services/Integration",
                    sessionCookie);
Logging In and Out is no problem, runs like music. But whenever LeadQueryPage is called, I just receive the following error:
org.apache.axis2.AxisFault: Server
     at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:512)
     at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:370)
     at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:416)
     at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:228)
     at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
     at crmondemand.LeadStub.LeadQueryPage(LeadStub.java:1026)
     at CODconnection.main(CODconnection.java:58)
I'm using Eclipse 3.4.2 with AXIS2 1.4, and the Eclipse Plug-In for AXIS 1.3 (with some small patch to get it to work).
I downloaded the custom WSDL from Oracle CoD (CRM On Demand) Admin page and used the AXIS-Wizard in Eclipse to transform it to Java.
For that, I already tried the -g option (which is "Create everything - Client and Server" in the wizard).
Anyone has a clue what the problem might be?
Btw.: I downloaded also V1.0 WSDL to check if that works. Some problem.
Found out that just the error reporting sucks and at the end the Server missed the correct Authentification.
Funnily I just did what I read a couple of time. With this small bit of code it works:
               ServiceClient client = stub._getServiceClient();
               client.getOptions().setManageSession(true);
               client.getOptions().setProperty(HTTPConstants.HEADER_COOKIE, "jsessionid="+sessionCookie);
               client.getOptions().setUserName(username);
               client.getOptions().setPassword(password);
-----

You are missing the end point location. See the sample client below:
MyHelloMyHelloSOAP11PortStub stub = new MyHelloMyHelloSOAP11PortStub("http://localhost:8080/axis2/services/MyHello");
               MyHelloMyHelloSOAP11PortStub.SayHello hello = new MyHelloMyHelloSOAP11PortStub.SayHello();
               hello.setS("ABCD");
               MyHelloMyHelloSOAP11PortStub.SayHelloResponse resp=stub.sayHello(hello);
               System.out.println("Response from Web Service "+resp.get_return());

Username and password token retrieval from SOAP web services

We are implementing one JAX-WS Web services which requires to retrieve the username and password in SOAP header elements and use those for further use/processing.
When we are retrieving username/password it’s coming as null. Please help ...
if (Boolean.FALSE.equals(context.get(MessageContext.MESSAGE_OUTBOUND_PROPERTY))) {
try {
SOAPMessage sm = context.getMessage();
//SOAPEnvelope envelope = context.getMessage().getSOAPPart().getEnvelope();
SOAPEnvelope envelope = sm.getSOAPPart().getEnvelope();
SOAPHeader sh = envelope.getHeader();
System.out.println("Message: "+envelope);
System.out.println("Envelope: "+envelope);
System.out.println("Header: "+sh.toString());
Iterator it = sh.examineAllHeaderElements();
while(it.hasNext()){
System.out.println(it.next());
String username;
username = sh.getAttribute("Username");
// username = sh.getAttributeValue("Username");
//String password = sh.getAttribute("Password");
System.out.println("uid:"+username);
//System.out.println("pass: "+password);
context.put("Username", username);
//context.put("Passsword", password);
// default scope is HANDLER (i.e., not readable by SEI
// implementation)
context.setScope("Username", MessageContext.Scope.APPLICATION);

<S12:Envelope xmlns:S11="..." xmlns:wsse="..." xmlns:wsu= "...">
<S12:Header>
<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<wsse:UsernameToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<wsse:Username>TestUser</wsse:Username>
<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">TestPassword</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>
</S12:Header>
</S12:Envelope>

Calling a asynchronous web service method

I am designing a game using web services(asp.net)
one player write to array and waite till other modify that
array.Assume i am player 1 and wait till player 2 modify array
in web service.Writing to array part is working.But reading part
is not working .I implement asynchronous call to web service
call reLabelAsync and pass argument 1.That means i am player 2
modify the array and return to my program onces other player(player 1)
modify the array.And modify my program according his updates.
private void jLabel1MouseClicked(java.awt.event.MouseEvent evt) {
jLabel1.setText("O");//this my player
// jProgressBar1.setIndeterminate(true);
writeArra(2,1);//this is working
reLabelAsync(1);
public static void main(String args[]) {
java.awt.EventQueue.invokeLater(new Runnable() {
public void run() {
new NewJFrame().setVisible(true);
public void reLabelAsync(int player){
// Call Web Service Operation(async. callback)
as.Service service = new as.Service();
as.ServiceSoap port = service.getServiceSoap();
// TODO initialize WS operation arguments here
javax.xml.ws.AsyncHandler<as.ReLabelResponse> asyncHandler = new javax.xml.ws.AsyncHandler<as.ReLabelResponse>() {
public void handleResponse(javax.xml.ws.Response<as.ReLabelResponse> response) {
// java.awt.EventQueue.invokeLater(new Runnable() {
// public void run() {
String s;
try {
// TODO process asynchronous response here
s = response.get().reLabelResult();
s=removeTags(s);//this to remove tags.working
System.out.println(s);
if (s=="1"){
jLabel1.setText("X");//update my program
else{
jLabel2.setText("X");//update my program
} catch(Exception ex) {
// TODO handle exception
jProgressBar1.setIndeterminate(false);
can some one please help me. I try to call asynchronous method in loop.
I think it's the way to do this. But it didn't work.Thanks..

Looking a bit at your history here... this is the fourth go around at least for dancing around this question.
To summarise the advice given to you previously "Please stop blathering on about asynchonous blah blah and start by sending and recieving a message correctly"
You really seem way over your head here. An empty catch block is a bad bad bad sign. You can run before you can walk and right now you're having problems crawling.

Which BAPI is implemented in a given Web Service?

Similar Messages

Maybe you are looking for