You're reading from Intelligent Automation with IBM Cloud Pak for Business Automation A practical guide to automating enterprise business workflows to deliver intelligent solutions

Product type Paperback

Published in Dec 2022

Publisher Packt

ISBN-13 9781801814775

Length 450 pages

Edition 1st Edition

Tools

IBM Automation

Concepts

Application Development

Authors (5):

Suzette Samoojh

Guilhem Molines

Stephen Kinder

Allen Chan

Kevin Trinh

+1 more

View More author details

Table of Contents (21) Chapters

Preface

1. Part 1: Business Automation and Cloud Pak Overview

2. Chapter 1: What Is Cloud Pak for Business Automation? FREE CHAPTER

3. Chapter 2: RPA, Workflow, Decisions, and Business Applications

4. Chapter 3: Process Discovery and Process Mining

5. Chapter 4: Content Management and Document Processing

6. Part 2: Use Cases and Best Practices

7. Chapter 5: Task Automation with RPA

8. Chapter 6: Chatbot with RPA

9. Chapter 7: Workflow for Process Automation

10. Chapter 8: Automating Decisions to Speed Up Your Processes

11. Chapter 9: Manage Documents with Content Management

12. Chapter 10: Extract Meanings with Document Processing

13. Chapter 11: Engaging Business Users with Business Applications

14. Chapter 12: Workforce Insights

15. Part 3: Deployment Considerations

16. Chapter 13: On-Premises and On-Cloud Deployments

17. Chapter 14: Deployment Topologies, High Availability, and Disaster Recovery

18. Chapter 15: Automating Your Operations and Other Considerations

19. Index

Why subscribe?

20. Other Books You May Enjoy

Disaster recovery

HA is not DR. They have similar objectives: business continuity and minimizing downtime. The difference between HA and DR is that DR focuses on policies and procedures to enable the recovery of the system, application, or entire data center to a fully operational state after a catastrophic event. Similar to HA, there are SLAs that help define requirements for DR, which, in turn, determine the policies, procedures, strategy, and even implementation details to meet the needed SLAs. Two important terms help define the DR requirement: Recovery Point Objective (RPO) and Recovery Time Objective (RTO).

RTO measures how quickly the system, application, or data center can be restored. This measurement of time for recovery is not only about restoring the application to a functional state to resume critical business processes but also about the data.

RPO is the enterprise measurement of data loss tolerance. How much data can the enterprise afford to lose without it having...