Cisco Cisco Intelligent Automation for Cloud 4.3.1 Installation Guide

Page of 130
35
 
Installing Cisco IAC Process Orchestrator Automation Packs
Installing the Cisco IAC Automation Packs
Note: 
Take a note of the folder name where the extracted data will be placed and uncheck the SQL Server Reporting 
Services Reports if you are not using the MS SQL Reporting solution. 
The Review Prerequisites panel displays the prerequisites for the automation pack being imported, and will indicate 
either pass or fail for each prerequisite. 
After the prerequisite check has completed (and passed), the Importing Objects panel displays.
After the objects have been imported, the General Information panel displays.
Installing the Cisco IAC Automation Packs
The four Cisco Automation packs are installed next. These include, in sequence:
Intelligent Automation for Compute.tap
Intelligent Automation for Cloud Starter.tap
Intelligent Automation for Cloud.tap
Intelligent Automation for Cloud Extension Samples.tap (optional but recommended)
The install process for each Automation Pack is explained next.
Installing the Intelligent Automation for Compute Pack
1.
On the General Information panel, review the information there. Note that the Name field now displays “Intelligent 
Automation for Compute.” This is the first Cisco IAC automation pack that you will be installing.
2.
Click Next.
3.
On the Default Incidents Assignee Setup panel, specify the default user which to assign cloud-related incidents. This 
is a CPTA (Cloud Provider Technical Administrator) account, or would be within an Active Directory group that was 
created for all of CPTAs in this Cloud.
4.
Click Next.
5.
On the Cisco Process Orchestrator Web Service panel, specify the following data. Check the Enable non-secure 
Web Service (HTTP)
 check box in the Web Service Settings area. This setting unencrypts the HTTP endpoints. 
Note: 
If or when presented with a security warning message, click OK.
6.
Enter or verify the HTTP Port for the Process Orchestrator web target.
7.
Choose the appropriate authentication method for the web service:
Basic—Standard method that provides a username and plain-text password to the authentication mechanism.
Digest—Method that provides a username and a hashed password to the authentication mechanism.
NTLMDefault. Authentication protocol that is used on networks that include systems running the Windows 
operating system and on stand-alone systems.
Note: 
The NTLM setting supports both NTLM and NTLMv2. In IIS, NTLM is not enabled by default; you must enable 
NTLM in IIS if you choose this authentication mechanism. The agents in Prime Service Catalog must also be set to 
use the same authentication that you specify here. 
8.
When you are done, click Next to continue.