Exposing as Web Services

I have checked with weblogic Server 8.1,
supposing exposing Java Components as web services.
I have checked with the examples.It is quite easily achievable.
But what i want to know as what mentioned in
http://www.javaworld.com/javaworld/jw-08-2004/jw-0802-ejbws.html by using the webservices.xml(deployement descriptor file) which is not used in the current version of weblogic 8.1.Is the use of webservices.xml to expose Java componenents as web services specific to Weblogic Serever 9.0?If yes then how?

HIIII...
Use this link ..
it will be usefull 4 u.
[http://help.sap.com/saphelp_nw2004s/helpdata/en/df/e6b74253ffda11e10000000a155106/frameset.htm]
thanks..
Regards
Mayank Saxena

Similar Messages

How to expose a web service to the outside world?

Hello,
i have created a Web service from a Session bean and successfully published it on one of my UDDI registries using the Admin tool.
At this point, what do I need to do further in order to expose this Web service not just in our LAN but to the outside world?
Roy

Offcourse it should be published at UDDI.
Four play key roles in Web services: Universal Description, Discovery and Integration (UDDI), Web Services Description Language (WSDL), Web Services Inspection Language (WSIL), SOAP, and Web Services Interoperability (WS-I).
The UDDI specification defines open, platform-independent standards that enable businesses to share information in a global business registry, discover services on the registry, and define how they interact over the Internet.
See this link too:
http://help.eclipse.org/help32/index.jsp?topic=/org.eclipse.jst.ws.consumption.ui.doc.user/concepts/cwsdlud.html
Regards, Suresh KB

Steps to expose a web service without using SR

Hello,
How can I expose a web service without using the service registry? Is there some documentation for this process?
Thanks,
Matt

Thanks for the response. Although, I do not have an * in the Sender Agreement.
Here is the situation:
When I attempt to reach the URL for my Web Service but using NWA instead of the Service Call I get into NWA.
https://xxxxx.steelcasedev.com/nwa
Result: Success
When I use SOAPSonar to run this URL I get the CPA error:
https://xxxxx.steelcasedev.com//XISOAPAdapter/MessageServlet?senderParty=&senderService=WSProcurement_Async_Sender&receiverParty=&receiverService=Steelcase_Dev&interface=WSProcure_Out&interfaceNamespace=urn:steelcasedev.com:wsprocure:xsuppliers
Result: Error
<context>XIAdapter</context>
          <code>ADAPTER.JAVA_EXCEPTION</code>
          <text><![CDATA[
com.sap.aii.af.service.cpa.CPAException: com.sap.aii.af.service.cpa.impl.exception.CPALookupException: Couldn't retrieve inbound binding for the given P/S/A values: FP=;TP=;FS=WSProcurement_Async_Sender;TS=Steelcase_SAPR3_D01;AN=WSProcurement_Out;ANS=urn:steelcase.com:wsprocurement:xml2suppliers;
     at com.sap.aii.af.service.cpa.impl.lookup.CommonLookup.checkForError(CommonLookup.java:53)
     at com.sap.aii.af.service.cpa.InboundRuntimeLookup.getBinding(InboundRuntimeLookup.java:411)
     at com.sap.aii.af.service.cpa.impl.lookup.AbstractLookupManager.getBinding(AbstractLookupManager.java:714)
     at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:430)
The sender adapter is active in ID but in RTWB it is "Started but Inactive". I have found that this status could be related to the fact that I have not had a successful transaction for that channel yet.
My NW Admin says he found this error:
Marked transaction for rollback for message 0015605e-09d7-1ddf-94f7-d5031c019713(INBOUND). Reason: Channel has been configured as inactive and cannot accept messages
I am quite confused.
Thanks,
Matt

Are all RFCs and BAPIs automatically exposed as web services?

Hello,
Our product helps business users exchange data with SAP. We use standard RFCs and BAPIs to communicate with SAP. This is a .NET application although my question is not specific to .NET.
It seems SAP obsolete their .NET connector in near future. The emphasis is on web services. This is a great move. We can simply drop using the .NET connector and start using the web services. However, I have a few doubts:
1. RFCs and BAPIs are automatically exposed for remoting. When the customer installs our application, it just works out of the box. Customers do not have to make any configuration changes to SAP to expose RFCs and BAPIs.
In the new world, are all RFCs and BAPIs automatically exposed as web services or one has to go through each RFC/BAPI and expose it explicitly?
2. Is there a comprehensive WSDL schema available anywhere for all the RFCs/BAPIs?
3. Are there any other web services (besides RFCs/BAPIs) that SAP Netweaver exposes? Where can I get more information?
Thank you in advance for your help.
Regards,
Pradeep

Darryl,
Thank you for your help or at least trying to help me. However, you left me with more questions than answers:-(.
1. "Old" does not mean "bad." Each RFC/BAPI serves a specific function. If some RFC is being obsoleted, there must be a replacement documented somewhere. Is there one?
2. I can look into SE80 (and other transactions) to see what is exposed. However, what I need to understand is what is SAP's stance on exposing standard web services.
Can others please share your thoughts?
Regards,
Pradeep

EJB exposed as web services

I am very new to web services.
I understand that a Stateless bean can be exposed using RPC style web services.
But I want to know if a stateless session bean can be accessed by EJB client and Web service client (java or non-java) simultaneously. ?
i.e. 1. Can same bean serve two types of client simultaneously.(java and non-java client)
2. Does this web service accept complex java object as input parameters. and how?

Hi Patrik,
> Exception raised from invocation of public void com.sap.sia.serviceMonitor.ServiceMonitorBean.initPostConstruct() method on bean instance com.sap.sia.serviceMonitor.ServiceMonitorBean@5a8ab489 ... ; nested exception is: java.lang.NullPointerException
The NPE occurs in the bean code, in the initPostConstruct() method or some other method it calls. Unfortunately, its stack trace is not available above, but you should be able to find it in the defaultTrace file.
HTH!
\-- Vladimir

Error: BLS is exposed as Web Service

Hi All,
I have one small BLS which will get two integers as input params and yield their Sum as output param with Integer Data type. This BLS itself is working fine. Now while generating WSDL file on this BLS, I have use the URL like following
http://<server>/XMII/WSDLGen/<trasnactionpathname>/<transactionname> which is running fine in browser session itself
But when Iu2019m trying to test the same WSDL in WSNavigator from Netweaver, this is giving error as follow
The markup in the document following the root element must be well-formed
And while checking the log in NW this is saying as follows
An error occurred while loading WSDL: http://<Host>:<Port>/XMII/WSDLGen/Default/<Package>/<BLS>
[EXCEPTION]
com.sap.engine.services.webservices.jaxrpc.exceptions.WebserviceClientException: GenericServiceFactory initialization problem. [Problem with WSDL file parsing. See nested message.]
at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService_NewInstance(GenericServiceFactory.java:667)
at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService_NewInstance(GenericServiceFactory.java:130)
at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:119)
at com.sap.esi.esp.wsnavigator.ManualTestView.createServiceByWSDL(ManualTestView.java:414)
at com.sap.esi.esp.wsnavigator.ManualTestView.onEventWSDLSelected(ManualTestView.java:1531)
at com.sap.esi.esp.wsnavigator.wdp.InternalManualTestView.wdInvokeEventHandler(InternalManualTestView.java:526)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:131)
at com.sap.tc.webdynpro.progmodel.components.Component.fireEvent(Component.java:488)
at com.sap.esi.esp.wsquery.ui.wsquerycomp.wdp.InternalWSQueryComp.wdFireEventWSDLSelected(InternalWSQueryComp.java:571)
at com.sap.esi.esp.wsquery.ui.wsquerycomp.WSQueryComp.searchByWSDL(WSQueryComp.java:826)
at com.sap.esi.esp.wsquery.ui.wsquerycomp.WSQueryComp.getSelectedService(WSQueryComp.java:459)
at com.sap.esi.esp.wsquery.ui.wsquerycomp.wdp.InternalWSQueryComp.wdInvokeMethod(InternalWSQueryComp.java:455)
at com.sap.tc.webdynpro.progmodel.generation.ExternalControllerPI$ExternalInterfaceInvocationHandler.invoke(ExternalControllerPI.java:339)
at $Proxy1834.getSelectedService(Unknown Source)
at com.sap.esi.esp.wsnavigator.ManualTestView.onActionStepChanged(ManualTestView.java:1314)
at com.sap.esi.esp.wsnavigator.ManualTestView.onActionNext(ManualTestView.java:1277)
at com.sap.esi.esp.wsnavigator.wdp.InternalManualTestView.wdInvokeEventHandler(InternalManualTestView.java:486)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:131)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:72)
at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.doHandleActionEvent(ProcessingEventPhase.java:156)
at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.execute(ProcessingEventPhase.java:91)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:162)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:110)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:97)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:512)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:52)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1549)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1363)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToApplicationDoProcessing(AbstractExecutionContextDispatcher.java:154)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForAppProcessing.doService(DispatchHandlerForAppProcessing.java:35)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:127)
at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:95)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToApplicationDoProcessing(ExecutionContextDispatcher.java:114)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:80)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:618)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:649)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingStandalone(ApplicationSession.java:570)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:309)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:743)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:258)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:259)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToRequestManager(AbstractExecutionContextDispatcher.java:202)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.doService(DispatchHandlerForRequestManager.java:38)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:127)
at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:95)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToDispatcherContext(ExecutionContextDispatcher.java:146)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:92)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:104)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:61)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:37)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:486)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:298)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:396)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:385)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:76)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:243)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
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.MemoryStatisticFilter.process(MemoryStatisticFilter.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.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
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:428)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.ProxyGeneratorException: Problem with WSDL file parsing. See nested message.
at com.sap.engine.services.webservices.espbase.client.ProxyGeneratorNew.loadWSDLapi(ProxyGeneratorNew.java:638)
at com.sap.engine.services.webservices.espbase.client.ProxyGeneratorNew.generateAll(ProxyGeneratorNew.java:400)
at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.loadProxy(DGenericServiceImpl.java:231)
at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.<init>(DGenericServiceImpl.java:69)
at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService_NewInstance(GenericServiceFactory.java:617)
... 87 more
Caused by: com.sap.engine.services.webservices.espbase.wsdl.exceptions.WSDLException: The markup in the document following the root element must be well-formed.
at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.loadDOMDocument(WSDLLoader.java:145)
at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.load(WSDLLoader.java:90)
at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.load(WSDLLoader.java:79)
at com.sap.engine.services.webservices.espbase.client.ProxyGeneratorNew.loadWSDLapi(ProxyGeneratorNew.java:632)
... 91 more
Caused by: org.xml.sax.SAXParseException: The markup in the document following the root element must be well-formed.
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:264)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.loadDOMDocument(WSDLLoader.java:131)
... 94 more
So is there anything Iu2019m missing or is there anything to be configured at NW server side? Please help
Our MII version : 12.1.5
Regards
Chandan
Edited by: Chandan Jash on Jun 8, 2011 6:47 PM

Hi Jeremy,
Thanks for your help. I am able to test it from WSnavigator but at the time of execution within XacuteRequest: two field are coming always.
XacuteRequest: 1) LoginName 2) LoginPassword:
Eithere I need to put the value there or I need to put the value within a popup when I click on next button.
But if I consume the Web Service from other place like as SAP ECC and trying to execute it then again I need to put the value for XacuteRequest: 1) LoginName 2) LoginPassword: as hardcode.
Is there any solution that I can avoid these two fields.
Thanks
Chandan

PAPI Service Interfaces not exposed as Web Services

Hi,
In guide Javadoc_PAPI_SAPME_150 there are some public interfaces that are not present as Web Services in SAP NetWeaver Application Server -> Single Service Administration: Service Definitions.
The list of missing interfaces is:
ArchiveServiceInterface
BrowseServiceInterface
BrowseSfcServiceInterface
DateGlobalizationServiceInterface
DBSequenceServiceInterface
DomainServiceInterface
DynamicInvocationServiceInterface
HookExecutionServiceInterface
LocalizedServiceInterface
NumberGlobalizationServiceInterface
OverrideDefinitionServiceInterface
PortletConfigurationServiceInterface
PredefinedFieldGroupConfigurationServiceInterface
PrintingFormatServiceInterface
PrintingTransportServiceInterface
ResourceBundleGlobalizationServiceInterface
RevisionableDomainServiceInterface
RunAsServiceInterface
SchedulingStandardsConfigurationServiceInterface
SpcChartServiceInterface
TextGlobalizationServiceInterface
I don't understand if this is by design or if there are some error in the customer NetWeaver implementation.
Thank you for your help,
Filippo.

Hello Konstantin,
thank you for your response.
Just another question: you say "It's indicated that listed services are not published" but I don't understand where it's indicated.
For example in documentation Javadoc_PAPI_SAPME_150, package com.sap.me.common, ObjectResolverServiceInterface and DynamicInvocationServiceInterface are documented in the same way and I don't see any indication that says if the interface is published as WS or not.
Best regards,
Filippo.

Stateless EJB expose as web service

I use JDeveloper 10.1.3.0.4 created the folllowing EJB:
BMP: ProductEntityEJB
Stateless session bean: ProductSessionEJB
After i generated session bean web service via web service wizard and
deploy the web service by the generated deployment file,
the error occurred:
---- Deployment started. ---- 2006年3月29日 下午02:41:16
Target platform is Standalone OC4J 10g 10.1.3 (oc4j).
Wrote EJB JAR file to C:\JCo\JDeveloper Workspace\JDevFYP\JDevFYPWS\EjbWebServices.jar
Wrote EAR file to C:\JCo\JDeveloper Workspace\JDevFYP\JDevFYPWS\JDevFYP-JDevFYPWS-EJB-WS.ear
Uploading file JDevFYP-JDevFYPWS-EJB-WS.ear ...
Application Deployer for JDevFYP-JDevFYPWS-EJB-WS STARTS.
Copy the archive to C:\SAP\JSF\jdevstudio1013\j2ee\home\applications\JDevFYP-JDevFYPWS-EJB-WS.ear
Initialize C:\SAP\JSF\jdevstudio1013\j2ee\home\applications\JDevFYP-JDevFYPWS-EJB-WS.ear begins...
Unpacking JDevFYP-JDevFYPWS-EJB-WS.ear
Done unpacking JDevFYP-JDevFYPWS-EJB-WS.ear
Initialize C:\SAP\JSF\jdevstudio1013\j2ee\home\applications\JDevFYP-JDevFYPWS-EJB-WS.ear ends...
Starting application : JDevFYP-JDevFYPWS-EJB-WS
Initializing ClassLoader(s)
Initializing EJB container
Loading connector(s)
Starting up resource adapters
Processing EJB module: EjbWebServices.jar
application : JDevFYP-JDevFYPWS-EJB-WS is in failed state
Operation failed with error:
     Missing class: fypws.bean.product.ProductSessionEJBBean
     Dependent class: com.evermind.server.ejb.deployment.BeanDescriptor
     Loader: oc4j:10.1.3
     Code-Source: /C:/SAP/JSF/jdevstudio1013/j2ee/home/lib/oc4j-internal.jar
     Configuration: <code-source> in META-INF/boot.xml in C:\SAP\JSF\jdevstudio1013\j2ee\home\oc4j.jar
This load was initiated at JDevFYP-JDevFYPWS-EJB-WS.root:0.0.0 using the Class.forName() method.
The missing class is available from the following locations:
     1. Code-Source: /C:/SAP/JSF/jdevstudio1013/j2ee/home/applications/ejb1/ejb1.jar (from <ejb> in C:\SAP\JSF\jdevstudio1013\j2ee\home\applications\ejb1)
     This code-source is available in loader ejb1.root:0.0.0.
Deployment failed
Elapsed time for deployment: 2 seconds
#### Deployment incomplete. #### 2006年3月29日 下午02:41:18
How can i solve it??

Can you try and see if installing JDeveloper into a directory with no spaces in it (i.e not in \JDeveloper Workspace\) solves the problem?

How to expose sort attributes in a web service created on a AM 11g TP4

I'm using Jdeveloper 11g TP4 to create a web service on the application module.
When I run the web service, it is working fine. Can someone tell me how to expose the sort attributes for the user to choose?
How do I expose the sort Order for the user to select?
These are the steps I followed:
1) Created a new application.
2) Created a view object in the Model project.
Created one bind variable.
Created new view Criteria and used the bind variable.
3) Created a new jspx page.
From the Data control dragged and dropped the Named Criteria on to the page and used "ADF Query Panel with Table..."
4) Ran the Jspx page. It works fine.
Double Click Application Module.
Click on tab Service Interface.
Hit New, this will open the Wizard to Create a new Service Interface.
Followed instructions and selected all the applicable methods to expose as web service.
At the end of the process, wsdl, xsd, java files are created.
I'm able to run this web service.
The field to query the data is exposed in the Web Service.
Is there a way to expose the sorting attributes to be selected by the user? i.e. I want to expose the fields to the user.
Thanks,
Jagadish.

Why bother with TP 4? JDev 11g is already production.
--olaf

Exposing EJB interfaces as Web Service

Hi all,
I created a prototype using EJBs and Web Services and found out that JDeveloper only allows to expose as Web
Services the Remote interfaces of EJBs and not the Local ones.
Assuming I have included Local and Remote interfaces for each of my EJBs exposed, my questions is, after deploying the application on OC4J 10g are the Web Services accessing the EJBs through the Local interface (I assume it should) but then why I am only allowed to expose the Remote one as Web Service?
TIA,
Best Regards,
Giovanni

Hi,
no, inbound interfaces can only call web services
that are exposed on some other web servers
only outobund XI interfaces can be exposed as web services
(in this case XI acts as a web server)
and other applicaitons can call this outbound interface
Regards,
michal

Exposing Inbound Interfaces as Web Service

Hi,
when it comes to expose XI interfaces as web services, the XI documentation quotes:
"Sie können sowohl von Outbound- als auch von Inbound-Message-Interfaces WSDL-Beschreibungen erzeugen."
-> i.e. Inbound interfaces can be exposed as web services.
But the web service definition wizard expects the quotation of an outbound interface. So am I right when I say that I always need an outbound interface? If yes, why is it possible to expose inbound interfaces???
Cheers,
Heiko

Hi,
no, inbound interfaces can only call web services
that are exposed on some other web servers
only outobund XI interfaces can be exposed as web services
(in this case XI acts as a web server)
and other applicaitons can call this outbound interface
Regards,
michal

Exposing business rules as web services in 11g

Hi all,
I have deployed my business rules in Enterprise Manager, but the test button is disabled and I'm getting the next message: "In Enterprise Manager only can be tested composites that are exposed as web services". Does anybody knows how can I do that?

There are a couple of ways you can do it.
1. Drag a Web Service Adapter in the 'Exposed Services' panel in your composite and during configuration choose the WSDL of the Decision service i.e Rules. This will expose the rules as a web service if not already.
2. Double Click on the Reference icon on the Decision Service component (small rounded blue arrow). An Update Interface window will pop up. Check box 'Create Composite Service with soap binding' and select the appropriate port type from the available list.
You can now invoke your rule as web services and even test them from the EM console

OSB Exposing Proxy Service as Web Service to external consumers

Hi all,
I am trying to expose my proxy service which I have defined in OSB11g to be exposed to external applications and consumers, rather than listening to a queue or using a business service to receive the traffic. What would be the best approach and practice to this issue? Needless to say that since I mentioned this proxy needs to be exposed as web service, I'll be expecting back response. The endpoint that I am getting as result of creating this proxy comes to be in following format:
/<project_name>/Services/ProxyServices/MyProxy
This fine for apps deployed on the same domain, but not if they are not deployed on the same domain.
thanks in advance

From the information shared you, looks like you want to create a SOAP over HTTP webservice in OSB which will be the one exposed to external consumers.
1. So to create such a Proxy service, you will need to define the interface using a WSDL (as mentioned by Pierluigi) first.
2. Once done, you can create a Proxy (SOAP/HTTP) based using the above WSDL. Then implement your business logic in the message flow.
3. As a part of the configuration, you can define the context root of the service. (by default you might be getting /<project_name>/Services/ProxyServices/MyProxy)
You can customize as required, for e.x change this to /services/MyProxy
4. The final URL that can be used to access the above proxy will be as follow:
http://<hostname>:<port>/services/MyProxy for HTTP
https://<hostname>:<port>/services/MyProxy for HTTPS accordingly.
Depending on the way your domain is configured (managed servers) you can change the hostname and port.
So irrespective of where this service is deployed, you should be able to access it.
Do let me know in case my understanding is incorrect.
Thanks,
Patrick

How to expose/convert my Portal Service as/to a Web Service??

Hi Experts,
How can i expose my Portal Service as a Web Service??
What configuration i need to do for that???
Please reply.
Help will be rewarded and Appreciated.

hi
In NWDS go to
New ->other -> portal application -> portal application object ->
portal web services -> portal web services from portal services and select ur portal service.
Generate portal web service with PDK wizard by choosing Portal web service from portal service
Select the interfaces by clicking the browser button.
select the methods to be exposed to web service.
Now WSDL files are generated for portal services.
You can view the WSDL by going to
System administration->support->portal runtime -> soap admin -> web services
Regards,
Ganesh N

Exposing Portal's User Management functionality via Web Service issue

Dear experts,
I am trying to create and deploy a web service that will tap into User Management functionality (UMFactory) of the Portal. I created a Java project with a Java class with one of the methods exposed via Web Service. Since this is a Java project and not a Web Dynpro project, a number of external jars and libraries, but I don't know how to add WD_RUNTIME and I am guessing that my problem is related to that.
When trying to run the application, I receive the following error message when trying to envoke UMFactory:
java.lang.NoClassDefFoundError: com/sap/tc/logging/Location
     at com.sap.security.api.UMFactory.<clinit>(UMFactory.java:166)
     at com.hollister.getusers.GetPortalUsers.getPortalUsers(GetPortalUsers.java:75)
     at com.hollister.getusers.GetPortalUsers.main(GetPortalUsers.java:39)
Please, help.
Thanks,
Alex

Container Managed Authentication. Does everything you need.

Exposing as Web Services

Similar Messages

Maybe you are looking for