Skip to main content

Skip over site navigation to main content

developerWorks  >   SOA & Web Services  >   Technical library  >  

Technical library view  RSS for SOA & Web Services

 developerWorks
 Related links:    Redbooks  |  Forums  |  Standards and specifications

Filter your search and/or enter a keyword. If you don't filter your search or enter a keyword, the search results will default to all results.

 
 
 
  1 - 12 of 12 results    Hide Summaries
Title   Type   Date  

Table that contains the results that meet the search criteria.

SOA programming model for implementing Web services: SOA and the mainframe software environment
Service-Oriented Architecture (SOA) is an evolutionary concept that's applicable to new and existing software systems. However, the best ways to apply SOA to an existing software system may not be obvious. Discover several approaches and how these can benefit your business. 		Articles 18 Apr 2006  
 
SOA programming model for implementing Web services, Part 10: SOA user roles
One of the advantages of using a Service-Oriented Architecture (SOA) is the alignment of the IT systems to the business they are serving. This has an effect on the people who develop and operate these IT systems both in terms of the tasks they perform and the knowledge and skills they require. This article walks you through a simple integration scenario to illustrate how a team creates and runs a services-oriented solution. It uses user roles to describe the skills and responsibilities of the people involved, and it's geared toward technical leaders to help you understand how to organize the work associated with service-oriented solution development. 		Articles 21 Feb 2006  
 
SOA programming model for implementing Web services, Part 9: Integrating rules with SOA
This article reviews how business rules integrate with the IBM Service-Oriented Architecture (SOA) as a component type, bringing advantages in business agility and alternate execution models that complement the features of other component types. You'll learn about three general rule categories -- sequential rules, event correlation rules, and inference rules. 		Articles 29 Nov 2005  
 
SOA programming model for implementing Web services, Part 8: Human-based Web services
The involvement of people in service compositions is a relatively new facet of Service-Oriented Architecture (SOA), expanding the ways software can model how humans work and interact in a business. This article describes functions offered by the Human Task Manager of IBM WebSphere Process Server and their use in a portal. 		Articles 21 Oct 2005  
 
SOA programming model for implementing Web services, Part 7: Securing service-oriented applications
Securing applications in a service-oriented architecture (SOA) is challenging, because the loose coupling that characterizes an SOA can expose existing security implementations' weaknesses. The following solution includes well-defined trust models based on acceptable forms of proof as well as reliance on policies, Web services security, and security engineering best practices. 		Articles 06 Sep 2005  
 
SOA programming model for implementing Web services, Part 6: The evolving component model
A language-neutral, component-based programming model for service-oriented architecture (SOA) facilitates the implementation of Web services and their assembly into solutions. The programming model enables non-programmers to use existing IT assets without mastering intricate technologies. It meets the needs of solution designers and business analysts, providing a higher level of abstraction that conceals differences between implementation technologies, yet enables business accountability. 		Articles 23 Aug 2005  
 
SOA programming model for implementing Web services, Part 5: Service-oriented user interfaces
A service-oriented programming model can simplify the development of program-to-human interactions by abstracting interfaces, standardizing messages, and aggregating independent information sources at the presentation layer under the control of a user or administrator. This fifth article in the series on the programming model for IBM's SOA covers services that are user facing and, as well as services provided by users through the Human Task Manager. Previous articles in this series introduced a language-neutral data access and programming model for Web services based on service-oriented architecture (SOA) concepts. 		Articles 09 Aug 2005  
 
SOA programming model for implementing Web services, Part 4: An introduction to the IBM Enterprise Service Bus
The Enterprise Service Bus (ESB) architectural pattern supports virtualization and management of service interactions in a service-oriented architecture (SOA). It enables interactions among service providers and requesters and can be implemented using a variety of middleware technologies and programming models. It extends the SOA programming model concepts introduced in previous articles of this series. 		Articles 26 Jul 2005  
 
SOA programming model for implementing Web services, Part 3: Process choreography and business state machines
One approach to service composition is to define services as business processes using Business Process Execution Language (BPEL) or represent them as business state machines. The mainline code orchestrating the invocations of a series of such services runs in a special container called a process choreography engine. Container-provided functions enable long-running process executions that can even span enterprise boundaries, survive planned and unplanned outages, and facilitate business-to-business (B2B) collaboration. 		Articles 12 Jul 2005  
 
SOA programming model for implementing Web services, Part 2: Simplified data access using Service Data Objects
Take advantage of Service Data Objects (SDOs) to simplify data access and representation in your service-oriented software. SDOs replace diverse data access models with a uniform abstraction for creating, retrieving, updating, and deleting business data used by service implementations. This is the second article in our series on the programming model for the IBM(R) Service-Oriented Architecture (SOA). 		Articles 28 Jun 2005  
 
SOA programming model for implementing Web services, Part 2: Simplified data access using Service Data Objects
Take advantage of Service Data Objects (SDOs) to simplify data access and representation in your service-oriented software. SDOs replace diverse data access models with a uniform abstraction for creating, retrieving, updating, and deleting business data used by service implementations. This is the second article in our series on the programming model for the IBM(R) Service-Oriented Architecture (SOA). 		Articles 28 Jun 2005  
 
SOA programming model for implementing Web services, Part 1: Introduction to the IBM SOA programming model
The IBM(R) programming model for Service-Oriented Architecture (SOA) enables non-programmers to create and reuse IT assets without mastering IT skills. The model includes component types, wiring, templates, application adapters, uniform data representation, and an Enterprise Service Bus (ESB). This is the first in a series of articles about the IBM SOA programming model and what is required to select, develop, deploy, and recommend programming model elements. The content presented here takes into account that developers come to this model with different skill levels and roles. 		Articles 14 Jun 2005  
 
  1 - 12 of 12 results    Hide Summaries
Not finding what you're looking for? Suggest Content