MQSeries.net :: View topic - SAP BAPI exposed as WSDL

MQSeries.net

Tech Exchange

Education

Certifications

Library

Info Center

SupportPacs

FAQÂ Â

Usergroups

RSS Feed - WebSphere MQ Support

RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » SAP BAPI exposed as WSDL

SAP BAPI exposed as WSDL

« View previous topic :: View next topic »

Author

Message

GeneRK4

Posted: Tue Aug 27, 2013 10:14 pm Post subject: SAP BAPI exposed as WSDL

Master

Joined: 08 Jul 2013
Posts: 220

This could be a basic question..Apologies me as I am new to WebServices.

This is my requirement.
There is a Application which is going to call three operations exposed as Webmethods in WebService.Message Broker flow is the WebService with SOAPInput node at the input.Each of the three operations is going to call SAP system through SAPWebSphere Adapter Request node individually.

Hence ,I have 3 BAPIs -RFC for each operations.

My questions are :
1)As SOAPInput exposes WSDL,whether Message broker developer has to write WSDL or SAP developer has to write his BAPI to be exposed for WebService?

-Input from Web Client to Broker is in the SAP RFC message format only.Hence mapping is not required apart from extracting SOAP message payload from SOAP Envelope.

2)When importing BAPIs from SAP,the BAPIs are imported in such a way that there is no single xsd as a total for request message alone or for response message alone for each operation.
For eg,one of the operation shown below as xsd after importing the BAPIs,
===================================================

Code:

<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sapasi="http://www.ibm.com/xmlns/prod/websphere/j2ca/sap/metadata" xmlns:sapretrievevirtualcampaignwrapper="http://schemas.boots.com/loyalty/digitalservices/v1_0/sapretrievevirtualcampaignwrapper" xmlns:sapzfmretrievedigitalv00="http://schemas.boots.com/loyalty/digitalservices/v1_0/sapzfmretrievedigitalv00" targetNamespace="http://schemas.boots.com/loyalty/digitalservices/v1_0/sapretrievevirtualcampaignwrapper">
<xsd:import namespace="http://schemas.boots.com/loyalty/digitalservices/v1_0/sapzfmretrievedigitalv00" schemaLocation="../sapzfmretrievedigitalv00/SapZfmRetrieveDigitalV00.xsd"/>
<xsd:import namespace="http://www.ibm.com/xmlns/prod/websphere/j2ca/sap/metadata" schemaLocation="../../../../../../ibm/www/xmlns/prod/websphere/j2ca/sap/metadata/SapBusinessObjectMetadata.xsd"/>

<xsd:annotation xml:space="preserve">
<xsd:appinfo source="http://www.ibm.com/xmlns/prod/j2ca/versionCompatability">
<info:resourceAdapter xmlns:info="http://www.ibm.com/xmlns/prod/j2ca/versionCompatability" version="6.1"/>
</xsd:appinfo>
</xsd:annotation>

<xsd:annotation xml:space="preserve">
<xsd:appinfo source="commonj.connector.asi">
<asi:annotationSet xmlns:asi="commonj.connector.asi" asiNSURI="http://www.ibm.com/xmlns/prod/websphere/j2ca/sap/metadata"/>
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType name="SapRetrieveVirtualCampaignWrapper">
<xsd:annotation xml:space="preserve">
<xsd:appinfo source="http://www.ibm.com/xmlns/prod/websphere/j2ca/sap/metadata">
<sapasi:sapBAPIBusinessObjectTypeMetadata xmlns:sapasi="http://www.ibm.com/xmlns/prod/websphere/j2ca/sap/metadata">
<sapasi:Type>BAPI</sapasi:Type>
<sapasi:Operation>
<sapasi:MethodName>ZFM_RETRIEVE_DIGITAL_V0_0</sapasi:MethodName>
<sapasi:Name>Retrieve</sapasi:Name>
</sapasi:Operation>
</sapasi:sapBAPIBusinessObjectTypeMetadata>
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence maxOccurs="1" minOccurs="1">
<xsd:element maxOccurs="1" minOccurs="0" name="SapZfmRetrieveDigitalV00" nillable="true" type="sapzfmretrievedigitalv00:SapZfmRetrieveDigitalV00">
<xsd:annotation xml:space="preserve">
<xsd:appinfo source="http://www.ibm.com/xmlns/prod/websphere/j2ca/sap/metadata">
<sapasi:sapBAPIPropertyTypeMetadata xmlns:sapasi="http://www.ibm.com/xmlns/prod/websphere/j2ca/sap/metadata">
<sapasi:FieldName>ZFM_RETRIEVE_DIGITAL_V0_0</sapasi:FieldName>
<sapasi:FieldType/>
<sapasi:PrimaryKey>true</sapasi:PrimaryKey>
<sapasi:ParameterType>INOUT</sapasi:ParameterType>
<sapasi:MaxLength>0</sapasi:MaxLength>
</sapasi:sapBAPIPropertyTypeMetadata>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>

<xsd:element name="SapRetrieveVirtualCampaignWrapper" type="sapretrievevirtualcampaignwrapper:SapRetrieveVirtualCampaignWrapper">
</xsd:element>
</xsd:schema>

===================================================

Is this something to be rectified from SAP system developer or from our side in the way of importing BAPIs?Is this really a problem for referring XSDs in WSDL?
I am really confused.Please do the needful...[/img]

Simbu

Posted: Wed Aug 28, 2013 2:24 am Post subject:

Master

Joined: 17 Jun 2011
Posts: 289
Location: Tamil Nadu, India

SAP providing BAPI to you and you providing WebService to Consumer. WSDL file should be created and published by WebService Provider. Please correct me if i'm wrong.

GeneRK4

Posted: Wed Aug 28, 2013 8:31 pm Post subject:

Master

Joined: 08 Jul 2013
Posts: 220

Yes Simbu..We need to create WSDL.I got it after discussing with Web consumer.
Thanks

Display posts from previous:

Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » SAP BAPI exposed as WSDL

Jump to:

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Protected by Anti-Spam ACP