Khoshnevis
Khoshnevis
Khoshnevis,
if you are so much of a hurray then you might want to try the open
source tools from
www.pi4tech.org and generate the WSDL and even the Java code or BPEL
to support
the project.
The tools will ensure that the WSDL - your interfaces - are
consistent with each other.
The tools will ensure that the contract that the services will meet
are consistent with the business goals of the project.
This could be rendered as asbtract BPEL or as SEDL (in the tools)
which is like WSDL with end-point behavior.
You will also get an overall description by exporting the entire WS-
CDL described project in to BPMN or HTML or
UML.
Good luck (email me directly if you have problems - [EMAIL PROTECTED])
On 2 Apr 2007, at 14:23, Anne Thomas Manes wrote:
I suggest you ask your advisor to provide a definition of the terms
"interface", "contract", and "description".
There are no standard definition files that correspond to those
names. You will need to define the following metadata files for
your services:
- WSDL - describes the operations the service exposes, the messages
exchanged for each operation, and protocols supported, and the
endpoint address for each protocol. You may define all this
information for one service in one WSDL or you might factor it into
logical and physical WSDLs.
- XML Schema - describes the structure of the messages being
exchanged. A schema can be defined within a WSDL or separately.
- WS-Policy - describes the runtime constraints and capabilities of
the service, such as security, reliability, or transaction
requirements. WS-Policy is an emerging specification and is not
widely used yet.
(These three types of metadata might be construed to be the
"interface")
It's also beneficial to provide documentation and describe the
semantics of your services in human-readable text. (This might be
construed to be the "description".)
You might also define usage agreements, such as service level
agreements, remuneration agreements, support agreements, incident
management agreements, etc. (This might be construed to be the
"contract", although a contract represents an agreement between two
parties. You could define a default contract.)
Anne
On 4/1/07, Khoshnevis <[EMAIL PROTECTED]> wrote:
Hi
I have to do a project for the class, suppose we're going to
architect a sales department based on SOA.
First of all, I have derived some composite services that are
exposed to external users like order_management, then I have
decomposed them into biz services like order fulfillment and order
shipping sevices and then I have identified what software services
there must be that provide those biz services,and in the end based
on the services I've found, I must find component services and
components that realize them.
Now I've got to determine interface,contract,and description.
1- what is the exact difference of these three terms?
(contact,interface,description),I've read in some books that there
is little difference b/w these three.
2-could you please help me out giving a sample documents for each
of these or intoduce me a website that contains such thing?
In fact I need a full and simple sample of service definition.
I'm in a hurry,looking fwd to you.
Thanks in advance.
Khosh
TV dinner still cooling?
Check out "Tonight's Picks" on Yahoo! TV.
