Book Image

Oracle SOA Governance 11g Implementation

By : Luis Weir
Book Image

Oracle SOA Governance 11g Implementation

By: Luis Weir

Overview of this book

Service-oriented Architecture (SOA) is an architectural style created to address the challenges posed by today’s highly distributed, fast-paced computing. This goal is achieved by constructing business-focused software systems from loosely coupled, interoperable building blocks called Services. Organizations often fail to successfully implement SOA due to a lack of effective governance. Oracle SOA Governance is a comprehensive, service-orientated architecture governance solution that is designed to make the transition to SOA easier."Oracle SOA Governance 11g Implementation" illustrates how to successfully implement SOA governance in your organization. To achieve this, we describe how goals and objectives need to be clearly laid out and used to align governance processes with governance tools, governance tools with people, and people with the different roles and responsibilities that are required to implement effective governance."Oracle SOA Governance 11g Implementation" begins with a short but concise overview of SOA governance. We then go to explore real world examples, based on previous experiences and working solutions, in order to learn the concepts of Oracle SOA Governance Suite.We will also learn how to implement an OER-centric SDLC process to address your organizations design-time governance requirements. Next, we will explore OSR, and discover how to use it to expose service implementations to consumers based on UDDI concepts. We will explore the features available within Web Service Manager (WSM), Oracle Enterprise Manager (OEM), and Business Transaction Manager (BTM). Finally, we discover how OER can be extended to govern Oracle Application Integration Architecture (AIA) implementations.Discover and learn how to use Oracle SOA Governance Suite to address your specific design-time and runtime governance challenges.
Table of Contents (21 chapters)
Oracle SOA Governance 11g Implementation
Credits
Foreword
About the Authors
Acknowledgments
About the Reviewers
www.PacktPub.com
Preface
Index

Understanding workflow


The first step to understand which customizations are needed is to do a gap analysis between the existing functionality and the desired functionality.

Let's start by understanding how the standard approval process works in OER by default:

  • When an Asset is submitted through the Harvester or REX API, the status of the Asset can be defined as desired. However, note that the user provided when executing the Harvester or REX API must belong to the relevant role, as otherwise, the Asset submission will fail.

  • When an Asset is submitted through the Asset Editor by any user with role Advance Editor, the status of the Assets is set to Unsubmitted. The Asset then needs to be approved by a user with the role of Advance Editor in order for the Asset to change its status to Submitted – Pending Review.

    Note

    Note that every time the status of the Asset changes, Event Managers throw an event. These events are then picked up by the workflow engine to execute a specified action.

  • When an Asset...