Invoking a webservice as an "application process"

Hello there,
I have setup a web service successfully and I can invoke it as a "Page Process", get the response in a collection , and do a few validation based on it.
However, I will need this validation for most of my pages in the application, so I thought, I would rather run it against the application as a whole.
The issue came when I try to invoke the web service as an "Application Process" rather than a page process. Unfortunately APEX does not seems to give an option to invoke a web service on application level as it does for page level.
For Application Process, apparently I can only run a PL/SQL block, which is fine; if I know how to make a call to the web service and fill the collection from a PL/SQL Block.
My application does not have a particular page as "home entry"; users basically will be accessing different pages as entry points. I really don't like to invoke WS calls on each of the page to get the collection filled, so my validation could run - I mean I will have only this option unless this tread yield me with an alternative :)-
I am sure someone must have gone through similar situation, and hopefully could provide a solution or workaround for me.
Thanks a lot in advance
Regards
Ligon Gopinathan

Ligon:
Yes, using NTLM authentication does complicate things a bit. However, I think it may be possible to to achieve the goal of pushing all users to a fixed landing page upon successful session establishment by the NTLM page-sentry function and from thereon to the page the user requested. This landing page will have 2 'before header' processes , one that will call the Web Service and the another that will simply re-direct the user to the page that was initially requested.
In the page-sentry function you can modify the call to 'wwv_flow_custom_auth_std.post_login' such that the parameter
p_flow_page is set to 'apex_application.g_flow_id ||':'<landing-page-id>'
You will also need to save off the actual page requested( the value of apex_application.g_flow_step_id) into an application_item which you can then reference in the pre-header process of the landing-page.
I must caution you that I have not tested whether this approach will work but decided to throw this out here anyhow :)
Check http://www.oracle-base.com/articles/10g/utl_dbws10g.php out for a how-to for calling out to Web Services using PL/SQL .
Varad

Similar Messages

Invoke JCAPS webservice from Java Application

I am getting
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Client
faultSubcode:
faultString: JAXRPC.TIE.01: caught exception while handling request: unrecognized operation: Test
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace: AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Client
faultSubcode:
faultString: JAXRPC.TIE.01: caught exception while handling request: unrecognized operation: Test
faultActor:
faultNode:
faultDetail:
JAXRPC.TIE.01: caught exception while handling request: unrecognized operation: Test
at org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:260)
at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:169)
at org.apache.axis.encoding.DeserializationContextImpl.endElement(DeserializationContextImpl. java:1015)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser. java:633)
at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanEndElement(XMLNSDocum entScannerImpl.java:719)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDisp atcher.dispatch(XMLDocumentFragmentScannerImpl.java:1685)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDoc umentFragmentScannerImpl.java:368)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.jav a:834)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.jav a:764)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java: 1242)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
==========================================================
JAVA CODE :
public static void main(String[] args) {
// TODO code application logic here
try {
WebServiceClient wsClient = new WebServiceClient();
String strTargetNameSpaceIn ="urn:stc:egate:jce roject3_Collaboration_1" ;
String strPortNameIn = "ExecutePortType";
String strServiceNameIn ="Project3_Collaboration_1Service" ;
String strOperationNameIn ="Test" ;
//String strWebserviceURLIn = "http://165.68.202.246:8080/uddidocs/Nonesecurewebservice/testweb3/jc/wsdl_jce_jc-2145777518.wsdl";
String strWebserviceURLIn = "http://localhost:8080/uddidocs/EnvUCHDevLocal/Project3/Collaboration_1/wsdl_jce_Collaboration_1771627736.wsdl ";
String strInputIn = " Test JCAPS WebService ";
String output = wsClient.callWebService(strTargetNameSpaceIn,strPortNameIn,strServiceNameIn,strOperationNa meIn,strWebserviceURLIn,strInputIn);
System.out.println("WebService Output " + output);
} catch (Exception err) {
System.out.println( " EXCEPTION OCCURED");
err.printStackTrace();
public String callWebService(String strTargetNameSpace,String strPortName,String strServiceName,String strOperationName,String strWebserviceURL,String strInput) throws ServiceException, MalformedURLException, RemoteException
if(strTargetNameSpace==null || strPortName == null || strServiceName == null || strOperationName == null || strWebserviceURL ==null || strInput == null )
throw new IllegalArgumentException();
ServiceFactory factory = ServiceFactory.newInstance();
// for webservice target namespace
String targetNamespace =strTargetNameSpace;
// for webservice name
QName serviceName = new QName(strTargetNameSpace,strServiceName);
// for webservice port name
QName portName = new QName(strTargetNameSpace,strPortName);
// for operation name
QName operationName = new QName("urn:stc:egate:jce roject3:Collaboration_1WSDL:Test",strOperationName);
// for url of webservice ".wsdl" file
URL wsdlLocation = new URL(strWebserviceURL);
if(wsdlLocation==null)
throw new ServiceException();
// for bind to service name with wsdl file
Service service = factory.createService(wsdlLocation, serviceName);
// for call to webservice using operation name
Call call = service.createCall(portName, operationName);
String result = null;
try{
System.out.println(" STR INPUT" + strInput);
result = (String) call.invoke(new Object[] {strInput});
}catch(Exception e){
e.printStackTrace();
result="Occur webservice processing error";
if(result==null)
result="Occur webservice processing error";
String str = "Webservice Responce from :"+strWebserviceURL;
return result;
}//close function
=========================================================
WSDL FILE :
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="Project3_Collaboration_1" targetNamespace="urn:stc:egate:jce roject3_Collaboration_1" xmlns:tns="urn:stc:egate:jce roject3_Collaboration_1" xmlns:inMsg="http://dn1318d-uwsxp:13000/repository/UCHDevLocal/Project3/UCHDevLocal23b1e1:1192e3ad66a:-8000/XSDDefinition1" xmlns:errMsg="urn:stc:egate:jce:JavaException" xmlnsutMsg="http://dn1318d-uwsxp:13000/repository/UCHDevLocal/Project3/UCHDevLocal23b1e1:1192e3ad66a:-7fff/XSDDefinition2" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns="http://schemas.xmlsoap.org/wsdl/">
<import namespace="http://dn1318d-uwsxp:13000/repository/UCHDevLocal/Project3/UCHDevLocal23b1e1:1192e3ad66a:-7fff/XSDDefinition2" location="XSDDefinition2.xsd"/>
<import namespace="http://dn1318d-uwsxp:13000/repository/UCHDevLocal/Project3/UCHDevLocal23b1e1:1192e3ad66a:-8000/XSDDefinition1" location="XSDDefinition1.xsd"/>
<types>
<xs:schema elementFormDefault="qualified" id="UID-20000000-DC88392E190100-A544977D-01" targetNamespace="urn:stc:egate:jce:JavaException" xmlns="urn:stc:egate:jce:JavaException" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="JavaException" type="JavaExceptionType"/>
<xs:complexType name="JavaExceptionType">
<xs:sequence>
<xs:element name="Type" type="xs:string"/>
<xs:element name="Message" type="xs:string"/>
<xs:element name="Trace" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:schema>
</types>
<message name="Output">
<part name="Body" element="outMsg utput"/>
</message>
<message name="Input">
<part name="Body" element="inMsg:Input"/>
</message>
<message name="JavaExceptionMessage">
<part name="FaultDetails" element="errMsg:JavaException"/>
</message>
<portType name="ExecutePortType">
<operation name="Test">
<input name="Input" message="tns:Input"/>
<output name="Output" message="tns utput"/>
<fault name="JavaException" message="tns:JavaExceptionMessage"/>
</operation>
</portType>
<binding name="ExecutePortTypeBinding" type="tns:ExecutePortType">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="Test">
<soapperation soapAction="urn:stc:egate:jce roject3:Collaboration_1WSDL:Test" style="document"/>
<input name="Input">
<soap:body parts="Body" use="literal" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</input>
<output name="Output">
<soap:body parts="Body" use="literal" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</output>
<fault name="JavaException">
<soap:fault name="JavaException" use="literal" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</fault>
</operation>
</binding>
<service name="Project3_Collaboration_1Service">
<port name="ExecutePortType" binding="tns:ExecutePortTypeBinding">
<soap:address location="http://localhost:18501/WsServer/ExecutePortType"/>
</port>
</service>
</definitions>

Hi Abinap.
If you are woking with JEE 1.3 or JAX-RPC.
You need to add some libraries to java project.
Go to the tab "Add Libraries" on context menu of the project: Properties --> Java build Path
Select "Add variable" button, after select the SAP_WEBSERVICES_EXT_LIBS_HOME variable and click on "Extend" Button, finally select all the libraries under lib folder, do the same to the SAP_XML_TOOLKIT_LIBS_HOME variable.
Greetings.
Manuel Loayza Gahona

How to invoke a webservice in the middle of a BPM process

I use BPM studio to create processes.
In the middle part of the BPM process, it need to invoke a web service (an ADF project deployed to weblogic as a web service). Then, it will wait.
After the process is finished, it will invoke another web service (an ADF project deployed to weblogic as a web service).
How to invoke web services in and after the process?
Thank you.

Hi,
Thanks for your reply. I use BPM studio 10.3
In the Catalogue, there are 3 default components which are Fuego, Java, and Plumtree.
In the Fuego, there is an item of WebServices. In the Plumtree, there is an item named WebServiceProperty.
If I create a new Module, I cannot find the option of web service.
How to invoke a webservice (ADF/Java web service developed in Jdeveloper deploy to weblogic ) ?
Thanks.

Regarding errors in client Application to invoke the webservices

hi,
i am using weblogic workshop to develop webservices on weblogic server8.1
i develop webservice and wsdl file also
but when i am writing dynamic client application to invoke the webservice( particular method)
then it gives error like this
javax.xml.rpc.JAXRPCException: failed to invoke operation 'requestContactList' due to an error in the soap layer (SAAJ); nested exception is: Message[ failed to serialize interface javax.xml.soap.SOAPElementweblogic.xml.schema.binding.SerializationException: mapping lookup failure. class=interface javax.xml.soap.SOAPElement class context=TypedClassContext{schemaType=['http://www.openuri.org/']:requestContactList}]StackTrace[
javax.xml.soap.SOAPException: failed to serialize interface javax.xml.soap.SOAPElementweblogic.xml.schema.binding.SerializationException: mapping lookup failure. class=interface javax.xml.soap.SOAPElement class context=TypedClassContext{schemaType=['http://www.openuri.org/']:requestContactList}
     at weblogic.webservice.core.DefaultPart.invokeSerializer(DefaultPart.java:332)
     at weblogic.webservice.core.DefaultPart.toXML(DefaultPart.java:297)
     at weblogic.webservice.core.DefaultMessage.toXML(DefaultMessage.java:645)
     at weblogic.webservice.core.ClientDispatcher.send(ClientDispatcher.java:206)
     at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:143)
     at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:471)
     at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:457)
     at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:566)
     at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:419)
     at test.Client.main(Client.java:57)
Caused by: weblogic.xml.schema.binding.SerializationException: mapping lookup failure. class=interface javax.xml.soap.SOAPElement class context=TypedClassContext{schemaType=['http://www.openuri.org/']:requestContactList}
     at weblogic.xml.schema.binding.RuntimeUtils.lookup_serializer(RuntimeUtils.java:151)
     at weblogic.xml.schema.binding.RuntimeUtils.invoke_serializer(RuntimeUtils.java:187)
     at weblogic.xml.schema.binding.RuntimeUtils.invoke_serializer(RuntimeUtils.java:174)
     at weblogic.webservice.core.DefaultPart.invokeSerializer(DefaultPart.java:328)
     ... 9 more
     at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:586)
     at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:419)
     at test.Client.main(Client.java:57)
Debugging Finished
Exception in thread "main"
my client program is
import java.net.URL;
import javax.xml.rpc.ServiceFactory;
import javax.xml.rpc.Service;
import javax.xml.rpc.Call;
import javax.xml.rpc.ParameterMode;
import javax.xml.namespace.QName;
* This class demonstrates a java client invoking a WebService.
* @author Copyright (c) 2005 by BEA Systems, Inc. All Rights Reserved.
public class Client {
public static void main(String[] args) throws Exception {
// Setup the global JAXM message factory
System.setProperty("javax.xml.soap.MessageFactory",
"weblogic.webservice.core.soap.MessageFactoryImpl");
// Setup the global JAX-RPC service factory
System.setProperty( "javax.xml.rpc.ServiceFactory",
"weblogic.webservice.core.rpc.ServiceFactoryImpl");
// create service factory
ServiceFactory factory = ServiceFactory.newInstance();
// define qnames
String targetNamespace =
"http://www.openuri.org/"
+ "wsdl/http://192.168.2.98:7001/ContactListWeb/ContactListJWS/ContactTest.jws";
QName serviceName =
new QName(targetNamespace,
"ContactTest");
QName portName =
new QName(targetNamespace,
"ContactTestSoap");
QName operationName = new QName("targetNamespace",
"requestContactList");
URL wsdlLocation =
new URL("http://192.168.2.98:7001/ContactListWeb/ContactListJWS/ContactTest.jws?WSDL");
// create service
Service service = factory.createService(wsdlLocation, serviceName);
// create call
Call call = service.createCall(portName, operationName);
// invoke the remote web service
String result =(String)call.invoke(new Object[] {
"BEAS"
System.out.println("\n");
System.out.println("This example shows how to create a dynamic client application that invokes a non-WebLogic Web service.");
System.out.println("The webservice used was: http://services.xmethods.net/soap/urn:xmethods-delayed-quotes.wsdl");
System.out.println("The quote for BEAS is: ");
System.out.println(result);
}

Hi I am also facing the issue. If any one got the solutoin for this please post it
Thanks
Kaal

How to invoke a WADL file from BPEL process

Hi,
We have requirement where our participating applications would provide us a WADL file(Restful interface) to invoke their webservice.
We need to invoke the WADL file (thus posting to their urls) from our BPEL process.
PLease let me know on how this can be done.
Thanks in advance!!!

Hi,
I have actually used http bindings and invoked some restful services and was successful in doing so.
But if I was wondering if there is any other way of actually invoking the WADL files, like we do the WSDL files.
Also , there are some places where I have to send one parameter through the URL and rest through the message that has to be posted.

Invoking a webservice using WSIF Binding

Hi All,
I have few queries regarding usage of WSIF Binding in BPEL
My understanding was it is useful for calling Java Classes from BPEL Process.
Can I use WSIF Binding for invoking the webservice ?
Or the use of WSIF Binding is limited to invoking Java classes.
If we can invoke web service , Can you please let me know how to do it?
you can mail your replies to [email protected]
Any help will be immensely appreciated..
Regards,
Bhanu

First of all thanks to Jens and clemens.
From both of your replies, i learnt that we can call webservice from BPEL process using WSIF binding .
Can you provide me a bpel sample where we're using wsif binding for invoking web service?
I have one more doubt:
"WSIF java binding means, which was used to call java classes. WSIF soap binding used to call web services"
Is my understanding correct?
Can you explain a bit on WSIF Java binding?
Regards,
Bhanu

Invoking ODI Scenario from a BPEL process - Resolved

I new to Oracle products.
I am exploring Oracle Data Integrator tool.
I would like to call ODI scenario from a BPEL process.
I created a scenario in ODI, I have SOA suite10.1.3.3 installed in my machine.
In some portal I have read that, we need to deploy apache axis to Oracle App server and then deploy the ODI public web service to axis. This public web service facilitates us to call scenario from partner link.
Following are my questions:
1) I guess Oracle App server acts as webservice container too. Why should I use apache axis here?
2)If axis must be used, please let me know how to deploy it to OAS.
If axis is not required, please guide me how to deploy public web service to OAS.
Thanks!!

Hi:
I have similar problem, when invoke ODI Scenario from a BPEL Process, the error in ODI Designer is:
java.lang.NullPointerException
     at com.sunopsis.dwg.dbobj.SnpSession.a(SnpSession.java)
     at com.sunopsis.dwg.dbobj.SnpSession.y(SnpSession.java)
     at com.sunopsis.dwg.dbobj.SnpSession.treatSessionPreTrt(SnpSession.java)
     at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java)
     at com.sunopsis.dwg.cmd.DwgCommandScenario.treatCommand(DwgCommandScenario.java)
     at com.sunopsis.dwg.cmd.DwgCommandBase.execute(DwgCommandBase.java)
     at com.sunopsis.dwg.cmd.e.i(e.java)
     at com.sunopsis.dwg.cmd.h.y(h.java)
     at com.sunopsis.dwg.cmd.e.run(e.java)
     at java.lang.Thread.run(Thread.java:595)
In the BPEL Console the result is OK and process complete, but in the INVOKE scenario send message:
<messages><ODI_REQUEST><part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="part1"><invokeScenarioRequest xmlns="xmlns.oracle.com/odi/OdiInvoke/">
*<RepositoryConnection xmlns=""*
<JdbcDriver>oracle.jdbc.driver.OracleDriver</JdbcDriver>
<JdbcUrl>jdbc:oracle:thin:@192.168.1.109:1521:ORCL</JdbcUrl>
<JdbcUser>dimaster</JdbcUser>
<JdbcPassword>sabr0sa</JdbcPassword>
<OdiUser>SUPERVISOR</OdiUser>
<OdiPassword>SUNOPSIS</OdiPassword>
<WorkRepository>TESTWORKREP1</WorkRepository>
</RepositoryConnection>
*<Command xmlns="">*
<ScenName>P_TRASPASOSOP09</ScenName>
<ScenVersion>2</ScenVersion>
<Context>Global</Context>
<LogLevel>5</LogLevel>
<SyncMode>0</SyncMode>
<SessionName/>
<Keywords/>
<Variables>
<Name/>
<Value xmlns:ns1="http://xmlns.oracle.com/Recepcion">
<ns1:Escenario>P_TRASPASOSOP09</ns1:Escenario>
<ns1:Version>2</ns1:Version>
<ns1:Contexto>Global</ns1:Contexto>
<ns1:ID>1</ns1:ID>
<ns1:NivelLogeo>5</ns1:NivelLogeo>
</Value>
</Variables>
</Command>
*<Agent xmlns="">*
<Host>192.168.1.109</Host>
<Port>20910</Port>
</Agent>
</invokeScenarioRequest>
</part></ODI_REQUEST><ODI_RESPONSE><part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="part1"><odi:invokeScenarioResponse xmlns:odi="xmlns.oracle.com/odi/OdiInvoke/">
<odi:CommandResultType>
<odi:Ok>true</odi:Ok>
<odi:SessionNumber>445000</odi:SessionNumber>
</odi:CommandResultType>
</odi:invokeScenarioResponse>
</part></ODI_RESPONSE></messages>

Issue in invoking the webservice on EBS 12.1.3

Hi,
We are using R12.1.3 version of EBS. We have developed the custome PL SQL logic and deployed it on the Integration repository. Generated the WSDL and Deploy process were successful on IR. Authentication type used was "Username Token". Created the necessary user grants.
When we try to invoke the webservice from SOAP UI, we are getting below error:
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header/>
<env:Body>
<env:Fault>
<faultcode>env:Server</faultcode>
<faultstring>oracle.apps.fnd.soa.util.SOAException: ServiceProcessingError: System Errornull</faultstring>
<faultactor/>
</env:Fault>
</env:Body>
</env:Envelope>
Also, we checked in the log files and found below entries.
<MSG_TEXT>An error occurred for port: SOAProvider: oracle.webservices.provider.ProviderException: oracle.apps.fnd.soa.util.SOAException: ServiceProcessingError: System Errornull.</MSG_TEXT>
<MSG_TEXT>Unable to determine operation id from SOAP Message.</MSG_TEXT>
Can someone help me in this issue? We are successfully able to invoke the same webservices on R12.1 version but getting an error in 12.1.3 version!!!
Thanks in advance.
Regards,
Vasanth

Hi,
Try seeing the log messages after doing the following setup in the instance :-
1. Telnet to environment
1. In $INST_TOP/ora/10.1.3/j2ee/oafm/config/oc4j.properties
1. Add following property at the end of the file : SOA_ENABLE_STANDALONE_LOGGING=TRUE
2. Bounce oafm container using script $ADMIN_SCRIPTS_HOME/adoafmctl.sh
3. Perform any SOA specific action like generate.
SOA specific log would be created at : $INST_TOP/soa/SOALog.log
This file should show you the exact error happening.
Thanks,
Sai.M

How to call webservice using standalone application

Hi,
Actually i am trying to connect with one free webservice using client. but i am uanble to get the result and it is throwing the Exception.Exception is Execution failed. Exception: java.net.ConnectException: Connection timed out: connection reset
i am using the following code.
import org.apache.axis.client.Call;
import org.apache.axis.client.Service;
import org.apache.axis.encoding.XMLType;
import org.apache.axis.utils.Options;
import javax.xml.namespace.QName;
import java.io.*;
public class AddFunctionClient {
public static void main(String [] args) {
try {
     String endpoint = "http://www.startvbdotnet.com/web/sample2.asmx?wsdl";
     System.setProperty("http.proxyHost", proxyHost);
          System.setProperty("http.proxyPort", portNumber);
     Service service = new Service();
     Call call = (Call) service.createCall();
     call.setTargetEndpointAddress( new java.net.URL(endpoint) );
     call.setOperationName(new QName(endpoint, "add"));
          System.out.println("connected");
          System.out.println("value is"+call.invoke(new Object[]{new Integer(10),new Integer(20)}));
     } catch (Exception e) {
     System.err.println("Execution failed. Exception: " + e);
can any one help on this

Hi,
If your JAVA Application is Web based application, you can expose it as Webservice.
JAVA People will pick the data from Dbase using their application and will send the data to XI by using our XI Details like Message Interface and Data type structure and all.
So we can Use SOAP Adapter or HTTP in XI..
If you use HTTP for sending the data to XI means there is no need of Adapter also. why because HTTP sits on ABAP Stack and can directly communicate with the XI Integration Server Directly
If you are dealing with the Webservice and SAP Applications means check this
Walkthrough - SOAP XI RFC/BAPI
REgards
Seshagiri

Problems Invoking Ebiz Webservice from 11g FMW Serve

Hi All,
We need to invoke a Webservice deployed on Ebiz host from 11g FMW Server in our PIP.
I created a simple BPEL process to invoke Ebiz Webservice and deployed the bpel process on 11g Server.
While executing the bpel process Iam getting Null Pointer Exception from Ebiz Webservice.
After checking the logs of Ebiz it was understood that SOA Provider is unable to recognize wsa header tags in the soap message used to invoke Ebiz Webservice.
Error message from logs is "An error occurred for port: AppsWSProvider: oracle.webservices.provider.ProviderException: java.lang.NullPointerException."
Unexpected header encountered: NameImpl: [localName: To, prefix:wsa, uri:http://www.w3.org/2005/08/addressing]
oracle.apps.fnd.wf.ws.common.WSException: InvalidHeader: Unexpected header encountered.
at oracle.apps.fnd.wf.ws.common.SOAPUtils.extractHeaders(SOAPUtils.java:92)
at oracle.apps.fnd.wf.ws.server.AppsWSProvider.processMessage(AppsWSProvider.java:470)
at oracle.j2ee.ws.server.provider.ProviderProcessor.doEndpointProcessing(ProviderProcessor.java:958)
at oracle.j2ee.ws.server.WebServiceProcessor$1.run(WebServiceProcessor.java:388)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:385)
at oracle.j2ee.ws.server.provider.ProviderProcessor.doRequestProcessing(ProviderProcessor.java:481)
at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:114)
at oracle.j2ee.ws.server.WebServiceProcessor.doService(WebServiceProcessor.java:96)
at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:200)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:734)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:391)
at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:908)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:458)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:313)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:199)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:234)
at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:29)
at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:879)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:619)
11g FMW Server is automatically adding these WSA Header tags in the soap message to invoke Webservice deployed on Ebiz host.
Have anyone encountered similar kind of issue?
Regards,
Sunitha.M

Hi
Hope below URL will resolve your issue
URL: https://cn.forums.oracle.com/forums/thread.jspa?threadID=1099613
Regards,
Phanikanth

Re: Problems Invoking Ebiz Webservice from 11g FMW Server

Hi All,
We need to invoke a Webservice deployed on Ebiz host from 11g FMW Server in our PIP.
I created a simple BPEL process to invoke Ebiz Webservice and deployed the bpel process on 11g Server.
While executing the bpel process Iam getting Null Pointer Exception from Ebiz Webservice.
After checking the logs of Ebiz it was understood that SOA Provider is unable to recognize wsa header tags in the soap message used to invoke Ebiz Webservice.
Error message from logs is "An error occurred for port: AppsWSProvider: oracle.webservices.provider.ProviderException: java.lang.NullPointerException."
Unexpected header encountered: NameImpl: [localName: To, prefix:wsa, uri:http://www.w3.org/2005/08/addressing]
oracle.apps.fnd.wf.ws.common.WSException: InvalidHeader: Unexpected header encountered.
at oracle.apps.fnd.wf.ws.common.SOAPUtils.extractHeaders(SOAPUtils.java:92)
at oracle.apps.fnd.wf.ws.server.AppsWSProvider.processMessage(AppsWSProvider.java:470)
at oracle.j2ee.ws.server.provider.ProviderProcessor.doEndpointProcessing(ProviderProcessor.java:958)
at oracle.j2ee.ws.server.WebServiceProcessor$1.run(WebServiceProcessor.java:388)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:385)
at oracle.j2ee.ws.server.provider.ProviderProcessor.doRequestProcessing(ProviderProcessor.java:481)
at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:114)
at oracle.j2ee.ws.server.WebServiceProcessor.doService(WebServiceProcessor.java:96)
at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:200)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:734)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:391)
at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:908)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:458)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:313)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:199)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:234)
at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:29)
at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:879)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:619)
11g FMW Server is automatically adding these WSA Header tags in the soap message to invoke Webservice deployed on Ebiz host.
Have anyone encountered similar kind of issue?
Regards,
Sunitha.M

I'm using Weblogic 7.0.
You must use two jars:
- webserviceclient+ssl.jar, which you can find somewhere in the
weblogic distribution, and
- the jar containing the proxy classes, which is created by the
tool jwsCompile when you compile the webservice (edited with Workshop). For this
latter you may follow the instructions in
http://e-docs.bea.com/workshop/docs70/help/index.html#guide/
tutorial/tutFirstWebServiceIntro.html at step 8
Still, if you happen to understand what my problem is, hints for
me are really welcome.

Error during invokation of webservices: "error: unknown java type:"

hi,
I'm having issues with invoking a webservice from the "WebLogic Test Client". The webservice exposes the methods from a stateless session EJB and Weblogic Workshop was used to create the webservice controls
Weblogic version: 10.0 mp1
Pls. advise.
Error message ...
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header />
<env:Body>
<env:Fault>
<faultcode>env:Server</faultcode>
<faultstring>error: unknown java type: com.margin.engine.entity.ClientSet</faultstring>
<detail>
<bea_fault:stacktrace xmlns:bea_fault="http://www.bea.com/servers/wls70/webservice/fault/1.0.0">com.bea.xml.XmlRuntimeException: error: unknown java type: com.margin.engine.entity.ClientSet
at com.bea.staxb.runtime.internal.FailFastErrorHandler.add(FailFastErrorHandler.java:45)
at com.bea.staxb.runtime.internal.MarshalResult.addError(MarshalResult.java:265)
at com.bea.staxb.runtime.internal.AnyTypeRuntimeBindingType.determineActualRuntimeType(AnyTypeRuntimeBindingType.java:84)
at com.bea.staxb.runtime.internal.RuntimeBindingProperty.getActualRuntimeType(RuntimeBindingProperty.java:110)
at com.bea.staxb.runtime.internal.PushMarshalResult.walkRankOneSoapArray(PushMarshalResult.java:570)
at com.bea.staxb.runtime.internal.PushMarshalResult.walkSoapArray(PushMarshalResult.java:534)
at com.bea.staxb.runtime.internal.PushMarshalResult.visit(PushMarshalResult.java:437)
at com.bea.staxb.runtime.internal.SoapArrayRuntimeBindingType.accept(SoapArrayRuntimeBindingType.java:59)
at com.bea.staxb.runtime.internal.PushMarshalResult.writeContents(PushMarshalResult.java:192)
at com.bea.staxb.runtime.internal.PushMarshalResult.marshalTopType(PushMarshalResult.java:93)
at com.bea.staxb.runtime.internal.MarshallerImpl.marshalBindingType(MarshallerImpl.java:302)
at com.bea.staxb.runtime.internal.MarshallerImpl.marshalType(MarshallerImpl.java:435)
at weblogic.wsee.bind.runtime.internal.LiteralSerializerContext.marshalType(LiteralSerializerContext.java:70)
at weblogic.wsee.bind.runtime.internal.BaseSerializerContext.internalSerializeType(BaseSerializerContext.java:175)
at weblogic.wsee.bind.runtime.internal.BaseSerializerContext.serializeType(BaseSerializerContext.java:95)
at weblogic.wsee.codec.soap11.SoapEncoder.encodePart(SoapEncoder.java:284)
at weblogic.wsee.codec.soap11.SoapEncoder.encodeReturn(SoapEncoder.java:205)
at weblogic.wsee.codec.soap11.SoapEncoder.encodeParts(SoapEncoder.java:192)
at weblogic.wsee.codec.soap11.SoapEncoder.encode(SoapEncoder.java:119)
at weblogic.wsee.codec.soap11.SoapCodec.encode(SoapCodec.java:128)
at weblogic.wsee.ws.dispatch.server.CodecHandler.encode(CodecHandler.java:103)
at weblogic.wsee.ws.dispatch.server.CodecHandler.handleResponse(CodecHandler.java:50)
at weblogic.wsee.handler.HandlerIterator.handleResponse(HandlerIterator.java:236)
at weblogic.wsee.handler.HandlerIterator.handleResponse(HandlerIterator.java:220)
at weblogic.wsee.ws.dispatch.server.ServerDispatcher.callHandleResponse(ServerDispatcher.java:135)
at weblogic.wsee.ws.dispatch.server.ServerDispatcher.dispatch(ServerDispatcher.java:108)
at weblogic.wsee.ws.WsSkel.invoke(WsSkel.java:80)
at weblogic.wsee.server.servlet.SoapProcessor.handlePost(SoapProcessor.java:66)
at weblogic.wsee.server.servlet.SoapProcessor.process(SoapProcessor.java:44)
at weblogic.wsee.server.servlet.BaseWSServlet$AuthorizedInvoke.run(BaseWSServlet.java:257)
at weblogic.wsee.server.servlet.BaseWSServlet.service(BaseWSServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3395)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2140)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2046)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
</bea_fault:stacktrace>
</detail>
</env:Fault>
</env:Body>
</env:Envelope>

Olivier, thank you so much
SOAMANAGER does not exist in my system (sp level 8), so node "/sap/bc/soap/rfc" should be active. Actually, it is active.
I think the problem is related to user rights/profiles.
I have tried to create another WS after assigning role SAP_BC_WEBSERVICE_ADMIN. The same error when trying to activate it, but now, I can see this WS in SE80 (under "Enterprise Services->Service Definition"). It is not active there and if I try to activate it, a success message appears indicating that user "is not authorized to use function netzwerkadministration". I cannot see any new services in SICF...
Probably the new entry in SICF will be created after activating WS in SE80...
Do u know what user profile should I add in order to properly activate the WS in SE80?
Thank you very much!
Vicente

Unable to invoke a EJB from a BPEL process

I am unable to invoke a EJB from a BPEL process. Whenever I try to test it from the oracle EM, I get the below exception. I am using WebLogic 10.3.3, SOA suite 11.1.1.3 and JDev 11.1.1.3 .
This is what I see from the EM....
Non Recoverable System Fault :
javaInterface attribute for the binding is missing or the inteface class is not available.
Below is a part of the stack trace from the soa server log…
Caused By: oracle.classloader.util.AnnotatedClassNotFoundException:
Missing class: com.abc.GreetingEJBBean
Dependent class: oracle.integration.platform.blocks.ejb.SDOEjbReferenceD
elegateImpl
Loader: sun.misc.Launcher$AppClassLoader@20929799
Code-Source: /C:/Oracle_latest/Middleware/home_11gR1/Oracle_SOA1/soa
/modules/oracle.soa.fabric_11.1.1/fabric-runtime.jar
Configuration: /C:/Oracle_latest/Middleware/home_11gR1/Oracle_SOA1/soa
/modules/oracle.soa.fabric_11.1.1/fabric-runtime.jar
Piece of xml from the composite.xml
<reference name="GreetingService"
ui:wsdlLocation="http://123.45.218.140:7001/GreetingEJBBean/GreetingEJBBeanService?wsdl">
<interface.wsdl interface="http://abc.com/#wsdl.interface(GreetingEJBBean)" />
<binding.ejb uri="GreetingEJB-GreetingEJB-GreetingEJB"
javaInterface="com.abc.GreetingEJB"/>
</reference>
Looks like its not able to find the javaInterface mentioned above.
I have a simple EJB with one business method and a very simple BPEL process.
@Stateless(name = "GreetingEJB", mappedName = "GreetingEJB-GreetingEJB-GreetingEJB")
@WebService
public class GreetingEJBBean implements GreetingEJB {
public GreetingEJBBean() {
public String greetUser(String name){
return ("Hello " + name);
Any help would be greatly appreciated.

I haven't tried from a BPEL process, but I have had success (as in Lucas's blogs) of using services and references as EJB Java Interface. This is with EJB java interfaces solely of base types (i.e. String foo(String s)).
At high level here's what I have noted so far:
1. Per Lucas's blog, @javaInterface is not being added to the ejb.binding automatically but it's not clear to me when this is and is not required given that interface.java is specified for the reference or service. Would interface.java and @javaInterface ever be different? I've been adding @javaInterface manually anyways since Lucas is a smart guy and I'd rather avoid errors. :-)
2. Dropping an EJB interface jar in SCA-INF/lib works, but I've had the problem that the JDeveloper SOA Plugin doesn't see those classes until I stop and restart JDeveloper. Until then, I'm confronted with the java->wsdl mapping error. I was sort of primed to figure this one out since I ran into similar issues with SOA SpringBean components.
3. Dropping EJB interface source in SCA-INF/src is more reliable, because then I can build the project (i.e. create SCA-INF/classes) and the JDeveloper SOA Plugin seems to resolve these brand new classes immediately.
4. I've tried to invoke an EJB java-interface reference with a slightly complicated java interface (a class parameter with some fields, one of which is an array of another class). The auto-generated WSDL doesn't look exactly right to me (but I'm new to JAXB). Mediator maps to it just fine and the project compiles and deploys normally but fails at runtime. I have not researched in depth. It's not clear to me from the documentation and release notes whether I should expect for it to work, or whether I should expect to have to create my own JAXB mapping. If the latter, I really need a good example!

Problem invoking XI webservice

We have created a webservice on XI that calls the BAPI_COMPANYCODE_GETLIST on an R/3 4.6C system. We generated the WSDL using the Integration builder and corrected the URL to point to the webservice (rather than the wizard proposed URL).
We can call the webservice through XMLspy and other tools. But we are not able to use webdynpro to invoke the webservice. We uploaded the webservice on the web application server so we can get to it through a URL.
The problem is that when we use webdynpro and try to link it to a webservice, we can point to the URL which is for the WSDL we uploaded to the webserver. But there is no other field in webdynpro to specify the URL for the webservice endpoint. The endpoint is actually in the WSDL and it seems correct:
http://servername:50000/XISOAPAdapter/MessageServlet?channel=:BS_EXTERNALAPP:BAPI_COMPANYCODE_GETLIST_WEBSERVICE_SOAP_SENDER;version=3.0;Sender.Service=BS_EXTERNALAPP;Interface=http://xyz.com/xi_demo/BAPI_COMPANYCODE_GETLIST_OUTBOUND_SYNC_MI
Through XMLspy we can just point to the WSDL. And then we can just specify the username and password and it runs. But with webdynpro, we are not able to invoke it.
Any ideas what we can do?
Here is the WSDL below:
Thanks,
Jay
<?xml version="1.0" encoding="ISO-8859-1"?>
<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:rfc="urn:sap-com:document:sap:rfc:functions" xmlns:p1="http://xyz.com/xi/xi_demo" name="BAPI_COMPANYCODE_GETLIST_OUTBOUND_SYNC_MI" targetNamespace="http://xyz.com/xi/xi_demo">
     <wsdl:types>
          <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:sap-com:document:sap:rfc:functions" targetNamespace="urn:sap-com:document:sap:rfc:functions">
               <xsd:element name="BAPI_COMPANYCODE_GETLIST.Response">
                    <xsd:complexType>
                         <xsd:all>
                              <xsd:element name="RETURN" type="BAPIRETURN" minOccurs="0"/>
                              <xsd:element name="COMPANYCODE_LIST">
                                   <xsd:complexType>
                                        <xsd:sequence>
                                             <xsd:element name="item" type="BAPI0002_1" minOccurs="0" maxOccurs="unbounded"/>
                                        </xsd:sequence>
                                   </xsd:complexType>
                              </xsd:element>
                         </xsd:all>
                    </xsd:complexType>
               </xsd:element>
               <xsd:element name="BAPI_COMPANYCODE_GETLIST">
                    <xsd:complexType>
                         <xsd:all>
                              <xsd:element name="COMPANYCODE_LIST">
                                   <xsd:complexType>
                                        <xsd:sequence>
                                             <xsd:element name="item" type="BAPI0002_1" minOccurs="0" maxOccurs="unbounded"/>
                                        </xsd:sequence>
                                   </xsd:complexType>
                              </xsd:element>
                         </xsd:all>
                    </xsd:complexType>
               </xsd:element>
               <xsd:complexType name="BAPI0002_1">
                    <xsd:sequence>
                         <xsd:element name="COMP_CODE" minOccurs="0">
                              <xsd:simpleType>
                                   <xsd:restriction base="xsd:string">
                                        <xsd:maxLength value="4"/>
                                   </xsd:restriction>
                              </xsd:simpleType>
                         </xsd:element>
                         <xsd:element name="COMP_NAME" minOccurs="0">
                              <xsd:simpleType>
                                   <xsd:restriction base="xsd:string">
                                        <xsd:maxLength value="25"/>
                                   </xsd:restriction>
                              </xsd:simpleType>
                         </xsd:element>
                    </xsd:sequence>
               </xsd:complexType>
               <xsd:complexType name="BAPIRETURN">
                    <xsd:sequence>
                         <xsd:element name="TYPE" minOccurs="0">
                              <xsd:simpleType>
                                   <xsd:restriction base="xsd:string">
                                        <xsd:maxLength value="1"/>
                                   </xsd:restriction>
                              </xsd:simpleType>
                         </xsd:element>
                         <xsd:element name="CODE" minOccurs="0">
                              <xsd:simpleType>
                                   <xsd:restriction base="xsd:string">
                                        <xsd:maxLength value="5"/>
                                   </xsd:restriction>
                              </xsd:simpleType>
                         </xsd:element>
                         <xsd:element name="MESSAGE" minOccurs="0">
                              <xsd:simpleType>
                                   <xsd:restriction base="xsd:string">
                                        <xsd:maxLength value="220"/>
                                   </xsd:restriction>
                              </xsd:simpleType>
                         </xsd:element>
                         <xsd:element name="LOG_NO" minOccurs="0">
                              <xsd:simpleType>
                                   <xsd:restriction base="xsd:string">
                                        <xsd:maxLength value="20"/>
                                   </xsd:restriction>
                              </xsd:simpleType>
                         </xsd:element>
                         <xsd:element name="LOG_MSG_NO" minOccurs="0">
                              <xsd:simpleType>
                                   <xsd:restriction base="xsd:string">
                                        <xsd:maxLength value="6"/>
                                        <xsd:pattern value="\d+"/>
                                   </xsd:restriction>
                              </xsd:simpleType>
                         </xsd:element>
                         <xsd:element name="MESSAGE_V1" minOccurs="0">
                              <xsd:simpleType>
                                   <xsd:restriction base="xsd:string">
                                        <xsd:maxLength value="50"/>
                                   </xsd:restriction>
                              </xsd:simpleType>
                         </xsd:element>
                         <xsd:element name="MESSAGE_V2" minOccurs="0">
                              <xsd:simpleType>
                                   <xsd:restriction base="xsd:string">
                                        <xsd:maxLength value="50"/>
                                   </xsd:restriction>
                              </xsd:simpleType>
                         </xsd:element>
                         <xsd:element name="MESSAGE_V3" minOccurs="0">
                              <xsd:simpleType>
                                   <xsd:restriction base="xsd:string">
                                        <xsd:maxLength value="50"/>
                                   </xsd:restriction>
                              </xsd:simpleType>
                         </xsd:element>
                         <xsd:element name="MESSAGE_V4" minOccurs="0">
                              <xsd:simpleType>
                                   <xsd:restriction base="xsd:string">
                                        <xsd:maxLength value="50"/>
                                   </xsd:restriction>
                              </xsd:simpleType>
                         </xsd:element>
                    </xsd:sequence>
               </xsd:complexType>
          </xsd:schema>
     </wsdl:types>
     <wsdl:message name="rfc.BAPI_COMPANYCODE_GETLIST.Input">
          <wsdl:part name="parameters" element="rfc:BAPI_COMPANYCODE_GETLIST"/>
     </wsdl:message>
     <wsdl:message name="rfc.BAPI_COMPANYCODE_GETLIST.Output">
          <wsdl:part name="parameters" element="rfc:BAPI_COMPANYCODE_GETLIST.Response"/>
     </wsdl:message>
     <wsdl:portType name="BAPI_COMPANYCODE_GETLIST_OUTBOUND_SYNC_MI">
          <wsdl:operation name="BAPI_COMPANYCODE_GETLIST_OUTBOUND_SYNC_MI">
               <wsdl:input message="p1:rfc.BAPI_COMPANYCODE_GETLIST.Input"/>
               <wsdl:output message="p1:rfc.BAPI_COMPANYCODE_GETLIST.Output"/>
          </wsdl:operation>
     </wsdl:portType>
     <wsdl:binding name="BAPI_COMPANYCODE_GETLIST_OUTBOUND_SYNC_MIBinding" type="p1:BAPI_COMPANYCODE_GETLIST_OUTBOUND_SYNC_MI">
          <soap:binding xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
          <wsdl:operation name="BAPI_COMPANYCODE_GETLIST_OUTBOUND_SYNC_MI">
               <soap:operation xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" soapAction="http://sap.com/xi/WebService/soap1.1"/>
               <wsdl:input>
                    <soap:body use="literal" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"/>
               </wsdl:input>
               <wsdl:output>
                    <soap:body use="literal" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"/>
               </wsdl:output>
          </wsdl:operation>
     </wsdl:binding>
     <wsdl:service name="BAPI_COMPANYCODE_GETLIST_OUTBOUND_SYNC_MIService">
          <wsdl:port name="BAPI_COMPANYCODE_GETLIST_OUTBOUND_SYNC_MIPort" binding="p1:BAPI_COMPANYCODE_GETLIST_OUTBOUND_SYNC_MIBinding">
               <soap:address location="http://servername:50000/XISOAPAdapter/MessageServlet?channel=:BS_EXTERNALAPP:BAPI_COMPANYCODE_GETLIST_WEBSERVICE_SOAP_SENDER&version=3.0&Sender.Service=BS_EXTERNALAPP&Interface=http%3A%2F%2Fxyz.com%2Fxi%2Fxi_demo%5EBAPI_COMPANYCODE_GETLIST_OUTBOUND_SYNC_MI" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"/>
          </wsdl:port>
     </wsdl:service>
</wsdl:definitions>

While generating a wsdl in XI the url provided should be as below:
Override the default URL with following while generating WSDL using web service wizard.
Default URL:
http://host:port/XISOAPAdapter/MessageServlet?channel=:<service>:<channel>
To import the WSDL in webdynpro,
In NWDS Create Model -> Import Web Service Model (referring the XI WSDL)
Instantiate the request object and pass the mandatory parameters for request object and call execute method.
Thanks and Regards,
Amar Bhagat Challa.

Problem invoking XI webservice through webdynpro

We have created a webservice on XI that calls the BAPI_COMPANYCODE_GETLIST on an R/3 4.6C system. We generated the WSDL using the Integration builder and corrected the URL to point to the webservice (rather than the wizard proposed URL).
We can call the webservice through XMLspy and other tools. But we are not able to use webdynpro to invoke the webservice. We uploaded the webservice on the web application server so we can get to it through a URL.
The problem is that when we use webdynpro and try to link it to a webservice, we can point to the URL which is for the WSDL we uploaded to the webserver. But there is no other field in webdynpro to specify the URL for the webservice endpoint. The endpoint is actually in the WSDL and it seems correct:
http://servername:50000/XISOAPAdapter/MessageServlet?channel=:BS_EXTERNALAPP:BAPI_COMPANYCODE_GETLIST_WEBSERVICE_SOAP_SENDER;version=3.0;Sender.Service=BS_EXTERNALAPP;Interface=http://xyz.com/xi_demo/BAPI_COMPANYCODE_GETLIST_OUTBOUND_SYNC_MI
Through XMLspy we can just point to the WSDL. And then we can just specify the username and password and it runs. But with webdynpro, we are not able to invoke it.
Any ideas what we can do?
Here is the WSDL below:
Thanks,
Jay
<?xml version="1.0" encoding="ISO-8859-1"?>
<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:rfc="urn:sap-com:document:sap:rfc:functions" xmlns:p1="http://xyz.com/xi/xi_demo" name="BAPI_COMPANYCODE_GETLIST_OUTBOUND_SYNC_MI" targetNamespace="http://xyz.com/xi/xi_demo">
     <wsdl:types>
          <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:sap-com:document:sap:rfc:functions" targetNamespace="urn:sap-com:document:sap:rfc:functions">
               <xsd:element name="BAPI_COMPANYCODE_GETLIST.Response">
                    <xsd:complexType>
                         <xsd:all>
                              <xsd:element name="RETURN" type="BAPIRETURN" minOccurs="0"/>
                              <xsd:element name="COMPANYCODE_LIST">
                                   <xsd:complexType>
                                        <xsd:sequence>
                                             <xsd:element name="item" type="BAPI0002_1" minOccurs="0" maxOccurs="unbounded"/>
                                        </xsd:sequence>
                                   </xsd:complexType>
                              </xsd:element>
                         </xsd:all>
                    </xsd:complexType>
               </xsd:element>
               <xsd:element name="BAPI_COMPANYCODE_GETLIST">
                    <xsd:complexType>
                         <xsd:all>
                              <xsd:element name="COMPANYCODE_LIST">
                                   <xsd:complexType>
                                        <xsd:sequence>
                                             <xsd:element name="item" type="BAPI0002_1" minOccurs="0" maxOccurs="unbounded"/>
                                        </xsd:sequence>
                                   </xsd:complexType>
                              </xsd:element>
                         </xsd:all>
                    </xsd:complexType>
               </xsd:element>
               <xsd:complexType name="BAPI0002_1">
                    <xsd:sequence>
                         <xsd:element name="COMP_CODE" minOccurs="0">
                              <xsd:simpleType>
                                   <xsd:restriction base="xsd:string">
                                        <xsd:maxLength value="4"/>
                                   </xsd:restriction>
                              </xsd:simpleType>
                         </xsd:element>
                         <xsd:element name="COMP_NAME" minOccurs="0">
                              <xsd:simpleType>
                                   <xsd:restriction base="xsd:string">
                                        <xsd:maxLength value="25"/>
                                   </xsd:restriction>
                              </xsd:simpleType>
                         </xsd:element>
                    </xsd:sequence>
               </xsd:complexType>
               <xsd:complexType name="BAPIRETURN">
                    <xsd:sequence>
                         <xsd:element name="TYPE" minOccurs="0">
                              <xsd:simpleType>
                                   <xsd:restriction base="xsd:string">
                                        <xsd:maxLength value="1"/>
                                   </xsd:restriction>
                              </xsd:simpleType>
                         </xsd:element>
                         <xsd:element name="CODE" minOccurs="0">
                              <xsd:simpleType>
                                   <xsd:restriction base="xsd:string">
                                        <xsd:maxLength value="5"/>
                                   </xsd:restriction>
                              </xsd:simpleType>
                         </xsd:element>
                         <xsd:element name="MESSAGE" minOccurs="0">
                              <xsd:simpleType>
                                   <xsd:restriction base="xsd:string">
                                        <xsd:maxLength value="220"/>
                                   </xsd:restriction>
                              </xsd:simpleType>
                         </xsd:element>
                         <xsd:element name="LOG_NO" minOccurs="0">
                              <xsd:simpleType>
                                   <xsd:restriction base="xsd:string">
                                        <xsd:maxLength value="20"/>
                                   </xsd:restriction>
                              </xsd:simpleType>
                         </xsd:element>
                         <xsd:element name="LOG_MSG_NO" minOccurs="0">
                              <xsd:simpleType>
                                   <xsd:restriction base="xsd:string">
                                        <xsd:maxLength value="6"/>
                                        <xsd:pattern value="\d+"/>
                                   </xsd:restriction>
                              </xsd:simpleType>
                         </xsd:element>
                         <xsd:element name="MESSAGE_V1" minOccurs="0">
                              <xsd:simpleType>
                                   <xsd:restriction base="xsd:string">
                                        <xsd:maxLength value="50"/>
                                   </xsd:restriction>
                              </xsd:simpleType>
                         </xsd:element>
                         <xsd:element name="MESSAGE_V2" minOccurs="0">
                              <xsd:simpleType>
                                   <xsd:restriction base="xsd:string">
                                        <xsd:maxLength value="50"/>
                                   </xsd:restriction>
                              </xsd:simpleType>
                         </xsd:element>
                         <xsd:element name="MESSAGE_V3" minOccurs="0">
                              <xsd:simpleType>
                                   <xsd:restriction base="xsd:string">
                                        <xsd:maxLength value="50"/>
                                   </xsd:restriction>
                              </xsd:simpleType>
                         </xsd:element>
                         <xsd:element name="MESSAGE_V4" minOccurs="0">
                              <xsd:simpleType>
                                   <xsd:restriction base="xsd:string">
                                        <xsd:maxLength value="50"/>
                                   </xsd:restriction>
                              </xsd:simpleType>
                         </xsd:element>
                    </xsd:sequence>
               </xsd:complexType>
          </xsd:schema>
     </wsdl:types>
     <wsdl:message name="rfc.BAPI_COMPANYCODE_GETLIST.Input">
          <wsdl:part name="parameters" element="rfc:BAPI_COMPANYCODE_GETLIST"/>
     </wsdl:message>
     <wsdl:message name="rfc.BAPI_COMPANYCODE_GETLIST.Output">
          <wsdl:part name="parameters" element="rfc:BAPI_COMPANYCODE_GETLIST.Response"/>
     </wsdl:message>
     <wsdl:portType name="BAPI_COMPANYCODE_GETLIST_OUTBOUND_SYNC_MI">
          <wsdl:operation name="BAPI_COMPANYCODE_GETLIST_OUTBOUND_SYNC_MI">
               <wsdl:input message="p1:rfc.BAPI_COMPANYCODE_GETLIST.Input"/>
               <wsdl:output message="p1:rfc.BAPI_COMPANYCODE_GETLIST.Output"/>
          </wsdl:operation>
     </wsdl:portType>
     <wsdl:binding name="BAPI_COMPANYCODE_GETLIST_OUTBOUND_SYNC_MIBinding" type="p1:BAPI_COMPANYCODE_GETLIST_OUTBOUND_SYNC_MI">
          <soap:binding xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
          <wsdl:operation name="BAPI_COMPANYCODE_GETLIST_OUTBOUND_SYNC_MI">
               <soap:operation xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" soapAction="http://sap.com/xi/WebService/soap1.1"/>
               <wsdl:input>
                    <soap:body use="literal" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"/>
               </wsdl:input>
               <wsdl:output>
                    <soap:body use="literal" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"/>
               </wsdl:output>
          </wsdl:operation>
     </wsdl:binding>
     <wsdl:service name="BAPI_COMPANYCODE_GETLIST_OUTBOUND_SYNC_MIService">
          <wsdl:port name="BAPI_COMPANYCODE_GETLIST_OUTBOUND_SYNC_MIPort" binding="p1:BAPI_COMPANYCODE_GETLIST_OUTBOUND_SYNC_MIBinding">
               <soap:address location="http://servername:50000/XISOAPAdapter/MessageServlet?channel=:BS_EXTERNALAPP:BAPI_COMPANYCODE_GETLIST_WEBSERVICE_SOAP_SENDER&version=3.0&Sender.Service=BS_EXTERNALAPP&Interface=http%3A%2F%2Fxyz.com%2Fxi%2Fxi_demo%5EBAPI_COMPANYCODE_GETLIST_OUTBOUND_SYNC_MI" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"/>
          </wsdl:port>
     </wsdl:service>
</wsdl:definitions>

When i try to make the call through Test Data service in Visual composer, i get the error: "Portal request failed (Could not execute Web service operation)". This happens regardless of whether we supply input values for Comp Code and Comp Name.
So Visual composer is reading the WSDL and showing the input parameters correctly. The link for the WSDL needs the same authentication user and pwd as the actual webservice invocation link which is in the WSDL.
So i am not sure why the call is failing because it works easily through XMLspy.
- Jay

Invoking a webservice as an "application process"

Similar Messages

Maybe you are looking for