Published on


Published in: Business, Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Add definition of direct cost and its elements
    Revenue definition (recognition and not sales booking)
    Define IPs cost structure (the cost of license)
  • SOA - BPM

    2. 2. Agenda Time Topic 9:00 BPM Overview 10:00 Oracle BPM & BPEL 11:00 Coffee Break 11:30 Oracle Human Task Oracle Business Rules Oracle BAM 1:30 Luch Break 2:30 Oracle ADF 3:00 SOA Guidelines & Best Practices 4:00 Coffee Break 4:15 SOA Guidelines & Best Practices 5:00 Case Study
    3. 3. Business Process Management ‫المعمال‬ ‫معمليات‬ ‫إدارة‬
    4. 4. What is BPM • Business Process Management is a generic term, that encompasses the techniques, structured methods, and means to streamline operations and increase efficiency. • BPM techniques and methods enable you to identify and modify existing processes to align them with a desired (improved) future state. •،‫التنظيم‬ ‫وأساليب‬ ‫تقنيات‬ ‫يشمل‬ ،‫عام‬ ‫مصطلح‬ ‫هو‬ ‫العمال‬ ‫عمليات‬ ‫إدارة‬ .‫الكفاءة‬ ‫وزيادة‬ ‫العمليات‬ ‫لتبسيط‬ ‫اللزمة‬ ‫والوسائل‬ •‫العمليات‬ ‫وتعديل‬ ‫تحديد‬ ‫من‬ ‫تمكنك‬ ‫العمال‬ ‫عمليات‬ ‫إدارة‬ ‫وطرق‬ ‫تقنيات‬ .‫المرجوة‬ (‫)المحسنة‬ ‫المستقبلية‬ ‫الحالة‬ ‫مع‬ ‫لمواءمتها‬ ‫الحالية‬
    5. 5. Business Process Management (BPM) Software and strategy for modeling, automating, managing and optimizing business processes across organizational divisions, systems and applications. ‫والنظم‬ ‫التنظيمية‬ ‫التقسيمات‬ ‫عبر‬ ‫العمال‬ ‫عمليات‬ ‫وتحسين‬ ‫وإدارة‬ ،‫وأتمتة‬ ،‫لقولبة‬ ‫وإستراتيجية‬ ‫برمجيات‬ .‫والتطبيقات‬ Systems Goals Process People Information Strategy Policies Compliance
    6. 6. Principles of BPM ‫العمال‬ ‫عمليات‬ ‫إدارة‬ ‫مبادئ‬ • Organize around outcomes not tasks • Correct and improve processes before (potentially) automating them • Establish processes and assign ownership • Standardize processes across the enterprise • Enable continuous change • Improve existing processes, rather than build radically new or ‘perfect’ processes •‫المهام‬ ‫وليس‬ ‫النتائج‬ ‫حول‬ ‫تنظيم‬ •‫أتمتها‬ ‫قبل‬ ‫من‬ ‫العمليات‬ ‫وتحسين‬ ‫تصحيح‬ •‫عنها‬ ‫المسؤولين‬ ‫وتعيين‬ ‫العمليات‬ ‫إنشاء‬ •‫المؤسسة‬ ‫عبر‬ ‫العمليات‬ ‫توحيد‬ •‫المستمر‬ ‫التغير‬ ‫تفعيل‬ •‫عمليات‬ ‫بناء‬ ‫من‬ ‫بدل‬ ،‫القائمة‬ ‫العمليات‬ ‫تحسين‬ .‘‫'مثالية‬ ‫أو‬ ‫جديدة‬ ‫جذرية‬
    7. 7. Typical Business Drives ‫الدوافع‬ • Reduce staff and office overhead numbers • Process business critical activities faster • Reduce the number of errors and exceptions • Reduce overall IT costs • Reduce duplications • Increase visibility into operational efficiencies and bottlenecks • Reduce business risks • Improve customer service and retention •‫العامة‬ ‫والنفقات‬ ‫الموظفين‬ ‫عدد‬ ‫خفض‬ •‫أسرع‬ ‫بشكل‬ ‫الحاسمة‬ ‫العمال‬ ‫أنشطة‬ ‫معالجة‬ •‫والستثناءات‬ ‫الخطاء‬ ‫عدد‬ ‫تقليل‬ •‫المعلومات‬ ‫تقنية‬ ‫تكاليف‬ ‫إجمالي‬ ‫خفض‬ •‫الزدواجية‬ ‫من‬ ‫الحد‬ •‫سير‬ ‫واختناقات‬ ‫التشغيلية‬ ‫الكفاءة‬ ‫في‬ ‫وضوح‬ ‫زيادة‬ ‫العمال‬ ‫عمليات‬ •‫العمال‬ ‫مخاطر‬ ‫من‬ ‫الحد‬ •‫بهم‬ ‫والحتفاظ‬ ‫العملء‬ ‫خدمة‬ ‫تحسين‬
    8. 8. Business Analysis ‫العمال‬ ‫تحليل‬ • No business process improvement or change activity can be undertaken without the use of business analysts and/or business analysis techniques • You must never attempt to change a business process without first analyzing the business impact of the change in detail • Most people think they understand the techniques of analysis (e.g., requirements gathering), but few actually do • Most projects failures do not stem from technology – Rather, a lack of insight, stakeholder support or planning -- all things that are the focus of business analysts!
    9. 9. Business Process Analysis ‫العمال‬ ‫عمليات‬ ‫تحليل‬ • Most common starting point is when something is not right in the organization… – A meta problem: there are duplicative processes and information across departments – A business problem: exception rate is too high – A micro problem: some user interface screens are confusing • Business Analyst needs to – evaluate the situation from various angles and identify core issues – review any documentation, interview workers – flowchart/document current process – recommend improvements • When to use: When you have already clearly identified a specific process or process for improvements
    10. 10. Benefits of BPM ‫العمال‬ ‫عمليات‬ ‫إدارة‬ ‫فوائد‬
    11. 11. BPM & SOA
    12. 12. Success Depends on Business Impact and Process Complexity ‫العملية‬ ‫تعقيد‬ ‫مدى‬ ‫وعلى‬ ‫العمال‬ ‫على‬ ‫التأثير‬ ‫مدى‬ ‫على‬ ‫يعتمد‬ ‫النجاح‬
    13. 13. Oracle BPM
    14. 14. Oracle BPM Solution Components Business user friendly Human centric Collaborative Frequent process changes SOA architecture Apps integration, AIA BPEL High performance STP Round-tripping with BPA BPM BPEL PM Human Centric Business Process Management System Centric Process Management and SOA
    15. 15. Unified Process Foundation • Unified engine –BPEL, Rules, Human Workflow to support ALL types of processes • Business catalog –A registry of services and objects that enables IT to provide prewired processes and human tasks to be assembled in Process Composer • End-to-end management & monitoring -Find faults that have happened anywhere in the system and take corrective action • Integration Services –Adapters, UDDI integration, CEP integration, BI action framework integration, Identity management integration • Scalable architecture –From simple to complex tasks, and large volumes of transactions
    16. 16. Unified Runtime Platform ‫موحدة‬ ‫تشغيل‬ ‫منصة‬ BPEL Create and Submit Order Process Payment Notify User Download Video Wait 3 days Call Customer Customer Customer SalesRep Copy to S3 Create and Submit Order Process Payment Notify User Download Video Wait 3 days Call Customer Customer Customer SalesRep Copy to S3 BPM (with Business and IT view) Business View Worklist Process Portal MS Office BAM, BI Process Core Human Task (BPEL4People) Business Rules SCA BPEL BPMN 2.0 BPM Server Enterprise Manager
    17. 17. Oracle Business Process Execution Language BPEL
    18. 18. What is BPEL • Business Process Execution Language • BPEL is an open industry standard – Oracle has made supported extensions to BPEL • Human Workflow Service Engine • Database Interfaces • Applications Adapter • SOA based (Service Oriented Architecture) BPEL allows for the integration of Web Services into end-to-end processes. • These BPEL processes can themselves be a Web Service. • BPEL is far more powerful than Workflow so keep an open mind as we all move through this transition.
    19. 19. BPEL Features • Supports Synchronous & Asynchronous Transactions • Flow Control‫التدفق‬ ‫في‬ ‫التحكم‬ • Compensating Transactions‫التعويضية‬ ‫الرجراءات‬ • Data Manipulation using XPath, XSLT, and Xquery • Human Workflow • Routing/Assignments ‫تكليف‬ / ‫تورجيه‬ • Notifications ‫إخطارات‬ • Nomination, Delegation and Reassignment ‫تكليف‬ ‫وإعادة‬ ‫تفويض‬ ،‫ترشيح‬ • Escalations ‫التصعيد‬ • JSP Forms‫نماذج‬ • Work List Application‫العمال‬ ‫قائمة‬ • Comments and Attachments‫المرفقات‬ ‫و‬ ‫الملظحظات‬ • Audit Trail‫والتدقيق‬ ‫المرارجعة‬
    20. 20. BPEL Process in JDeveloper
    21. 21. BPEL Mapping / Transformation
    22. 22. BPEL Console
    23. 23. BPEL Console – Process Flow
    24. 24. Human Task Flow ‫بشري‬ ‫تدخل‬ ‫تتطلب‬ ‫التي‬ ‫الرجراءات‬
    25. 25. Human Task
    26. 26. Human Task • A BPEL process invokes a special activity of the human task type when it needs a human to perform a task. • The process waits for the task to complete. • There is metadata associated with the task that is used by the human task service component to manage the lifecycle of the task: • Who performs the task • Who are the other stakeholders • When must the task be completed • How do users perform the task, • The human task service component uses an identity directory, such as LDAP, to determine people's roles and privileges. • The human task service component presents tasks to users through a variety of channels: • Worklist Application • Worklist Portlet • Notifications: email, phone, SMS, etc.
    27. 27. Work List‫العمال‬ ‫قائمة‬
    28. 28. Human Task Features Escalation & Notifications Flow Patterns & Routing PoliciesFlow Patterns & Routing Policies
    29. 29. Workflow Services
    30. 30. Oracle Business Rules ‫العمل‬ ‫سير‬ ‫قواعد‬
    31. 31. Business Rules‫العمل‬ ‫سير‬ ‫قواعد‬ Business rules are statements that describe business policies or describe key business decisions. ‫العمال‬ ‫قرارات‬ ‫تصف‬ ‫أو‬ ‫العمل‬ ‫سياسات‬ ‫تصف‬ ‫التي‬ ‫العبارات‬ ‫هي‬ ‫العمل‬ ‫سير‬ ‫قواعد‬ .‫الرئيسية‬ Examples: •Business policies such as spending policies and approval matrices. •Constraints such as valid configurations or regulatory requirements. •Computations such as discounts or premiums. •Reasoning capabilities such as offers based on customer value.
    32. 32. Business Rules – Declarative Rules
    33. 33. Business Rules – Decision Table
    34. 34. Oracle Business Activity Monitor BAM ‫المعمال‬ ‫نشاط‬ ‫مراقب‬
    35. 35. Business Activity Monitor - BAM Oracle BAM provides a framework for •Creating dashboards that display real-time data inflow. •Creating rules to send alerts under specified conditions.
    36. 36. Business Activity Monitor - BAM • Data and Event Collection: The Oracle BAM provides mechanisms to collect event and data information from various sources, and it is integrated with Oracle BPEL Process Manager to link process-related events in real time. • Event Analysis: This allows the filtering and analysis of event-based information in line with the KPI information set by the users. • Intuitive Dashboards: This allows detailed reports regarding the process to be available to the users as per their requirements. It allows data from various sources to be made available using intuitive dashboards, which a user can use to take decisions or set customized alerts. • Real Time Alerts: The Oracle BAM provides the capability for setting alerts in case a business process is performing outside the range of acceptable standards.
    37. 37. Oracle Applications Development Framework ADF
    38. 38. Oracle Application Development Framework (ADF) – Is an end-to-end Java EE framework that is extensible – Utilizes and adds value to the Java EE platform – Abstracts Java EE complexity – Provides declarative and visual development – Enables developers to focus on the application, not the low- level infrastructure – Creates reusable and maintainable code – Uses metadata, simplifying the basic task of wiring user interfaces to services – Implements Java EE best practices and design patterns, including MVC
    39. 39. The Model-View-Controller Design Pattern
    40. 40. Implementing MVC with the ADF Framework ADF Bindings (JSR 227) Business Services Data Services Model Controller View JSF Desktop Browser-based Struts JSF/ADF Task Flow OfficeADF Swing JSP ADF Faces / DVT XML Data Legacy DataRelational Data Packaged Apps TopLink EJB BAM ADFbc PortletsBI EssbaseBPEL Web Services Java
    41. 41. Types of ADF Business Components CustomerEO OrderEO LineItemEO OrdVO CustVO CustomerOrder AllOrders Customer Application Module with View Object Instances View Objects and View Link Entity Objects and Associations StorefrontAM
    42. 42. SOA Guidelines & Best Practices ‫الممارسات‬ ‫أفضل‬ ‫و‬ ‫التوجيهية‬ ‫المبادئ‬
    43. 43. Understand Your Organization
    44. 44. Start with Business First‫أول‬ ‫بالمعمال‬ ‫إبداء‬ • Do not try to boil the ocean. • Focus on what is strategically important --- NOW! • Front End E-Services first • Regulations & Compliancy • E-Government Coverage • Near-term focus, grow scope over time •‫المور‬ ‫تعقد‬ ‫ل‬ •‫إستراتيجية‬ ‫ناحية‬ ‫من‬ ‫مهم‬ ‫هو‬ ‫ما‬ ‫معلى‬ ‫ركز‬ •‫أول‬ ‫للجمهور‬ ‫الموجهة‬ ‫الخدمات‬ •‫للقوانين‬ ‫المتثال‬ ‫و‬ ‫اللوائح‬ •‫اللكترونية‬ ‫للحكومة‬ ‫كاملة‬ ‫تغطية‬ •‫إلى‬ ‫النطل ق‬ ‫ثم‬ ‫المدى‬ ‫قريبة‬ ‫الخطط‬ ‫معلى‬ ‫التركيز‬ ‫المدى‬ ‫بعيدة‬
    45. 45. Be Flexible‫بالمرونة‬ ‫تمتع‬ • Executives will probably never, ever, use EA models but they will always need the outputs • Provide what they need in a form that they like • Recognize Business Architecture for business planning is an emerging discipline •‫هيكلية‬ ‫نماذج‬ ‫يستخدموا‬ ‫لن‬ ‫التنفيذيون‬ ‫المديرون‬ ‫لنواتج‬ ‫دائما‬ ‫يسعون‬ ‫لكنهم‬ ، ‫الرجح‬ ‫معلى‬ ‫المؤسسات‬ .‫منها‬ ‫المتأتية‬ •.‫لهم‬ ‫يرو ق‬ ‫أن‬ ‫يمكن‬ ‫شكل‬ ‫في‬ ‫له‬ ‫يحتاجون‬ ‫ما‬ ‫توفير‬ ‫حاول‬ •‫وانضبات‬ ‫كعلم‬ ‫المعمال‬ ‫وتخطيط‬ ‫بمعمارية‬ ‫المعتراف‬ .‫ناشئ‬
    46. 46. SOA Guidelines • Align architecture principles across lines of business by creating reference architectures • Centralize the creation of standards, policies, and processes • Select technical solutions and vendor partners that adhere to industry standards • Establish an enterprise data management function to define and monitor enforcement of data governance across governmental entities. • Enforce security policies at the data service layer with declarative policy definition centrally • The SOA approach should focus on high-value business processes • EA and SOA should be driven by multiyear strategic plans that integrate business and IT goals • Provide enterprise SOA training for managers and stakeholders as well as architects, developers, PMs, BAs, and QAs • Utilize a service registry to catalogue existing services and define processes to identify and submit potentially sharable services
    47. 47. SOA Guidelines • Centralize SOA operations and support until greater maturity is realized • Deploy a Web services management solution for runtime policy enforcement through distributed policy enforcement points • Establish SOA goals and strategies that are tightly aligned with the business • Establish SOA goals, standards, policies, and procedures proportionate to your SOA maturity • Define clear metrics that are obtainable and can show your progress in maturing your SOA and EA efforts • Put repeatable and well-defined governance processes in place and capture metrics • Automate as many of the governance processes and collection of metrics as possible • Use a multiyear financial strategy to justify SOA investments • Consider central funding for services that are to be used across departments
    48. 48. Service Design Best Practices  Service Size: Granular and not complicated  Self Contained and reflects a real life service rendered to consumers  Very well defined interface and contract  Stick to WS Interoperability standards and data types  There is no versioning support in WS*. You need to add version number to the Service namespace to make it part of the name.  Do not use code generation tools to generate a service interface. Always start with building the service interface first.  Internal Error Handling and Logging is essential  Clearly document the transaction behavior of the service
    49. 49. Enterprise Message Data Model Canonical Data Model
    50. 50. Composition vs. Orchestration  Oracle SOA Suite SCA-based architecture is all about composition of components together into an “integrated circuit” that might well be part of a bigger application.  Orchestration concerns the control of a process across multiple systems and people. That control involves branching, state management and human task flows.  One should use SOA composite for composition and BPEL for process orchestration.
    51. 51. BPEL Best Practices  BPEL is for orchestrating services and should not be used to add complex business logic. This should go into the service layer.  Simplify your BPEL process as much as you can for easier change in the future.  Create scopes for each step of the flow in the process so as to make it modular. This will help in creating local variables within that scope. Use Global variables only when required.  Adopt naming standards and comply to it. This should be part of the governance strategy.  It is good practice to have a Mediator in the Composite. Try to get most of the transformations done by the Mediator.  Have all the business rules implemented by the Oracle Business Rules.  Handle all the exceptions, provide notifications, and recover errors if needed.  Take care of transactions  Apply compensating transaction where applicable
    52. 52. Error & Exception Handling  Define policies for handling faults in a loosely coupled manner. It externalizes the fault-handling mechanism from process implementation.  Use fault logging and notification.  Catch faults that should be handled by the business process to take a corrective action.  Re-Try the process after correcting actions have been taken.
    53. 53. Logging  Attaching the Log Policy With a logging policy you can extend logging with exact entries with the contents of the messages coming in to and flowing out of the composites and components.  Setting the Name of a Composite Instance Distinguish instances by dynamically assigning a meaningful name to an instance of a composite.  Composite Sensors Composite sensors make tracing easy by allowing you to expose information from within composite instances. These sensors are typically used to expose the data enable search of the instances.
    54. 54. General Guidelines  Use technology to simplify business process and make it more efficient.  Never over use technology for the sake of being trendy.  Gradual and multi-stage implementation is the key to any successful Enterprise IT project.  Align your technology selection with the vendors technology roadmap
    55. 55. Case Study Greater Amman Municipality
    56. 56. Integrating EBS with Legacy Systems Vertical Systems •‫التحققات‬ ‫نظام‬ •‫المخالفات‬ ‫نظام‬ •‫تراخيص‬ ‫مخالفات‬ ‫نظام‬ ‫المسالخ‬ ‫و‬ ‫والصحة‬ ‫المهن‬ ‫والنبنية‬ •‫والذنبيحات‬ ‫المسالخ‬ ‫نظام‬ •‫المحال‬ ‫تراخيص‬ ‫نظام‬ ‫التجارية‬ •‫التستمل