Table Of Contents
Planning and Preparing Environment
Supported SAP Versions
Required SAP Components
SAP ABAP and Solution Manager Requirements
Installing SAP .NET Connector Files
SAP JAVA Requirements
Installing SAP Java Library Files
Configuring SAP v7.1x JARM Tracing Service
SAP HANA Requirements
Installing SAP HANA Database Client for Windows
Configuring Windows Host File and Path
Creating Data Source for ODBC System DSN
Unix/Linux Target Prerequisites
Reporting Database Sizing Requirements for SAP Environment
SAP User Account Recommendations
SAP User Account
SAP Support User Account
SAP System Information
SAP ABAP System and Solution Manager Information
SAP Java System Information
SAP HANA System Information
SAP BOBJ Information
SAP Database Access Rights
Microsoft SQL Server Windows Authentication
SQL Server SQL Authentication
Process Database Logon Script
Reporting Database Authentication Script
Oracle Database Access Rights
DB2 Database Access Rights
Registering Process Orchestrator with SAP System Landscape Directory
Pre-Registration Requirements
Manually Registering Product
Importing Product Information
Transferring Product Information via XML
Configuring SAP Multi-Tenant Support in Web Console
Error Handling, Logging and Tracing for Cisco Add-On
Error Handling
SAP Standard RFC Tracing
Log Entries
Support Desk Management for Cisco Add-On
Planning and Preparing Environment
This chapter provides information on the requirements and recommendations for installing and using the Intelligent Automation for SAP solution. The information in this chapter assumes that Process Orchestrator and the Core automation pack are already installed.
It includes the following sections:
•
Supported SAP Versions
•Required SAP Components
•Reporting Database Sizing Requirements for SAP Environment
•SAP User Account Recommendations
•SAP System Information
•SAP Database Access Rights
•Registering Process Orchestrator with SAP System Landscape Directory
•Configuring SAP Multi-Tenant Support in Web Console
•Error Handling, Logging and Tracing for Cisco Add-On
•Support Desk Management for Cisco Add-On
Note It is recommended that you verify your environment meets the minimum hardware and software requirements. See the Cisco Process Orchestrator Installation and Administration Guide for information on system requirements.
Supported SAP Versions
The following versions of SAP are supported by Process Orchestrator.
Table 2-1 Supported Versions of SAP
SAP Application
|
Supported Versions
|
SAP R/3
|
•4.7
•6.10 (Support Package 6)
•6.20 (including 4.7)
•6.30
•6.40
•7.0
•7.10
•7.11
•7.20
•7.30
Note To monitor Java portals on SAP v7.1x application servers, you must configure the JARM tracing service with custom values. See "Registering Process Orchestrator with SAP System Landscape Directory" section.
Note SAP Task automation for ABAP add-on and add-on upgrades are provided for extended capabilities.
|
SAP BW
|
•3.0
•3.1
•3.5
•7.0
•7.0 SP13
•7.01 SP8
•7.30
Note RFCs that depend on the Process Orchestrator ABAP Transport files are only supported on SAP BW 7.00 SP16 or later.
BW remote function calls using the Cisco Add-on are supported on BW 7.01 SP8 or higher and BW 7.3.
|
SAP BWA
|
•7.2 (Rev. 8 or later)—for BWA TREX Scripting
|
SAP Solution Manager
|
•SAP Solution Manager 7.1 SP05 or later
–The SAP Solution Manager 7.1 system and basic setup must be completed.
–Managed Objects must be configured.
•SAP ABAP/Netweaver 7.02 SP10
|
Note It is recommended that you install the latest kernel patch for the installed SAP version.
|
Note It is recommended that Process Orchestrator be installed within a secure environment. The communication mechanisms that are used by Process Orchestrator are not currently configured to enable SAP Secure Network Communications (SAP SNC) or secure HTTP.
The communication that occurs between Process Orchestrator and the SAP system targets use one of the following technologies:
•SAP .NET Connector for RFC
•SAP JMX
Required SAP Components
This section provides information about the required SAP components to enable full functionality in Process Orchestrator. Refer to the appropriate section based on your SAP environment.
SAP ABAP and Solution Manager Requirements
SAP .NET Connector 3.0 for .NET 4.0 on x64 version 3.0.7.0 or higher must be installed and the following dll files copied to the Process Orchestrator server prior to configuring SAP ABAP system or SAP Solution Manager targets:
•sapnco.dll
•sapnco_utils.dll
See "Installing SAP .NET Connector Files" for instructions on installing these files.
Installing SAP .NET Connector Files
Perform the following steps to install the required SAP .NET Connector files.
Note SAP .NET Connector 3.0 for .NET 4.0 on x64 v3.0.7.0 or higher can be downloaded from the SAP web site.
Step 1 From the SAP .NET Connector 3.0 for .NET 4.0 on x64 program files folder on the server where NCo is installed, locate the following files:
•sapnco.dll
•sapnco_utils.dll
Step 2 Copy the files to the following folder on the Process Orchestrator server:
<Install drive>:\Program Files\Cisco\Process Orchestrator\Adapters
Step 3 Restart the Cisco Process Orchestrator Server service.
SAP JAVA Requirements
The following requirements must be met prior to installing SAP Java Application Server targets.
•SAP Java Library files must be installed on the Process Orchestrator server prior to configuring SAP Java Application Server targets. You must have access to one of the following SAP Installation CDs to install the files:
–SAP NetWeaver 7.0 SR3
Java based Software Components
Number 51033513
–SAP NetWeaver CE 7.1 SR5
Java Components
Documentation
Developer Workplace
Number 51033845
See "Installing SAP Java Library Files" for instructions on installing the files.
•JARM tracing service must be configured on SAP v7.1x systems if you want to monitor iView response time. See "Configuring SAP v7.1x JARM Tracing Service".
Installing SAP Java Library Files
Perform the following steps to install the required SAP Java Library files.
Step 1 Stop the Cisco Process Orchestrator Server service.
Step 2 Go to Start > All Programs > Cisco > Cisco Process Orchestrator > SAP Libraries Install Wizard.
Step 3 On the Welcome panel of the wizard, click Next to run the checker and determine whether the JMX libraries have been installed.
The results of the checker display on the SAP Dependency Libraries Checker panel.
Step 4 Click Next to continue.
If the required files cannot be found, the SAP JMX Adapter Dependency Libraries Installer panel displays. Use this panel to specify the version of SAP that is installed and the location of the SAP installation files.
Step 5 Check the check box next to the version of SAP that is installed (you can check both versions), and then enter the path or click the Browse tool to navigate to the location of the SAP installation files.
Step 6 Click Next to install the files.
Step 7 On the Finishing the SAP Libraries Install Wizard panel, verify that the files were successfully installed and then click Close to exit the installer.
Step 8 Restart the Process Orchestrator Server service to complete the procedure.
Configuring SAP v7.1x JARM Tracing Service
Perform the following steps to configure the JARM tracing service on the SAP application server.
Launch the SAP ConfigTool
Perform the following steps to launch the SAP ConfigTool.
Step 1 On the SAP server, navigate to the following directory:
usr\SAP\[SID]\J01\j2ee\configtool
Step 2 Use one of the following methods to open the ConfigTool, depending on your operating system:
•In Windows, double-click the configtool.bat file.
•In UNIX, double-click the configtool.sh file.
Step 3 On the Connection Settings dialog box, click Yes to use the default DB settings.
The AS Java ConfigTool opens. Proceed to "Configuring Apptracing Properties".
Configuring Apptracing Properties
Perform the following steps to configure the apptracing and monitor settings with custom values.
Step 1 In the navigation pane, navigate to cluster-data > template > instance > services and click apptracing.
Step 2 In the results pane, change the following properties by selecting the property name, entering the new value in the Custom value field and clicking Set.
•jarm/switch—On
•jarm/maxreqcomphigh—2600
•jarm/maxreqcomplow—2500
Step 3 In the navigation pane, navigate to cluster-data > template > instance > services and click monitor.
Step 4 In the results pane, click jarm_history.started.
Step 5 In the Custom value field, enter false and click Set.
Step 6 Click Save on the toolbar.
The Logs dialog box displays showing the changes that have been completed.
Step 7 Click OK and close the ConfigTool.
Step 8 Stop and restart the application server to complete the procedure.
SAP HANA Requirements
The following prerequisites must be met prior to configuring SAP HANA targets in Process Orchestrator.
Table 2-2 SAP HANA Requirements
Requirement
|
Description
|
SAP HANA Database Client
|
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.
See Installing SAP HANA Database Client for Windows.
|
Configure Windows Host File
|
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.
See Configuring Windows Host File and Path.
|
Create Data Source
|
Before you can create HANA system targets, you must add the ODBC system data source used to connect to the HANA data provider from Process Orchestrator.
See Creating Data Source for ODBC System DSN.
|
Unix/Linux Target Prerequisites
|
The following prerequisites must be met for Unix/Linux system 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 after creating the HANA Linux target in Process Orchestrator. See Configuring Auto-SSH Login Proxy.
|
Installing 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.
Configuring 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 Cisco Prime 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 (use the format suse-hana.xxx.domain.local) and press Enter on the keyboard.
Step 4 Click File > Save to save the file and complete the procedure.
Creating Data Source for ODBC System DSN
Before you can create HANA system 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 system 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.
Reporting Database Sizing Requirements for SAP Environment
The formula for calculating the disk space for the Process Orchestrator Reporting database for an SAP environment is based on the following record statistics.
Note See the Cisco Process Orchestrator Installation and Administration Guide for disk space sizing formulas for environments other than SAP.
Table 2-3 Calculating Disk Space Formula for Process Orchestrator Reporting Database for SAP Environment
| |
Incident
|
Alert
|
Event
|
Metric
|
Process Audit
|
Task Audit
|
Record Size
|
2 KB
|
2 KB
|
1.5 KB
|
0.06 KB
|
0.2 KB
|
0.15 KB
|
Record Rate (estimate)
|
30/day per system
|
200/day per system
|
1/min per application server
|
0.2 records/sec per application server
|
3000/day per system
|
3x number of alerts
|
Daily Total
|
60 KB per system
|
400 KB per system
|
2160 KB per application server
|
1036 KB per application server
|
600 KB per system
|
90 KB per system
|
Retention (months)
|
6
|
6
|
6
|
12
|
6
|
6
|
The disk space requirements formula as shown in the following table is based on an environment that includes 1 SAP system with 5 application servers:
Table 2-4 Calculating Disk Space Formula
Data
|
Formula
|
Incident Size
|
60 KB/system/day x 1 system x 6 months = 10 MB
|
Alert Size
|
400 KB/system/day x 1 system x 6 months = 72 MB
|
Event
|
2160 KB/application server/day x 5 servers x 6 months = 1920 MB
|
Metrics
|
1036 KB/application server/day x 5 servers x 6 months = 1864 MB
|
Process Audit
|
600 KB/system/day x 1 system x 6 months = 108 MB
|
Task Audit
|
90 KB/system/day x 1 system x 6 months = 16 MB
|
Total Size
|
10 MB + 72 MB + 1920 MB + 1864 MB + 108 MB + 108 MB + 16 MB = 3.99 GB
|
SAP User Account Recommendations
This section provides recommendations for creating SAP user accounts.
SAP User Account
An SAP user account must be created for Process Orchestrator to log into SAP. Cisco recommends the user account is created with the following settings:
Recommendation
|
Description
|
Required Authorization
|
S_A.System profile
|
Account Type
|
System, Service, or Communication user type is recommended
|
Language Setting
|
English, German. The Process Orchestrator server regional setting should match the language setting in SAP.
|
SAP Support User Account
The Process Orchestrator Auditor Role, which has read-only permissions, can be used for SAP support users to perform troubleshooting and maintenance tasks in Process Orchestrator. The default assignment of the Process Orchestrator Auditor Role is for themembers of the Process Orchestrator Auditors group in Windows Computer Management.
Create the support user account and add it to the Process Orchestrator Auditors group in Windows Computer Management. Alternately, the created account may be directly assigned to the Process Orchestrator Auditor Role in Process Orchestrator.
For information on assigning support users to the Process Orchestrator Auditors security group, refer to the "Configuring Process Orchestrator Security" chapter in the Cisco Process Orchestrator Installation and Administration Guide.
SAP System Information
It is recommended that the following SAP system information be gathered prior to installing the SAP automation packs. This information will be required to create the SAP targets.
SAP ABAP System and Solution Manager Information
The following information is needed to create SAP ABAP System and Solution Manager targets.
Connection Information
|
Description
|
Display Name
|
Name used to identify the SAP system
|
Application Server
|
Name or IP address for the ABAP application server
|
System Number
|
SAP-specific system number
|
SAP Router String (optional)
|
Used for SAP systems outside the firewall
|
Logon Information
|
User name, password and client for logging onto the SAP ABAP application server
|
Organization (optional)
|
Group or organization within the company that owns the target. For multiple SAP systems with the same SID, you must specify the organization for each SAP system target.
|
Note Prior to creating an SAP Solution Manager target, you must have at least one managed object created and actively monitored in Solution Manager. Then, you can define an ABAP/JAVA system as a target. Simulataneously, you can define the SAP Solution Manager target.
SAP Java System Information
The following information is needed to create an SAP Java Application Server target.
Connection Information
|
Description
|
Application Server
|
Name or IP address for the Java application server
|
JMX Port
|
The JMX port number to connect to the Java application server. The following convention should be used for specifying the port number:
5<J2EEinstance_number>04
Example:
If your J2EE instance number is 15, the P4 port is 51504.
|
Telnet Port
|
The Telnet port number used to connect to the Java application server.
|
Logon Information
|
User name and password for logging onto the SAP Java application server.
Note The user account must be a J2EE Admin account.
|
SAP HANA System Information
The following information is needed to create SAP HANA targets.
Target Type
|
Connection Information
|
Description
|
SAP HANA Database Target
|
Host name or data source
|
Name of the server or data source where the HANA database resides.
<server name>:port
Note Port number will be 3XX15, where XX is the HANA System Number.
|
Database owner
|
Name of the database. For example, DH1.
|
Logon information
|
User name and password for connecting to the data source.
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
|
DSN connection string to the data source.
|
HANA Web Target
|
Base URL
|
Target URL to use as a base for the execution.
For example:
http://<hanahostname>:5XX13/?wsdl
where XX=HANA System Number
|
Logon Information (Optional)
|
User credentials for connecting to the Web target, if required.
Note The user account should be a HANA OS SIDADM user.
|
HANA.SAP Administration Unix Target
|
Host name
|
Host name or IP address of the server.
|
Port
|
Port number used to access the server.
|
Prompt prefix
|
Command prompt prefix used by the device type configurations and expects when issuing commands and connecting to the device.
|
Logon information
|
User name and password for connecting to the server.
Note The user account should be a HANA OS SIDADM user.
|
HANA.Linux Administration Unix Target
|
Host name
|
Host name or IP address of the server.
|
Port
|
Port number used to access the server.
|
Prompt prefix
|
Command prompt prefix used by the device type configurations and expects when issuing commands and connecting to the device.
|
Logon information
|
User name and password for connecting to the server.
Note The user account should be a Linux user with OS administration permissions.
Note Install a Linux/Unix adapter on the target OS or define a terminal adapter. The HANA OS level processess use the terminal adapter capabilities of the Linux/Unix adapter.
|
SAP BOBJ Information
The following information is needed to create SAP BOBJ DS and BOBJ XI targets.
Target Type
|
Connection Information
|
Description
|
BOBJ DS Web Target
|
Base URL
|
Target URL to use as a base for the execution.
|
Logon Information (Optional)
|
User credentials for connecting to the Web target, if required.
|
BOBJ DS Database Target
|
See the online help for the type of database you are using.
|
|
BWA Unix/Linux Target
|
Host name
|
Host name or IP address of the server.
|
Port
|
Port number used to access the server.
|
Prompt prefix
|
Command prompt prefix used by the device type configurations and expects when issuing commands and connecting to the device.
|
Logon information
|
User name and password for connecting to the server.
|
BOBJ XI—JMX Server Target
|
Application Server
|
Name or IP address for the JMX application server
|
JMX Port
|
Port number to connect to the JMX server.
|
URL path
|
Optional. URL path to the JMX server.
|
Logon Information
|
User name and password for logging onto the JMX server.
|
SAP Database Access Rights
These access rights are optional. If you want to collect SAP database SQL query information, you must have the following access rights to the SAP database.
Microsoft SQL Server Windows Authentication
If SQL Server Windows authentication is being used, the following access rights must be set on the machine where Process Orchestrator is installed. To change the connection settings through the database user configuration utility on Process Orchestrator server, the logged in user needs to have write permission to the Process Orchestrator installation folder.
•Windows Server 2003—The following user rights are required:
–The user account that connects to the database must be assigned Logon as Service rights.
–The user account that is logged in and using the user interface must be assigned Act as part of the OS rights.
•Windows Server 2008—The following user rights are required:
–The user account that connects to the database must be assigned Logon as Service rights.
–The user account that is logged in and using the user interface must be assigned Act as part of the OS rights.
SQL Server SQL Authentication
If SQL authentication is being used, the user account that connects to the database must have sysadmin (sa) rights on the machine where Process Orchestrator is installed. However, if the company requires a higher level of access than the standard sysadmin access, then use the following scripts to create the logon script for access.
Process Database Logon Script
Use the following logon SQL script to create the necessary credentials for accessing the Process Orchestrator processes database.
IF EXISTS (SELECT * FROM sys.server_principals WHERE name = N'Process
Orchestratorprocess')
DROP LOGIN [Process Orchestratorprocess]
CREATE LOGIN [Process Orchestratorprocess] WITH PASSWORD=N'Process Orchestrator',
DEFAULT_DATABASE=[Process OrchestratorProcess], CHECK_EXPIRATION=OFF, CHECK_POLICY=OFF
--For Windows authentication
--CREATE LOGIN [domain\userID] FROM WINDOWS WITH DEFAULT_DATABASE=[Process
OrchestratorProcess]
USE [Process OrchestratorProcess]
IF EXISTS (SELECT * FROM sys.database_principals WHERE name = N'Process
Orchestratorprocess')
DROP USER [Process Orchestratorprocess]
CREATE USER [Process Orchestratorprocess] FOR LOGIN [Process Orchestratorprocess] WITH
DEFAULT_SCHEMA=[dbo]
EXEC sp_addrolemember N'db_datareader', N'Process Orchestratorprocess'
EXEC sp_addrolemember N'db_datawriter', N'Process Orchestratorprocess'
Reporting Database Authentication Script
Use the following logon script to create a SQL user account for the Process Orchestrator reporting database. The assumption is that Process Orchestrator Reporting database will be created by a sysadmin account first, after which the script can be used to create a Process Orchestratorreporting database account with limited permission, and change reporting database to use the Process OrchestratorReporting user account.
IF EXISTS (SELECT * FROM sys.server_principals WHERE name = N'Process
Orchestratorreporting')
DROP LOGIN [Process Orchestratorreporting]
CREATE LOGIN [Process Orchestratorreporting] WITH PASSWORD=N'Process Orchestrator',
DEFAULT_DATABASE=[Process OrchestratorReporting], CHECK_EXPIRATION=OFF, CHECK_POLICY=OFF
--For Windows authentication
--CREATE LOGIN [domain\userID] FROM WINDOWS WITH DEFAULT_DATABASE=[Process
OrchestratorReporting]
USE [Process OrchestratorReporting]
IF EXISTS (SELECT * FROM sys.database_principals WHERE name = N'Process
Orchestratorreporting')
DROP USER [Process Orchestratorreporting]
CREATE USER [Process Orchestratorreporting] FOR LOGIN [Process Orchestratorreporting] WITH
DEFAULT_SCHEMA=[dbo]
EXEC sp_addrolemember N'db_datareader', N'Process Orchestratorreporting'
EXEC sp_addrolemember N'db_datawriter', N'Process Orchestratorreporting'
Oracle Database Access Rights
If you are using an Oracle database, it is recommended that the user account have read access rights to all tables and views assigned to it. The following minimum access rights must be assigned to the user account:
•SAP tables (SNAP and EDIDC)
|
•V$lock
|
•V$session
|
•V$sqlarea
|
•V$rowcache
|
•V$sql_plan
|
•V$librarycache
|
•V$sgastat
|
•Dba_free_space
|
•all_objects
|
•Dba_data_files
|
|
DB2 Database Access Rights
The following rights must be assigned to the user accounts for DB2 databases:
•The user account that connects to the DB2 UDB database must have SYSMON authority.
Note After assigning the user account to the SYSMON group, the DB2 instance needs to be restarted to ensure that the privilege is active.
•The user account should have Select access on the following SAP tables:
–SNAP
–EDIDC
Registering Process Orchestrator with SAP System Landscape Directory
This section provides instructions for registering Process Orchestrator to the SAP System Landscape Directory (SLD). You can manually register the product, import the registration information or transfer the product information via XML file.
After installing Process Orchestrator, refer to the following paths:
File Name
|
Location:
|
Default installation path
|
C:\Program Files\Cisco\Process Orchestrator
|
Default log/trace file path
|
C:\Documents and Settings\[local user]\Local Settings\Application Data\Cisco\Process Orchestrator
|
Default configuration file
|
C:\Program Files\Cisco\Process Orchestrator\Configuration Data
|
Pre-Registration Requirements
Prior to registering the product with SLD, you must obtain the following information for the SLD server:
•Host—Name of the server hosting the SLD
•Port—Port number used for the server hosting the SLD
•User—User name assigned to the account logging onto the SLD (User must have a LcrInstanceWriterLD role.)
•Passwd—Password assigned to the user account logging onto the SLD
Manually Registering Product
You can manually register the product to the SLD by creating a product name/version and software component name/version in the software catalogue of the SLD.
Step 1 Log on to the SLD.
Step 2 Click Products > New Product Version and enter the following information:
•Product name—Process Orchestrator
•Vendor name—Cisco Systems Inc
•Product version—V2.1
Step 3 Click Create.
Step 4 In the fourth empty field, enter the following information:
•Technical name—CISCO_PROCESS_ORCHESTRATOR
•Software component name—Cisco Process Orchestrator
•Software component version—V2.1
•Production state—released
Step 5 Click Create.
Importing Product Information
You can also import the product information to register it to the SLD.
Step 1 Log on to the SLD.
Step 2 Click Administration > Content > Import.
Step 3 In the Selected File field, enter the path to the SLD data zip file and then click Import Selected File.
Transferring Product Information via XML
You can also register the product information by transferring it via the XML file.
Step 1 Create the following folder to store the files:
C:\Example
Step 2 Copy the Test.class and the ThirdPartySystem.xml files into the folder.
Step 3 Enter the following command with the provided XML file:
- java -cp . example/Test SLD_host http_port user password ThirdPartySystem.xml
For example, enter the following:
C:\example>java -cp "../.." example.Test iccsolman40.sap.com 80 3rd_party isvconnect08 ThirdPartySystem.xml
After running the command, Retcode:200 displays.
Configuring SAP Multi-Tenant Support in Web Console
When using the SAP multi-tenant feature and viewing the SAP systems in the Web Console, the organizations do not display by default. To view the organization column in the Task view, you must configure the WebConsole.config file to enable this column.
Perform the following procedure to modify the WebConsole.config file.
Step 1 On the Process Orchestrator server, navigate to the folder where the Web.config file is located. By default, the files are located in the following directory:
C:\Program Files\Cisco\Process Orchestrator\WebConsole
Step 2 Open the Web.config file in Notepad and navigate to the "AffectedOrganizations" setting.
name="AffectedOrganizations"
enabled="false" />
Step 3 Change the enabled setting to true and then save the file to complete the procedure.
Error Handling, Logging and Tracing for Cisco Add-On
The Cisco Add-On contains API enabled ABAP function modules (RFC's) that are called by Process Orchestrator. This is performed in Process Orchestrator by defining an ABAP adapter step and specifying a method for the SAP Target system in a process. The ABAP custom methods perform individual tasks such as updating RFC destinations and configuring printers.
Error Handling
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. The activity that generated the error can be analyzed and actions can then be taken to resolve the issue that returned the error.
SAP Standard RFC Tracing
All RFC activity performed by 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.
Log Entries
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 Cisco Add-On
SAP Root Cause Analysis ABAP tools can be used to review the performance and execution of the RFC calls performed by Process Orchestrator. 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
Feedback