The advantage of the Web Service
08.42 Posted In Design , Management , Monitoring , Security Edit This 0 Comments »
• the use of open formats for all platforms.
• Easy to understand and easy in debug.
• Support a stable interface.
• Using standards "to open the service once and have multiple users.
• Easy to mediate messages and processes to add value.
• Routing and delivery.
• Security.
• management and monitoring.
• schema design and service.
• Acceleration.
• easy to develop with additional semantic transport.
• Open, standards-based text.
• Achieving a modular.
• No expensive to implement (relative).
• Reduce the cost of enterprise application integration.
• Implementation of the incremental.
• XML allows software developers to expose valuable resources in the form of interoperability which has high, where the resources are all types of applications or pnyimpanan data used by the organization. XML Web services architecture defines a standard mechanism to provide resources through the delivery of XML messages. To access the resources only with mentransmisikan XML messages through a standard protocol such as TCP, HTTP, or SMTP. The word "Web Service" (in short "service") refers to the code of the XML interface to be a source of power, where the bias so difficult to access.
• Architecture allows consumers to support the application with integrated XML Web Service. However, to meet this, consumers should determine the appropriate XML interface along with the message that the message diverse and have the details right. XML scheme can memnuhi needs because this allows developers to explaining the structure of XML messages. XML own scheme, however, can not announce additional details concerning the communication with the Web Service.
• Definition of the scheme to tell the XML messages that can be used but not how the messages relate to one another. For example, if there is an XML element named Add the name and other AddResponse, this is likely the second name is related but can not indicate its scheme. Therefore, in addition to know the messages, consumers should also know the possible exchange of messages that are supported by the Web Service (example:., If you send a message Add, you get a message back form AddResponse).
Can exchange messages intended as an exchange operation. Operations conducted by consumers on the most important point menginteraksikan service image. Each time you use a Web Service, will be conducted inspection operations that supported the list to get all the processes that are available.
• It is normal for developers to group operations to be connected to the interface-interface. Consumers need to know of these affect the way they create the code. This is important for developers, developers working with Web Service on the scope of object-oriented interface because XML can become a map interface programmatis (or abstract classes) in the language options selected.
• Consumers also need to know what the communication protocol used for sending messages to the service, along the specific mechanisms involved when using the protocol defined as the use of the command, the header-header, an error code. Packing (binding) specify concrete details of what happened on the cable (wire) with mensketsakan how to use interface with specific communication protocol. Binding also affect message-peasn way in the abstract enkodisasi specify on the wire with the style of service (vs. document. RPC) mechanism and enkodisasi (vs. literal. Terenkodisasi).
• Service can support binding on the double-binding interface that is determined, but each must be binding dapta accessible at the address identified by a unique URI, is also intended as the end point of the Web Service.
• Consumers should find out all details outlined before they can interact using the Web Service.
• Easy to understand and easy in debug.
• Support a stable interface.
• Using standards "to open the service once and have multiple users.
• Easy to mediate messages and processes to add value.
• Routing and delivery.
• Security.
• management and monitoring.
• schema design and service.
• Acceleration.
• easy to develop with additional semantic transport.
• Open, standards-based text.
• Achieving a modular.
• No expensive to implement (relative).
• Reduce the cost of enterprise application integration.
• Implementation of the incremental.
• XML allows software developers to expose valuable resources in the form of interoperability which has high, where the resources are all types of applications or pnyimpanan data used by the organization. XML Web services architecture defines a standard mechanism to provide resources through the delivery of XML messages. To access the resources only with mentransmisikan XML messages through a standard protocol such as TCP, HTTP, or SMTP. The word "Web Service" (in short "service") refers to the code of the XML interface to be a source of power, where the bias so difficult to access.
• Architecture allows consumers to support the application with integrated XML Web Service. However, to meet this, consumers should determine the appropriate XML interface along with the message that the message diverse and have the details right. XML scheme can memnuhi needs because this allows developers to explaining the structure of XML messages. XML own scheme, however, can not announce additional details concerning the communication with the Web Service.
• Definition of the scheme to tell the XML messages that can be used but not how the messages relate to one another. For example, if there is an XML element named Add the name and other AddResponse, this is likely the second name is related but can not indicate its scheme. Therefore, in addition to know the messages, consumers should also know the possible exchange of messages that are supported by the Web Service (example:., If you send a message Add, you get a message back form AddResponse).
Can exchange messages intended as an exchange operation. Operations conducted by consumers on the most important point menginteraksikan service image. Each time you use a Web Service, will be conducted inspection operations that supported the list to get all the processes that are available.
• It is normal for developers to group operations to be connected to the interface-interface. Consumers need to know of these affect the way they create the code. This is important for developers, developers working with Web Service on the scope of object-oriented interface because XML can become a map interface programmatis (or abstract classes) in the language options selected.
• Consumers also need to know what the communication protocol used for sending messages to the service, along the specific mechanisms involved when using the protocol defined as the use of the command, the header-header, an error code. Packing (binding) specify concrete details of what happened on the cable (wire) with mensketsakan how to use interface with specific communication protocol. Binding also affect message-peasn way in the abstract enkodisasi specify on the wire with the style of service (vs. document. RPC) mechanism and enkodisasi (vs. literal. Terenkodisasi).
• Service can support binding on the double-binding interface that is determined, but each must be binding dapta accessible at the address identified by a unique URI, is also intended as the end point of the Web Service.
• Consumers should find out all details outlined before they can interact using the Web Service.