Define external web services

Hello all,
We are running CCM 1.0.Have a doubt regarding "defining the external web services" in catalog content management.
In the documents it says " you must define external web services to define the connection to:
1.] CCM catalogs; 2.] OCI Catalogs
What is the difference between the two?? Are CCM catalogs not OCI compliant?
I always thought that once we load catalogs in CAT and CSE..that is it.What are these OCI catalogs now??
Please help
Sam

Sam,
I can help you to define external webservices -
You can define webservices using WF_EXTSRV.
You will have to enter service id, Log, Servers, and Port, specify your system access data for HTTP. You can get these details from your BASIS team. You will have to specify path for your BSP (Web Page).
Select the call mode as 'Dialog Based Services'.
After this you will have to define import/export parameters. Normally export parameters is a 'Decision' made by the user (Approved / Rejected).
You will have to maintain entry for your service id and Web task in table SWLWPTSSID. (Use SM30 to do it).
Hope these details will help you.
Regards.
Pras

Similar Messages

Define External Web services in SPRO. in SRM

Hi SRM Gurus,
We are doing an Upgrade from SRM3.0 to SRM7.0 with MDM.
In SRM 7.0 -SPRO -We have to do the config in Define External Web services
What are the parameters to maintain.
I read from SDN that
Following parameters are not required in SRM 7.0. It was for ITS.
~OkCode ADDI
~target _top
~forcetarget yes
~caller CTLG
You need additional parameter in SRM 7.0.
returntarget _parent - for this what is the input parameters
Hi Masa /Muthu
Can you list down what are the Input parameters required for this config and the details?
Regards
G.Ganesh Kumar

Hi Masa,
We have deployed the SRM-MDM Catalog Search UI in Portal.
we tried accessing the http://<Portal Host>:<Portal Port>/SRM-MDM/SRM_MDM
Then we got a screen (Search UI App screen), where in we have provided the MDM Server name, then the MDM Server Password, then presses the Connect button, then below this, it displayed the Repository name created in the MDM. We have selected the Repository, then provided the Credentials of a User (Name: T_CORP) in MDM which has "Catalog Manager", and the "UI Configuration Manager" Roles. Please note that these Role names were created by us in MDM. Is it the right procedure or do we have any standard Roles delivered by SAP in MDM to map? If any standard Roles are available, where we need to check these.
Once the Credentials of MDM User is provided, and then selected the "Login" button.
Then we are getting the below error.
"java.lang.IllegalArgumentException: Table with Code 'null' does not exist in the repository 'Repository' or is one of the system table (e.g. Workflows) that is not exposed in repository schema"
Please clarify; we are not configuring any values in iViews. Where we need to do this, I mean name of the iView, and what values do we need provide generally? We are just running the Search UI App application; I don't think it is an iView, because the URL shows the Application name details, etc...
Please guide us, how to fix this Error.
Regards
G.Ganesh Kumar

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

Maintain External Web Services

Hi gurusu2026
We have implemented SRM-MDM and we are maintaining the catalogs what are available in SRM from the SPRO  SRM  SRM Server  Master Data  Define External Web Services (catalogs, vendors lists etc.)
Our problem comes when this options is not transportable from Development to production and we have to maintain it from Production directly (open the system). Is there any way to maintain it in development and transport to production? Or, is there any transaction to go directly and give role permissions to it?
Thanks in advance,
Jordi

Hello Jordi,
There is no way to be able to transport from development environment to production environment your external web services definition.
Indeed, even if you can have same call structure between all environments, technical settings for your web service cannot be the same: for example, logical system is used among those data.
So, you have to see with your production team to open customizing via SCC4 transaction in order to allow you to make mandatory modifications.
Regards.
Laurent.

Using an external web service and local element declarations

I am attempting to use (call) an external web service from workshop
8.1. It seems that if the web service's schema contains local element
declarations with the same name then workshop will generate incorrect
JCX code because it doesn't scope the generated classes.
I think the following simple example will do a better job explaining
than that last paragraph ;). In the following WSDL, the element
"testLocalDec" is used inside two different element types. In XML
Schema this is not a problem because each one is "scoped" by the
element types its included in. However, the generated JCX (listed
second) simply contains the testLocalDec structure twice which causes
problems in Java.
Is there some workaround for this? Note that making this element
declaration in the WSDL will not work because they are different
structures (with different names).
Also see my next email around using XMLBeans with external services
(since that could be a workaround if I knew how to do it).
thanks,
dave
*** sample WSDL ***
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:tns="urn:tutorial/hello"
targetNamespace="urn:tutorial/hello"
xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:apachesoap="http://xml.apache.org/xml-soap"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:types>
<s:schema targetNamespace="urn:tutorial/hello">
 <s:element name="sayHelloResponse" >
<s:complexType>
<s:sequence>
<s:element name="sayHelloReturn" type="s:string" />
<s:element name="testLocalDec" >
<s:complexType />
</s:element>
</s:sequence>
</s:complexType>
</s:element>
 <s:element name="sayHello" >
<s:complexType>
<s:sequence>
<s:element name="caller" type="s:string" />
<s:element name="testLocalDec" >
<s:complexType >
<s:sequence>
<s:element name="different" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
</s:sequence>
</s:complexType>
</s:element>
</s:schema>
</wsdl:types>
<wsdl:message name="sayHelloRequestMsg">
<wsdl:part name="message" element="tns:sayHello"/>
</wsdl:message>
<wsdl:message name="sayHelloResponseMsg">
<wsdl:part name="sayHelloReturn" element="tns:sayHelloResponse"/>
</wsdl:message>
<wsdl:portType name="HelloWorld">
<wsdl:operation name="sayHello" >
<wsdl:input message="tns:sayHelloRequestMsg" />
<wsdl:output message="tns:sayHelloResponseMsg" />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="HelloWorldServiceSoapBinding"
type="tns:HelloWorld">
<wsdlsoap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="sayHello">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="sayHelloRequestMsg">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="sayHelloResponseMsg">
<wsdlsoap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="HelloWorldService">
<wsdl:port binding="tns:HelloWorldServiceSoapBinding"
name="HelloWorldService">
<wsdlsoap:address
location="http://localhost:18080/tutorial/HelloWorldService"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
*** generated JCX ***
package helloTest;
* @jc:location
http-url="http://localhost:18080/tutorial/HelloWorldService"
* @jc:wsdl file="#HelloWorldServiceWsdl"
* @editor-info:link source="HelloWorldService.wsdl" autogen="true"
public interface HelloWorldServiceControl extends
com.bea.control.ControlExtension, com.bea.control.ServiceControl
public static class testLocalDec
implements java.io.Serializable
public static class sayHelloResponse
implements java.io.Serializable
public java.lang.String sayHelloReturn;
public testLocalDec testLocalDec;
public static class testLocalDec
implements java.io.Serializable
public java.lang.String different;
* @jc:protocol form-post="false" form-get="false"
public sayHelloResponse sayHello (java.lang.String caller,
testLocalDec testLocalDec);
static final long serialVersionUID = 1L;
/** @common:define name="HelloWorldServiceWsdl" value::
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:tns="urn:tutorial/hello"
targetNamespace="urn:tutorial/hello"
xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:apachesoap="http://xml.apache.org/xml-soap"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:types>
<s:schema targetNamespace="urn:tutorial/hello">
 <s:element name="sayHelloResponse" >
<s:complexType>
<s:sequence>
<s:element name="sayHelloReturn" type="s:string" />
<s:element name="testLocalDec" >
<s:complexType />
</s:element>
</s:sequence>
</s:complexType>
</s:element>
 <s:element name="sayHello" >
<s:complexType>
<s:sequence>
<s:element name="caller" type="s:string" />
<s:element name="testLocalDec" >
<s:complexType >
<s:sequence>
<s:element name="different" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
</s:sequence>
</s:complexType>
</s:element>
</s:schema>
</wsdl:types>
<wsdl:message name="sayHelloRequestMsg">
<wsdl:part name="message" element="tns:sayHello"/>
</wsdl:message>
<wsdl:message name="sayHelloResponseMsg">
<wsdl:part name="sayHelloReturn"
element="tns:sayHelloResponse"/>
</wsdl:message>
<wsdl:portType name="HelloWorld">
<wsdl:operation name="sayHello" >
<wsdl:input message="tns:sayHelloRequestMsg" />
<wsdl:output message="tns:sayHelloResponseMsg" />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="HelloWorldServiceSoapBinding"
type="tns:HelloWorld">
<wsdlsoap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="sayHello">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="sayHelloRequestMsg">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="sayHelloResponseMsg">
<wsdlsoap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="HelloWorldService">
<wsdl:port binding="tns:HelloWorldServiceSoapBinding"
name="HelloWorldService">
<wsdlsoap:address
location="http://localhost:18080/tutorial/HelloWorldService"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>

Hi David,
The folks in the workshop newgroup may have a suggestion, if you could
try your post there:
http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=xover&group=weblogic.developer.interest.workshop
Thanks,
Bruce
David Rees wrote:
>
I am attempting to use (call) an external web service from workshop
8.1. It seems that if the web service's schema contains local element
declarations with the same name then workshop will generate incorrect
JCX code because it doesn't scope the generated classes.
I think the following simple example will do a better job explaining
than that last paragraph ;). In the following WSDL, the element
"testLocalDec" is used inside two different element types. In XML
Schema this is not a problem because each one is "scoped" by the
element types its included in. However, the generated JCX (listed
second) simply contains the testLocalDec structure twice which causes
problems in Java.
Is there some workaround for this? Note that making this element
declaration in the WSDL will not work because they are different
structures (with different names).
Also see my next email around using XMLBeans with external services
(since that could be a workaround if I knew how to do it).
thanks,
dave
*** sample WSDL ***
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:tns="urn:tutorial/hello"
targetNamespace="urn:tutorial/hello"
xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:apachesoap="http://xml.apache.org/xml-soap"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:types>
<s:schema targetNamespace="urn:tutorial/hello">
<s:element name="sayHelloResponse" >
<s:complexType>
<s:sequence>
<s:element name="sayHelloReturn" type="s:string" />
<s:element name="testLocalDec" >
<s:complexType />
</s:element>
</s:sequence>
</s:complexType>
</s:element>
<s:element name="sayHello" >
<s:complexType>
<s:sequence>
<s:element name="caller" type="s:string" />
<s:element name="testLocalDec" >
<s:complexType >
<s:sequence>
<s:element name="different" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
</s:sequence>
</s:complexType>
</s:element>
</s:schema>
</wsdl:types>
<wsdl:message name="sayHelloRequestMsg">
<wsdl:part name="message" element="tns:sayHello"/>
</wsdl:message>
<wsdl:message name="sayHelloResponseMsg">
<wsdl:part name="sayHelloReturn" element="tns:sayHelloResponse"/>
</wsdl:message>
<wsdl:portType name="HelloWorld">
<wsdl:operation name="sayHello" >
<wsdl:input message="tns:sayHelloRequestMsg" />
<wsdl:output message="tns:sayHelloResponseMsg" />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="HelloWorldServiceSoapBinding"
type="tns:HelloWorld">
<wsdlsoap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="sayHello">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="sayHelloRequestMsg">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="sayHelloResponseMsg">
<wsdlsoap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="HelloWorldService">
<wsdl:port binding="tns:HelloWorldServiceSoapBinding"
name="HelloWorldService">
<wsdlsoap:address
location="http://localhost:18080/tutorial/HelloWorldService"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
*** generated JCX ***
package helloTest;
* @jc:location
http-url="http://localhost:18080/tutorial/HelloWorldService"
* @jc:wsdl file="#HelloWorldServiceWsdl"
* @editor-info:link source="HelloWorldService.wsdl" autogen="true"
public interface HelloWorldServiceControl extends
com.bea.control.ControlExtension, com.bea.control.ServiceControl
public static class testLocalDec
implements java.io.Serializable
public static class sayHelloResponse
implements java.io.Serializable
public java.lang.String sayHelloReturn;
public testLocalDec testLocalDec;
public static class testLocalDec
implements java.io.Serializable
public java.lang.String different;
* @jc:protocol form-post="false" form-get="false"
public sayHelloResponse sayHello (java.lang.String caller,
testLocalDec testLocalDec);
static final long serialVersionUID = 1L;
/** @common:define name="HelloWorldServiceWsdl" value::
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:tns="urn:tutorial/hello"
targetNamespace="urn:tutorial/hello"
xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:apachesoap="http://xml.apache.org/xml-soap"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:types>
<s:schema targetNamespace="urn:tutorial/hello">
<s:element name="sayHelloResponse" >
<s:complexType>
<s:sequence>
<s:element name="sayHelloReturn" type="s:string" />
<s:element name="testLocalDec" >
<s:complexType />
</s:element>
</s:sequence>
</s:complexType>
</s:element>
<s:element name="sayHello" >
<s:complexType>
<s:sequence>
<s:element name="caller" type="s:string" />
<s:element name="testLocalDec" >
<s:complexType >
<s:sequence>
<s:element name="different" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
</s:sequence>
</s:complexType>
</s:element>
</s:schema>
</wsdl:types>
<wsdl:message name="sayHelloRequestMsg">
<wsdl:part name="message" element="tns:sayHello"/>
</wsdl:message>
<wsdl:message name="sayHelloResponseMsg">
<wsdl:part name="sayHelloReturn"
element="tns:sayHelloResponse"/>
</wsdl:message>
<wsdl:portType name="HelloWorld">
<wsdl:operation name="sayHello" >
<wsdl:input message="tns:sayHelloRequestMsg" />
<wsdl:output message="tns:sayHelloResponseMsg" />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="HelloWorldServiceSoapBinding"
type="tns:HelloWorld">
<wsdlsoap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="sayHello">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="sayHelloRequestMsg">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="sayHelloResponseMsg">
<wsdlsoap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="HelloWorldService">
<wsdl:port binding="tns:HelloWorldServiceSoapBinding"
name="HelloWorldService">
<wsdlsoap:address
location="http://localhost:18080/tutorial/HelloWorldService"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>

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

External web service provided by third party application

Hi all,
Hope to clarify some doubts on usage of Enterprise Service Repository. I understand that ESR is the storage of service interfaces that may be provided or consume by different systems in the landscape.
If a business process is required to consume an external web service that is provided by a third party application on some web server, does the ESR stores the definition of the web service and provides it to the business process?
Is ESR only a repository for service interfaces that would be implemented by the internal systems?
Regards

I was looking to confirm my understanding about defining external webservices in Enterprise Repository few weeks back. Though i did not get proper confirmation any one yet on this forum, here is my understanding,
1. One can define the service interface for the third party webservice in Enterprise Service Repository for the purposes of keeping track of available services in the organization and also to provide some documentation about it for other developers looking to reuse it.
2. One can also import the WSDL as external definition in to Enterprise Service Repository.
3. We may not be able to generate proxies for these third party provided applications
Arul

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,

Problem when defining a web service

Hello,
I have defined several BAPI that I am calling from an external application by exopsing those BAPI using the SOAP adaptor.
All goes well for all of them except one.
For the one having problems the Integrantion engine is routing that call to different webservice than the one I expect it to do it,
these are some of the paramenters I use when defining the web service in the Integration Builder:
Interface name: MI_BAPI_PPMSRVAPS_GETLIST
Communitcation chanel: CC_SOAP_BAPI_PPMSRVAPS_GETLIST
Address: http://sapxi:50000/xisoapadapter/messageservlet?channel=:BS_WEBSERVICE_GREYCON:CC_SOAP_BAPI_PPMSRVAPS_GETLIST
but instead when I test the generated wsdl using soapUI: the integration engine returns this error:
Canceled with Errors 02.06.2010 15:04:22 02.06.2010 15:04:23 [websericename] [namespace]MI_BAPI_PDSSRVAPS_GETLIST
My guess is that at some point I defined wrong the web service but I have no way to redefine it or revert how it was defined.
I redefined the webservice with correct parameters, but there is no change in behaviour.
I checked server address and port (it is the exact same of the other BAPIs that work)
Where can I see all defined web services when they are defined via the Integration builder define web service option?
How to delete a webservice published this way?
Any advise?
Any help is very much appreciated.
Regards,
Mauricio Pego

Hello there.
Error: 404 Not Found
Description: The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address. This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable.
Possible Tips:- for HTTP_RESP_STATUS_CODE_NOT_OK 404
u2022 404 is an HTTP response code that indicates that the resource in question couldn't be found. Usually this is due to an incorrect URL, so it is better to cross check all URLs. Check pipeline URL in the SLD in the business system of the Integration Server For this go to SLD->Business System-><yourIntegrtaion Server>->Pipeline URL: It should be like this http://<host>:<port>/sap/xi/engine?type=entry Where host is the host name of the Integration Server and port is the HTTP(8xxx) port. To verify this in Integration Server you can do like this. Go to SXMB_ADM->Integration Engine Configuration->Choose Edit from Menu -> Change Global Configuration Data to switch to change mode. Then select System Landscape - Load Configuration. (This is not required always)
u2022 Check that the port really is the ICM HTTP Port and not the J2EE port i.e SMICM then menu GOTO --> SERVICES and check the port number for HTTP. It should be HTTP port
u2022 If the error is Page cannot be displayed, cannot find server in https configurations Check and correct the SSL configuration for the ABAP and the J2EE side of the system
u2022 If the error is because of integration server when using Proxy communications then check these. i.e SXMB_ADM->Integration Engine Configuration->Corresponding Integration Server enrty should be dest://<Http Integration server-Destination> Where < Http Integration server -Destination > is the RFC destination (SM59) of type HTTP connection (type H) to the Integration Server. In this case, host name, port, and path prefix are saved in the RFC destination.
Try some of the recommendations that most apply to your case.
Hope it helps!
Regards,
Caio Cagnani

Human task flow call back events with external web service

Hi All,
I have a requirement to call webservice inside human task flow. I have three participant in my human task flow. Let suppose A, B and C. When A approves then task will be assigned to B and when B approves it will go for C.
My requirement is that, when A approves , then i need to call one external webservice to update database. For this i have enabled call back events from human task flow.
In this way i got while loop inside my BPEL. In onTaskAssigned operation i am now trying to call external web service. My requriment is to call external service and get data from service. After getting response from the webservice, i want to assign it to next participant.
But in this case, when user B approves, it goes to onTaskAssigned block and i am able to make external web service also but mean time, it has been assigned to User C which i do not want.
I want Human task flow to wait for the web service response then only assign it to next participant.
Please help.
Regards,
Sunil

Hi Sunil
Have you tried using WebServices Adapter. The usecase seems pretty straight forward. You have a WebService that has some code and some Operations to update some Database. First thing, I hope you have methods/Operations defined with request and response xsd for each operation.
Now you define the main master payload, that should have all elements specific to your process and also few elements to store the output coming from each operation. Because response of each operation may need to go to other Task and get saved in the Payload also.
You have like 3 Tasks. To complicate, I will assume that each Task can either Approve or Reject. And last 2 Tasks gets data from payload, previous task and also output from the WebService Operation (method).
Task A -> Xor Gateway (Approve/Reject) -> If Approve -> Call WebServices Adapter -> Task B -> Xor Gateway(...) -> ......
At each intersection, you can map the attributes for incoming and outgoing. Based on WebServices output also, you can have Another XOR Gateway and decide to send to Task B or do something else. So combinations of outputs of each service (task or webservice adapter) and XOR gateways, you can have a decent control on the overall flow.
Note: I am hoping the webservices is Synchronous where you get the response immediately.
Let me know if I am missing something.
Thanks
Ravi Jegga

Resetting User Password by calling an external Web Service

Hi, 

We have an external Web Service, which handles Active Directory related activities. We would like to use this service to help users reset their passwords. We created a Portal Service from the external Web Service's WSDL. We have exposed the methods we require from this Web Service and are able to call these methods by creating Abstract Portal Components. We are currently testing the exposed methods via the Portal Component Starter and Viewer.

The current logon.par has a ResetPasswordPage. The corresponding form within the JSP is submitting data to the following string:
 
inPortal?proxy.getAlias("RPWFS"):logonBean.getLogonURL(proxy, null)
 

From what I can understand, the proper action URL will be returned by the method getAlias("RPWFS"). However, I am unable to find the definition of "RPWFS" in the PAR file.

Questions: 
<li>
What does "RPWFS" stand for? Where is this defined?
</li><li>
Would it be possible to modify the ResetPassword JSP file in the logon.par so that upon data submission, the Portal Service is called?
</li><li>
Where can I find documentation on JSPDynPage and DynPage (and how to create and edit the above-mentioned items)?
</li><li>
Is there any documentation on the functions used in the logon.par? For example, what is IAccessToLogic? Where is this defined? What does it do? Is there a library where we can search for information on this kind of stuff (like MSDN for Microsoft and API docs at java.sun.com)?
</li>
 Thank You.

Is there any documentation on the functions used in the logon.par? For example, what is IAccessToLogic? Where is this defined? What does it do? Is there a library where we can search for information on this kind of stuff (like MSDN for Microsoft and API docs at java.sun.com)?
Possible Answer:
https://help.sap.com/javadocs/NW04S/SPS09/ep/index.html 
While some packages are listed on this page, many other packages are missing (eg. com.sap.security.core.logonadmin.IAccessToLogic)

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 ????

Deliver data to external web service possible in OBIEE 11g?

Hi all,
I'm looking into the possibility of "pushing" data from OBIEE and out to an external web service, e.g. through executing a scheduled report that instead of delivering the result on screen, it would call an external web service that would consume the generated data for storage in an external system.
Does anyone know if this is possible to implement in OBIEE 11g? (So far, all I've found is how to display data in OBIEE through consumation of web service(s), but I'd like to "push out" data to a web service from OBIEE).
Regards,
-Haakon-

Action Links 11g - Invoke webservice you can try out..... I never tried... Just sharing my views.
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi1113/actionframework/actionframework.htm

How can I call external web service from BPEL

1. I have "EmpService" webservice (simple webservice to get emp salary, not in BPEL domain) running in Oracle AS host1. If I want to call this web service from BPEL in another host2. How can I do this?
2. Is it a must to deploy this EmpService to Oracle BPEL domain in order to call it? If so, how can I deploy it. As many BPEL example tutorial demonstrate the "obant" command to deploy the BPEL process, but not show how to deploy a external web service not in BPEL project. Please help. ...

Create a partner link in BPEL and point it to the WSDL deployed on external server.
this thread will also help
Axis generated WS to Bpel WS

Error in calling External web service from soa suite 11.1.1.3

Hi
I am getting following error while calling external web service......
####<Jan 20, 2011 6:54:26 PM IST> <Warning> <oracle.integration.platform> <in-mum-adina05> <soa_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-490B9BABECE372A277DF> <24b9eca72eaaa6a3:-4bc6fb7c:12da206ca2c:-7ffd-0000000000006287> <1295529866047> <SOA-20136> <WS Binding: exception durign SOAP invocation: java.util.NoSuchElementException>
####<Jan 20, 2011 6:54:26 PM IST> <Warning> <oracle.soa.mediator.common> <in-mum-adina05> <soa_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-490B9BABECE372A277DF> <24b9eca72eaaa6a3:-4bc6fb7c:12da206ca2c:-7ffd-0000000000006287> <1295529866047> <BEA-000000> < Payload after BaseActionHander.requestMessage :{parameters=oracle.xml.parser.v2.XMLElement@bd2382}>
####<Jan 20, 2011 6:54:26 PM IST> <Warning> <oracle.soa.mediator.common> <in-mum-adina05> <soa_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-490B9BABECE372A277DF> <24b9eca72eaaa6a3:-4bc6fb7c:12da206ca2c:-7ffd-0000000000006287> <1295529866063> <BEA-000000> < Properties after BaseActionHander.requestMessage :{ReferenceInstance=[email protected]63ea5,
####<Jan 20, 2011 6:54:29 PM IST> <Error> <oracle.webservices.service> <in-mum-adina05> <soa_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <24b9eca72eaaa6a3:-4bc6fb7c:12da206ca2c:-7ffd-0000000000006287> <1295529869375> <OWS-04115> <An error occurred for port: FabricProvider: javax.xml.rpc.soap.SOAPFaultException: oracle.fabric.common.FabricInvocationException.>
I am able to hit external ws from soap ui and getting response but while calling from soa suite getting this error.
Any clues?
Thanks
Vibhor

WS Binding: exception durign SOAP invocation: java.util.NoSuchElementException
Looks like the error is in the data sent to or expected from the service in your composite. Check that audit logs and composite flow to make sure your soap message when using soapui matches what you are working with in soa suite.

Define external web services

Similar Messages

Maybe you are looking for