The Hebrew University Magnes Press


 View book pages:
  




Services In this chapter

by Ben Margolis, Joseph Sharpe
Services In this chapter we continue our SOA overview with a focus on services. A service includes the following aspects: • a service implementation • elementary access details • a contract A service implementation is the core business logic, which might be written in Java, COBOL, Enterprise Generation Language ( EGL), or any other programming language. Elementary access details include the location, which is an address where the service implementation resides, and the binding, which identifies the transport protocol ( such as HTTP or Java Message Service) that formats a message at the start of transmission and unformats it at the end of transmission. Formatting occurs when the invocation message originates at the requester; in that case, unformatting occurs when the message arrives at the service location. Formatting also occurs if the service issues a response; in that case, unformatting occurs when the response arrives at the requester. A contract describes the service’s intended behavior and is independent of the implementation details. The contract includes two elements: a service interface and a Quality of Service. C H A P T E R 2

Zoom in  zoom  Zoom out
  << Topic >>  | Contents | Index             |<   <<    Page       >>   >|  
Services In this chapter we continue our SOA overview with a focus on services. A service includes the following aspects: • a service implementation • elementary access details • a contract A service implementation is the core business logic, which might be written in Java, COBOL, Enterprise Generation Language ( EGL), or any other programming language. Elementary access details include the location, which is an address where the service implementation resides, and the binding, which identifies the transport protocol ( such as HTTP or Java Message Service) that formats a message at the start of transmission and unformats it at the end of transmission. Formatting occurs when the invocation message originates at the requester; in that case, unformatting occurs when the message arrives at the service location. Formatting also occurs if the service issues a response; in that case, unformatting occurs when the response arrives at the requester. A contract describes the service’s intended behavior and is independent of the implementation details. The contract includes two elements: a service interface and a Quality of Service. C H A P T E R 2
Zoom in  zoom  Zoom out
  << Topic >>  | Contents | Index             |<   <<    Page       >>   >|  

MC Press Online - 9781583470657


 Other related titles:
Developing Web 2.0 Applications with EGL for IBM iDeveloping Web 2.0 Applications with EGL for IBM i
Enterprise Web 2.0 with EGLEnterprise Web 2.0 with EGL
HTML for the Business DeveloperHTML for the Business Developer
IBM Data Governance Unified Process, TheIBM Data Governance Unified Process, The
MDM for Customer DataMDM for Customer Data
Programming PortletsProgramming Portlets

 Already viewed books:
SOA for the Business DeveloperSOA for the Business Developer