Web Service connector using ICF

I'm starting to look at developing a connector for a web service. I have heard that the GTC connectors are going away in the next release and that all new development should be made within the ICF.
I'm just beginning to start to go through the documentation around using the ICF. Are there any pre-built ICF connectors that can function with a web service via SOAP or some other type of protocol? The connector would be one way from OIM to the web service.
Any guidance is appreciated!
Thanks.

ICF pre-defined connectors are scheduled to be released in 2013.
Edited by: 949865 on Dec 19, 2012 7:11 AM

Similar Messages

Web Service Connector Export Issue

Hi,
Version: Crystal Xcelsius Designer 4.5
I have a Crystal Xcelsius dashboard with a Web Service Connector component on it, as well as some graph components.
When I "Preview" the file, the display works fine and the graph is filled with data obtained through the Web Service Connector.
However, when I try to "Export" the file, either as .swf, .ppt, etc, there is no sign of the display refreshing, either on load or at intervals. I've tried clicking on the Connector button, but it doesn't appear to be connecting to the data source at all.
Any help or advice on how to get the exported display working would be appreciated.

Xcelsius creates the SWF file which is operated through the Flash Player. Therefore, it uses the security features of the Flash Player that you have installed on the browser. It is possible that this issue is Flash Security which is preventing access across a different domain.
This error occurs for one of the following reasons:
The domain name used in the URL in the web browser and the URL used in the web service configuration in Crystal Xcelsius are not the same.
Or, if the URL in the web browser uses the domain http://machine1 and the URL in the web service connector uses the domain http://machine1.companyname.com, the SWF refresh will not be successful.
When running inside a web browser, a Macromedia SWF file cannot access data that is outside the domain in which it was created. To work around this behavior, use a cross-domain policy file to allow the SWF file to access information on the Web Service server that is sitting on the other domain.
To use the cross-domain policy file:
1. Create a cross-domain policy file. For details on how to create this file, refer to technote tn_14213 at www.macromedia.com
2.Copy this file into the root of web application server. For example, for Tomcat, copy the file to 'drive':\Program Files\Business Objects\Tomcat\webapps\ROOT
For more information about the cross-domain policy file, see Macromedia technote tn_14213 at www.macromedia.com

Connect to SharePoint web service using the XML / Web Service connector

Hi experts,
I am currently trying to display my SharePoint list in Crystal Report. Therefore my plan is to use a SharePoint web service to get the data and paste them to the Crystal Report.
Is it possible to use the "XML and Web services" connector of the Crystal Reports database expert?
When I enter the web service URL, for instance:
https://[url]/_vti_bin/lists.asmx?wsdl
and click next... I have to enter the web service credentials.
On the next page I have to enter Service, Port and Method.
Do I have to enter the service URL again here?
What If, there is no port? Can I leave that field empty?
I know the methods, but where can I add the mandatory parameters?
Thanks for any helps and comments!
Sebastian

Hi Ananth,
thank you, but this document does not help at all.
We are using Crystal Reports 2008 SP2.
We want to use the Web Service Connector.
What I need is more informationen about the Web service connect. For example - the connection in Microsoft InfoPath is much easier - there I don't have to enter a port and can choose the methods from a list.
Is it possible to use the Crystal web service connector for MS SharePoint Webservices?
Or must I use the Crystal SDK to carry out a connection?
Best regards,
Sebastian

Integrating FIM with SAP using web services connector

Hi
I am implementing the FIM web services connector to integrate with SAP. The MS connector config guide for SAP documentation seems to me missing some content or at least I think it might be written for an earlier version of
SAP than the version we are working with(different screenshots, options, etc). The version of SAP we have implemented is EHP6 for SAP ERP6 which I believe translates to ECC6.
SAP web services have been configured and FIM performs successful discovery of the wsdl endpoint and BAPI operations as expected. Our issue is that FIM fails to run a full import. From the digging around web service config and error logs two observations comes
out:
1. FIM Full Import workflow does not render correctly through the web service configuration tool and complains of a duplicate attribute "xml:space is a duplicate attribute on line on line 424 on position 103". Review of the wsconfig generated by the
webservice config tool points to an variable supplied to a construct the query to a BAPI of HR infotype 0006. Extract below:
...<InArgument x:TypeArguments="d:BAPIP0006L" xml:space="preserve">[If(Not IsNothing(addressInfo) AndAlso Not IsNothing(addressInfo.item), addressInfo.item, Enumerable.Empty(Of BAPIP0006L)()).
OrderByDescending(Function(a) DateTime.ParseExact(a.VALIDBEGIN, dataSourceDateFormatValue, Nothing)).
ThenByDescending(Function(a) Integer.Parse(a.RECORDNR)).FirstOrDefault()]</InArgument>...
I can only guess that it means the query should keep the spaces within the string it passes to SAP but this is where my understanding stops.
2. SAP returns errors about not implementing a BAPI EMPLOYEE_GETDATA function which is not part of the exposed BAPI operations. Well the obvious solution to this would be expose this missing operation (which is undocumented in MS config guide) however this
BAPI is a core requirement to retrieve person information. I would be hugely surprised if this operation was not factored into the config. This makes me think that to understand this better I need to resolve issue 1 first and get the rendering sorted first.
Has anyone come across the above issues with a recent implementation with this connector? Or help point me in the right direction?
any help would be greatly appreciated!
thanks!!

Hi Joe,
you most probably missed the sentence "Add the required BAPI’s in the function group and select those required BAPI’s and click continue." in the "Connector for SAP.docx" document on page 8. In other words your webservice does not provide the required
BAPIs.
In the "DefaultSAPECC_6.wsconfig" the workflows for import and export require specific BAPIs.
Also make sure that your Service Definition has got the same name as in the documentation and the workflow template.
I was fighting with this for the last 4 days but in the end got it working.
Hope this helps
Chris

FIM 2010 R2 Web Service Connector SAP HCM HTTP binding

Hi all,
I'm currently configuring the FIM web service connector to connect to a SAP HCM system.
I followed the documentation (http://www.microsoft.com/en-us/download/details.aspx?id=29943) to create the necessary web service on the SAP system. With the only difference that
I'm not able to select "None" (HTTP) under the Web Service Communication Security Settings as described in the documentation.
I had to select SSL and now get the following error message in the Web Service Configuration Tool.
Synchronization Service Manager
Following Endpoints are configured with unsupported binding:
- 'customBinding' binding for 'Z_IDM_CONNECTOR_SOAP12' endpoint
Please configure endpoint(s) with http binding only and refresh service(s).
Web service connector cannot be configured through Synchronization Service Manager if endpoint binding is not basic http.
Any help how to fix this is highly appreciated. I already can see the available BAPIs in the Web Service Configuration Tool. (In other words "Discovery" is working.)
I'll get the same error if I try to load the configration file into the Web Service Connector in the Sync Engine.
Thanks
Chris

Ok. I got that fixed by changeing the Transport Security to "None" in the Security Profile of the Service Definition.
I'm now facing a different error that you might be able to help.
I'm not able to add additional BAPIs to the SU_USER Function Group as described in the documentation because the "Plus" Button is missing in my screen. How can I add these BAPIs in order to use the Web Service Configuration Tool with the provided SAP ECC
6 configuration template?
Thanks
Chris

How to Pass BAPIPWD from Export workflow in Web Services Connector MA

Hello,
I need to export users from FIM to SAP using web services connector. I have created Export Work flow and added the values like user name , first name, last name and etc. I couldnt set the value for password because the data type is BAPIPWD. Could you please
tell me how to create a user in SAP from FIM using Export Workflow and how to pass the password parameter.
Thanks,
Nallasivan

Hi you can add parameters to your FPM application and launch the aplication from POWL action.
Insder FPM, using FPM parameters you can access these varaibles inside your local webdynpro component.
Regards
Ravi

SAP Web Services Connector specifications

Hi,
First of all, I have to say that I do not know about web services, so I'm sorry if this question is not clear.
I am implementing Web Services connector for SAP.
I ask the Customer to configure SAP endpoint (I give the documents downloaded from Microsoft Web), but they say that this information is not complete.
They ask me for a "functional specification" for the endpoint indicating what FIM connector send and what FIM connector expected.
Is there information about these specification (besides docs with Connector).
Thanks
JuanCC Technology Specialist

Hi Juan
I have implemented a few of FIM projects with SAP SOA and FIM Web Services Connector.
Well a function specification is just a statement what FIM will do using those web services so it should be straight forward. If you are creating SAP Users and/or assigning Roles to them it should be stated.
As far as what BAPI functions that would be required to do this depends on your scenario. If you could give a brief of what your scenario is i can provide you with a list of BAPI functions in SAP that those guys need to expose as a web service.
The EndPoint needs to be created using SAP Trans Code: SOAManager, and the authentication scheme should be http:basic
The document what Microsoft provides is usually enough for the SAP technical guys.
some of the functions for SAP User are:
BAPI_USER_CREATE
BAPI_USER_CREATE1
BAPI_USER_GETLIST
BAPI_USER_GET_DETAIL
BAPI_USER_EXISTANCE_CHECK
RH_ACTGROUP_INDEX_GET (for getting all the roles in SAP)
Regards Furqan Asghar

Web Service Connector Button Question

from harini_d
Hi,
I am using the web service connector component to get some data from Qaaws. However, when I view the flash file i have to keep clicking on the web service button and some other components ( like the country label) in order to populate the chart. Is there anyway that i can skip clicking the web service button.
I would ideally like to just choose the country and the chart should be populated ( with all the related data from the query from the web service). I want to avoid clicking the web service button. How do i go about this ? Any help would be appreciated.
Also, whlie selecting ranges for the i/p and o/p values for a web service connector component, I would like to select a dynamic range since sometimes i dont know how many records will be returned by the query. Is there any way to define a dynamic range.
Thank you.

I would suggest setting up your model so that when you select a region on the map, this triggers the web service connector.
Basically, the insert in of the map must be the same cell as the trigger cell for the web service connector.
Once setup properly, you can then set the web service connector's transparency to zero to clean things up.

Web Services Connector for JMX available

We are glad to announce that the Reference Implementation of our Web-Services Connector for JMX Agents, being defined by JSR 262, is available in Early Access on http://ws-jmx-connector.dev.java.net/. This major milestone is aligned with the second Early Draft Review of the Specification in the Java Community Process.
The WS-Connector for JMX is based on the WS-Management protocol, defined by the DMTF. Its greatest benefit is to provide interoperability between a variety of client applications compliant with this standard, including those not based on the Java platform, and any JMX-based instrumentation.
This week, at JavaOne, we will demonstrate examples of this interoperability on stage during the technical session "TS 2656 - JMX Technology: Who's Doing What". We will show in particular how Windows Vista's management tools can use the JVM telemetry instrumentation. Join Eamonn McManus and Jean-Francois Denise, or watch their blogs, for more details on this.
We encourage you to use and provide feedback on the WS-Connector RI early access, which is fully functional and, we believe, already pretty stable.
Note that our implementation of the WS-Management protocol is based on the Wiseman open source project, which lives at http://wiseman.dev.java.net/.
The JMX Team.

We are glad to announce that the Reference Implementation of our Web-Services Connector for JMX Agents, being defined by JSR 262, is available in Early Access on http://ws-jmx-connector.dev.java.net/. This major milestone is aligned with the second Early Draft Review of the Specification in the Java Community Process.
The WS-Connector for JMX is based on the WS-Management protocol, defined by the DMTF. Its greatest benefit is to provide interoperability between a variety of client applications compliant with this standard, including those not based on the Java platform, and any JMX-based instrumentation.
This week, at JavaOne, we will demonstrate examples of this interoperability on stage during the technical session "TS 2656 - JMX Technology: Who's Doing What". We will show in particular how Windows Vista's management tools can use the JVM telemetry instrumentation. Join Eamonn McManus and Jean-Francois Denise, or watch their blogs, for more details on this.
We encourage you to use and provide feedback on the WS-Connector RI early access, which is fully functional and, we believe, already pretty stable.
Note that our implementation of the WS-Management protocol is based on the Wiseman open source project, which lives at http://wiseman.dev.java.net/.
The JMX Team.

Create Web Service System using WSDL URL

Hi,
Please help me create a Web Service System.
Following is the test result when I perform Connection Test after creating a system
Test Connection with Connector
Test Details:
The test consists of the following steps:
1. Retrieve the default alias of the system
2. Check the connection to the backend application using the connector defined in this system object
Results
Retrieval of default alias successful
Connection failed. Make sure that Single Sign-On is configured correctly
Thanks,
Atul

Let me reiterate my problem.
I created the System as following
Creating System's Object:
1) Go to System Administration
2) Go to System Configuration
3) Go to Portal Content on Object Based Navigation Area (Right Side Panel)
Note: For avoiding confusion it is recommended to create a folder in which we are creating System Object.
4) Right Click on Portal Content, select New -> System (from Template)
5) This action will display a new view on right side, now choose Web Service System using WSDL URL radio button from the existing templates. Click Next
6) Give the System Name i.e. System_WS and System Id (which are mandatory fields) incase you want to give any brief notes about the system then give it in Description field. Click Finish.
8) Choose Open the object for editing Click OK.
9) Now to create a Web Service System, we need WSDL URL.
10) There are lots of freely available WSDL files on internet, search for any such WSDL file.
11) In the Properties area of system give the appropriate WSDL URL
12) Choose System alias, from display menu and give alias as System_WS.
This alias name will be the name of Web Service System.
I used the following url
http://soap.amazon.com/schemas2/AmazonWebServices.wsdl
After the system is created,
1) Right click on the created system> open > object
2) Drop down for Display options is changed to Connection Tests from what it shows as object
3) Check the check box for the test name Connection Test for Connectors
4) Result shows that the connection failed. The error message was posted in my first question.
Thanks,
Atul

Web service connector's trouble

I have created web service connector in portal, specified wsdl url. How i can use it in my java programm, like a integrating 3rd-Party search engines into KM index management or other? The likn(http://help.sap.com/saphelp_nw04/helpdata/en/e1/d0d240caeb752ae10000000a155106/frameset.htm) have poor description and i have not understand how work with web service connector. Please show me example or help to start on it.

I would suggest setting up your model so that when you select a region on the map, this triggers the web service connector.
Basically, the insert in of the map must be the same cell as the trigger cell for the web service connector.
Once setup properly, you can then set the web service connector's transparency to zero to clean things up.

Web service connector trouble

I have created web service connector in portal, specified wsdl url. How i can use it in my java programm, like a integrating 3rd-Party search engines into KM index management or other? The likn(http://help.sap.com/saphelp_nw04/helpdata/en/e1/d0d240caeb752ae10000000a155106/frameset.htm) have poor description and i have not understand how work with web service connector. Please show me example or help to start on it.

I would suggest setting up your model so that when you select a region on the map, this triggers the web service connector.
Basically, the insert in of the map must be the same cell as the trigger cell for the web service connector.
Once setup properly, you can then set the web service connector's transparency to zero to clean things up.

XML Parser Error while creating Web service Client using JAX RPC

hello evryone,
Im facing XML Parser Error while creating web service client using JAX RPC. Im using Net Beans IDE for development purpose. I have wrote configuration file for client. Now i want to create Client stub. However i dont know how to do this in Net Beans. So i tried to do it from Command promt using command :
wscompile -gen:client -d build -classpath build config-wsdl.xml
here im getting Error:
error parsing configuration file: XML parsing error: com.sun.xml.rpc.sp.ParseException:10: XML declaration may only begin entities
Please help me out.
Many thanks in advance,
Kacee

Can i use the client generated using jdeveloper 11g to import into the oracle forms 10g, i.e., form builder 10g. Currently this is the version we have in our office.

Errors creating a Web Service Proxy using Microsoft WSDL.exe tool

I have deployed a BPEL process using JDeveloper. This process can be invoked from the BPEL console and completes as expected. I am trying to create a Web Service Proxy using the Microsoft WSDL.exe tool so that the process can be invoked from a Microsoft Word document. This process is based on the AutoLoan example in the Developer's Guide for Microsoft Office Interoperability B25781-01.
WSDL.exe returns the following error message
Error: There was an error processing 'http://erp.template.co.uk:8889/orabpel/default/HonorariumSmartDoc/1.0/HonorariumSmartDoc?wsdl'.
- The document at the url http://erp.template.co.uk:8889/orabpel/default/HonorariumSmartDoc/1.0/HonorariumSmartDoc?wsdl was not recognized as a known document type. The error message from each known type may help you fix the problem:
- Report from 'WSDL Document' is 'There is an error in XML document (19, 7).'.
- A schema with the namespace '' has already been added.
- Report from 'DISCO Document' is 'Discovery document at the URL http://erp.template.co.uk:8889/orabpel/default/HonorariumSmartDoc/1.0/HonorariumSmartDoc?wsdl could not be found.'.
- The document format is not recognized.
- Report from 'XML Schema' is 'Expected Schema root. Make sure that the root element is <schema> and the namespace is 'http://www.w3.org/2001/XMLSchema' for an XSD schema or 'urn:schemas-microsoft-com:xml-data' for an XDR schema. An error occurred at , (2, 2).'.
How do I resolve this error?

The WSDL file is below.
<?xml version="1.0" encoding="UTF-8" ?>
- <definitions name="HonorariumSmartDoc" targetNamespace="http://xmlns.oracle.com/HonorariumSmartDoc" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:tns="http://xmlns.oracle.com/HonorariumSmartDoc" xmlns:wsa="http://schemas.xmlsoap.org/ws/2003/03/addressing" xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:client="http://xmlns.oracle.com/HonorariumSmartDoc">
- <types>
- <schema xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://xmlns.oracle.com/HonorariumSmartDoc" schemaLocation="HonorariumSmartDoc.xsd" />
</schema>
- <schema xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://schemas.xmlsoap.org/ws/2003/03/addressing" schemaLocation="http://erp.template.co.uk:8889/orabpel/xmllib/ws-addressing.xsd" />
</schema>
</types>
- <message name="HonorariumSmartDocResponseMessage">
<part name="payload" element="tns:HonorariumSmartDocProcessResponse" />
</message>
- <message name="HonorariumSmartDocRequestMessage">
<part name="payload" element="tns:HonorariumSmartDocProcessRequest" />
</message>
- <message name="WSARelatesToHeader">
<part name="RelatesTo" element="wsa:RelatesTo" />
</message>
- <message name="WSAReplyToHeader">
<part name="ReplyTo" element="wsa:ReplyTo" />
</message>
- <message name="WSAMessageIDHeader">
<part name="MessageID" element="wsa:MessageID" />
</message>
- <portType name="HonorariumSmartDocCallback">
- <operation name="onResult">
<input message="tns:HonorariumSmartDocResponseMessage" />
</operation>
</portType>
- <portType name="HonorariumSmartDoc">
- <operation name="initiate">
<input message="tns:HonorariumSmartDocRequestMessage" />
</operation>
</portType>
- <binding name="HonorariumSmartDocBinding" type="tns:HonorariumSmartDoc">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
- <operation name="initiate">
<soap:operation style="document" soapAction="initiate" />
- <input>
<soap:header message="tns:WSAReplyToHeader" part="ReplyTo" use="literal" encodingStyle="" />
<soap:header message="tns:WSAMessageIDHeader" part="MessageID" use="literal" encodingStyle="" />
<soap:body use="literal" />
</input>
</operation>
</binding>
- <binding name="HonorariumSmartDocCallbackBinding" type="tns:HonorariumSmartDocCallback">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
- <operation name="onResult">
<soap:operation style="document" soapAction="onResult" />
- <input>
<soap:header message="tns:WSARelatesToHeader" part="RelatesTo" use="literal" encodingStyle="" />
<soap:body use="literal" />
</input>
</operation>
</binding>
- <service name="HonorariumSmartDocCallbackService">
- <port name="HonorariumSmartDocCallbackPort" binding="tns:HonorariumSmartDocCallbackBinding">
<soap:address location="http://set.by.caller" />
</port>
</service>
- <service name="HonorariumSmartDoc">
- <port name="HonorariumSmartDocPort" binding="tns:HonorariumSmartDocBinding">
<soap:address location="http://erp.template.co.uk:8889/orabpel/default/HonorariumSmartDoc/1.0" />
</port>
</service>
- <plnk:partnerLinkType name="HonorariumSmartDoc">
- <plnk:role name="HonorariumSmartDocProvider">
<plnk:portType name="tns:HonorariumSmartDoc" />
</plnk:role>
- <plnk:role name="HonorariumSmartDocRequester">
<plnk:portType name="tns:HonorariumSmartDocCallback" />
</plnk:role>
</plnk:partnerLinkType>
</definitions>

How to invoke a web service asynchronously using ws-addressing model?

Hi Gurus,
We are invoking an external web service asynchronously using Oracle Work Flow Business events using the following mechanism -
1)Created a web service invoker event to invoke the web service.
2)Created a subscription that invokes the web service (provided the wsdl address, operation info).
3)Defined a subscription parameter WFBES_CALLBACK_EVENT with value pointing to a recieve event.
4)Created a receive event(parameter value for WFBES_CALLBACK_EVENT) and a subscription that directs the response to a custom PL/SQL function to process response.
so far so good. We were able to invoke the web service and get and process the response.
Problem: The external web service can take upto 10 hrs to process the request. A time out of 2 hrs is set on the server hosting the external web service. So when the external web service takes more than 2 hrs to process the request and it times out and we get the following error on EBS side -
'l_error_message:oracle.apps.fnd.wf.bes.InvokerException: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: oracle.j2ee.ws.saaj.ContentTypeException: Not a valid SOAP Content-Type: text/html; charset=iso-8859-1'
Now the external web service providers are suggesting that we are not calling their web service asynchronously and we should use ws-addressing model to do so.
Is there a way to invoke this web service using ws-addressing model using business events or from PL/SQL or OA middle-tier?
Regards,
Sunil
CMRO Development.
I am providing here the WSDL of the external web service -
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions targetNamespace="http://service.sdk.webservices.enigma.com" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:ns1="http://org.apache.axis2/xsd" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" xmlns:ax21="http://service.sdk.webservices.enigma.com/xsd" xmlns:ns="http://service.sdk.webservices.enigma.com" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
<wsdl:types>
<xs:schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://service.sdk.webservices.enigma.com/xsd" xmlns:ax22="http://service.sdk.webservices.enigma.com">
<xs:import namespace="http://service.sdk.webservices.enigma.com"/>
<xs:complexType name="JCGWebServicesException">
<xs:complexContent>
<xs:extension base="ax22:Exception">
<xs:sequence>
<xs:element minOccurs="0" name="id" nillable="true" type="xs:string"/>
<xs:element minOccurs="0" name="message" nillable="true" type="xs:string"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="JCGServiceReply">
<xs:sequence>
<xs:element maxOccurs="unbounded" minOccurs="0" name="pdfStatus" nillable="true" type="ax21:PdfStatus"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="PdfStatus">
<xs:sequence>
<xs:element minOccurs="0" name="jobCardID" nillable="true" type="xs:string"/>
<xs:element minOccurs="0" name="pdfPath" nillable="true" type="xs:string"/>
<xs:element minOccurs="0" name="status" nillable="true" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:schema>
<xs:schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://service.sdk.webservices.enigma.com" xmlns:ax23="http://service.sdk.webservices.enigma.com/xsd">
<xs:import namespace="http://service.sdk.webservices.enigma.com/xsd"/>
<xs:complexType name="Exception">
<xs:sequence>
<xs:element minOccurs="0" name="Exception" nillable="true" type="xs:anyType"/>
</xs:sequence>
</xs:complexType>
<xs:element name="JCGWebServicesException">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="JCGWebServicesException" nillable="true" type="ax21:JCGWebServicesException"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="runJobCard">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="a_WorkpackageFilePath" nillable="true" type="xs:string"/>
<xs:element minOccurs="0" name="a_userName" nillable="true" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="runJobCardResponse">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="return" nillable="true" type="ax21:JCGServiceReply"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
</wsdl:types>
<wsdl:message name="JCGWebServicesException">
<wsdl:part name="parameters" element="ns:JCGWebServicesException">
</wsdl:part>
</wsdl:message>
<wsdl:message name="runJobCardResponse">
<wsdl:part name="parameters" element="ns:runJobCardResponse">
</wsdl:part>
</wsdl:message>
<wsdl:message name="runJobCardRequest">
<wsdl:part name="parameters" element="ns:runJobCard">
</wsdl:part>
</wsdl:message>
<wsdl:portType name="JCGServicePortType">
<wsdl:operation name="runJobCard">
<wsdl:input message="ns:runJobCardRequest" wsaw:Action="urn:runJobCard">
</wsdl:input>
<wsdl:output message="ns:runJobCardResponse" wsaw:Action="urn:runJobCardResponse">
</wsdl:output>
<wsdl:fault name="JCGWebServicesException" message="ns:JCGWebServicesException" wsaw:Action="urn:runJobCardJCGWebServicesException">
</wsdl:fault>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="JCGServiceSoap11Binding" type="ns:JCGServicePortType">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="runJobCard">
<soap:operation soapAction="urn:runJobCard" style="document"/>
<wsdl:input>
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
<wsdl:fault name="JCGWebServicesException">
<soap:fault name="JCGWebServicesException" use="literal"/>
</wsdl:fault>
</wsdl:operation>
</wsdl:binding>
<wsdl:binding name="JCGServiceSoap12Binding" type="ns:JCGServicePortType">
<soap12:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="runJobCard">
<soap12:operation soapAction="urn:runJobCard" style="document"/>
<wsdl:input>
<soap12:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap12:body use="literal"/>
</wsdl:output>
<wsdl:fault name="JCGWebServicesException">
<soap12:fault name="JCGWebServicesException" use="literal"/>
</wsdl:fault>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="JCGService">
<wsdl:port name="JCGServiceHttpSoap12Endpoint" binding="ns:JCGServiceSoap12Binding">
<soap12:address location="http://localhost:8080/JCG/services/JCGService"/>
</wsdl:port>
<wsdl:port name="JCGServiceHttpSoap11Endpoint" binding="ns:JCGServiceSoap11Binding">
<soap:address location="http://localhost:8080/JCG/services/JCGService"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
Edited by: sikumar on Jun 22, 2010 1:50 PM

Bharat,
You dont need a Business Event setup to invoke a BPEL process from PL/SQL unless you have a special case and you need to process the response from the BPEL process in a separate thread (or in background)..
For a straight call to BPEL process from PL/SQL, here is a sample script -
function "MYTEST0" return varchar2 AS
soap_request varchar2(30000);
soap_respond varchar2(30000);
http_req utl_http.req;
http_resp utl_http.resp;
resp XMLType;
i integer;
helpStr varchar2(30000);
BEGIN
soap_request:= '<?xml version = ''1.0'' encoding = ''UTF-8''?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:ns0="
http://xmlns.oracle.com/TestWS">
<env:Body>
<ns0:TestWSProcessRequest>
<ns0:input>abc</ns0:input>
</ns0:TestWSProcessRequest>
</env:Body>
</env:Envelope>
/* the BPEL process name is TestWS */
http_req:= utl_http.begin_request
( 'http://hostname:7777/orabpel/default/TestWS/1.0'
, 'POST'
, 'HTTP/1.1'
utl_http.set_header(http_req, 'Content-Type', 'text/xml');
utl_http.set_header(http_req, 'Content-Length', length(soap_request));
utl_http.set_header(http_req, 'SOAPAction', 'process');
utl_http.write_text(http_req, soap_request);
http_resp:= utl_http.get_response(http_req);
utl_http.read_text(http_resp, soap_respond);
utl_http.end_response(http_resp);
resp:= XMLType.createXML(soap_respond);
resp:= resp.extract('/soap:Envelope/soap:Body/child::node()',
'xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"');
helpStr := '';
i:=0;
loop
helpStr := helpStr || substr(soap_respond,1+ i*255,250);
i:= i+1;
if i*250> length(soap_respond)
then
exit;
end if;
end loop;
return helpStr;
END;

Web Service connector using ICF

Similar Messages

Maybe you are looking for