Search

While BPM and SOA have evolved independently, there is an inevitable symbiotic relationship between them. As well, a SOA can be developed using various service formats, whether unique Web Services, orchestrated services using the Business Process Execution Language (BPEL), or other service providers. A SOA promotes the creation of highly accessible, loosely coupled, discrete business services. For greatest reach, BPM consumes and leverages such services, tying them together to solve and streamline broad business challenges. Not surprisingly however, there are certain considerations while designing a SOA to support BPM. Certain service designs align well within a BPM solution or strategy, while others can cause significant headaches for an overall BPM solution. Conversely, SOA with BPM layered on top can become an entirely different value proposition as compared to SOA alone. As a backbone for SOA components, BPM can integrate important functionalities to extend the value of the SOA investment. Similarly, BPM can provide a platform for SOA service management. We will explore the interdependencies between BPM and SOA, and will provide practical guidance on how to make each implementation mutually supportive, extending the reach and value of each. We will also discuess whether SOA alone can provide the business service functionality required for BPM solutions of the future, or if other complementary architectures may also have a role to play. [ABSTRACT FROM AUTHOR]

This Industry Track Panel poses a strategic question, "Are We Ready for the Service Oriented Architecture (SOA)?" We discuss this issue from both vendor and adopter perspectives in the company of 5 IT Executives. In particular, we go beyond the discussion of SOA standards as such, and try to assess the importance of this approach from the point of view of related technologies, such as Business Process Management, Enterprise Architecture, Configuration Management, Business Rules Systems, and Open Source Solutions. [ABSTRACT FROM AUTHOR]