Table Of Contents
Getting Started Using the Automation Pack
Prerequisites
Install SAP HANA Database Client for Windows
Configure Windows Host File and Path
Create Data Source for ODBC System DSN
Unix/Linux Target Prerequisites
Creating and Configuring HANA Targets
Creating SAP HANA Target
Creating SAP HANA Database Target
Creating a Runtime User
Creating Web Targets
Creating Unix/Linux Target
Configuring Auto-SSH Login Proxy
Creating SAP System Target
Creating an SAP User Account
Configuring References to Targets
Creating Reference to HANA ABAP Target
Creating Reference to SAP HANA Database Target
Creating Reference to SAP HANA Web Target
Creating Reference to SAP HANA Unix Target
Managing Target Properties
Accessing Target Properties
Configuring Target Properties
Using Task Rules for Assignments and Notifications
Accessing Task Rules View
Configuring Task Rules
SAP Default Assignment
Creating a New Task Rule
Managing Task Rule Definitions
Enabling a Task Rule
Disabling a Task Rule
Creating a Copy of a Task Rule
Sorting Task Rules
Deleting a Task Rule
Enabling Notification Based on Assignment Processes
Getting Started Using the Automation Pack
Before you begin using the content that ships with the automation pack, you must create the objects in Cisco Process Orchestrator that are referenced in the processes. These objects include targets, runtime users, task rules for assignments and notifications, and target properties.
This chapter provides basic information on defining the objects. It includes the following sections:
•
Prerequisites
•Creating and Configuring HANA Targets
•Managing Target Properties
•Using Task Rules for Assignments and Notifications
For additional information about the objects discussed in this chapter, refer to the following documentation:
Document
|
Description
|
Cisco Process Orchestrator User Guide
|
General information about Core product features.
|
Cisco Process Orchestrator User Guide
|
Information about the Unix objects (Unix target and runtime user)
|
Cisco Process Orchestrator Online Help
|
Information about the adapter prerequisites and the objects provided by it.
|
Intelligent Automation for SAP 3.0 Installation Guide
|
Information about the SAP targets and SAP User runtime user account.
|
Prerequisites
The following prerequisites must be met prior to configuring the SAP HANA targets in Process Orchestrator.
Install SAP HANA Database Client for Windows
The SAP HANA Database Client for Windows must be installed on the server where Process Orchestrator is installed. Download the SAP HANA CLIENT 1.00 (SP05 Revision 60 or later) for Windows on x64 64-bit from the SAP Service Marketplace.
Note The revision number of SAP HANA CLIENT 1.00 for Windows on x64 64-bit installed on the Process Orchestrator server must be the same as the revision number on the HANA database.
The minimum supported version for the SAP HANA Client 1.00 is SP05 Revision 60 or later.
Configure Windows Host File and Path
Before you can connect to the ODBC system DSN, you must add the HANA data source hostname and IP address to the Windows hosts file.
Step 1 On the Process Orchestrator server, navigate to the following location:
C:\Windows\System 32\drivers\etc\hosts
Step 2 Right-click the hosts file and open in Notepad.
Step 3 Enter the IP address and host name for the HANA host server and press Enter on the keyboard.
Step 4 Click File > Save to save the file and complete the procedure.
Create Data Source for ODBC System DSN
Before you can create SAP HANA targets, you must add the ODBC system data source used to connect to the HANA data provider from Process Orchestrator.
Step 1 In the Control Panel, double-click Administrative Tools > Data Source (ODBC).
Step 2 On the ODBC Data Source Administrator dialog box, click the System DSN tab.
Step 3 Click Add to open the Create New Data Source dialog box.
Step 4 In the list of drivers, select HDBODBC and click Finish.
Step 5 On the SAP HDB dialog box, specify the following information:
•Data Source Name
•Description
•Server:Port
Step 6 Click Connect.
Step 7 On the SAP HDB Connection dialog box, enter the User Name and Password for connecting to the HANA Database and then click OK.
Unix/Linux Target Prerequisites
The following prerequisites must be met for Unix/Linux target functionality:
•The following versions of Linux are supported:
–SUSE Linux Enterprise 11 Service Pack 1
–SUSE Linux Enterprise 11 Service Pack 2
•Linux performance monitoring requires that the SYSSTAT Linux package be installed. To install the package, run the command yast -i sysstat.
•If you want to monitor all Linux hosts, you must configure Auto-SSH login proxy. See Configuring Auto-SSH Login Proxy.
Creating and Configuring HANA Targets
The Automation for SAP HANA automation pack includes a SAP HANA target template that can be used to create a target for the HANA environment. The SAP HANA target will hold the reference to all of the connections to HANA that are needed for automation.
Before you can reference the connections in the SAP HANA target, you must create the targets that will be referenced (Web target, Linux/Unix targets, Database target, SAP HANA target). After you create these targets, you create a unique SAP HANA target using the template and reference them.
This section guides you through creating the targets in the HANA environment, creating a SAP HANA target using the template, and then referencing the target using the Target Properties feature.
Creating SAP HANA Target
Before you can create or run processes, you must create the SAP HANA target on which the processes will run. This section guides you through creating SAP HANA target using the New SAP HANA Wizard.
After creating the SAP HANA target, you can reference the ABAP target, database target, Linux Administration Unix target, SAP Administration Unix Target, and web target.
Note To configure the references to targets, see Configuring References to Targets.
Step 1 On the Definitions workspace, right-click Targets and choose New > SAP HANA to open the SAP HANA Properties dialog box.
Step 2 In the Display name text field, enter a name for the SAP HANA target.
Step 3 Click OK to save the target and close the dialog box.
Step 4 In the Targets pane, right-click the newly created SAP HANA target and choose Enable to enable the target.
Creating SAP HANA Database Target
You must create a database target for the SAP HANA using the Generic Data Source (OLEDB) target type. Use the New Generic Data Source (OLEDB) Properties dialog box to create the database target.
Step 1 On the Definitions workspace, right-click Targets and choose New > Generic Data Source (OLEDB) to open the New Generic Data Source (OLEDB) Properties dialog box.
Step 2 On the General tab, specify the following information:
Field
|
Description
|
Display name
|
Name for the target. This is the name that will display in the Targets pane.
|
Type
|
Display only. Type of target.
|
Owner
|
User name of the owner of the target. This is typically the person who created the target.
|
Status
|
Display only. Status of the target.
|
Status information
|
Display only. Detailed information regarding the target status.
|
Organization
|
Name of the group or organization within the company that owns the target.
|
Description
|
Optional field to enter a description for the target.
|
Step 3 Click the Connection tab.
Note The Required Value 
icon displayed on a tab or page indicates that the field is required and is either missing a value or contains an invalid value.
Step 4 On the Connection tab, specify the following connection information for the target:
Field
|
Description
|
Hostname or Datasource
|
Name of the server or data source where the HANA database resides. Enter the information in the following format:
<server name>:port
Note Port number will be 3XX15, where XX is the HANA System Number.
|
Database Owner
|
Principal owner of the database.
|
Default time out for activities (seconds)
|
Indicates the length of time to wait before a command is complete
|
Runtime User
|
Choose the runtime user account that is used to connect to the data source from the drop-down list.
Note To view the properties for the selected runtime user, click the Properties  tool.
To create a new runtime user account, click New and then choose Runtime User. See Creating a Runtime User.
Note The HANA User account created for Process Orchestrator should have the following authorizations:
MONITORING HANA: This role authorizes the read monitoring activities.
SESSION ADMIN: This role adds system privileges to the accounts to support the corrective actions in the content.
These two authorizations cover all authorized content shipped in the automation pack for HANA.
|
Connection string
|
Check the check box and enter the DSN connection string to the data source.
For example:
DSN=DH1;
|
Step 5 Click the Permission tab.
Step 6 Click the Execute SQL command radio button.
Step 7 Click OK to close the dialog box and complete the procedure.
Creating a Runtime User
The Runtime User is the account that will be used to connect to the targets. You can create the runtime users for all targets prior to creating the targets, or when specifying the target connection information.
When creating runtime users, refer to the following information regarding the required user accounts for the HANA environment.
HANA Target
|
Runtime User Account Requirements
|
SAP HANA Database Target
|
The HANA User account created for Process Orchestrator should have the following authorizations:
MONITORING HANA: This role authorizes the read monitoring activities.
SESSION ADMIN: This role adds system privileges to the accounts to support the corrective actions in the content.
These two authorizations cover all authorized content shipped in the automation pack for HANA.
|
HANA Web Target
|
The runtime user for this target should be the HANA OS SIDADM user.
|
Unix/Linux Targets:
|
HANA.SAP Administration Unix Target
|
The runtime user for this target is the HANA OS SIDADM user)
|
HANA.Linux Administration Unix Target
|
The runtime user for this target is a Linux user with OS administration permissions.
|
Note For additional information on creating and managing runtime users, see the Cisco Process Orchestrator Reference Guide.
Step 1 Open the New Runtime User Properties dialog box using one of the following methods:
•In the Definitions workspace, right-click Runtime Users and choose New > Runtime User.
•On the target Connection tab, click New > Runtime User in the Runtime User field.
Step 2 On the General tab, specify the following information:
Note The Required Value 
icon displayed on a tab or page indicates that the field is required and is either missing a value or contains an invalid value.
Field
|
Description
|
Display name
|
Name for the user account. This field can be populated with the information specified in the Domain and User name text fields, or you can enter a different name to display for the user account.
|
User name
|
User name assigned to the user account that connects to the Remedy Server target.
|
Password
|
Check the check box and enter the password assigned to the user account.
Note No password verification is done for the simple (generic) runtime user.
|
Description
|
A description of the user account.
|
Step 3 Click OK to close the dialog box and complete the procedure.
Creating Web Targets
If you want to configure Process Orchestrator to monitor the Web targets in your HANA environment, you must create a Web target using the New Web Target Properties dialog box.
Step 1 On the Definitions workspace, right-click Targets and choose New > Web Target to open the New Web Target Properties dialog box.
Step 2 On the General tab, enter the information in the following text fields:
Field
|
Description
|
Display name
|
Name for the target. This is the name that will display in the Targets pane.
|
Type
|
Display only. Type of target.
|
Owner
|
User name of the owner of the target. This is typically the person who created the target.
|
Status
|
Display only. Status of the target.
|
Status information
|
Display only. Detailed information regarding the target status.
|
Organization
|
Name of the group or organization within the company that owns the target.
|
Description
|
Optional field to enter a description for the target.
|
Step 3 Click the Connection tab.
Note The Required Value 
icon displayed on a tab or page indicates that the field is required and is either missing a value or contains an invalid value.
Step 4 On the Connection tab, specify the following connection information for the target:
Field
|
Description
|
Base Url
|
Enter the appropriate target URL to use as a base for the execution.
For example:
http://<hanahostname>:5XX13/?wsdl
where XX=HANA System Number
|
Runtime User
|
Click one of the following radio buttons to indicate which runtime user account to use to connect to the target:
•No runtime user—Click this radio button to indicate that no runtime user is required to execute a process or activity against the target.
•Default runtime user—Click this radio button and then choose the default runtime user account that contains the credentials to connect to the target.
Note To view the properties for the selected runtime user, click the Properties  tool.
To create a new runtime user account, click New and then choose Runtime User. See Creating a Runtime User.
Note The runtime user for this target should be the HANA OS SIDADM user.
|
Ignore certificate errors
|
Check or uncheck the check box to indicate whether the target should ignore any certificate errors on the specified web site. If the check box is checked, all errors will be ignored.
|
Step 5 Click OK to close the dialog box and complete the procedure.
Creating Unix/Linux Target
If you want to monitor the SAP HANA Linux systems in your environment, you must create the Unix/Linux System targets. The Automation for SAP HANA content requires that two different Unix/Linux targets be created with different runtime user accounts:
•HANA.SAP Administration Unix Target—This target is used for SAP command line applications and uses the HANA OS SIDADM runtime user account.
•HANA.Linux Administration Unix Target—This target is used for LINUX command line administration applications and uses a Linux user with OS administration permissions as the runtime user account.
Note Review the Unix/Linux Target Prerequisites prior to creating the targets
Note For additional information on creating and managing Unix/Linux targets, see the Cisco Process Orchestrator User Guide.
Step 1 On the Definitions workspace, right-click Targets and choose New > Unix/Linux System to open the New Unix/Linux System Properties dialog box.
Step 2 On the General tab, specify the following information:
Field
|
Description
|
Display name
|
Enter a name for the Database target. This is the name that will display in the Targets pane.
|
Type
|
Display only. Type of target.
|
Owner
|
User name of the owner of the target. This is typically the person who created the target.
|
Status
|
Display only. Status of the target.
|
Status information
|
Display only. Detailed information regarding the target status.
|
Organization
|
Name of the group or organization within the company that owns the target.
|
Description
|
Optional field to enter a description for the target.
|
Enabled
|
Check or uncheck the check box to enable or disable the target. The check box is checked by default.
|
Step 3 Click the Connection tab.
Note The Required Value 
icon displayed on a tab or page indicates that the field is required and is either missing a value or contains an invalid value.
Step 4 On the Connection tab, specify the connection information to connect to the Unix/Linux server:
Field
|
Description
|
Host name
|
Host name or IP address of server.
|
Port
|
Port number used to access the server.
|
Prompt prefix
|
Enter the command prompt prefix that will be used by the device type configurations and expects when issuing commands and connecting to the device.
Adding a regex character, such as $, >, and #, at the end of a prompt in the Prompt Prefix field invalidates the command prompt prefix.
Regular expressions should be placed in the appropriate Terminal Interaction Pattern fields.
Example:
Unix system prompt prefix is defined by the user default login script. it usually contains username, node name or current directory name. If the user does not define anything, the prompt prefix is empty.
If you connect to the terminal, and the prompt is jsmith@TBD-SH03-IT ~$, enter the regular expression that will match the entire prefix (before #) using any of the following expressions:
•.*TBD-SH03-IT.*
•\[\w+@TBD-SH03-IT.*\]
|
Default runtime user
|
Choose the default runtime user account that contains the credentials to connect to the target from the drop-down list.
•HANA.SAP Administration Unix Target—Select the HANA OS SIDADM runtime user account.
•HANA.Linux Administration Unix Target—Select the Linux user with OS administration permissions runtime user account.
To view the properties for the selected runtime user, click the Properties  tool.
To create a new runtime user account, click New > [Runtime User Type] to create a new Runtime User account. See Creating a Runtime User.
|
Enable code injection prevention
|
Check this check box to enable the protection which prevents code that is injected to exploit the security vulnerability.
|
Maximum allowed concurrent sessions
|
Enter the maximum allowed open sessions to run concurrently (default value is 3).
If the user tries to open new session via Open Session activity, it will wait in a queue until there is a session available to open.
|
Step 5 Click the Authentication tab and specify the following information to indicate whether the target should allow authentication based on the host system:
Field
|
Description
|
Use host-based authentication
|
Check this check box to indicate that host-based authentication will be used with this target.
If this check box is unchecked, then host-based authentication will not be used.
|
Use the default host keys
|
This check box becomes enabled after the Use host-based authentication check box is checked.
Check this check box to indicate the host keys defined on the Terminal Adapter property page will be used for this target.
If this check box is unchecked, then the user will need to load the appropriate private key to be used to validate this target.
|
Private key
|
This box becomes enabled only if the Use the default host keys check box is unchecked.
To the right of the display-only field, click the Browse  tool to launch the Load Private Key dialog box and select a private key.
|
Step 6 Click the Advanced tab and specify the interaction patterns for the target.
Field
|
Description
|
Use patterns common for the following device
|
Click the radio button one of the pre-defined device targets from the drop-down list.
•Cisco IOS Device—Select this option to use the default pattern values used by the device during the completion of a session command.
•Unix/Linux System—Select this option to use the default pattern values indicated for a Unix or Linux system during the completion of a session command.
To view the properties for the selected device, click the Properties  tool.
To create a new device, click New > Expect Template to create a new expect template.
|
Customize patterns for this target
|
Select this radio button to enable the display-only sections in order to customize the default values for the selected device type.
|
Step 7 Click OK to close the dialog box and complete the procedure.
Configuring Auto-SSH Login Proxy
If you want to monitor all Linux hosts in your environment, you must configure an Auto-SSH login proxy.
Note If you choose not to set up auto login proxy, only the Process Orchestrator Linux system target will be monitored.
Note If the auto-ssh proxy connection fails due to the network changes made to the host Linux systems, rebuild the linux auto-ssh connection by deleting the /.ssh directory (which includes the id_rsa, id_rsa.pub, and known_hosts files for the auto-login). After deleting the directory, follow the procedure as mentioned from Step 2.
Step 1 Create a Linux user with permissions for the following linux commands:
•top
•iostat
•mpstat
•vmstat
•df
Step 2 Perform SSH login to the HANA Unix/Linux system target configured in Process Orchestrator using the Linux user account created in Step 1.
Step 3 Execute the command ssh-keygen -t rsa.
a. Enter passphrase as empty.
b. Note the file location of the key.
Step 4 Execute the command ssh-copy-id -i <file path to key> < remote host> and replace the <remote host> with the hostname for all HANA hosts in the instance.
Step 5 Test the remote connection by executing the command ssh <remote host> and confirm that you are no longer prompted for a password.
Step 6 Add the new Linux user name to the Process Orchestrator target property HANA Linux Configuration - HANA Linux Shell User.
Creating SAP System Target
If you want to use the Landscape Transformation (LT) processes, you must create the SAP System (ABAP) targets for the LT replication servers that replicate data into HANA. The SAP System Wizard is used to create these targets.
Note The SAP ABAP Adapter requires the dll files for SAP .NET Connector 3.0 for .NET 4.0 on x64 version 3.0.7.0 or higher. Before you can configure an SAP ABAP system target, these files must be installed on the Process Orchestrator server.
See the Intelligent Automation Guide for SAP 3.0 Installation Guide for instructions on installing these files, and additional information on configuring SAP HANA targets.
Step 1 On the Definitions workspace, right-click Targets and choose New > SAP System to open the New SAP System wizard.
Step 2 On the Welcome panel, click Next to display the System Setup panel.
The System Setup panel is used to specify the SAP system name, the type of system components to be configured, and the monitoring level for the SAP system.
Note The Required Value 
icon displayed on a tab or page indicates that the field is required and is either missing a value or contains an invalid value.
Note You can only create one target for each SAP system. However, for multi-tenant environments, you can create targets for different SAP systems with the same system ID (SID).
When using the same SID for different SAP systems, you must enter the organization for each SAP system so Process Orchestrator can differentiate the alerts and incidents for each system.
Step 3 Specify the following information about the SAP system:
Field
|
Description
|
Display name
|
Enter a name for the SAP system. This is the name that will display in the Targets pane.
|
System Components
|
ABAP application servers
|
Check this check box if the SAP system uses an ABAP connection to the application server.
|
Java application servers
|
Not applicable for LT replication servers.
|
SAP database
|
Check this check box if you want to configure the SAP database that is associated with the SAP system.
|
Monitor as production system
|
This check box is checked by default. Certain processes will run only on production systems. If you want to monitor the system as a non-production system (development or sandbox), uncheck the check box.
|
Organization
|
Enter the group or organization within the company that owns the target.
Note If you are configuring multiple SAP systems with the same SID, you must specify the organization for each SAP system target.
|
Step 4 Click Next to display the ABAP Connection panel.
Use the ABAP Connection panel to enter the connection information for the SAP system.
Note The system information entered on this panel must be unique.
Step 5 Specify the connection information for connecting to the SAP application server:
Field
|
Description
|
Connect using
|
Choose the connection method from the drop-down list. The fields that display on the panel depend on the connection method selected.
|
Application server
|
Choose this option to connect to the SAP system using the SAP application server connection information.
Specify the information in the following fields:
•Server name—Enter the name of the SAP application server.
•System number—Enter the SAP system number.
|
Logon group
|
Choose this option to establish a connection using a logon group, which contains a group of SAP system instances. When a user logs on to a logon group, the message server directs the users to the server of this group that currently has the lightest load.
Specify the information in the following fields:
•System ID—Enter the SAP system ID (SID).
•Message server—Enter the name of the server a user logs on to and that handles the communication between the application servers. For example, transport of update requests and lock requests.
•Group name—Enter the name of the Logon Group to be accessed. The name entered in this field is case-sensitive.
|
Router string (optional)
|
Enter the router string for accessing the SAP systems via SAPRouter. If you do not specify a router string, Process Orchestrator accesses the SAP system directly.
The router string must be formatted as:
/H/host01/H/host02/H/
where host01 and host02 are the SAP systems that you want to access through the SAPRouter.
|
Default runtime user
|
Choose the user account that contains the credentials to connect to the target from the drop-down list.
•To view the properties for the selected runtime user, click the Properties  tool.
•To create a new SAP User, click New > SAP User. See Creating an SAP User Account.
|
Step 6 Click Next to display the Server Availability panel.
The Server Availability panel is used to specify the SAP application servers that you want to monitor for availability and the ability to log in a user.
Step 7 Specify the following information:
Field
|
Description
|
Servers available for monitoring
|
All detected servers are checked by default. Verify that the check box next to each server that you want to monitor is checked.
|
Add
|
If a server is offline during configuration, it will not be displayed in the list of available servers. To manually add the server, click Add and enter the name of the server.
|
Remove
|
If you want to remove a server from the list, select the server and click Remove.
|
Select All
|
If the check boxes have been unchecked and you want all servers to be monitored, click Select All.
|
Deselect All
|
If all the check boxes are checked and you want to uncheck all of them, click Deselect All.
|
Step 8 Click Next.
If you are configuring the SAP database, the Database Connection panel displays. Otherwise, proceed to Step 12.
Note The fields that display on this panel depend on the type of database that is being configured.
Step 9 Choose the Database type from the drop-down list to display the fields for the specific type of database.
Step 10 Specify the information for the type of database that is being configured. The fields that display depend on the database type.
Field
|
Description
|
Server
|
Enter the name of the SAP application server where the database resides.
|
Hostname or data source
|
Name of the host server or data source for the Oracle or Generic database.
|
SID
|
System ID for the server where the Oracle database resides.
|
Database name
|
Enter the name of the SAP database that is associated with the SAP system.
|
Database owner
|
Enter the name of the user that owns the rights to the database.
|
Database source
|
Enter the Data source to connect to the database.
|
Port Number
|
Enter the Port number used to connect to the database.
|
Default timeout for activities (seconds)
|
Enter the number of seconds before the activity times out. The default timeout period is 120 seconds.
|
Default runtime user
|
Choose the user account that contains the credentials to connect to the database from the drop-down list.
•To view the properties for the selected runtime user, click the Properties  tool.
•To create a new runtime user, click New > Runtime User. See Creating a Runtime User.
|
Connection string
|
If the database has a custom connection string label appended to the name, check the check box and modify the string in the text field.
|
Step 11 Click Next.
Step 12 On the Completing the New SAP System Wizard, verify that the information is correct and click Finish to complete the procedure.
Creating an SAP User Account
The SAP User is the account that will be used to connect to an SAP ABAP application server or SAP system target.
Step 1 In the Definitions workspace, right-click Runtime Users and choose New > SAP User to open the New SAP User Properties dialog box.
Note The Required Value 
icon displayed on a tab or page indicates that the field is required and is either missing a value or contains an invalid value.
Step 2 On the General tab, specify the following information:
Field
|
Description
|
Display name
|
Name for the user account.
|
User name
|
User name assigned to the SAP user account that connects to the SAP system or ABAP application server.
|
Password
|
Password assigned to the SAP user account that connects to the SAP system or ABAP application server.
|
Client
|
SAP client number assigned to the user account.
|
Description
|
A description of the user account.
|
Step 3 Click OK to close the dialog box.
Configuring References to Targets
You must now configure the SAP HANA target to reference the Web target, Unix target and Database target. Use the SAP HANA Target Properties feature to reference the targets.
Creating Reference to HANA ABAP Target
Use this procedure to reference the HANA ABAP target that was created in "Creating SAP System Target" section.
Step 1 On the Definitions workspace, click Targets.
Step 2 Right-click the SAP HANA target and choose Properties.
Step 3 On the [SAP HANA Target] Properties dialog box, click the HANA Connections tab.
Step 4 Click the Browse 
tool next to the value field.
Step 5 On the Select Target dialog box, select the SAP HANA ABAP target and click OK to add the system to the value field.
Step 6 Click OK to close the SAP HANA Target Properties dialog box.
Creating Reference to SAP HANA Database Target
Use this procedure to reference the SAP HANA Database target that was created in "Creating SAP HANA Database Target" section.
Step 1 On the Definitions workspace, click Targets.
Step 2 Right-click the SAP HANA target and choose Properties.
Step 3 On the [SAP HANA Target] Properties dialog box, click the HANA Connections tab.
Step 4 Click the Browse 
tool next to the value field.
Step 5 On the Select Target dialog box, select the HANA Database target and and click OK to add the system to the value field.
Note If you are configuring all the target references at one time, proceed to Step 6 in Creating Reference to SAP HANA Unix Target.
Step 6 Click OK to close the SAP HANA Target Properties dialog box.
Creating Reference to SAP HANA Web Target
Use this procedure to reference the Web target that was created in "Creating Web Targets" section.
Step 1 On the Definitions workspace, click Targets.
Step 2 Right-click the SAP HANA target and choose Properties.
Step 3 On the [SAP HANA Target] Properties dialog box, click the HANA Connections tab.
Step 4 Click the Browse 
tool next to the value field.
Step 5 On the Select Target dialog box, select the HANA Web target and and click OK to add the system to the value field.
Step 6 Click OK to close the SAP HANA Target Properties dialog box.
Creating Reference to SAP HANA Unix Target
Use this procedure to reference the Unix target that was created in "Creating Unix/Linux Target" section.
Step 1 On the Definitions workspace, click Targets.
Step 2 Right-click the SAP HANA target and choose Properties.
Step 3 On the [SAP HANA Target] Properties dialog box, click the HANA Connections tab.
Step 4 Click the Browse 
tool next to the Linux Administration Unix Target value field.
Step 5 On the Select Target dialog box, select the Linux Administration Unix Target and click OK to add the system to the value field.
Step 6 To select the SAP Administration Unix target, click the Browse 
tool next to the SAP Administration Unix Target value field.
Step 7 On the Select Target dialog box, select the SAP Administration Unix target and click OK to add the target to the value field.
Step 8 Click OK to close the SAP HANA Target Properties dialog box.
Managing Target Properties
The HANA processes use target properties to specify the values to override certain target properties. This section provides information on configuring the target properties that ship with the Automation for SAP HANA automation pack.
Accessing Target Properties
The target properties that ship with the Automation for SAP HANA automation pack can be accessed from the Definitions—Target Properties view.
Note If the Target Properties view is hidden, go to Tools > Options. On the Options dialog box, click the Windows and Layout tab and select the Display target properties definitions node check box.
Step 1 On the Console, select the Definitions workspace and click Target Properties in the navigation pane. By default, all the properties display in the Target Properties pane.
The following information about the target properties displays by default:
Column
|
Description
|
Display Name
|
Name of the target property.
|
Description
|
Text description of the target property.
|
Value
|
Value assigned to the target property.
|
Data Type
|
Type of value being used for the target property (Boolean, Encrypted String, Identity, Numeric, String, Table).
|
Automation Pack
|
Name of the automation pack that provides the target property.
|
Customizable
|
Indicates the customization setting for the target property in the automation pack.
|
Target Types
|
Indicates the targets associated with the target property.
|
Last Modified Time
|
Date and time the variable was last modified.
|
Last Modified By
|
Name of the user who last modified the target property.
|
Id
|
Unique ID of the target property.
|
Owner
|
User name of the owner of the target property. This is typically the person who created the target property.
|
Created Time
|
Date and time the target property was created.
|
Created By
|
User name of the person who created the target property.
|
Step 2 Click the Filter by link and choose Automation Pack > Automation for SAP HANA to filter for only the target properties that ship with the specific automation pack.
Configuring Target Properties
You use the Target Properties dialog box to view or modify the target property. You access the properties from the Definitions—Target Properties view.
The following section provides information on configuring target properties that ship with the Automation for SAP HANA automation pack.
Step 1 On the Target Properties pane, right-click [Target Property] and choose Properties.
Step 2 On the General tab, review the information in the Description field to determine the values that need to be specified for the target property.
Step 3 Click the Value tab to view or modify the default value for all targets.
Note The tab in the second position will depend on the variable type. See the Cisco Process Orchestrator Reference Guide for instructions on configuring the different types of target properties.
Step 4 Click in the cell to specify the default value or change the default value for all targets.
Step 5 If you want to specify different values to be used on specific targets, click the Target Values tab to specify the values to override the default values and the targets on which to use the overrides.
Step 6 Click New to add a new target override.
Step 7 On the Target Property Value dialog box, click one of the following radio buttons to indicate which target(s) will use the override value:
•Set the value for a single target—Click this radio button to specify only one target that will use the override value.
•Set the same value for multiple targets—Click this radio button to specify multiple targets that will use the override value.
Step 8 Click the Browse 
icon to open the Select Target dialog box.
Step 9 Select the target(s) in the list and click OK.
Step 10 In the Value area, click in the cell to specify the override values to be used for the specified targets and click OK.
The target override displays on the Target Values tab.
Step 11 Click OK to close the dialog box and save your changes.
Note The Target Types tab is only available if you have explicit rights to the object. See the Cisco Process Orchestrator Reference Guide for information on using this property page.
Using Task Rules for Assignments and Notifications
Task rules are used to manage task assignments and notifications for tasks, such as incidents and alerts, that are generated from processes. When you import the Core Automation for SAP automation pack, you are prompted to specify the default user or group who should be assigned SAP incidents. By default, this person will receive all assignments unless task rules are created to specify alternate users or groups for specific tasks.
This section guides your through configuring the task rule that ships with the Core Automation for SAP automation pack and provides instructions for creating and managing task rules.
Note If you do not want to create task rules for email notifications, you can use the default notification based on assignment processes that ship with the Core automation pack. These processes are disabled by default and must be enabled if you want notifications to be sent (see Enabling Notification Based on Assignment Processes).
Accessing Task Rules View
The task rule that ships with the Core Automation for SAP automation pack can be accessed from the Definitions—Task Rules view.
Step 1 On the Console, select the Definitions workspace and click Task Rules in the navigation pane. By default, all the rules display in the Task Rules pane.
Step 2 Click the Filter by link and choose Automation Pack > [Automation Pack Name] to filter for only the task rules that ship with the specific automation pack.
The following information about the task rules displays by default:
Column
|
Description
|
Display Name
|
The name assigned to the task rule.
|
Enabled
|
Indicates whether the task rule is enabled (True) or disabled (False). A disabled task rule is unavailable for execution.
|
Type
|
Type of task.
|
Owner
|
User name of the person or group who assigned the task rule.
|
Last Modified Time
|
The date and time the task rule was last modified.
|
Last Modified By
|
The object or user name that last modified the task rule.
|
Id
|
Unique ID of the task rule.
|
Description
|
Brief description of the task rule.
|
Type Description
|
Brief overview of the task rule type.
|
Created Time
|
Time at which the task rule was created.
|
Created Date
|
Date the task rule was created.
|
Automation Pack
|
Name of the automation pack associated with the task rule.
|
Configuring Task Rules
Use the Task Rules view to configure the task rule that ships with the Core Automation for SAP automation pack.
SAP Default Assignment
The Core Automation for SAP automation pack ships with the Default SAP Assignment task rule, which is used to specify the default user or group who will be assigned all SAP-related incidents unless otherwise specified in task rules. This task rule can be configured during the import process on the Default Incidents Assignee Setup panel or from the Task Rules view in the Console.
Step 1 In the Definitions workspace, click Task Rules in the navigation pane to display the task rules in the results pane.
Step 2 Click the Filter by link and choose Automation Pack, and then choose Core Automation for SAP from the drop-down list to display the task rules that ship with the automation pack.
Step 3 Right-click the SAP Default Assignment task rule and choose Properties to open the SAP Default Assignment Properties dialog box.
Step 4 Click the Assign tab to specify the user or group that should receive assignments for incidents and alerts generated by the processes.
Step 5 On the Assign tab, click Add to open the Select Assignee to Add dialog box.
Step 6 On the Select Assignee to Add dialog box, specify the assignees using one of the following methods:
•Click the Reference 
tool to select the appropriate variable reference containing the assignee or list of assignees from the Insert Variable Reference dialog box.
•Click the Browse 
tool to launch the Select User or Group dialog box to add user to the list of assignees.
Step 7 Click OK to add the assignee to the task rule.
Step 8 When you have completed adding assignees to the task rule, click OK to close the dialog box.
Creating a New Task Rule
Use the Task Rules view to create a new task rule. The procedure is the same for all types of task rules with the exception of the task-specific tab (Assign, Notify, Update) for the type of task rule you are creating.
Note Only users with administrative rights can create task rules in Process Orchestrator.
You can create the following types of task rules:
Task Rules
|
Description
|
Assign Task Rule
|
Assigns users to a task.
|
Notify Task Rule
|
Notifies users that a task has been created.
|
Update Task Rule
|
Specifies the properties to be updated in a task.
|
Step 1 In the Definitions workspace, right-click Task Rules and choose New > [Task Rule Type] to open the New Rule Properties dialog box.
Step 2 On the General tab, enter the following information:
Field
|
Description
|
Display Name
|
Name of the task.
|
Type
|
Display only. Shows the type of object.
|
Trigger
|
Display only. Type of trigger associated with the task rule.
|
Owner
|
User name of the owner of the task rule. This is typically the person who created the task rule.
Click the Browse  tool to launch the Select User or Group dialog box to change the owner.
|
Description
|
A brief description of the task rule.
|
Enabled
|
The check box is checked by default to indicate that the task rule is available for execution.
Uncheck the check box to disable the task rule. If the check box is unchecked, the task rule is disabled and will be unavailable for execution.
|
Step 3 Click the Task Types tab to specify the types of tasks to be executed by the rule.
Step 4 Check the check box for the type of task that will execute the rule.
Task Type
|
Description
|
Alert
|
Alerts reflect potential problems that a user may want to investigate and possibly diagnose the problem.
|
Approval Request
|
Specifies the message and choices for the assignee who is approving the task.
|
Guided Operation
|
Details the steps a user takes to complete an assigned task.
|
Incident
|
Task requires an operator to take action in order to resolve an issue.
|
Input Request
|
Task requires input from an individual or group.
|
Review
|
Task assigns a document for review.
|
Step 5 Click the Conditions tab to specify the conditions of when the task rule action is to be taken based on an evaluation of the defined conditions.
Note The Required Value 
icon displayed on a tab or page indicates that the field is required and is either missing a value or contains an invalid value.
Step 6 On the Conditions tab, define the conditions that must be met for the rule to execute.
Defining a Basic Condition:
a. On the Basic page, click New to add a new property for the condition that must be met.
b. In the Property text field, click the Reference 
tool to choose a defined variable or reference an object on the Insert Variable Reference dialog box.
c. Choose the condition expression from the drop-down list.
d. Enter the condition description in the text box or click the Reference 
tool to choose a defined variable or reference an object on the Insert Variable Reference dialog box.
e. Click New to define additional properties, if necessary.
Defining an Advanced Condition:
a. Click the Advanced tab to define a specific type of condition (Compound, Prior Process Instance, Time, or Variable).
b. Click the link to modify the option for the condition equation.
Option
|
Description
|
AND condition (all conditions must be met)
|
Click this option if an action is to be taken only when all conditions in the list are true.
|
OR condition (one condition must be met)
|
Click this option if an action is to be taken when one condition in the list is true.
|
c. Click New and choose the type of condition from the drop-down list.
d. Specify the relevant information for the type of condition selected.
Note Click the Reference 
tool to choose a defined variable or reference an object on the Insert Variable Reference dialog box.
e. Click New to define additional properties, if necessary.
Step 7 Click the task rule specific tab (Assign, Notify, or Update) and specify the relevant information for the specific type of rule.
Assign Task Rule
If you are creating an Assign Task Rule, the Assign tab displays on the New Rule Properties dialog box.
On the Assign tab, specify the assignees for task rule.
Field
|
Description
|
Add
|
Click this button to launch the Select Assignee to Add dialog box to specify the assignees.
On the Select Assignee to Add dialog box, use one of the following methods to specify the assignee:
•Click the Reference  tool to select the appropriate variable reference containing the assignee or list of assignees from the Insert Variable Reference dialog box.
•Click the Browse  tool to launch the Select User or Group dialog box and add user to the list of assignees.
|
Edit
|
Select the appropriate assignee in the list and click this button to view or modify the assignee of the task rule.
|
Remove
|
Select the appropriate assignee and click this button to remove the assignee from the list.
|
Remove All
|
Click this button to remove all specified assignees from the list.
|
Notify Task Rule
If you are creating a Notify Task Rule, the Notify tab displays on the New Rule Properties dialog box.
On the Notify tab, specify the recipients of the notification that the task rule has executed. You can add individual recipients or include a notification recipient list.
Field
|
Description
|
Add notification recipients
|
Displays list of users to be notified by the task rule.
•Add—Click this button to launch the Select Notification Recipient to Add dialog box to specify the recipients.
On the dialog box, enter the email address for the recipient or click the Reference  tool to select the appropriate variable reference containing the recipient or list of recipients from the Insert Variable Reference dialog box and then click OK.
•Edit—Select the appropriate recipient in the list and click this button to view or modify the recipient of the task rule.
•Remove—Select the appropriate recipient in the list and click this button to remove the recipient from the list.
•Remove All—Click this button to remove all specified recipients from the list.
|
Add notification recipient list
|
Click the Reference  tool to select the appropriate variable reference containing list of recipients from the Insert Variable Reference dialog box.
|
Update Task Rule
If you are creating an Update Task Rule, the Update tab displays on the New Rule Properties dialog box.
On the Update tab, specify the properties to be updated after the task rule has executed.
Field
|
Description
|
Add
|
Click this button to add a new property to the Properties to update area.
|
Remove
|
Click this button to remove the last property added to the Properties to update area.
|
Property
|
From the Property drop-down list, choose the item to update within the task. The properties displayed depend on the selected item.
|
List action
|
Choose the appropriate item from the drop-down list to determine which action to take with the selected property:
•Add Item—Adds item to task.
•Remove item—Removes item from task.
•Clear—Removes property value from task.
|
Value
|
Enter new value for the property.
|
Step 8 Click OK to save the task rule definition and close the dialog box.
Managing Task Rule Definitions
This section provides instructions on modifying task rules in the Definitions—Task Rule view. Only users with administrative rights can modify task rules in Process Orchestrator.
Note For additional information on managing task rules, see the Cisco Process Orchestrator Reference Guide.
Enabling a Task Rule
A task rule is enabled by default. If a task rule is manually disabled, the task rule must be enabled before it is available for execution.
On the Definitions—Task Rules view, select the task rule and then use one of the following methods to enable it:
•On the Results pane, right-click and choose Enable.
-or-
•On the Details pane, select Click here to enable.
The Enabled column on the Results pane changes to True. If necessary, click the Refresh 
tool to update the view.
Disabling a Task Rule
Disabling a task rule prevents the item from being available for execution. The disabled task rule is not removed from the list of task rules on the Definitions—Task Rules Results pane.
On the Definitions—Task Rule view, select the task rule and then use one of the following methods to disable it:
•On the Results pane, right-click and choose Disable.
-or-
•On the Details pane, select Click here to disable.
The Enabled column on the results pane changes to False. If necessary, click the Refresh 
tool to update the view.
Creating a Copy of a Task Rule
The copy option is used when the user wants to leverage an existing task rule to define a new task rule using existing properties.
Step 1 On the Definitions—Task Rules view, select the appropriate task rule, right-click and choose Copy.
Step 2 On the Results pane, right-click and choose Paste.
A copy of the defined task rule is pasted onto the Results pane.
Step 3 To rename the copied task rule or other properties, right-click and choose Properties.
Step 4 Modify the task rule name, as appropriate, and click OK to close the dialog box.
Sorting Task Rules
The task rules are executed according to the order they are listed on the Definitions—Task Rules view. You should sort the task rules based on the order in which you want them to execute.
Note All task rules will execute even if there is more than one task rule assigned for the same condition. For example, if you have two assignment rules for the same incident, both rules will be executed in the order listed in the Task Rules view.
On the Definitions—Task Rules view, select the task rule and use one of the following methods to move it to the desired position in the list:
•Drag and drop the task rule into the appropriate position in the list.
•On the Actions toolbar, click Move Up or Move Down.
•Click the Actions menu and choose Move Up or Move Down.
•Right-click and choose Move Up or Move Down.
The list of task rules are sorted according to the selected action.
Deleting a Task Rule
Use the Definitions—Task Rules view to delete task rules that are no longer used.
Step 1 On the Definitions—Task Rules view, select the task rule, right-click and choose Delete.
Step 2 On the Confirm Delete dialog box, click Yes to confirm the deletion.
Enabling Notification Based on Assignment Processes
If you want to have emails sent to whoever is assigned to a task but do not want to create notification task rules, you can enable the processes that ship with the Core automation pack that send emails based on assignment.
When these processes are enabled, the user or user group who was assigned to tasks will receive the email notification.
Step 1 In the Definitions workspace, click Processes.
Step 2 Click the Filter by link and choose Automation Pack > Core to filter for the processes that ship with the Core automation pack.
Step 3 Right-click the appropriate Notification Based on Assignment process and choose Enable.
The following processes are for notification based on assignment:
Process Name
|
Description
|
Default Alert Notification Based on Assignment
|
Sends email when an alert gets assigned.
|
Default Approval Request Notification Based on Assignment
|
Sends email when an approval request gets assigned.
|
Default Change Request Notification Based on Assignment
|
Sends email when an change requests gets assigned.
|
Default Guided Operation Request Notification Based on Assignment
|
Sends email when a guide operation request gets assigned.
|
Default Incident Notification Based on Assignment
|
Sends email when an incident gets assigned.
|
Default Input Request Notification Based on Assignment
|
Sends email when an input request gets assigned.
|
Default Review Request Notification Based on Assignment
|
Send email when a review request gets assigned.
|
Feedback