9/29/2014

OSB standards and guide lines | Service Oriented Architecture - SOA

OSB standards and guide lines

After implementing some OSB projects I want to share some guidelines that Im using on this
projects. Like BPEL you need to have define some standard naming conventions, to make
your application maintainable, shareable and explainable to customers.
The following naming convention should be used:
Proxy services
Every proxy service should start with the PS_ prefix, followed by the functional name and
ends with a verion and release number.
PS_<functional-name>_v1r0

End points
The end point of the proxy service should be changed to
/<category>/PS_<functional-name>_v1r0
Business services
Every proxy service should start with the BS_ prefix, followed by the functional name and
ends with a verion and release number.
BS_<functional-name>_v1r0

Categories
Discover all the services that need to be implement for OSB. Catelog the services in a
category. This category is used as OSB project to collect the proxy services and business
services. There is one special category; common..
The structure of a category is as follows:
<category>/BusinessService
<category>/ProxyService
<category>/Schema
<category>/Transformation
<category>/Wsdl

Common objects
http://www.soaguru.com/osb-standards-and-guide-lines

1/2

9/29/2014

OSB standards and guide lines | Service Oriented Architecture - SOA

Objects as such as XSD files, xqueries, xslt etc, that are used in more then one proxy /
business services are stored in the common category.
Actions
In OSB actions are executed in the message flow of the proxy service. Each action has a
default name. Rename each action into the following format.
<action>_<function_name>

For example
Assign_saveBody
Replace_tranform2OrderMessage

http://www.soaguru.com/osb-standards-and-guide-lines

2/2