Generating Web Services bases on the WSDL interface

Hello everybody.
my question is.
How can i generated all the java classes of a web services basen on a wsdl definition.
how can i generate a simple java classe or how can i generate a ejb session, thet serve as a end point for my services
any sugestion could be so helpfull

The tool used to generate java class from WSDL is vender dependent, because each JAX-RPC engine is implemented differently (even they have to implement all JAX-RPC API, but low level stub call is engine dependent).
So to generate you class from WSDL, you have to have tool first. Since all J2EE 1.4 app servers are required to have implementation of JAX-RPC API and its run time engine (but many J2EE 1.3 app servers also included JAX-RPC API and engine) , what you want to do could be to find any J2EE 1.4 app server, such as WAS or WSAD, or Sun's Application Server PE 8.1, read their examples carefull and you will find the way how to generate classes from WSDL.

Similar Messages

How to generate web services for OAS with wsdl extension

Hi,
I wanted to know how to generate web services from Oracle Application Server especially with .wsdl extension and with document/literal style.
I know that earlier there was a tool called SmartConnect from BEA WebLogic.
But that will work only with ALSB (Aqua logic Service Bus). I guess that ALSB has been renamed as Oracle Service Bus by Oracle after the acquisition of WebLogic. My question is what is the new name for the SmartConnect Tool from WebLogic, which generates wsdl very easily from Oracle database.
I am unable to know the new name for SmartConnect and how to download that tool from Oracle web site.
Also, I want to know, whether there is any other way to generate the wsdl from Oracle, if so, please let me know.
Regards
Raman

Hi Jeethandra,
Please refere to the below link might be some help.
[http://help.sap.com/saphelp_mdmgds55/helpdata/en/45/069152856241e1e10000000a1553f6/frameset.htm]
regards
shankar

Where is the Web Service fault in the WSDL definition?

Hi all,
I have created a Web Service out of function module, using the SAP standard wizard. The creation went fine, I can receive the WSDL file via the SOAMANAGER application. But: In this WSDL file it seems that the Web Service faults (i.e. the exceptions of the underlying function module) are not part of the "wsdl:operation" definition (even if they and their format are defined in that file).
Is that a bug or do I miss something here?
How are the faults integrated in the response definition of the service?
Thanks in advance for your help!
Kind regards, Matthias

solved, see SAP note 1270688

Invoking Web Services Without Using the WSDL File - RPC

I would apprecite if someone can provide sample code
for RPC client for WeatherEJB sample code without using wsdl file.
Thanks ,
ag

Hi,
Attached is a small program that calls a service CurrencyExchangeRate
registered at www.xmethods.com.
The program uses pure java to call the service.
Hope that helps
Thanks
Amit Chauhan
ag <[email protected]> wrote in message
news:3c59734d$[email protected]..
>
I would apprecite if someone can provide sample code
for RPC client for WeatherEJB sample code without using wsdl file.
Thanks ,
ag[webservice.java]

Workshop 10.1 WSDL - cannot publish generated Web service

I'm trying to create a Web service starting from a WSDL using the doc Web Service Development Starting Points ([url http://edocs.bea.com/wlw/docs101/guide/webservices/conWebServiceDevelopmentCycle.html]http://edocs.bea.com/wlw/docs101/guide/webservices/conWebServiceDevelopmentCycle.html) .
I create a Web service project, import my WSDL into my src directory, click on the WSDL and select Web Services > Generate Web Service.
Workshop generates the implementation class and the JAR file, just like the doc describes.
When I try to publish it to my server in the IDE< however, I get an error :
Error with publish task 'WebServicesProjectBuildTask'.
Web services in WLW101Example_WebServiceFromWSDL_JAXRPC have errors.
java.lang.UnsupportedMethodException: Method not implemented.
Error(s) occurred during publish assembly. No modules will be published.
The operation in the WSDL has been implemented, and the class is pretty simple :
package com.kohls.services;
import javax.jws.WebService;
import weblogic.jws.*;
import com.kohls.is.soa.x09.meta.*;
* KohlsDynamicWsPortTypeImpl class implements web service endpoint interface KohlsDynamicWsPortType */
@WebService(serviceName = "KohlsDynamicWS",
            targetNamespace = "http://www.kohls.com/is/soa/0.9/meta",
            endpointInterface = "com.kohls.services.KohlsDynamicWsPortType")
@WLHttpTransport(contextPath = "is/soa/0.9", serviceUri = "meta", portName = "KohlsDynamicWsBinding")
public class KohlsDynamicWsPortTypeImpl implements KohlsDynamicWsPortType
public KohlsDynamicWsPortTypeImpl()
public com.kohls.is.soa.x09.meta.KohlsMessageDocumentType process(com.kohls.is.soa.x09.meta.KohlsMessageDocumentType Message)
    KohlsMessageDocumentType message = null;
    message = new KohlsMessageDocumentType();
    MessageHeaderType        header = new MessageHeaderType();
    MessagePayloadType       payload = new MessagePayloadType();
    message.setHeader(header);
    message.setPayload(payload);
    return message;
}The only thing unusual here is that the @WLHttpTransport annotation overrides the context, but I don't see that as a problem.
Is there something simple I am missing here ? I guess I'm always surprised when Workshop cannot publish something it generates, but there is usually a reason - library setting or something.
I'd appreciate any advice !
Edited by ethan_kohls at 01/10/2008 11:59 AM

Hi Ethan
I tested it using Workshop10.0Mp1 and didn't see any issue with publish.
Here are the steps I followed:
1) Create a default webservice project with default facets.(no ear)
2) Drop the business and meta folder and under project/src folder
3) Create a test package under src
4) Right click on the wsdl and choose generate webservice and create it under the test folder
5) Replace the process method implementation with the one you have here
6) Create a 10.0mp1 Workshop server (please make sure you create a workshop server and not wls server) and deploy the app to the server
I was able to run the webservice successfully.
Let me know if I am doing anything different from you.
Vimala-

Parameter names change when generating web service from WSDL

Hi,
I have a problem with BEAs web services that I'm hoping someone can help me with.
I have a
WSDL file, and from that I want to generate a web service implementation and a
web service
client. In the WSDL file, I have a message defined like this:
<message name="someRequest">
<part xmlns:partns="http://www.w3.org/2001/XMLSchema" type="partns:base64Binary"
name="data"/>
</message>
I generate the server using the server using the wsdl2service Ant task, I implement
the necessary classes, and I deploy it. When I access the deployed web service,
the parameter name has changed, from "data" to "bytes". If I access the WSDL file
of the deployed web service, it says:
<message name="someRequest">
<part xmlns:partns="http://www.w3.org/2001/XMLSchema" type="partns:base64Binary"
name="bytes"/>
</message>
This happens for all parameters, string parameters are renamed to "string", base64Binary
parameters are renamed to "bytes", etc...
This poses a problem to me, because if I generate a web service client from the
original WSDL file, it will not be able to talk to my web service. Is there any
way of forcing a web service generated from a WSDL file to keep the parameter
names of the original WSDL file?
Any help in this is greatly appreciated.
Regards,
Petter

From a quick look of your WSDL, it seams that you are mixing document-literal-bare and document-literal-wrapped flavor of web services. WSA may be able to do a better job at working around this mixed flavors than JDeveloper.
If you have hand crafted this WSDL, I would recomend that you spend some time looking at the way WSDL are generated, with the java-first mode (or bottom-up), then author the WSDL you need for the final service.
Here are sample of bare-style :
<xsd:element name="getPupilAddressResponse" type="xsd:string"/>
<xsd:element name="getPupilAddressRequest" type="xsd:int"/>
Wrapped will looks like that:
<xsd:element name="getSENLevelResponse">
<xsd:complexType>
<xsd:sequence maxOccurs="1" minOccurs="1">
<xsd:element name="LevelDetails" type="tns:SENLevelRecord"/>
<xsd:element name="RecordCount" type="xsd:int">
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
Hope this helps,
Eric

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

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

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

Error generating Web Service control in Workshop 9.2 from any wsdl

When trying to generate web service control from service control wizard I get the following error:
An error was encountered while generating types: null
The full stack trace is:
<pre>java.lang.reflect.InvocationTargetException
     at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:327)
     at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:830)
     at com.bea.wlw.controls.service.ui.GenerateSCWizard.performFinish(GenerateSCWizard.java:213)
     at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:676)
     at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:349)
     at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:556)
     at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90)
     at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
     at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:843)
     at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3125)
     at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2758)
     at org.eclipse.jface.window.Window.runEventLoop(Window.java:809)
     at org.eclipse.jface.window.Window.open(Window.java:787)
     at org.eclipse.ui.internal.actions.NewWizardShortcutAction.run(NewWizardShortcutAction.java:110)
     at org.eclipse.jface.action.Action.runWithEvent(Action.java:996)
     at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:538)
     at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488)
     at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:400)
     at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
     at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:843)
     at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3125)
     at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2758)
     at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1699)
     at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1663)
     at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:367)
     at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143)
     at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:103)
     at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:226)
     at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376)
     at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:163)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.eclipse.core.launcher.Main.invokeFramework(Main.java:334)
     at org.eclipse.core.launcher.Main.basicRun(Main.java:278)
     at org.eclipse.core.launcher.Main.run(Main.java:973)
     at org.eclipse.core.launcher.Main.main(Main.java:948)
Caused by: java.lang.NullPointerException
     at com.bea.wlw.controls.service.ui.GenerateSCWizard$Finisher.run(GenerateSCWizard.java:501)
     at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:113)
</pre>
I have tried different wsdls simple and complex and still getting the same error. What could be the problem? Is it a bug or my misconfiguration? Has anybody succeded to generate service control in workshop 9.0 and above?

Did you also get a CrashWeb dialog?
Andrey Adamovich wrote:
When trying to generate web service control from service control wizard I get the following error:
An error was encountered while generating types: null
The full stack trace is:
<pre>java.lang.reflect.InvocationTargetException
     at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:327)
     at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:830)
     at com.bea.wlw.controls.service.ui.GenerateSCWizard.performFinish(GenerateSCWizard.java:213)
     at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:676)
     at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:349)
     at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:556)
     at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90)
     at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
     at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:843)
     at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3125)
     at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2758)
     at org.eclipse.jface.window.Window.runEventLoop(Window.java:809)
     at org.eclipse.jface.window.Window.open(Window.java:787)
     at org.eclipse.ui.internal.actions.NewWizardShortcutAction.run(NewWizardShortcutAction.java:110)
     at org.eclipse.jface.action.Action.runWithEvent(Action.java:996)
     at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:538)
     at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488)
     at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:400)
     at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
     at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:843)
     at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3125)
     at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2758)
     at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1699)
     at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1663)
     at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:367)
     at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143)
     at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:103)
     at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:226)
     at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376)
     at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:163)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.eclipse.core.launcher.Main.invokeFramework(Main.java:334)
     at org.eclipse.core.launcher.Main.basicRun(Main.java:278)
     at org.eclipse.core.launcher.Main.run(Main.java:973)
     at org.eclipse.core.launcher.Main.main(Main.java:948)
Caused by: java.lang.NullPointerException
     at com.bea.wlw.controls.service.ui.GenerateSCWizard$Finisher.run(GenerateSCWizard.java:501)
     at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:113)
</pre>
I have tried different wsdls simple and complex and still getting the same error. What could be the problem? Is it a bug or my misconfiguration? Has anybody succeded to generate service control in workshop 9.0 and above?

Preserve original WSDL when generating Web Service

When generating a Web Service using an existing WSDL, I need to preserve the structure of the original WSDL as much as possible.
The existing WSDL is generated using Apache AXIS. We're hoping to develop a new Web Service using the existing WSDL in JDeveloper, and deploy to OAS. Because of the nature of the client system, the structure of the original WSDL needs to be preserved as much as possible when deploying the new Web Service.
Is this possible using JDeveloper?
-a

Thanks for the response Yogesh.
I'd seen the top-down approach documentation for JDeveloper, but not the command-line version from OAS. I've been able to successfully develop a top-down service using JDeveloper, the problem is that the resulting WSDL file for the new Web Service is too different in structure from the original. Functionally, I believe they define the same thing. It's a bit contrived, but I'm trying to match the form and function of the original WSDL with the new one generated by a top-down approach.
I'll give the command line tools a try, thanks very much for the link.

I generated web service from function module.Where can I find .wsdl file ?

Hi,
I generated web service from function module.
Where can I find .wsdl file ?
I want to use .wsdl file in .Net application.
Thanks.

Hii Cemil Bozlagan,
All Remote enabled Function Modules in Web AS 6.20 and Above are available as Webservices and the WSDL documents are available in the web service repository at
[http://<host>:<port>/sap/bc/bsp/sap/webservicebrowser/search.html]
Find the respective BAPI.
Click on the WSDL link in the browser and download the WSDL document and use it as per the requirement
Regards,
Varun

Generate web services form WSDL as part of build process

Hi, I am using Jdev drop7build2.
I have wsdl and schema types. From Jdeveloper we can generate webservices using "web services from WSDL". But I want to generate web services as part of my build process.
Is it possible to do this as part of build process ? any ant tasks or API etc ?
Thanks
-Siva

Arrrgggg
Drop 7 is an Oracle-internal build, as far as I know.
You should be asking on an internal Oracle list.
John

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.

Invoke a business service base in a WSDL with customer WS-Security Policy

Customer write a Web service (Refer to the attachment file “HTTPS_PartyServicePortType.WSDL”)which declare a WS-Security Policy and apply this it to WS binding ,How can I generate a business service base in this WSDL and invoke it successfully?
When create a business service in OSB, we get a error with below messages
[[OSB Kernel:398133]The service is based on WSDL with Web Services Security Policies that are not natively supported by Oracle Service Bus. Please select OWSM Policies - From OWSM Policy Store option and attach equivalent OWSM security policy. For the Business Service, either you can add the necessary client policies manually by clicking Add button or you can let Oracle Service Bus automatically pick and add compatible client policies by clicking Add Compatible button.
After enhanced the OSB domain with OWSM extension, we found the OOTB OWSM defined cannot support the HttpsToken and OSB cannot support below WS-Policy defined in OWSM, refer to http://docs.oracle.com/cd/E21764_01/doc.1111/e15866/owsm.htm#OSBDV1681
51.2.8.1 Unsupported Assertion
•     binding-permission-authorization
•     http-security
•     OptimizedMimeSerialization (MTOM)
•     RMAssertion (Reliable Messaging)
•     sca-component-authorization
•     sca-component-permission-authorization
•     UsingAddressing
•     wss-saml-token-bearer-over-ssl (Authentication)
it means that we cannot generate a web service with customer WS-security Policy
The WS-Security Policy is shown as below:
<wsp:Policy wsu:Id="WSHttpBinding_IPartyServicePortType_policy">
<wsp:ExactlyOne>
<wsp:All>
<sp:TransportBinding xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
<wsp:Policy>
<sp:TransportToken>
<wsp:Policy>
<sp:HttpsToken RequireClientCertificate="false"/>
</wsp:Policy>
</sp:TransportToken>
<sp:AlgorithmSuite>
<wsp:Policy><sp:Basic256/></wsp:Policy>
</sp:AlgorithmSuite>
<sp:Layout><wsp:Policy><sp:Strict/></wsp:Policy></sp:Layout>
</wsp:Policy>
</sp:TransportBinding>
<wsaw:UsingAddressing/>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
BestRegards!
Simon

Hi
According to
http://e-docs.bea.com/wls/docs90/webserv/annotations.html#1050414
If you are going to publish the policy file in the Web Service archive, the policy XML file must be located in either the META-INF/policies or WEB-INF/policies directory of the EJB JAR file (for EJB implemented Web Services) or WAR file (for Java class implemented Web Services), respectively.
Can you make sure the policy file is in there?
Also there is a sample from the developer at http://dev2dev.bea.com/blog/jlee/archive/2005/09/how_to_use_anno.html
Vimala-

Error when generating Web Services Proxy for SCA Application Module

Hello,
I'm trying to create Web Services for a simple Application Module with JDeveloper 11g (11.1.1.3.0).
I start a new ADF Project, I create an Application Module as simple as possible : it contains only a simple View Object on the DEPT Entity.
On my Application Module, I choose "Service Interface" and I add my View Object in the service interface.
I test my Web Service in the Embedded Weblogic Server, it works well. (I succeed in using the Get operation, for example).
But when I try to generate a Web Service proxy (right-click on the WSDL File -> Generate Web Service Proxy), It always fail with such errors :
oracle.jdeveloper.webservices.tools.WsdlValidationException: Error creating model from wsdl "file:/C:/JDeveloper/mywork/ApplicationAppelServiceSCA/Model/src/model/common/AppModuleService.wsdl": 'unset' is already defined'Bytes' is already defined'ref' is already defined'Duration' is already defined'Types' is already defined'Character' is already defined'type' is already defined'Day' is already defined'nestedInterfaces' is already defined'Date' is already defined'datagraph' is already defined'Type' is already defined'Integer' is already defined'ModelsType' is already defined'ChangeSummaryType' is already defined'instanceClass' is already defined'Month' is already defined'DataObject' is already defined'javaClass' is already defined'LongObject' is already defined'DateTime' is already defined'dataObject' is already defined'YearMonth' is already defined'ShortObject' is already defined'Long' is already defined'types' is already defined'JavaInfo' is already defined'IntObject' is already defined'Boolean' is already defined'DoubleObject' is already defi...
Can someone help me to understand this error ?
i never manually edited the WSDL File, so I don't understand why the generated WSDL or XSD files might contain errors.
Thanks for your Help,
Laurent

We have the same problem, and the problem was in the xsd import:
The wdsl import a schema that import other schema, the second import use a relative path, that was wrong.
So check the xsd import sequence....

MII doesn't generate web service properly if transaction has XML typed prm.

Hi,
MII doesn't generate web service properly if transaction has XML typed input/output parameter.
I did lots of test.
When i do add web reference from vs.Net, there is no xml structure of input/output parameter.
I use MII version 12.05
How can it be solved?
Thanks.
Below is log in http://host:port/nwa
java.util.zip.ZipException: error in opening zip file
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:111)
at java.util.zip.ZipFile.<init>(ZipFile.java:127)
at com.sapmarkets.bam.jmxadapter.AbstractLog.getArchiveInfo(AbstractLog.java:328)
at com.sapmarkets.bam.jmxadapter.AbstractLog.getArchives(AbstractLog.java:454)
at com.sapmarkets.bam.jmxadapter.AbstractLog.getArchives(AbstractLog.java:477)
at sun.reflect.GeneratedMethodAccessor1024.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.getAttribute(DefaultMBeanInvoker.java:129)
at javax.management.StandardMBean.getAttribute(StandardMBean.java:229)
at com.sap.pj.jmx.server.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1296)
at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.getAttribute(MBeanServerWrapperInterceptor.java:181)
at com.sap.engine.services.jmx.CompletionInterceptor.getAttribute(CompletionInterceptor.java:309)
at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.getAttribute(BasicMBeanServerInterceptor.java:169)
at com.sap.jmx.provider.ProviderInterceptor.getAttribute(ProviderInterceptor.java:195)
at com.sap.engine.services.jmx.RedirectInterceptor.getAttribute(RedirectInterceptor.java:232)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getAttribute(MBeanServerInterceptorChain.java:124)
at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.getAttribute(MBeanServerSecurityWrapper.java:234)
at com.sap.engine.services.jmx.ClusterInterceptor.getAttribute(ClusterInterceptor.java:522)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getAttribute(MBeanServerInterceptorChain.java:124)
at com.sapmarkets.bam.logcontroller.jmx.LogControllerFacade.getLogInfo(LogControllerFacade.java:227)
at com.sapmarkets.bam.logcontroller.jmx.LogControllerFacade.getLogInfosWithPattern(LogControllerFacade.java:193)
at com.sapmarkets.bam.logcontroller.jmx.LogControllerFacade.getLogInfos(LogControllerFacade.java:174)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.getAttribute(DefaultMBeanInvoker.java:129)
at javax.management.StandardMBean.getAttribute(StandardMBean.java:229)
at com.sap.pj.jmx.server.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1296)
at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.getAttribute(MBeanServerWrapperInterceptor.java:181)
at com.sap.engine.services.jmx.CompletionInterceptor.getAttribute(CompletionInterceptor.java:309)
at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.getAttribute(BasicMBeanServerInterceptor.java:169)
at com.sap.jmx.provider.ProviderInterceptor.getAttribute(ProviderInterceptor.java:195)
at com.sap.engine.services.jmx.RedirectInterceptor.getAttribute(RedirectInterceptor.java:232)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getAttribute(MBeanServerInterceptorChain.java:124)
at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.getAttribute(MBeanServerSecurityWrapper.java:234)
at com.sap.engine.services.jmx.ClusterInterceptor.getAttribute(ClusterInterceptor.java:522)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getAttribute(MBeanServerInterceptorChain.java:124)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.tc.logviewer.mbean.LocalLVMBeanServer.invoke(LocalLVMBeanServer.java:73)
at $Proxy139.getAttribute(Unknown Source)
at com.sapmarkets.bam.application.logdepot.AbstractLogDepot.getAttribute(AbstractLogDepot.java:236)
at com.sapmarkets.bam.application.logdepot.AbstractLogDepot.getLogDescriptors(AbstractLogDepot.java:84)
at com.sap.tc.logviewer.mbean.ServerModelLogDepot.getLogDescriptors(ServerModelLogDepot.java:79)
at com.sap.tc.logviewer.mbean.ServerModelLogDepotGroup$GetLogDescriptorsTask.run(ServerModelLogDepotGroup.java:60)
at com.sap.tc.logviewer.mbean.ServerModelLogDepotGroup.execute(ServerModelLogDepotGroup.java:173)
at com.sap.tc.logviewer.mbean.ServerModelLogDepotGroup.getLogDescriptors(ServerModelLogDepotGroup.java:119)
at com.sap.tc.logviewer.mbean.LogviewerServer.getLogs(LogviewerServer.java:137)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
at javax.management.StandardMBean.invoke(StandardMBean.java:286)
at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:776)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
at com.sap.tc.logviewer.client.j2ee.J2EELogviewerServerInvoker.invoke(J2EELogviewerServerInvoker.java:111)
at com.sap.tc.logviewer.client.j2ee.J2EELogviewerServerProxy.getLogs(J2EELogviewerServerProxy.java:105)
at com.sap.tc.logviewer.client.base.LogviewerClientImpl$GetLogs.run(LogviewerClientImpl.java:442)
at java.lang.Thread.run(Thread.java:534)

I have an XML input in my transaction. I was able to generate the WSDL without problems. But need to know how to test it by sendig in some XML data. Probably, we could both be helping each other in the process.
Regards,
Chanti.

Generating Web Services bases on the WSDL interface

Similar Messages

Maybe you are looking for