Process Automation Guide for BW and BWA Release 3.0 - Release 3.0 [Cisco Intelligent Automation for SAP]

Table Of Contents

Importing Automation Packs

Accessing the Automation Pack Import Wizard

Opening the Import Wizard After Running Setup Wizard

Opening the Import Wizard in Console

Importing the Core Automation for SAP BW, BOBJ and In-Memory Computing.tap

Importing the Common Activities.tap

Importing the Automation for SAP BW and BWA.tap

Importing ABAP Transport or Cisco Add-On

Importing the ABAP Transport Files On SAP Systems

Importing the Cisco Add-On On SAP Systems

Error Handling, Logging and Tracing for ABAP Add-on

Support desk management for ABAP Add-on

Installing TREX Script Files

Importing Automation Packs

The Cisco Process Orchestrator Installation Guide provides instructions for installing Cisco Process Orchestrator and the core components. During the initial installation of Cisco Process Orchestrator, you can choose to import the automation packs, or import them later from within the Console.

The SAP Automation Pack for Automation for SAP BW and BWA has a dependency on other automation packs so these must be imported prior to importing the Automation for SAP BW and BWA automation pack.

This chapter guides you through importing the automation packs, which contain the content for automating processes to manage and monitor your SAP environment. It contains the following sections:

•Accessing the Automation Pack Import Wizard

•Importing the Core Automation for SAP BW, BOBJ and In-Memory Computing.tap

•Importing the Common Activities.tap

•Importing the Automation for SAP BW and BWA.tap

•Importing ABAP Transport or Cisco Add-On

•Installing TREX Script Files

Note It is recommended that you review the system requirements and prerequisites before importing automation packs. See the Intelligent Automation for SAP 3.0 Installation Guide.

Accessing the Automation Pack Import Wizard

You use the Automation Pack Import Wizard to import the automation packs (tap files). You can either open the wizard immediately after installing Cisco Process Orchestrator or from within the Console.

Opening the Import Wizard After Running Setup Wizard

Step 1 After running the Setup wizard to install the product, ensure that the Launch automation pack import wizard now check box is checked before closing the wizard.

The Select Automation Packs dialog box displays the available automation packs. All automation packs are checked by default.

Step 2 Ensure that the following check boxes are checked and then click OK to launch the Automation Pack Import Wizard:

•Assessment for SAP BWA (dependency)

•Automation for SAP BW and BWA

•Common Activities (dependency)

•Core Automation for SAP (dependency)

•Core Automation for SAP BW, BOBJ and In-Memory Computing (dependency)

Note See the Cisco Process Orchestrator Cisco Process Automation Guide for Assessment for SAP BWA for instructions on importing the Core Automation for SAP and Assessment for SAP BWA automation packs.

Note See the Cisco Process Orchestrator Installation Guide for instructions on importing and configuring the Core components for the product.

Proceed to Importing the Core Automation for SAP BW, BOBJ and In-Memory Computing.tap.

Opening the Import Wizard in Console

You can open the Automation Pack Import Wizard from within the Console after installing the product. When importing automation packs from within the Console, you must re-open the Automation Pack Import Wizard for each automation pack that you are importing.

Because the Automation for SAP BW and BWA automation pack has dependencies on the Core Automation for SAP BW, BOBJ and In-Memory Computing automation pack, you must first import this automation pack.

Note The following instructions assume you have already imported the Core Automation for SAP and the Assessment for SAP BWA automation packs.

Step 1 In the Administration workspace on the Console, click Automation Packs in the navigation pane.

Step 2 Use one of the following methods to open the Automation Pack Import Wizard:

•In the navigation pane, right-click Automation Packs and choose Import.

•On the Menu bar, choose Actions > Import.

Step 3 On the Windows Open dialog box, select the Core Automation for SAP BW, BOBJ and In-Memory Computing.tap file and click Open to open the Automation Pack Import Wizard.

Proceed to Importing the Core Automation for SAP BW, BOBJ and In-Memory Computing.tap.

Importing the Core Automation for SAP BW, BOBJ and In-Memory Computing.tap

You must first import the Core Automation for SAP BW, BOBJ and In-Memory Computing automation pack (Core Automation for SAP BW, BOBJ and In-Memory Computing.tap). If you opened the Automation Pack Import Wizard from the Setup Completed panel, the wizard will guide you through importing each automation pack.

Step 1 On the Automation Pack Import Wizard Welcome panel, click Next.

Note If you do not want to display the Welcome panel the next time the wizard is opened, check the Do not show this page next time check box.

Step 2 On the General Information panel, review the information about the automation pack.

Step 3 If you want to disable all the processes that are imported with the automation pack, check the Disable all imported processes check box.

Note If you disable the imported processes, you will need to manually enable the processes in the Console before they can execute.

Step 4 Click Next to continue.

The Data Extraction panel is used to specify the destination where the BWA Script files will be extracted. The script files are used in the direct TREX monitoring processes and must be copied to the TREX server.

Note If you uncheck the BWA Scripts check box, the files will not be extracted.

Step 5 Accept the default location or click the Browse tool to specify a different location to extract the files and then click Next.

The Review Prerequisites panel displays the prerequisites for the automation pack being imported. The green check mark indicates that the prerequisite was found on the computer.

The red X indicates that the prerequisite was not found on the computer. When this occurs, the import process is stopped and cannot continue until all prerequisites have been met.

If all prerequisites are passed, the wizard automatically continues to the next panel.

Note If you opened the Automation Pack Import Wizard from the Setup Completed panel, the wizard displays the General Information panel for the next automation pack.

Step 6 After the objects have been imported, review the information on the Completing the Automation Pack Import Wizard panel to verify that it is correct and then click Close to exit the wizard.

Importing the Common Activities.tap

If you are importing the automation packs from within the Console, you must re-open the Automation Pack Import Wizard to import the Common Activities automation pack.

Step 1 Use one of the following methods to open the Import Automation Pack Wizard:

•In the navigation pane, right-click Automation Packs and choose Import.

•On the Menu bar, choose Actions > Import.

Step 2 On the Windows Open dialog box, select the Common Activities.tap file and click Open to launch the Automation Pack Import Wizard.

Step 3 On the Welcome panel, click Next.

Step 4 On the General Information panel, review the information about the automation pack.

Step 5 If you want to disable all the processes that are imported with the automation pack, check the Disable all imported processes check box.

Note If you disable the imported processes, you will need to manually enable the processes in the Console before they can execute.

Step 6 Click Next to continue.

If all prerequisites are passed, the wizard automatically continues to the next panel.

Step 7 After the objects have been imported, review the information on the Completing the Automation Pack Import Wizard panel to verify that it is correct and then click Close to exit the wizard.

Importing the Automation for SAP BW and BWA.tap

If you are importing the automation packs from within the Console, you must re-open the Automation Pack Import Wizard to import the Automation for SAP BW and BWA automation pack.

Step 1 Use one of the following methods to open the Import Automation Pack Wizard:

•In the navigation pane, right-click Automation Packs and choose Import.

•On the Menu bar, choose Actions > Import.

Step 2 On the Windows Open dialog box, select the Automation for SAP BW and BWA.tap file and click Open to launch the Automation Pack Import Wizard.

Step 3 On the Welcome panel, click Next.

Step 4 On the General Information panel, review the information about the automation pack.

Step 5 If you want to disable all the processes that are imported with the automation pack, check the Disable all imported processes check box.

Note If you disable the imported processes, you will need to manually enable the processes in the Console before they can execute.

Step 6 Click Next to continue.

The Data Extraction panel is used to specify the destination where the ABAP Transport files will be extracted. The ABAP Transport files must be installed on the SAP systems on which some remote function calls that are used in this automation pack will be executed.

Note If you uncheck the ABAP Transport check box, the files will not be extracted.

Step 7 Accept the default location or click the Browse tool to specify a different location to extract the files and then click Next.

If all prerequisites are passed, the wizard automatically continues to the next panel.

Step 8 After the objects have been imported, review the information on the Completing the Automation Pack Import Wizard panel to verify that it is correct and then click Close to exit the wizard.

Importing ABAP Transport or Cisco Add-On

The Automation for SAP BW and BWA automation pack contains processes that execute RFC calls on the SAP system targets. These RFCs require either the ABAP Transport files or the Cisco Add-On file to be installed on the SAP system targets where the RFCs will be used.

After you have imported the Automation for SAP BW and BWA automation pack, you must import one of the following on the SAP systems where the RFCs will be used:

•ABAP Transport Files (SAP 3.5, 7.0 and 7.1 systems)

•Cisco Add-On File (SAP 7.0 and 7.1 systems)

Importing the ABAP Transport Files On SAP Systems

You can use the ABAP Transport files that ship with the automation pack on SAP 3.5 and 7.0 systems.

Perform the following procedure to import the ABAP Transport files on all the SAP System targets where the RFCs will be used.

Step 1 Navigate to the location where the ABAP Transport data was extracted for the SAP version of the systems in your environment. The default location is:

C:\user\[username]\Documents\Cisco\Cisco Process Orchestrator\Extracted Data\ABAP Transports\SAP BW\Transports\

3.5

7.0

7.1

Step 2 Copy the files to the following locations on the SAP server:

•K files should be copied to usr\sap\trans\cofiles

•R files should be copied to usr\sap\trans\data

Step 3 Log onto the SAP system and run T-code STMS.

Step 4 Follow SAP procedures for performing the transport.

Importing the Cisco Add-On On SAP Systems

Perform the following procedure to import the Cisco add-on file on all SAP System targets where the RFCs will be used.

Step 1 Navigate to the location where the ABAP Transport data was extracted for the SAP version of the systems in your environment. The default location is:

C:\user\[username]\Documents\Cisco\Cisco Process Orchestrator\Extracted Data\ABAP Transports\SAP BW\Add-on\

7.0

7.1

Step 2 Copy the SAP Add-On Package file(s) to the following location on the SAP server:

usr\sap\trans\EPS\in

Step 3 Log onto client 000 of the SAP system using an administrator account (DDIC or SAP* are not valid accounts) and run the SAP transaction code SAINT.

Step 4 Follow the standard SAP procedures for performing an add-on product installation using SAINT.

Note To verify whether the add-on is on the SAP system, use the SAP menu path System > Status and review the software component versions for the Cisco software component add-on.

Error Handling, Logging and Tracing for ABAP Add-on

The ABAP Add-On contains API enabled ABAP function modules (RFC's) that are called by the Cisco Process Orchestrator application. This is performed in Process Orchestrator by defining an ABAP adapter step and specifying a method for the SAP Target system in a process. Process Orchestrator ABAP custom methods perform individual tasks such as updating RFC Destinations, configuring printers, and so on.

In the event the method encounters an error, such as attempting to modify an RFC destination that does not exist, an error result is returned to the Process Orchestrator process. This can then be modeled as an outcome to the activity, and then subsequent actions based on the error returned may be performed.

All RFC activity performed by Cisco Process Orchestrator may be traced through SAP Standard RFC tracing functionality. Refer to SAP online help for enabling the trace level for RFC communication on the SAP target system using SAP transaction SM59. The SAP methods that are called may either write log entries to the SAP System Log (SAP Transaction SM21) or to the Application log (SAP Transaction SLG1) depending on the SAP standard application functionality. For instance, the SAP Application log is updated during the BDLS process scenario as this part of the SAP standard application functionality.

Support desk management for ABAP Add-on

SAP Root Cause Analysis ABAP tools can be used to review the performance and execution of the RFC calls performed by the Process Orchestrator system. A read-only SAP Administrator user is used to review the functionality performed by the ABAP methods. The following roles are to be the basis for a composite role that can be adapted to the customer environment:

•SAP_BC_BASIS_MONITORING,

•SAP_BC_SEC_USER_DISPLAY,

•SAP_BC_BTC_DISPLAY,

•SAP_BC_MID_ALE_DISPLAY

Installing TREX Script Files

After you have completed importing the automation packs, you must install the script files to the TREX server. These script files are used in the direct TREX monitoring and corrective actions processes.

Note SAP BWA TREX Scripting is supported only on SAP BWA v7.20, Release 8 or later.

The script files are imported to the following location on the Process Orchestrator server by default:

Microsoft Windows Server 2003:

C:\Documents and Settings\local_user\My Documents\Cisco\Cisco Process Orchestrator\Extracted Data\BWA Scripts

Microsoft Windows Server 2008:

C:\Users\local_user\Documents\Cisco\Cisco Process Orchestrator\Extracted Data\BWA Scripts

Copy the BWA Scripts folder to the BWA host filesystem and run the install.sh command from the Bash shell to install the script files.

Note Both the install.sh and cisco_teo_python.tar files need to be copied to the server prior to running the install.sh command.

The script files are copied to the $DIR_INSTANCE\exe\python_support directory.

	Process Automation Guide for BW and BWA Release 3.0
	Release 3.0
Process Automation Guide for BW and BWA Release 3.0 Release 3.0 Release 3.0 Release 3.0 Release 3.0 Release 3.0 Release 3.0 Release 3.0	Download this chapter Release 3.0 Download the complete book Release 3.0 (PDF - 770 KB) Feedback Table Of Contents Importing Automation Packs Accessing the Automation Pack Import Wizard Opening the Import Wizard After Running Setup Wizard Opening the Import Wizard in Console Importing the Core Automation for SAP BW, BOBJ and In-Memory Computing.tap Importing the Common Activities.tap Importing the Automation for SAP BW and BWA.tap Importing ABAP Transport or Cisco Add-On Importing the ABAP Transport Files On SAP Systems Importing the Cisco Add-On On SAP Systems Error Handling, Logging and Tracing for ABAP Add-on Support desk management for ABAP Add-on Installing TREX Script Files Importing Automation Packs The Cisco Process Orchestrator Installation Guide provides instructions for installing Cisco Process Orchestrator and the core components. During the initial installation of Cisco Process Orchestrator, you can choose to import the automation packs, or import them later from within the Console. The SAP Automation Pack for Automation for SAP BW and BWA has a dependency on other automation packs so these must be imported prior to importing the Automation for SAP BW and BWA automation pack. This chapter guides you through importing the automation packs, which contain the content for automating processes to manage and monitor your SAP environment. It contains the following sections: •Accessing the Automation Pack Import Wizard •Importing the Core Automation for SAP BW, BOBJ and In-Memory Computing.tap •Importing the Common Activities.tap •Importing the Automation for SAP BW and BWA.tap •Importing ABAP Transport or Cisco Add-On •Installing TREX Script Files Note It is recommended that you review the system requirements and prerequisites before importing automation packs. See the Intelligent Automation for SAP 3.0 Installation Guide. Accessing the Automation Pack Import Wizard You use the Automation Pack Import Wizard to import the automation packs (tap files). You can either open the wizard immediately after installing Cisco Process Orchestrator or from within the Console. Opening the Import Wizard After Running Setup Wizard Step 1 After running the Setup wizard to install the product, ensure that the Launch automation pack import wizard now check box is checked before closing the wizard. The Select Automation Packs dialog box displays the available automation packs. All automation packs are checked by default. Step 2 Ensure that the following check boxes are checked and then click OK to launch the Automation Pack Import Wizard: •Assessment for SAP BWA (dependency) •Automation for SAP BW and BWA •Common Activities (dependency) •Core Automation for SAP (dependency) •Core Automation for SAP BW, BOBJ and In-Memory Computing (dependency) Note See the Cisco Process Orchestrator Cisco Process Automation Guide for Assessment for SAP BWA for instructions on importing the Core Automation for SAP and Assessment for SAP BWA automation packs. Note See the Cisco Process Orchestrator Installation Guide for instructions on importing and configuring the Core components for the product. Proceed to Importing the Core Automation for SAP BW, BOBJ and In-Memory Computing.tap. Opening the Import Wizard in Console You can open the Automation Pack Import Wizard from within the Console after installing the product. When importing automation packs from within the Console, you must re-open the Automation Pack Import Wizard for each automation pack that you are importing. Because the Automation for SAP BW and BWA automation pack has dependencies on the Core Automation for SAP BW, BOBJ and In-Memory Computing automation pack, you must first import this automation pack. Note The following instructions assume you have already imported the Core Automation for SAP and the Assessment for SAP BWA automation packs. Step 1 In the Administration workspace on the Console, click Automation Packs in the navigation pane. Step 2 Use one of the following methods to open the Automation Pack Import Wizard: •In the navigation pane, right-click Automation Packs and choose Import. •On the Menu bar, choose Actions > Import. Step 3 On the Windows Open dialog box, select the Core Automation for SAP BW, BOBJ and In-Memory Computing.tap file and click Open to open the Automation Pack Import Wizard. Proceed to Importing the Core Automation for SAP BW, BOBJ and In-Memory Computing.tap. Importing the Core Automation for SAP BW, BOBJ and In-Memory Computing.tap You must first import the Core Automation for SAP BW, BOBJ and In-Memory Computing automation pack (Core Automation for SAP BW, BOBJ and In-Memory Computing.tap). If you opened the Automation Pack Import Wizard from the Setup Completed panel, the wizard will guide you through importing each automation pack. Step 1 On the Automation Pack Import Wizard Welcome panel, click Next. Note If you do not want to display the Welcome panel the next time the wizard is opened, check the Do not show this page next time check box. Step 2 On the General Information panel, review the information about the automation pack. Step 3 If you want to disable all the processes that are imported with the automation pack, check the Disable all imported processes check box. Note If you disable the imported processes, you will need to manually enable the processes in the Console before they can execute. Step 4 Click Next to continue. The Data Extraction panel is used to specify the destination where the BWA Script files will be extracted. The script files are used in the direct TREX monitoring processes and must be copied to the TREX server. Note If you uncheck the BWA Scripts check box, the files will not be extracted. Step 5 Accept the default location or click the Browse tool to specify a different location to extract the files and then click Next. The Review Prerequisites panel displays the prerequisites for the automation pack being imported. The green check mark indicates that the prerequisite was found on the computer. The red X indicates that the prerequisite was not found on the computer. When this occurs, the import process is stopped and cannot continue until all prerequisites have been met. If all prerequisites are passed, the wizard automatically continues to the next panel. Note If you opened the Automation Pack Import Wizard from the Setup Completed panel, the wizard displays the General Information panel for the next automation pack. Step 6 After the objects have been imported, review the information on the Completing the Automation Pack Import Wizard panel to verify that it is correct and then click Close to exit the wizard. Importing the Common Activities.tap If you are importing the automation packs from within the Console, you must re-open the Automation Pack Import Wizard to import the Common Activities automation pack. Step 1 Use one of the following methods to open the Import Automation Pack Wizard: •In the navigation pane, right-click Automation Packs and choose Import. •On the Menu bar, choose Actions > Import. Step 2 On the Windows Open dialog box, select the Common Activities.tap file and click Open to launch the Automation Pack Import Wizard. Step 3 On the Welcome panel, click Next. Step 4 On the General Information panel, review the information about the automation pack. Step 5 If you want to disable all the processes that are imported with the automation pack, check the Disable all imported processes check box. Note If you disable the imported processes, you will need to manually enable the processes in the Console before they can execute. Step 6 Click Next to continue. If all prerequisites are passed, the wizard automatically continues to the next panel. Step 7 After the objects have been imported, review the information on the Completing the Automation Pack Import Wizard panel to verify that it is correct and then click Close to exit the wizard. Importing the Automation for SAP BW and BWA.tap If you are importing the automation packs from within the Console, you must re-open the Automation Pack Import Wizard to import the Automation for SAP BW and BWA automation pack. Step 1 Use one of the following methods to open the Import Automation Pack Wizard: •In the navigation pane, right-click Automation Packs and choose Import. •On the Menu bar, choose Actions > Import. Step 2 On the Windows Open dialog box, select the Automation for SAP BW and BWA.tap file and click Open to launch the Automation Pack Import Wizard. Step 3 On the Welcome panel, click Next. Step 4 On the General Information panel, review the information about the automation pack. Step 5 If you want to disable all the processes that are imported with the automation pack, check the Disable all imported processes check box. Note If you disable the imported processes, you will need to manually enable the processes in the Console before they can execute. Step 6 Click Next to continue. The Data Extraction panel is used to specify the destination where the ABAP Transport files will be extracted. The ABAP Transport files must be installed on the SAP systems on which some remote function calls that are used in this automation pack will be executed. Note If you uncheck the ABAP Transport check box, the files will not be extracted. Step 7 Accept the default location or click the Browse tool to specify a different location to extract the files and then click Next. If all prerequisites are passed, the wizard automatically continues to the next panel. Step 8 After the objects have been imported, review the information on the Completing the Automation Pack Import Wizard panel to verify that it is correct and then click Close to exit the wizard. Importing ABAP Transport or Cisco Add-On The Automation for SAP BW and BWA automation pack contains processes that execute RFC calls on the SAP system targets. These RFCs require either the ABAP Transport files or the Cisco Add-On file to be installed on the SAP system targets where the RFCs will be used. After you have imported the Automation for SAP BW and BWA automation pack, you must import one of the following on the SAP systems where the RFCs will be used: •ABAP Transport Files (SAP 3.5, 7.0 and 7.1 systems) •Cisco Add-On File (SAP 7.0 and 7.1 systems) Importing the ABAP Transport Files On SAP Systems You can use the ABAP Transport files that ship with the automation pack on SAP 3.5 and 7.0 systems. Perform the following procedure to import the ABAP Transport files on all the SAP System targets where the RFCs will be used. Step 1 Navigate to the location where the ABAP Transport data was extracted for the SAP version of the systems in your environment. The default location is: C:\user\[username]\Documents\Cisco\Cisco Process Orchestrator\Extracted Data\ABAP Transports\SAP BW\Transports\ 3.5 7.0 7.1 Step 2 Copy the files to the following locations on the SAP server: •K files should be copied to usr\sap\trans\cofiles •R files should be copied to usr\sap\trans\data Step 3 Log onto the SAP system and run T-code STMS. Step 4 Follow SAP procedures for performing the transport. Importing the Cisco Add-On On SAP Systems Perform the following procedure to import the Cisco add-on file on all SAP System targets where the RFCs will be used. Step 1 Navigate to the location where the ABAP Transport data was extracted for the SAP version of the systems in your environment. The default location is: C:\user\[username]\Documents\Cisco\Cisco Process Orchestrator\Extracted Data\ABAP Transports\SAP BW\Add-on\ 7.0 7.1 Step 2 Copy the SAP Add-On Package file(s) to the following location on the SAP server: usr\sap\trans\EPS\in Step 3 Log onto client 000 of the SAP system using an administrator account (DDIC or SAP* are not valid accounts) and run the SAP transaction code SAINT. Step 4 Follow the standard SAP procedures for performing an add-on product installation using SAINT. Note To verify whether the add-on is on the SAP system, use the SAP menu path System > Status and review the software component versions for the Cisco software component add-on. Error Handling, Logging and Tracing for ABAP Add-on The ABAP Add-On contains API enabled ABAP function modules (RFC's) that are called by the Cisco Process Orchestrator application. This is performed in Process Orchestrator by defining an ABAP adapter step and specifying a method for the SAP Target system in a process. Process Orchestrator ABAP custom methods perform individual tasks such as updating RFC Destinations, configuring printers, and so on. In the event the method encounters an error, such as attempting to modify an RFC destination that does not exist, an error result is returned to the Process Orchestrator process. This can then be modeled as an outcome to the activity, and then subsequent actions based on the error returned may be performed. All RFC activity performed by Cisco Process Orchestrator may be traced through SAP Standard RFC tracing functionality. Refer to SAP online help for enabling the trace level for RFC communication on the SAP target system using SAP transaction SM59. The SAP methods that are called may either write log entries to the SAP System Log (SAP Transaction SM21) or to the Application log (SAP Transaction SLG1) depending on the SAP standard application functionality. For instance, the SAP Application log is updated during the BDLS process scenario as this part of the SAP standard application functionality. Support desk management for ABAP Add-on SAP Root Cause Analysis ABAP tools can be used to review the performance and execution of the RFC calls performed by the Process Orchestrator system. A read-only SAP Administrator user is used to review the functionality performed by the ABAP methods. The following roles are to be the basis for a composite role that can be adapted to the customer environment: •SAP_BC_BASIS_MONITORING, •SAP_BC_SEC_USER_DISPLAY, •SAP_BC_BTC_DISPLAY, •SAP_BC_MID_ALE_DISPLAY Installing TREX Script Files After you have completed importing the automation packs, you must install the script files to the TREX server. These script files are used in the direct TREX monitoring and corrective actions processes. Note SAP BWA TREX Scripting is supported only on SAP BWA v7.20, Release 8 or later. The script files are imported to the following location on the Process Orchestrator server by default: Microsoft Windows Server 2003: C:\Documents and Settings\local_user\My Documents\Cisco\Cisco Process Orchestrator\Extracted Data\BWA Scripts Microsoft Windows Server 2008: C:\Users\local_user\Documents\Cisco\Cisco Process Orchestrator\Extracted Data\BWA Scripts Copy the BWA Scripts folder to the BWA host filesystem and run the install.sh command from the Bash shell to install the script files. Note Both the install.sh and cisco_teo_python.tar files need to be copied to the server prior to running the install.sh command. The script files are copied to the $DIR_INSTANCE\exe\python_support directory.
	Terms & Conditions \| Privacy Statement \| Cookie Policy \| Trademarks