Automation 360

Configure API Task for Private Database Access

Download as PDF

Automation 360
Features, licenses, and deployment
- Platform licenses
  - Enterprise Platform
  - Automator AI Platform Base
- Deployment models
- Cloud licensing FAQ
- GUID licensing model
Release Notes
- Automation 360 Release Notes
- Community Edition Release Notes
- Sandbox environment
- Package updates overview
- Previous Package SDK Release Notes
- Process Discovery Release Notes
- Browser extensions for Automation 360
- Automation 360 feature comparison matrix
- Automation 360 IQ Bot feature comparison matrix
- Automation 360 IQ Bot version compatibility
Automation 360 Cloud
- Automation 360 FAQ
- Automation 360 architecture and resiliency
- Automation 360 Cloud FAQ
- Automation 360 software lifecycle policy
- Automation resiliency
  - Managing unexpected pop-ups
    - Configure pop-up handling
  - Record automation execution
    - Configure automation recording
    - Manage automation recording
- Upcoming feature deprecations
- In-product user assistance
Automation and generative AI
- AI Agent Studio
- Automator AI
- Data security for generative AI - FAQ
Set up Automation 360
- Get started with Automation 360 Cloud
  - Automation 360 Cloud prerequisites
- Installing Control Room On-Premises
- Set up Community Edition
  - Community Edition capabilities
- Get started with Bot Agent
- Naming guidelines for Control Room URLs
- Post-installation user management
- Update Automation 360 to latest version
  - Update Automation 360 on Microsoft Windows Server using scripts
- Install and update Automation 360 IQ Bot
- Log in to Automation Anywhere Control Room
- Create your first bot
- Run your first bot
- Moving from Automation 360 On-Premises to Cloud
  - Moving data using Control Room operations
  - Migrate using Control Room APIs
- Migrate to Automation 360
Configure Automation 360
- Manage Control Room users
- Roles
- Manage licenses
  - View license details
  - Installing additional licenses
- Create your users and assign their licensed roles
- Configure Settings
- Edit My settings
  - Edit profile settings
- Set up your bot repository
- Working with repositories, credentials and roles
  - Manage user credentials
- Credentials and lockers in the Credential Vault
- Control Room IP addresses for external integrations
Manage Automation 360
- Devices
  - About multi-user devices
    - Configure RDP-based deployment for multi-user devices
    - Convert an existing device to a multi-user device
  - Edit multiple devices simultaneously
- About device pools
- Add queue, Bot Runner, and device pool
- Configure Active Directory in Control Room
- Configure OAuth connections in Control Room
- Packages
- External key vaults for Automation 360
- Workload management
- Bot Lifecycle Management
Monitor Automation 360
- Automation Command Center
- Automation program lifecycle with CoE Manager
- Activities
- Audit log
  - Audit events list
  - Export audit data to CSV
- Code analysis
- Notifications
- Control Room log files
Build automations
- Process Composer
- Interactive forms
  - Add a form to bot
- API Task
- Connector Builder
- Recorders
  - Universal Recorder for object-based automation
  - AISense for recording tasks from remote applications
- Task Bots
- Templates
- Bot Store
- Advanced bots and packages
- Troubleshooting and debugging
Automation Co-Pilot
Automation Co-Pilot for Business Users
- Embed automations in your application using Automation Co-Pilot
- Using Automation Co-Pilot for Business Users on desktop
- Automation Co-Pilot for Business Users on the web interface
- Approvals in Automation Co-Pilot
  - Using and sorting the Tasks view
- Automation Co-Pilot status and notifications
Users and roles for Automation Co-Pilot
- Create users for Automation Co-Pilot
- Create a team and assign roles to team members
- Manage roles and teams for Automation Co-Pilot
- Scheduler users and device pools in Automation Co-Pilot
- Configure deployment type for bots
Automation scenarios
- Scenario: Generating insurance quote with Automation Co-Pilot and Process Composer
- Scenario: Developing and using templates in an automation
Document Automation
- Key concepts
- Get started
- Licensing
- Document preprocessing
  - IQ Bot Pre-processor package
- Document classification
- Document extraction
- Document validation
- Move learning instance to production
  - Publish the learning instance to production
    - Build a bot to upload documents to Document Automation
    - Deploy the learning instance assets
- Moving from IQ Bot to Document Automation
- Community Edition
  - Document Automation Community Edition
    - Create a learning instance in Community Edition
    - Process documents in Community Edition
Automation 360 IQ Bot
- IQ Bot architecture diagram
- Using Automation 360 IQ Bot On-Premises
- Using Automation 360 IQ Bot Cloud
- IQ Bot user personas and roles
  - Defining a custom role for IQ Bot
  - Creating a user with an IQ Bot specific role
- Languages supported in Automation 360 IQ Bot
- About the Classifier
  - Create a new document group
- Create a learning instance
- Train a learning instance
- Manage learning instances
- Rotate the external key
- Use the IQ Bot Validator
- Review the dashboard
  - Performance report page
  - Performance report details
- Custom domains in IQ Bot
- Using IQ Bot for standard forms
Process Discovery
- Overview of Process Discovery
  - Options to reduce exposure of sensitive data
- Process Discovery user roles
- Create Process Discovery users and assign roles
- Integrate SAML with SSO for Process Discovery
- Create your event reporting password
- Create a URL and application list
- Configure Observer activity
- Use Process Discovery with Kibana dashboard
  - Access the Kibana dashboard
- Create a cycle
- Classify application screens and create web applications
  - Applications with auto-assigned screen signatures
- Review Events and filter data
- Mining for processes
- Analyze and prioritize processes
- Creating groups for the process and generate a PDD
- Process Discovery - CoE Manager integration
- Getting started with Privacy Enhanced Gateway
- Process Discovery Sensor application
- Process Discovery FAQ
- Process discovery by using Discovery Bot
Bot Insight
- Business analytics through Bot Insight
- Accessing Bot Insight
- Using Bot Insight
  - Business analytics
    - Configuring a task for business analytics
- Using widgets
- Data connector for Power BI
- Configure Tableau web data connector in Bot Insight
API References
- Control Room APIs
- Filtering, pagination, and sorting
- API response codes
- Comparing Automation 360 and Enterprise 11 APIs
- Configure the Control Room
- Roles and permissions
- How to find a migration journalid
- Using Auto registration API
Glossary

Configure API Task for Private Database Access

Download as PDF

Version:
Updated: 2024/08/20

Configure API Task for Private Database Access

This guide outlines the steps involved in securely connecting an API Task to a private database within a Virtual Private Cloud (VPC) using a Network Load Balancer (NLB) in a public subnet. This configuration provides a secure and scalable way to access the database from the API Task while maintaining isolation within the private network.

Key Components:

VPC: A virtual private cloud network.
Public Subnet: Hosts the network load balancer and internet gateway.
Private Subnet: Contains the EC2 instance running the database.
Network Load Balancer: Distributes traffic across multiple EC2 instances.
API Task: An API-based cloud automation solution.

Configuration Steps:

Create VPC and Subnets: Set up a VPC with public and private subnets.
Configure Network Load Balancer:
- Place the load balancer in the public subnet.
- Associate it with the internet gateway.
- Create a listener (e.g., port 443 for HTTPS).
- Configure target groups for the EC2 instance(s) hosting the database.
Whitelisted API Task IPs: Add the IP addresses of your API Tasks to the load balancer's whitelist. For more information, see API Task IP addresses for external integrations.
Configure EC2 Instance:
- Launch an EC2 instance in the private subnet.
- The EC2 instance hosts database software (e.g., Microsoft SQL Server). For instance, if you are using Microsoft SQL Server then open port 1443 (or the appropriate database port) on the EC2 instance's security group.
Note: SQL Server uses TCP port 1433 as the default for communication. In this configuration, the network load balancer forwards traffic to the database instance in the private subnet on this port.
Configure API Task:
- In the Control Room, create an API Task.
- Set the API Tasks endpoint to the public IP address of the network load balancer.
- Configure authentication and authorization settings as needed.
  SQL Server Authentication: The supported authentication method for SQL Server is username and password.