External Web Service setting for Supplier Registration ROS to EBP

Dear guys,
We are working on Supplier registration scenario where potential supplier are accepted in ROS client and then transferred to EBP via Suppliers Directory.
For this we have defined External Web Service in both clients ROS and EBP
Can anyone tell me what are the Parameters and setting required to define External Web Service?
We have created New Web Service with following parameters in both the clients ROS and EBP.
Web Service ID                     : ROS
Description                          : Suppliers Directory in ROS Client
Bus. Type of Web Service               : Lost of Vendors
Display Partners Data Again in Vendor List      : X
Vendor Root Node                     : 50000620
Use Error Log                         : X
Use HTTP GET to call Web Service          : <blank>
Codepage of Service                    : <blank>
Technical Type of Service               : <blank>
Logical system                    : SRDCLNT300 (EBP Logical system)
Path for Symbol for Service               : <blank>
Define Standard Call Structure with following Parameters
1        <blank>     http://erpdevsrci.egat.co.th:8010/sap/bc/bsp/sap/ros_prescreen/main.do
          URL
2        HOOK_URL      <blank>     Return URL
Please correct us.
With this setting system does display the Suppliers Directory option in Supplier Screening (Suppliers Directory in ROS Client), however after selecting suppliers directory instead of listing the accepted supplier to transfer to EBP, system displays the same suppliers Prescreen again with no option to transfer accepted supplier to EBP client.
I think I have not set the External Web services setting properly ..
So can anyone send me the correct web service parameter setting?
Regards,
Sandeep parab

Ramki/disha,
I have defined following setting in external web services in EBP client
Web Service ID : ROS
Description: External Web Service in EBP
Bus Type of a Web service : List of Vendors
Display Partner Data again in Vendor List : X
Vendor Root Node : 50000620 (this is Vensor Root node in EBP client)
Use Error Log : X
Use HTTP GET to call Web Service : <blank>
Codepage of Service: <blank>
Techinical type of Service : <Blank>
Logical system : SRDCLNT310 (this is ROs client from there supplier will be transfered)
Path for symbol for service : <blank>
Standard Call Structure Parameter setting as follows
1. <blank> http://....ros_prescreen/main.do URL
2. sap-client 310 fixed_value
3. sap-username dineshp fixed_value
4. sap-password GAJANAN fixed_value
5. HOOK_URL <blank> Return_URL
6. ~OkCode ADDI fixed_value
7. ~target top fixedvalue
8. ~caller CTLG fixed_value
Also defined ROS external web service as default CAT attribute in the organization setting.
Maintained ROS client in SAP_BBP_STAL_STRAT_PURCHASER role.
Created New Users in ROS as well as EBP and tried the scenario. still it failed to transfer the supplier from Ros to EBP.
Where can we debug the error message?
Regards,
Sandeep

Similar Messages

Not able to use external Web service

Hi All,
I am facing an issue where in I am not able to access the external web service through webi rich client.
Error is Provided URL is not valid WIS 10853
It works fine for QAAWS and the external web service opens fine through Browser ( it opens an XML page ).
Additionally I have xcelcius installed and the external web service works fine on it.
What can be the problem??
Regards
KP

i want to expose data from share point through a webservice and use that webservice as a data source in Bi Publisher. But i am not able to use the webservice directly since it is a external web service.
But i am not able to use the webservice directly since it is a external web service.
why?
look at "Creating a BI Publisher Report Based on External Web Services" ExternalWebServices
For that i made below config changes. But it is causing weblogic server starting issues.
why do you want to change some weblogic server settings?

External web service call from WebDynpro for ABAP

Hi...
I'm inspecting Web Dynpro For ABAP, and trying to call external web services.
I'm created Web Service, CAF-AS.
I create the proxy class(se80) and Logical Port(lpconfig), and I take the web service in componentcontoroller of my web dynpro using Web Dynpro Wiserd.
Though I expected the context to be registered by the same type as the service interface,
they are created strange structure as follow.
<Context>
CONTEXT
---FIND_BY_PARAMS
IMPORTING
INPUT
CONTROLLER
ORDER_TEXT_BY_PARAMS_REQ
---EXPORTING
OUTPUT
CONTROLLER
ORDER_TEXT_BY_PARAMS_RES
The CONTOROLLER is defined by the type PRXCTRLTAB, and
ORDER_TEXT_BY_PARAMS_* has deep structure, as follow.
ORDER_TEXT_BY_PARAMS_REQ
---CONTROLLER type:PRXCTRLTAB(structure)
---QUERY_TABLE type:ZTABLE_NAME
---QUERY_FIELD type:ZFIELD_NAME
---QUERY_OPTIONS type:ZORDER_TEXT_QUERY_OPTION_TAB
I want to use only service paralmeters, that is named query_*.
I tried to excute the webService but dump "OBJECTS_OBJREF_NOT_ASSIGNED" occurs.
I think I must set any value to CONTOROLLER,?but I have no idea What & How I should set value.
please let me know, what is the CONTOROLLER, and how to call external web services.
Regards,
Naoya Tsugo,

I solved problem by myself.
There was carelessmiss in activation of LP.
Now, I'm closing the topic.
Thanks and Regards.
Naoya Tsugo,

Use BizTalk 2006 as a proxy for an external Web Service

Hi
We have a solution that is going to work just as a proxy for an external Web Service.
It works like this:
1. We have a Request-Response receive port that receives the calls for the WS.
2. Different Static Solicit-Response ports that have filters for each method in the WS receive the requests and then send them to the external WS.
3. The response from the external WS is then sendt back to the caller via the Request-Response port in point 1.
This generally works like it should. The only problem i have is when the external WS returns a Fault message. I get this fault from the external WS:
<s:Fault xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>s:Client</faultcode><faultstring xml:lang="nb-NO">Some error message the caller should see.</faultstring><detail><GenericFault
xmlns="http://register.test.com/Common" xmlns:i="http://www.w3.org/2001/XMLSchema-instance"><ErrorCode>SomthingWentWrong</ErrorCode><Message>Some error message the caller should see.</Message></GenericFault></detail></s:Fault>
This message then failes on BizTalk and BizTalk returns this Fault message to the caller:
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><SOAP:Body><SOAP:Fault><faultcode>Microsoft BizTalk Server Negative Acknowledgment
</faultcode><faultstring>An error occurred while processing the message, refer to the details section for more information </faultstring><faultactor>/Hemit.BizTalk.NHN.Position.ws/IPositionService.asmx</faultactor><detail><ns0:NACK
Type="NACK" xmlns:ns0="http://schema.microsoft.com/BizTalk/2003/NACKMessage.xsd"><NAckID>{7AC314FE-2CA3-44AE-8208-180495500481}</NAckID><ErrorCode>0xc0c016b7</ErrorCode><ErrorCategory>0</ErrorCategory><ErrorDescription>There
is an error in XML document (1, 2).</ErrorDescription><ErrorDetail><Fault xmlns='http://schemas.xmlsoap.org/soap/envelope/'> was not expected.</ErrorDetail></ns0:NACK></detail></SOAP:Fault></SOAP:Body></SOAP:Envelope>
So the problem seems to be that the Request-Response port in point one will ONLY accept the real response that is specified in the response schema for that particular method, and not a Fault. And when it receives a fault, it generates its own Fault saying
a Fault message was not expected.
Does anyone know how i can be able to send the actual fault from the external WS all the way back to the caller on the inside?
I know how to do it with an orchestration, but can not figure out how to get it done just with the ports.
Kind regars
John Viggo

Hi John,
Enable Propagate fault message
on the WCF solict –response port.
For the two-way send port, you can choose whether to forward
SOAP fault messages on to the original caller over a solicit-response send port by selecting
Propagate fault message. If this option is not selected, BizTalk Server will generate a NACK. What you see is the NACK.
If it is selected, BizTalk Server will treat the message as a valid WCF response message from the external service and the response message will not be suspended because it is propagated.
Then you need to map the fault message to the actual response in the map. Set this Fault-Message to Caller-Response map in the outbound map of the Requeust-Response port.
In this case of messaging-only scenario, this method shall help in handling the fault message and passing fault details back to the caller. Refer the following articles for more details.
Synchronous web services calls and Faults
BizTalk and
SOAPFault
version issues
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful.

Calling external Web Service: PI is looking for a logical port and proxy.

Hi,
My scenario is ECC Proxy -> PI -> External Webservice (WS adapter).
the Web service adapter fails with the error message:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">WS_ADAPTER_SYS_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>System error while calling Web service adapter: Error when initializing SOAP client application: 'error_text'</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
When I debug the message processing, it is looking for a port in table SSRVRTCONFIG, finds it(entry created automatically when WS adapter and the corresponding receiver agreement is activated in ID.
Then the program looks for an entry in "SRT_CFG_CLI_ASGN" for a proxy and logical port combination and errors out.
to be able to call an external web service, do we need a proxy to be created? I tried to create but the proxy creation fails because the external WSDL has some unsupported tags.
Also do we need to do any other configuration in SOAMANAGER? I am assuming not because the Web service is external.
Any help would be appreciated.
Thanks
Vijay

I already checked that note and made sure that the points mentioned are met. I have a trace set up on the target system and would know if the call reaches them and then fails in authorization. Right now the call doesnt even reach the target system and also from debugging I know that the program is looking for a proxy and then fails.

Sun BPEL engine sets wrong Content-Type on calling an external web service

I have a WSDL for an external web service (which as it happens is running in Websphere locally) and have implemented it as a
partnerlink on a BPEL diagram in an SOA composite project. The binding style is Document and if you use SOAPUI to test it it
works fine. Tracing on the web service's server shows the SOAP request coming in. It has a content-type of text/xml, as expected. If I do a JUnit test from NetBeans based on this WSDL alone it also works - same result. BUT if I do
a full test and call my BPEL process the invocation of this service from BPEL fails.
On the Test result you see
BPCOR-6135:A fault was not handled in the process scope; Fault Name is http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault;
(This happens because I did not handle the fault in the BPEL.)
On the trace I see it now has Content-type of application/xop+xml. Why would the Sun BPEL engine change this? I just
accepted the usual defaults when I created the PartnerLink and the Invoke. Anyway, the format of the request doesn't match what the WS server expects, so it fails.
As far as I'm aware I'm just using SOAP1.1. This is NetBeans 6.5 with Glassfish 2.1. I tried with NetBeans 6.7 and it got worse, not better. I would certainly appreciate any advice?
Thanks

Perhaps when the BPEL file based process calls the WSDL file to execute,their message communication is not correct.
the head part in the WSDL file should be manually set to "text/xml", or the IDE or Server will use the default value;
for example as follow:
SOAPUI tool would use the default value "text/xml" to request.(depends the tool support).
NetBeans tool would use the default value "text/xml" to request.
when you do a full test and you do not set the head "context-type" value ,the WSDL file use the server's default head
value"application/xop-xml" so that return the contents under the control of the server's default value.
I hope these will be useful for you.

BPEL engine sets wrong Content-Type on calling an external web service

I have a WSDL for an external web service (which as it happens is running in Websphere locally) and have implemented it as a
partnerlink on a BPEL diagram in an SOA composite project.
The binding style is Document and if you use SOAPUI to test it it
works fine. Tracing on the web service's server shows the SOAP request
coming in. It has a content-type of text/xml, as expected. If I do a
JUnit test from NetBeans based on this WSDL alone it also works - same result. BUT if I do
a full test and call my BPEL process the invocation of this service
from BPEL fails.
On the Test result you see
BPCOR-6135:A fault was not handled in the process scope; Fault Name is http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault;
(This happens because I did not handle the fault in the BPEL.)
On the trace I see it now has Content-type of
application/xop+xml. Why would the Sun BPEL engine change this? I just
accepted the usual defaults when I created the PartnerLink and the
Invoke. Anyway, the format of the request doesn't match what the WS server expects, so it fails.
As far as I'm aware I'm just using SOAP1.1. This is NetBeans 6.5 with
Glassfish 2.1. I tried with NetBeans 6.7 and it got worse, not better.
I would certainly appreciate any advice?
Thanks

Perhaps when the BPEL file based process calls the WSDL file to execute,their message communication is not correct.
the head part in the WSDL file should be manually set to "text/xml", or the IDE or Server will use the default value;
for example as follow:
SOAPUI tool would use the default value "text/xml" to request.(depends the tool support).
NetBeans tool would use the default value "text/xml" to request.
when you do a full test and you do not set the head "context-type" value ,the WSDL file use the server's default head
value"application/xop-xml" so that return the contents under the control of the server's default value.
I hope these will be useful for you.

Best practice for integrating oracle atg with external web service

Hi All
What is the best practice for integrating oracle atg with external web service? Is it using integration repository or calling the web service directly from the java class using a WS client?
With Thanks & Regards
Abhishek

Using Integration Repository might cause performance overhead based on the operation you are doing, I have never used Integration Repository for 3rd Party integration therefore I am not able to make any comment on this.
Calling directly as a Java Client is an easy approach and you can use ATG component framework to support that by making the endpoint, security credentials etc as configurable properties.
Cheers
R
Edited by: Rajeev_R on Apr 29, 2013 3:49 AM

Stub(Proxy) generation for external Web Service in SAP NW WebAS 6.40

Hi,
Can anyone tell me what tool is used to generate the proxy files for accessing any external web services in SAP NetWeaver WebAS 6.40 for JAVA (SAP DevStudio 2.0.5).
Do i have to install any components or configuration for using external web services?
Thanks,
Mital.

Hi Peter,
Thanks for the reply.
I have already gone through the Email Web Service tutorial. And implemented the tutorila.But no where they have mentioned about the toolkit they are using to generate stub files and SOAP request.(for eg Axis tool for WSDL to java generation).
Also I am facing problems while I am trying to use an external webservice. I have posted the problem at Re: WebDynpro External Web Service Model.
It would be nice if uyou can go through the problem and help me in solving the problem.
Also can you please tell me the link for the mentioned documents on importing web service model.
Thanks,
Mital.

Not able to registred the external Web service on CF8

I am not able to registred the external Web service on CF8 (Error creating web service. Please ensure that you have entered a correct Web Service name or URL.), but same Web service has no problem on CF6.1

Hi,
Please close this duplicated thread.
Thanks & Regards,
Nagarajan

What is the URL for an external web service

I have an external web service that I want to invoke a BPEL process. I was wondering how to find the URL for the BPEL process.
cheers
James

We're invoking the BPEL endpoint from a .NET app using the 'endpoint location' but seemed to be forced to use the embedded version number. For instance we have to say 'http://<server>:<port>/orabpel/<domain>/<process>/1.0' and I can't seem to get rid of the '1.0'. This contrasts to the WSDL location where I can use a browser and remove the version number to get the current default.
Am I doing something wrong? I'd like to avoid embedding the version in the endpoint.

Error while trying to call external web service from oracle PL/SQL 10.2 g

Hi I am trying to call an external web service from oracle PL/SQL .I am getting following run time error when I try to set the opeartion style.
But as per the oracle documentation this is one of the 2 valid values.
ORA-29532: Java call terminated by uncaught Java exception: operation style: "document" not supported.Teh webservice does expect the operation style as document.
Following is the code I am executing.
FUNCTION email
return varchar2
AS
service_ SYS.utl_dbws.SERVICE;
call_ SYS.utl_dbws.CALL;
service_qname SYS.utl_dbws.QNAME;
port_qname SYS.utl_dbws.QNAME;
operation_qname SYS.utl_dbws.QNAME;
string_type_qname SYS.utl_dbws.QNAME;
retx ANYDATA;
retx_string VARCHAR2(1000);
retx_double number;
retx_len number;
params SYS.utl_dbws.ANYDATA_LIST;
l_input_params SYS.utl_dbws.anydata_list;
l_result ANYDATA;
l_namespace VARCHAR2(1000);
begin
-- open internet explorer and navigate to http://webservices.imacination.com/distance/Distance.jws?wsdl
-- search for 'targetNamespace' in the wsdl
l_namespace := 'http://service.xmlservices.global.freedomgroup.com/';
-- search for 'service name' in the wsdl
service_qname := SYS.utl_dbws.to_qname(l_namespace, 'ClientCoreWebServiceBeanService');
-- this is just the actual wsdl url
service_ := SYS.utl_dbws.create_service(HTTPURITYPE('http://hostname/GlobalWebServices/services/ClientCoreWebService?wsdl'), service_qname);
-- search for 'portType name' in the wsdl
port_qname := SYS.utl_dbws.to_qname(l_namespace, 'ClientCoreWebServiceBeanPort');
-- search for 'operation name' in the wsdl
-- there will be a lot, we will choose 'getCity'
operation_qname := SYS.utl_dbws.to_qname(l_namespace, 'postalCodelookup');
-- bind things together
call_ := SYS.utl_dbws.create_call(service_, port_qname, operation_qname);
-- default is 'FALSE', so we make it 'TRUE'
SYS.utl_dbws.set_property(call_, 'SOAPACTION_USE', 'TRUE');
-- search for 'operation soapAction' under <wsdl:operation name="getCity">
-- it is blank, so we make it ''
SYS.utl_dbws.set_property(call_, 'SOAPACTION_URI', '');
-- search for 'encodingstyle' under <wsdl:operation name="getCity">
SYS.utl_dbws.set_property(call_, 'ENCODINGSTYLE_URI', 'http://schemas.xmlsoap.org/soap/encoding/');
-- search for 'binding style'
SYS.utl_dbws.set_property(call_, 'OPERATION_STYLE', 'DOCUMENT');
-- search for 'xmlns:xs' to know the value of the first parameter
-- under <wsdl:message name="getCityResponse"> you will see the line <wsdl:part name="getCityReturn" type="xsd:string" />
-- thus the return type is 'string", removing 'xsd:'
string_type_qname := SYS.utl_dbws.to_qname('http://www.w3.org/2001/XMLSchema', 'string');
-- in the line <wsdl:operation name="getCity" parameterOrder="zip">
-- the parameterOrder is 'zip', thus we put in 'zip'
-- the 'ParameterMode.IN' is used to specify that we will be passing an "In Parameter" to the web service
-- the 'ParameterMode.IN' is a constant variable in the sys.utl_dbws package
--vj this cud be either params or xml
SYS.utl_dbws.add_parameter(call_, 'param1', string_type_qname, 'ParameterMode.IN');
SYS.utl_dbws.add_parameter(call_, 'param2', string_type_qname, 'ParameterMode.IN');
SYS.utl_dbws.set_return_type(call_, string_type_qname);
-- supply the In Parameter for the web service
params(0) := ANYDATA.convertvarchar('<TFGGlobalBasicXMLDO><systemCd>GLOBAL</systemCd><username>GlobalAdmin</username><password>GlobalAdmin</password><localID>1</localID></TFGGlobalBasicXMLDO>');
params(1) := ANYDATA.convertvarchar('<TFGGlobalPostalCodeLookupIDDO><postalCode>02446</postalCode><countryCode>USA</countryCode><stateCode>MA</stateCode><cityDisplay>BROOKLINE</cityDisplay><countyDisplay>NORFOLK</countyDisplay><include_inactive_flag>True</include_inactive_flag></TFGGlobalPostalCodeLookupIDDO>');
-- invoke the web service
retx := SYS.utl_dbws.invoke(call_, params);
dbms_output.put_line(retx.gettypename);
-- access the returned value and output it to the screen
retx_string := retx.accessvarchar2;
dbms_output.put_line('done' || retx_string);
dbms_output.put_line('PL/SQL DII client return ===> ' || retx_string);
-- release the web service call
SYS.utl_dbws.release_service(service_);
return retx_string;
end email;

thsi is urgent anybody ????

Error when calling an external web service (blank soap action)

I did a lot of searching on this message and did not find an answer. Most of the issues i found related to XI/PI, which we are not using.
There is a web service created outside of SAP for which i generated (from the WSDL) a proxy class in my DEV system, client 050, a few years ago. This was subsequently moved to QA and production, and all is working fine.
Now, i want the same web service to work in client 100. I created the logical port, and the RFC destination, but when i try to call the web service, i get the following error
Server did not recognize the value of HTTP Header SOAPAction
Since only the basis group around here can access the logical port definition,and rfc destination, i have no idea where this information should be set up. I should not have to reimport the WSDL, since the proxy was imported from DEV to QA and it is working in QA client 050. There is something i need to set up, specific to client 100, and i am missing it. I looked in SOAMANAGER, and i didnt see anything even set up there for client 050, so i did set up anything for client 100.
Any help would be appreciated.

I tried adding the web reference in a console app and works fine. In the plugins this can't be done, because the plugins are deploy in database.
I tried another basic test using ChannelFactory. Only want to retrieve some entity through the external web services:
IPluginExecutionContext context = localContext.PluginExecutionContext;
IOrganizationService service = localContext.OrganizationService;
ITracingService tracer = localContext.TracingService;
try
BasicHttpBinding binding = new BasicHttpBinding();
binding.Name = "BasicHttpBinding_IAxxisWcfServices";
binding.Security.Mode = BasicHttpSecurityMode.None;
binding.Security.Transport.ProxyCredentialType = HttpProxyCredentialType.None;
binding.Security.Transport.ClientCredentialType = HttpClientCredentialType.None;
EndpointAddress endpoint = new EndpointAddress(@"http://*****.svc");
ChannelFactory<IAxxisWcfServices> factory = new ChannelFactory<IAxxisWcfServices>(binding, endpoint);
IAxxisWcfServices channel = factory.CreateChannel();
var entity = channel.FindByEntities(new CRM.Application.Context.Dtos.Asegurado( { CrmGuid = "7C3E96C6-C3BC-E411-80DF-0A736AE14667" }, null, new CRM.Framework.Session() { User = "***", Password = "***" });
catch (Exception ex)
throw new InvalidPluginExecutionException(ex.Message);
That test threw the following exception on the GenericParameterAttributes of channelType of factory object:
http://s27.postimg.org/4wf3er8up/Error.png

Consuming external web services in CAF

Hi there,
I am trying to set up a show case where a composite CAF app (exposed via WD or VC) uses SAP web services as well as external services. In this case, I chose to use the Fedex web services (http://fedex.com/developer).
Everything works fine, I am able to import the webservice using the locally stored WSDL into my composite app, apply the mapping and implement the application service......build, deploy...all good.
The problem occurs when trying to create the physical destination (under nwa/destination template management). NW expects a pointer/url to the wsdl or wsil file, but Fedex doesn't provide that via http. Putting the wsdl on a different web server doesn't help either as the SOAP call will be routed to the same host where the wsdl resides (in this case NOT the fedex system).
Is there any way to circumvent the WSDL retrieval with external web services in Netweaver ? One alternative solution could be to use the Netweaver Service registry and publish the fedex wsdl to that, but I would like to avoid that as we haven't configured the SR at the moment.
Thx, Nick

Looks like I don't need it necessarily.
There seems to be a bug in NW/CE 7.1. When defining a destination which points to a WSDL file which in turn points to a different server for SOAP messages (ServicePort), the endpoint URL is incorrectly defined.
WSDL URL: http://www.server1.com/test.wsdl
SOAP URL/Port: http://server2.com/webservices
the server tries to dispatch the SOAP call to http://server1.com/webservices which can't be found.
In CE 7.1.1. though, that bug is fixed, and everything works fine without the need to publish the remote service (wsdl) to the SR and to subsequently query it.
Nick

Issue with calling external web service with authentication details ...

Hi,
     I am facing a deployment issue with Oracle ESB. I am trying to call an external Web Service with authentication from ESB SOAP Service. It is working fine with my local ESB version 10.1.3.3.0 Build PCBPEL_10.1.3.3.0_GENERIC_070615.0525; however it is getting an error at our development ESB version 10.1.3.3.1 Build PCBPEL_10.1.3.3.1_GENERIC_RELEASE.
     I am getting following error.
An unhandled exception has been thrown in the ESB system. The exception reported is: "org.collaxa.thirdparty.apache.wsif.WSIFException: exception during SOAP invoke: Server was unable to process request. ---> Object reference not set to an instance of an object.; nested exception is: javax.xml.rpc.soap.SOAPFaultException: Server was unable to process request. ---> Object reference not set to an instance of an object. at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.populateFaultMessage(WSIFOperation_JaxRpc.java:3086) at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.invokeOperation(WSIFOperation_JaxRpc.java:1728) at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.invokeRequestResponseOperation(WSIFOperation_JaxRpc.java:1473) at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.executeRequestResponseOperation(WSIFOperation_JaxRpc.java:1196) at oracle.tip.esb.server.common.wsif.WSIFInvoker.executeOperation(WSIFInvoker.java:867) at oracle.tip.esb.server.common.wsif.WSIFInvoker.nextService(WSIFInvoker.java:770) at oracle.tip.esb.server.common.wsif.WSIFInvoker.nextService(WSIFInvoker.java:790) at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.nextService(OutboundAdapterService.java:208) at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.processBusinessEvent(OutboundAdapterService.java:127) at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatchNonRoutingService(InitialEventDispatcher.java:118) at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(InitialEventDispatcher.java:95) at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1424) at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:112) at oracle.tip.esb.server.service.EsbRouterSubscription.onBusinessEvent(EsbRouterSubscription.java:307) at oracle.tip.esb.server.dispatch.EventDispatcher.executeSubscription(EventDispat
     Could one of you please help me out to understand why it is happining.
Thanks in advance.
Jyotirmoy.

Hi Mahesh,
One you are missing is authentication token or credentials.
Please refer to the following articles.
http://www.cleverworkarounds.com/2014/02/05/tips-for-using-spd-workflows-to-talk-to-3rd-party-web-services/
A Series of articles related to Web Service in SPD Workflow
Trials or tribulation?
Inside SharePoint 2013 workflows–Part 1
Trials or tribulation?
Inside SharePoint 2013 workflows–Part 2
Trials or tribulation?
Inside SharePoint 2013 workflows–Part 3
Trials or tribulation?
Inside SharePoint 2013 workflows–Part 4
Trials or tribulation?
Inside SharePoint 2013 workflows–Part 5
Trials or tribulation?
Inside SharePoint 2013 workflows–Part 6
Trials or tribulation?
Inside SharePoint 2013 workflows–Part 7
Trials or tribulation?
Inside SharePoint 2013 workflows–Part 8
Trials or tribulation?
Inside SharePoint 2013 workflows–Part 9
Trials or tribulation?
Inside SharePoint 2013 workflows–Part 10
Trials or tribulation?
Inside SharePoint 2013 workflows–Part 11
Trials or tribulation?
Inside SharePoint 2013 workflows–Part 12
Please don't forget to mark it answered, if your problem resolved or helpful

External Web Service setting for Supplier Registration ROS to EBP

Similar Messages

Maybe you are looking for