B2B WEBSERVICE Publishing and Consumption boilerplate

- A complete set of program source code templates for fully understanding, creating, publishing and consuming webservices for real-life, real-business-to-business (B2B) implementations.

If you are programmer/developer that needs to create and implement a webservice program, whether it is to publish a webservice that other websites will tap into, or a program that consumes an existing webservice from another company or organization䨩s very helpful product is for you.

Will show you how to write your own webservice by way of a real working example.
Will show you how to write your own program that consumes another website෥bservice.
Comes with working source code templates/examples of actual webservice programs, both for serving and consuming a web service.
- This webservice program features web-methods that publishes (but not limited to) read-only information 毲 publishing information inquiry contents. It also includes a web-method that accepts parameters as input for posting (Read/Write) into its own internal system and returning a result-set. The format of the result set can be a value pair or an xml, explained below.
- Contains a sample implementation of a web-method that returns a value pairs. This is an example that you can use as a template for developing your own program that requires you to create an interface for HTTP-GET and HTTP-POST web delivery method types.
- Contains example implementation of a web-method that returns a set of values in the form of an XML document, for use on SOAP web delivery types. Developers and programmers can use this example as boilerplate for a program that will enable your website to exchange XML documents with another website.
- You may copy the example web-method(s) provided and just change the appropriate values to come up with your own web-service for your system or website.
Comes with a documentation with in-depth explanation how the webservice examples are created and implemented.
There are many free resources out on the internet, but the information that they contain are all over the place, disorganized, and simply not sufficient enough to give a full grasp of helping developers to understand and do by example how to create a real-life based webservices. This is not the typical tutorial info that you see on newsgroups or web forums. These are NOT just a 'hello world' or simple calculator webservices that are of no use to serious developers and programmers. This product is a complete set of how tos from creation to consumption of rea-life, real requirements situations. It explains both sides of the equation 䨥 publishing part and the consuming part.

Boilerplate 1: Sales Order Inquiry Webservice

Contains 2 separate website template/examples, a publisher and a consumer.
Publisher website: Sales Order Inquiry engine
A webservice publisher that publishes the status of an online order. It accepts a Customer ID and/or Order ID as input, and returns the corresponding sales order info like name, order date and ship-to information. When you use this set of codes on your own project, you can easily add more information to expose more info like order amount, tracking info, etc.
Consumer website: Sales Order Lookup webpage
A client-end program that consumes a real-life situation information publisher webservice like the one demonstrated by Sales Order Inquiry engine. You may use this example as boiler plate for your own project when you want to tap-into the information that is published by another website via a webservice. You just need to change the placeholder variables, optionally add your own touch and you堧ood to go.
The pair of projects in boilerplate 1 demonstrates three ways of exchanging information between the webservice and the consumer. Most company IT Departments choose their method based on the capability of their developers, what their existing infrastructure is, as well as the infrastructure of the partners that it intends to exchange the service with. Whatever consideration there may be, companies that publish web services usually allow a variation of all these 3. By knowing them all, you젧et a much better understanding of why and when it is appropriate to implement your webservice in a certain way.
1. By generic typed parameters
2. By 졳sect model
3. By XML Document
Just seeing how the 2 programs run and interact with each other will give you a more solid grasp of web service technology, far more than what you can get from reading and attending programming classes for days.
Boilerplate 1 summary
Includes: 2 sets of website program templates and documentations
Cost: $129.95

Boilerplate 2: Purchase Order Processing Webservice

Contains 2 separate website template/examples, a publisher and a consumer.
Publisher website: Purchase Order processor engine
An advanced webservice example that accepts a Purchase Order, process it to post a Sales Order, and returns instant Sales Order confirmation to the client.
Consumer website: Purchase Order submitter
A client-side website program that interacts with a real-life situation order taker webservice, like the service demonstrated by Purchase Order processor engine. It submits or posts a Purchase Order to a Purchase Order processor engine webservice, receives an XML result and parses that result for use in its own information processing.
The pair of projects in boilerplate 2 also demonstrates three ways of exchanging information between the webservice and the consumer. Most company IT Departments choose their method based on the capability of their developers, what their existing infrastructure is, as well as the infrastructure of the partners that it intends to exchange the service with. Whatever consideration there may be, companies that publish web services usually allow a variation of all these 3. By knowing them all, you젧et a much better understanding of why and when it is appropriate to implement your webservice in a certain way.
1. By generic typed parameters
2. By 졳sect model
3. By XML Document
Just seeing how the 2 programs run and interact with each other will give you a more solid grasp of web service technology, far more than what you can get from reading and attending programming classes for days.
Boilerplate 2 summary
Includes: 2 sets of website program templates and documentations
Cost: $169.95

Requirements

1. You must have MS Visual Studio. MS Visual Studio 2005 or 2008 are ideal but MS Visual Studio Express will work just fine.
2. You must have basic understanding of how websites work like how to setup a website instance in IIS.
3. You must know C# because that෨ere the examples were written on.

Purchasing Options

WEBSERVICE Boilerplate 1: Sales Order Inquiry Webservice
Includes: 2 sets of website program templates and documentations
Cost: $129.95