Added by Thor Henning Hetland, last edited by Thor Henning Hetland on Jul 06, 2009  (view change)

Labels:

Enter labels to add to this page:
Wait Image 
Looking for a label? Just start typing.

Application 2 Application Services

Application 2 Application Services
Application 2 Application Services is services which orchestrates services from several applications, typically asynchronous and workflow-backed. I.e. a Auction type request against a set of suppliers or an booking/order/delivery process.

Characteristics

Services orchestrated to produce real busuness value

  • Workflow-oriented processes
  • Orchestrated functionality from several services
  • ACS/CS services as Business/Domain Objects
  • External applications for sub-processes & tasks
  • Long running processes
  • Should not have any long-running transactions
  • Could (should) have cache (state full)

Patterns for Application 2 Application Services

Application 2 Application Services

Technology/Implementation strategy (Java)

Technology, implementation and products

  • Pick your favorite JEE/ESB/SOA platform vendor
    • Sun, IBM, Oracle
  • Choose your favorite open source ESB/SOA platform
    • OpenESB or another Open Source JBI container
    • write a simple admin framework (upgrade tool support)

Technology/Implementation strategy (.NET)

Technology, implementation and products

  • BizTalk Server
  • Enterprise Human Workflow products can do some tasks
    • Enterprise Human Workflow with K2.NET / Skelta/ Captaris++
    • Portal connectors useful

Design rules

P1. A service shall have one named owner
P1. A service shall have one named owner
P2. A service shall provide documented business value
P2. A service shall provide documented business value
P20. All services shall be in the service universe
P20. All services shall be in the service universe
P21. A service shall be categorized (OW SOA category)
P22. A service shall have an "authentication, authorisation, endpoint strategy"
P23. A service shall document its Service Level Agreement SLA (response time, availabillity++)
P3. A service shall do one only thing, and one thing well
P3. A service shall do one only thing, and one thing well
P30. A service shall have a versioning strategy (ACS, CS)
P31. A service shall provide for audit and monitoring of service usage
P31. A service shall provide for audit and monitoring of service usage
P41. A service shall provide heartbeat and traffic monitoring
P90. A service shall have a documented coupling to the contractual and requirement for service usage
P90. A service shall have a documented coupling to the contractual and requirement for service usage
  • [Policy Rules for A2A services]

Other technical details

Content is moved to Service Categories
All content on this wiki is licensed under a Creative Commons Attribution 3.0 Unported License.