Advantages and disadvantages of SOAP adapter

Hi all,
Currently we need to provide a solution connecting to the .NET environment from SAP system, one of the option is proxy <-> PI <-> soap (web service), can anybody tell me the advantages and disadvantages of web service communication via PI? Because we may also be able to connect directly via the .NET connector.
It will be very appreciated if you could provide some proposals, thanks.
Bean

Hi bean qian ,
These are the advantages of SOAP:
SOAP(Web Services) IS A Technical Adapter.
Openness and Interoperability are features of SAP XI.
1)Openness
Use open, XML-based standards
Leverage Industry Standards in B2B scenarios
2)Interoperability
Connect to applications using specialized adapters
Connect to existing integration solutions using JMS (e.g. MQSeries) or SOAP
Web Service: SOAP on the Ropes
u2022 The Good
u2022 By default the SAP builds the XML per the selected protocol
u2022 All container elements with values are added to XML document
u2022 SOAP protocol is a synchronous process, therefore SAP waits on a
response
u2022 SAP automatically matches data elements in the returned XML document to
container elements and transfers the data (in theory)
u2022 The Bad
u2022 Current problems with return binding for SOAP processes require special
handling
u2022 The Web step allows manipulation of the outgoing and incoming XML
document via rules
u2022 the following may ease some learning pains
These r disadvantages of SOAP :
The SAP XI SOAP Adapter supports Exactly-Once end-to-end processing using unique message IDs.
This is an excellent blog which neatly explains u in detail of SOAP with WEB:
An Overview of SOAP

Similar Messages

Advantages and Disadvantages of Soap

Advantages and Disadvantages of Soap
Hi Firends,
Could you please tell me the Advantages and Disadvantages of using Soap adapter, i need them urgently.
Note: High reward points will be given for each answer

Hello
SOAP is an XML-based protocol for exchanging information in a decentralized, distributed environment. It was made for Web, a combination of XML and HTTP opens up new options for distributed data exchange and interaction in a loosely coupled web environment. SOAP is a technology that allows XML to move easily over the Web. SOAP does this trough an XML envelope for delivering XML content and specifying a set of rules for services to follow when they receive a SOAP message.
The fundamental change brought about by SOAP has been the ability to move data anywhere across the Web. Before SOAP there were only two main options for moving data between partners.
One was to build a wide area network spanning a broad geographic region and let the partners plug into it. This was the approach taken by EDI, which defined messages and protocols for data transfer but left the network details up to the partners. The result was a collection of networks that pretty much locked the partners in and made it difficult and expensive to reach out to other EDI networks and costly to bring in new partners.
The second approach for moving data between partners was to build a distributed object infrastructure than ran over the internet. This was the approach taken by Common Object Request Broker (CORBA), Remote Method Invocation (RMI) and Distributed Component Object Model (DCOM). The problem was that each had to decide on a protocol that could sit on top of TCP/IP and handle inter object communication. CORBA Chose Internet Inter-ORB Protocol (IIOP), DCOM chose object Remote Procedure Call (ORPC), and RMI chose Remote Method Protocol (JRMP). While this approach reduced the need to share the same underlying network, the drawback was that CORBA could talk to CORBA, RMI to RMI and DCOM to DCOM, but they neither could talk to each other nor directly to the web except through special sockets that required adding extra layers to an already complex architecture.
SOAP the third option, combines the data capabilities of XML with the transport capabilities of HTTP, there by overcoming drawbacks of both EDI and tightly coupled distributed object system such as CORBA, RMI and DCOM. It does this by breaking dependence between data and transport and in doing so opens up a new era of loosely coupled distributed data exchange.
SOAP Carries an XML RPC tradition by defining an XML language for packaging arbitrarily XML inside an XML envelope. Although SOAP does not depend on HTTP, the momentum behind SOAP is attributable to the fact that HTTP will usually be used for transfer protocol for SOAP messages.
SOAP is a transport protocol similar to IIOP for CORBA, ORPC for DCOM or JRMP for RMI.
SOAP differs from CORBA, RMI or DCOM in several ways.
IIOP, ORPC and JRMP are binary protocols, while SOAP is a text based protocol that uses XML. Using XML for data encoding makes SOAP easier to read than a binary stream.
1) Because SOAP is text based, it is able to move more easily across the firewalls than IIOP, ORPC or JRMP.
<p2) SOAP is based on XML, which is standard driven rather than vendor driven. Potential adaptors are less likely to fear vendor lock in with SOAP. </p2>
The net effect is that SOAP can be picked up by different transport protocol and delivered in different ways. For example, when used with HTTP it can be delivered to a web server, when used over FTP it can be deposited directly into a file system and when used with SMTP it can be delivered to a user's mailbox.
Many companies exchange data between established partners is proving totally satisfactory way to leverage the benefits of XML and the web. In this scenario the required are an agreed upon schema either DTD or an XML schema, for XML data being exchanged and the SOAP server capable of handling the incoming XML as it arrives over the web. Details about what kind of schemau2019s to expect and who will check the XML conforms to the schema are decided offline by individuals participating in the process. On the software side senderu2019s needs to be involved in packaging their data in an XML document. For those companies already storing data in XML, this should require only minimal effort. If the stored XML data is not in the form required by the agreement, an XSL Transformation(XSLT) style sheet can be programmed to automate the transformation.
SOAP messages define one way data transmission from sender to the receiver. However SOAP messages are often combined to implement patterns such as request-response. When using HTTP binding with SOAP, SOAP messages can use the same connection as the inbound request.
Regard's
CHETAN AHUJA

Advantages and disadvantages of SOAP over Http

Hi!
Can any one explain about advantages and disadvantages of SOAP over HTTP.
Thanks
Sreenath

Hi,
Yes you can use RMI to communicate to your soa suite server allthough i could not get it to work from weblogic 10.3, there is a conflict with certain other libraries. From any other 10.1.3 oracle application server there should not be any problem. The biggest advantage of RMI over SOAP is performance. The soap client also generates lots of logging which can not be disabled, ... i already logged a bug on that. The advantage of SOAP over RMI is its underlying HTTP protocol which is, in some cases, the only protocol allowed by network engineers to pass through firewalls.
Kind Regards,
Andre

Advantages and Disadvantages of webdynpro JAVA over J2ee?

Hi,
Can anybody provide me the advantages and disadvantages of webdynpro java over the J2EE?
Regards,
Harish.

Hi,
Webdynpro is the SAP standard technology for developing business user intrefaces.
Webdynpro is like the frame work which follows the MVC Design pattern.
Webdynpro uses most of the UI developement as declarative approach , i.e. most of the code will generated by the framework. so it will reduce the developement efforts.
Adaptive RFC model to connect with SAP systems.
All these are advantages over than the J2ee.
Regards,
Naga

Advantages and Disadvantages of Proxy

Advantages and Disadvantages of Proxy
Hi Firends,
Could you please tell me the Advantages and Disadvantages of using Proxy, i need them urgently.
Note: High reward points will be given for each answer

HI,
Advantage:
The advantage of proxy is that it is send directly to the integration engine.There is no processing in adapter engine involved.
So the processing time is saved since there is no processing in adapter engine involved and that leads to a better performance.This is the biggest adavantage of the PROXY
Also we can use proxy only when we have SAP WAS>=6.2
Also it provides Excellent Error handling
They can be used for both synchronous and asynchronous communication
Whereas if u go for Idocs they can be used for asynchronous commn and rfc consumes lots of resources
Disadvantages
1) You need to write custom code. In case of IDoc scenario, you need to write custom code to post the IDocs.
2) Debugging may be difficult in some cases...
Plz rewards points
Vikas
Edited by: vikas jain on Jun 23, 2008 6:15 AM
Edited by: vikas jain on Jun 23, 2008 6:35 AM

Advantages and Disadvantages of Jdbc

Advantages and Disadvantages of Jdbc
Hi Firends,
              Could you please tell me the Advantages and Disadvantages of using jdbc adapter, i need them urgently.
Note: High reward points will be given for each answer

Hi,
Advantages : 1) Can read any database if proper drivers are installed.
                    2) Creates XML structure of data from database
                        automatically
                    3) No content conversion required
                    4) Query and Stored procedure supported.
                    5) Can be used for both Synchronus and Asynchronous
                        processing.
                    6) Supports modules
Disadvantages : 1) Correct drivers need to be deployed for each type
                            of database
                         2) Cannot update or insert multiple tables with
                              sequence. ( Sequence is always randomn)
Kulwinder
Reward if helpful

Advantages and Disadvantages of Idoc

Advantages and Disadvantages of Idoc
Hi Firends,
Could you please tell me the Advantages and Disadvantages of using Idoc adapter, i need them urgently.
Note: High reward points will be given for each answer

Hi,
If u choose IDOC the data transfer will be done completely by IDOC method. The records will be as Control Record, Data Record & Status Record. Under the InfoIdoc, the data will be stored in segments. The data is safe here & using status redord could identify the status of the transfer.
some pros and cons....
1. Limited to 1000 bytes / record.
2. User cannot access the data as in PSA.
3. Data Security is more.
4. Good for less volume of data.
5.Fast to load, easy processing, low programming for standard IDOCs
6.Good knowledge of IDOC processing required, time consuming if changes have to be made to a created IDOC
7.It cannot be used for SYNCHRONOUS COMMN
8.Maintence of port and Genration of partner profile is difficult.
9.ALE configuration steps required for both in XI and SAP-R/3.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b2b4035c-0d01-0010-31b5-c470d3236afd
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098
I ) In the case where we encounter a standard IDOC provided by SAP or Situation where a mapping is available or an IDOC as well as a BAPI exits, the approach will be dependent on the specific integration scenarioo......
for For example, options might be
1) sending one IDOC at a time
2) combing multiple IDOCS and sending as a single IDOC.
3) making one single RFC call, for each business transation.
4) avoiding multiple calls to the same BAPI / RFC by deploying a wrapper BAPI and sending all records in one call.
5) Using the proxy and sending all data in one shot and making single calls to the BAPI from the proxy.
Regards.
Srinivasreddy
Thanks
Srinivasreddy
Edited by: Srinivas Reddy on Jun 23, 2008 10:36 AM

Advantages and Disadvantages of File

Advantages and Disadvantages of File
Hi Firends,
Could you please tell me the Advantages and Disadvantages of using File adapter, i need them urgently.
Note: High reward points will be given for each answer

Disadvantage:
The disadvantage of file adapter is tht it doesnt understand the hierarchy i.e it produces the output in a single line
It cannot produce the output in the form a hierarchy
Also File adapter doesnt produce the response neither it supports the acknowledgement.
Advantages:
monitoring of file adapter is simplest of all
It provides us with the facility for using xml file as well as comma separated or falt file or tab separated file
There is an option while we configure file adapter
In comm channel in
Message protocol:File or file content conversion
plz rewards points
vikas

Advantages and Disadvantages of XML over CSV

Hi friends,
We have a requirement in our implimentation project. We are implimenting HR module. The company is using SABA for Education and Certification.
We are implimenting Education and certification in BW and the data for BW will be comming from SABA.
We had a discussion on thursday about the integration of SABA to BW. We can do it through DBconnect or by using XI and for this there is time and cost involved.
The techical team has come with some idea where there will give the data in the form of XML or in CSV format.
I would like to know the advantages and disadvantages of each and also please consider the performance point in view.
I would also like to know about the things that need to be considered if we process the data in multiple files.
Please give me inputs and the answers will be appreciated with valuable points.
Regards
Raghav Reddy

Hi,
my advice is to go for CSV anytime compared to XML.
XML is first made available to the BW system via SOAP ( Simple Object Acess protocol) interface. Next it is updated into the required data targets as before , Via a data source for the myself source system.
SOAP = XML+HTTP.
XML cannot be used for mass data. It is only to load small data into SAP BW on a single document level.
BW provides flat file interface so, there is no all these hassles in case of CSV. go for CSV

Advantages and Disadvantages of JMS Queue over Fabric

HI,
I want to know both the advantages and disadvantages of using JMS queue over the default Fabric queue in B2B adapter.
Is it ok if I configure all my inbound and outbound transactions across all the trading partners to communicate with their respective SOA composite via the default JMS Queues(B2B_IN_QUEUE and B2B_OUT_QUEUE)?
Please advise.
Thanks in advance.
Regards,
Monica

Hi Monica,
But the size of the payload which I am using is unpredictable, it can differ from 1 MB to 40MB in future.This is not a problem. B2B can handle MB's of file if server has enough resources.
all other payloads greater than 3MB, it is getting faulted with the message:
"SAX Exception in translator. SAX Exception raised while trying to SAX Parse InputStream . Please make sure that the xml data is valid."Please remember that when B2B will find a large payload then it will write the large payload into the "Large Payload Directory" (defined in Administration--> Configuration) and pass it's reference to the middleware. So at middleware, you will not receive the actual payload but you will receive it's reference. Using File adapter sync read option, you may read the large file from "Large Payload Directory" at SOA layer.
If you are using PS5 (11.1.1.6) then you will see that for large payload, B2B passes the JMS header LARGE_PAYLOAD to the back-end so in your composite, you may build logic around this. If this header (LARGE_PAYLOAD) is not coming at SOA layer then payload will be available in the body and if it is populated then payload will be available in the "Large Payload Directory" and it's reference will be available in the message body.
Regards,
Anuj

Advantage and disadvantages of XI

Dear All,
I was asked to list down the Advantages and Disadvantages of XI over other middleware tools in an interview
Please advice.
Regards,
Ashish

Hi Ashish,
Advantages of XI:
XI is a middleware like many others. It is well suited for connecting SAP systems with each other and with non-SAP.If your focus is not on SAP systems, other solutions might be a better choice today. SAP XI provides an integrated workflow engine that allows to define adapters to non-XML-protocols and mappings to convert data content from source to target.
Any fully mature middleware should provide these three layers.
1. An independent Message Queue
2. A data consolidator and mapping engine
3. Workflow processor.
XI is lacking full-fledged Message Queue compared to other established Middleware products.
Currently, SAP XI does not have the features like IBM Websphere, Seeburger or TIBCO.
SAP's next XI release might provide this missing piece and many more features which is due 2007 i guess.
Here are the advantages of SAP XI from my point of view.There are lots of advantages but to list a few :
Easy Integration with SAP products & components (RFC, IDOC, Proxy).
Data security as expected from any SAP product.
Standards based - XML, XSD, Xpath etc
Ability to communicate with other messaging systems/products.
Business Process Management
Synchronous & Asynchronous communication possible.
Complex processes for communication possible instead of only sending and receiving (business process management) (connect e.g. asynchronous and synchronous steps, define complex communication scenarios)
Mapping etc possible to accomplish in Java. Platform independent Java components.
Java & .Net support.
Big range of adapters for different technologies / tools (SOAP, Mail, JDBC, CDIX...)available in standard or offered by other companies (EDI e.g. by Seeburger).
Process functionalities inside XI to modify content in the communication channel on own defined rules fpr business purposes.
Central monitoring for data communication for all your communication between different systems.
And the marketing issue: SAP and its partners provide high volume of development capabilities to make XI always up-to-date for new requirements
Regards,
Subhasha Ranjan

Advantage and disadvantage of xml publisher, report builder and discoverer

Hi,
anyone can explain advantage and disadvantage of xml publisher, report builder and discoverer?
thanks in advance!

The best way i found was to put a equals and then double quotes... this only works for excel however it will allow you to cut and paste (ie to use the value to search in Oracle) and also to do vlookups.
In a bit more detail:
- I used word to generate my default table
- this created a field INVOICE_NUM
- in the cell in the table i put = " before the INVOICE_NUM field and then put the closing " afterwards.
The theory is that excel will concatenate the values together... because it has quotes around it, it will treat it as a string rather than simply a value.
For any other formats this will not work.
I'm guessing most people have moved on and resolved this some other way, but just thought I'd share the wealth!

Advantages and Disadvantages of Client Object Model in sharepoint 2013

I need Advantages and Disadvantages of Client Object Model in sharepoint 2013
like below in javascript. Users will have read/edit and approve access to the list.
var clientContext = new SP.ClientContext.get_current();
var oList = clientContext.get_web().get_lists().getByTitle('Workflow Tasks');
MCTS Sharepoint 2010, MCAD dotnet, MCPDEA, SharePoint Lead

Thanks
AlexanderShelopukho for
right answer!
Alex-
I do not need comparison-
I need Advantages and Disadvantages of Client Object Model in sharepoint 2013
MCTS Sharepoint 2010, MCAD dotnet, MCPDEA, SharePoint Lead

Advantages and Disadvantages of Dual booting Windows on PXI Device

Hello,
In solving my previous problem of running a DLL in RTOS I've stumbled upon another solution. But i wanted to know the pros and cons of this before i make the leap.
I want to install windows on the PXI device so that the NHR DLL files are run inherently on the windows kernel and i have access over my DAQ devices without placing them in the remote target.
What are the advantages and disadvantages of installing a windows only on the DAQ device and running all my operation from it. Do i loose my real time features? I dont know, I'm really new to LabView and may sound really dumb. Please excuse my lack of knowledge.
With Regards,
Khalid.

Hello Bob,
Thank you for your insightful answer. I also thought this might happen, loosing all the RT features.
I have another question for you. If i use a RT variant of windows like "Windows Embedded 8", will this make any difference? Can i regain my RT features by it or i have to go with the LabView RTOS.
I'm pushing towards a windows system because i have to run this DLL file from NHR which is not supported by the LabView RTOS.
Moreover, I could just install just windows onto the PXI controller. I'm not being able to make it dual boot. Can you guide me towards proper guideline to do so? I looked at the knowledge base file about dual booting, but the instructions dont exactly match with my available options in BIOS setup.
Any suggestions from anyone is much appreciated.
With Regards,
Khalid.

Singl/Multiple Server Oracle 10g DB and AS- Advantages and DisAdvantages

Hi Friends,
I am using Application1 using Oracle 10g Application Server and Oracle 10g database.
Now i planned to use Application2 using Oracle 10g AS and Oracle 10g DB
I need to know what will be the Advantages and Disadvantages if i have the schema for Application2 in the existing Oracle 10g DB / having it in another Oracle 10g DB Server
sameway what will be the advantages and disadvantages if i have the Application2 regsiterd in existing Oracle 10g AS(Multiple OC4J Instance) / having it in another Oracle 10g AS Server.
Regards

To start the list, for me some of the advantages are:
Same DB:
- less overhead and wasted CPU Cycles (therefore potentially lower license fees)
- easier maintenance (backup, recovery)
- easier tuning (fewer conflicting external environments asking for same resources)
- Oracle is designed for this, allows use of Resource Manager
- technically RAC is a clustered 'same DB'
Same AS:
- less overhead and wasted CPU Cycles (therefore potentially lower license fees)
- easier maintenance (backup, recovery)
- easier tuning (fewer conflicting external environments asking for same resources)
- Oracle is designed for this, use AS clustering
Different DB:
- separate maintenance (patch, upgrade) cycles for different SLA
- easier tuning (isolate tuning to one app)
- easier security (most developers have no idea about Oracle security and make merge impossible)
Different AS:
- separate maintenance (patch, upgrade) cycles for different SLA
- easier tuning (isolate tuning to one app)
- easier security (most developers have no idea about security)

Advantages and disadvantages of SOAP adapter

Similar Messages

Maybe you are looking for