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

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

Advantage and disadvantage of view over physical table

Hi,
Can you explain me Advantage and disadvantage of view over physical table

Hi Nitin,
A view can be thought of as either a virtual table or a stored query. The data accessible through a view is not stored in the database as a distinct object. What is stored in the database is a SELECT statement. The result set of the SELECT statement forms
the virtual table returned by the view. A user can use this virtual table by referencing the view name in Transact-SQL statements the same way a table is referenced.
For more information about the advantages and disadvantages of views in SQL Server, please refer to the following two articles:
http://www.c-sharpcorner.com/Blogs/10575/advantages-and-disadvantages-of-views-in-sql-server.aspx
http://www.toadworld.com/platforms/sql-server/w/wiki/10274.views-advantages-and-disadvantages.aspx
Regards,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Advantages and disadvantages of BAPI_PO_CREATE1 over BAPI_PO_CREATE.

Advantages and disadvantages of BAPI_PO_CREATE1 over BAPI_PO_CREATE. Please provide details.

Hi,
see this
Re: PGI in vl01n
Regards
Kiran Sure

Advantages and Disadvantages of OIM11gR2 over 11gR1

Hello experts,
I would like to list out the advantages and disadvantages of OIM 11g R2 over R1. Can you guys please help me in completing the list??
Advantages:
1. Shopping cart experience / request catalog model / interactive user interface
2. UI customisations made easy
3. Secure access to cloud, mobile and social networks
I am not sure of the disadvantages but heard that its a lenghty process (risky) to upgrade from R1 to R2.
Can any of you have ideas on the changes to workflows, provisioning and reconcilation and other procesess.
Thanks,
Bob

http://rajivdewan.blogspot.com/2012/08/oracle-identity-manager-11g-r2-oim-11g.html
anyone come across any cons with R2Some known and unknown issues are there but those you'll find with each and every product and version.
http://docs.oracle.com/cd/E27559_01/relnotes.1112/e35820/id_mgr.htm#CHDDGDCC

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 Applet over JSP/servlet

Can some one please let me know what are the major advantages and disadvantages of using Applets over JSP/Servlet technology?

Well, a servlet / jsp is generated on the server, an applet on the client side. That's the most important difference.
Appelt's usually are for little applications like games and stuff, you can run in a browser.
Servlets are for dynamic pages, for example database-viewing and stuf...

Reg : Advantages and Disadvantages of WAD over Bex in Reporting

Hi BW Gurus,
I wish to know the advantages and disadvantages of using WAD Over BEx .Please reply back with some strong points, as I have to project the same to our customer.
Thanks in Advance,
Krishna

Hi Krishna,
Here are some:
- User friendly access (less educational cost).
- Web reporting is faster, less overhead in executing Web reports.
- Learning curve for NEW users in BW is lower on Web Reporting.
- Accessibility of reports to a wider audience.
- No SAP front-end is needed anymore to execute reports.
Hope it helps,
David.

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

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

Advantages and disadvantages of Internet Sales R/3 Edition over ITS

Hello,
I want to know what are the Advantages and disadvantages of Internet Sales R/3 Edition over ITS? If we shift from ITS to Internet Sales R/3 Edition, what would be added advantages?
Note: Here ITS is used only for Sales Transactions.
Thanks & Regards,
Pratik Gandhi.

Hi
E-Service&E-Marketing is not part of the R/3 Internet sales edition.
Cheers

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 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 64 bit over 32 bit

Hi,
Can anyone please let me know the advantages and disadvantages of 64 bit over 32 bit Essbase. The version i am currently using is 9.3.1 on 32 bit.
Will appreciate your help.
Thanks in advance
RG

Thanks Giri for high level infromation.
Can you please provide me information that is there any matrix available provide the comparision on 32 bit over 64 bit. Like the comparision on maximum dimensions and members, Maximum number of parallel calc threads ( BSO) OR Maximum number of parallel loads ( ASO), Maximum number of user threads on Analytics access via smart view, excel add in or EAS console, etc.
It would be really helpful if you could provide the same.
Many Thanks
Suman

Advantage and Disadvantags of ActionScript 3

Hi professionals of ActionScript 3!
I just started flash animation and learning ActionScript. But
I found one thing that there existing ActionScript 1, 2, 3 versions
and ActionScript 2 components is using only ActionScript 2 code.
Please tell me advantages and disadvantages of both ActionScript.
Please advise which is powerful and has more info and sources. What
kind of links between then existing.
Thanks in advance!
Said Babanli

Said,
> Please tell me advantages and disadvantages of both
> [versions of] ActionScript. Please advise which is
> powerful and has more info and sources.
ActionScript 1.0 and 2.0 both run on the same virtual
machine (AVM1)
inside Flash Player. As of Flash Player 9, the player runtime
features two
virtual machines (AVM1 and AVM2), the second of which runs
ActionScript 3.0.
Right off the bat, this tells you that Flash Player 9 or
higher is required
if you want to program with ActionScript 3.0. In one sense,
that's a
potential "disadvantage" of AS3: if your users have Flash
Player 8 or lower
installed, you simply can't use that version of the language.
Instead,
you'll have to use AS2 (as far back as Flash Player 6) or AS1
(as far back
as Flash Player 5), or slash-notation proto-ActionScript if
you need to go
even further back than that. Ultimately, then, the version of
ActionScript
you use depends on the version of Flash Player you expect
your users to have
installed.
AS2 is the first version of ActionScript to officially
support custom
classes (external text files structured in a particular way,
using folders
for classpaths and the "class" keyword). For more information
on
classpaths -- written for AS2, but basically applies to AS3
-- see this URL:
http://www.quip.net/blog/2006/flash/understanding-classpaths
For many people (myself included), custom classes provide a
powerful way
to organize code into reusable objects -- just like the given
objects in
ActionScript's native API. Be aware, however, that custom
classes are *not
a required workflow* in AS2 or AS3. If you prefer, you may
place your AS2
or AS3 code into timeline keyframes, just like with AS1.
Contrarily, even
though true classes are not officially supported by AS1, you
can mimic many
of the benefits of classes by following the instructions here
(an incomplete
resource, but very useful):
http://www.debreuil.com/docs/
It would take pages and pages of notes to give you a
thorough list of
the benefits (and disadvantages!) of every version of
ActionScript. Even
then, it would be difficult to demonstrate that such a list
was complete, so
to keep things simple: as a general rule, each new version of
ActionScript
is presumed to be better than its predecessor. AS1 was more
powerful than
Flash 4-era ActionScript because it provided a considerably
larger API. AS1
also made it easier to target objects with dot notation than
with slash
notation and cumbersome getProperty() and setProperty()
functions. AS2 was
more powerful than AS1 because it provided native support for
classes. It
introduced variable typing, which helped with code completion
and
compile-time error checking. (AS2 also coincided with an even
larger API,
but that's a parallel benefit due to increased functionality
in subsequent
versions of Flash Player.) AS3 is more powerful than AS2
because the syntax
of custom classes has become more strict. I personally find
that stricter
syntax helps a programmer avoid "lazy" or "sloppy" practices,
encouraging
the programmer to code with purpose.
For more thoughts along these lines, here's a free excerpt
from a book I
recently co-authored for O'Reilly (bear in mind, these are
largely
subjective opinions, but they work for me):
http://www.communitymx.com/abstract.cfm?cid=16D76
I'll probably start repeating myself soon, but to sum up:
AS2 has
advantages over previous versions because it provides
numerous options and
improvement in ease of use. AS3 improves even further by
"cleaning up" the
language by making it more strict and by providing a stronger
internal
consistency.
Here are a few quick examples.
In AS2, to create an instance of the Sound class (that is,
an object you
can use for programming audio), you simply use the "new"
keyword:
// AS2
var mySound:Sound = new Sound();
Most classes can be instantiated in this way, but in AS2,
there are
notable exceptions, including movie clips and text fields.
// AS2 -- this does NOT work!
var myMC:MovieClip = new MovieClip();
var myTF:TextField = new TextField();
This can be confusing to a newcomer, because it seems so
arbitrary.
(Someone new might well think, "Why can't instances be made
the same way
across the board?") In AS3, instantiation is more consistent:
// AS3
var mySound:Sound = new Sound();
var myMC:MovieClip = new MovieClip();
var myTF:TextField = new TextField();
This is also true for event handling. In AS2, there are four
or five
ways to do it: the on() and onClipEvent() functions, their
dot notation
equivalents, addListener(), and addEventListener(). They're
all valid in
AS2, but not all interchangeable. Some work for components,
some for other
sorts of objects. It takes effort to memorize which objects
work with which
approach. In AS3, outside of a very small number of
exceptions, most event
handling is done with a single, consistent approach:
addEventListener().
For a newcomer, this is easier to learn because once the
technique is
understood, it works in nearly every scenario.
As far as performance is concerned, AS3 trumps AS2
significantly. AS3
performs better and faster than all previous versions of
ActionScript -- but
you'll only notice this with complex applications, especially
those
involving a high volume of number crunching.
Here are a few more links that may prove helpful to you:
ActionScript 3.0 Overview
http://www.adobe.com/devnet/actionscript/articles/actionscript3_overview.html
Tips for Learning ActionScript 3.0
http://www.adobe.com/devnet/actionscript/articles/actionscript_tips.html
ActionScript 3.0: Is it Hard or Not?
http://www.insideria.com/2008/01/actionscript-30-is-it-hard-or.html
You also asked which version of the language has more "info
and
resources." By that, I assume you mean online resources, such
as blogs,
tutorials, and so on. That question is hard to answer, but my
*guess* is
that there are still more resources online about AS2 than AS3
... but AS3
will probably catch up soon.
David Stiller
Co-author, Foundation Flash CS4 for Designers
http://tinyurl.com/5j55cv
"Luck is the residue of good design."

Advantages and disadvantages of SOAP over Http

Similar Messages

Maybe you are looking for