Download Report

2015-01-13
SAP Operational Process Intelligence
Installation and Upgrade Guide
Content
1
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2
Hardware and Software Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3
Installing SAP Operational Process Intelligence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4
Authorizations and Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
4.1
Assigning Roles to SAP Operational Process Intelligence Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
5
Configuring SAP Operational Process Intelligence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.1
Generating Time Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
5.2
Configuring the SAP Operational Process Intelligence Scheduler. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Scheduling the Correlation Job. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
Scheduling the Notification Job. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Changing the Schedule of the Job. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.3
Setting Up Service Connection for Task Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.4
Enable HANA Workflow Repository Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
5.5
Configuring the Developer Mode for HANA Workflow Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
6
Configuring Source System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
6.1
Configuring the SAP LT Replication Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
6.2
(Optional) Configuring the Process Gateway to Provider Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
6.3
Configuring Provider System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
7
Upgrading SAP Operational Process Intelligence to 1.0 SP04. . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
8
Product Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
9
Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
2
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP Operational Process Intelligence Installation and Upgrade Guide
Content
1
Overview
SAP Operational Process Intelligence powered by SAP HANA is an application based on SAP HANA that aims for
end-to-end process operational visibility across multiple business systems.
SAP Operational Process Intelligence consists of the following:
●
SAP Operational Process Intelligence business scenario editor in the SAP HANA studio
●
HANA workflow modeler in the SAP HANA studio and HANA workflow runtime on the SAP HANA server
●
SAP Operational Process Intelligence space.me Web-based workspace
●
SAP HANA Rules Framework in the SAP HANA studio
SAP Operational Process Intelligence Installation and Upgrade Guide
Overview
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
3
4
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP Operational Process Intelligence Installation and Upgrade Guide
Overview
Using Native SAP HANA Engines
SAP Operational Process Intelligence is a native SAP HANA application leveraging SAP HANA as the platform for
data calculation handling and lightweight application services.
Leveraging SAP NetWeaver Gateway
Process Gateway reuses gateway concepts and technologies to build an integrated content provider
implementation using standard Gateway techniques. Process Gateway exposes process definitions from provider
systems, which can then be accessed in a uniform way by using OData protocol.
SAP LT Replication Server Replication
Data provisioning includes the copying of data from its source (provider system), using the replication technology
of the SAP LT Replication Server, into the SAP HANA system. The structure of the replicated Event Log varies for
the different provider systems. Supported systems are Process Observer on SAP Business Suite, Business
Workflow on SAP Business Suite, SAP NetWeaver Process Integration, and SAP NetWeaver Business Process
Management.
SAP Operational Process Intelligence Installation and Upgrade Guide
Overview
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
5
2
Hardware and Software Requirements
Hardware Requirements
You can find a complete list of all SAP HANA components and the respective SAP HANA hardware and software
requirements in the Product Availability Matrix (PAM) at https://support.sap.com/pam .
Software Requirements
Only the software installed by your hardware partners is recommended for use on SAP HANA. Do not install
additional software on the SAP HANA appliance.
For more information about SAP HANA software requirements, see http://help.sap.com/hana_appliance and
navigate to
Installation and Upgrade Information
SAP HANA Server Installation and Update Guide
SAP
HANA Installation Overview .
To use SAP Operational Process Intelligence 1.0 SP04, you need to have the following components installed and
running:
●
SAP HANA 1.0 SP09 Revision 90 - SAP Operational Process Intelligence 1.0 SP04 requires either the SAP
HANA Limited Edition for Applications and Accelerators or SAP HANA, enterprise edition
Note
Both of the editions includes the SAP UI 5 delivery unit in version 1.20.6 or higher. SAP UI05 1.20.6 or
higher is required for using the operator's workspace space.me in SAP Operational Process Intelligence.
SAP HANA 1.0 SPS09 components:
○
SAP HANA Unified Server 1.0 SPS09 Revision 90 for x32-bit or x64-bit depending upon whether the
operation system is x32-bit or x64-bit.
○
SAP HANA Studio 1.0 SPS09 Revision 90 for x32-bit or x64-bit depending upon whether the operation
system is x32-bit or x64-bit to be installed locally on your PC.
○
HANA Lifecycle Manager - recommended for deploying delivery units of SAP Operational Process
Intelligence 1.0 SP04 in the HANA Studio. It comes, by default, with unified server installation.
○
(Optional) SAP HANA DB Client 1.0 SPS09 Revision 90 for x32-bit or x64-bit depending upon whether the
operation system is x32-bit or x64-bit to be installed locally on your PC.
●
(Optional) Process Gateway add-on (part of SAP NetWeaver Gateway 2.0 SP05).
●
SAP LT Replication Server 2010_1_700 SP06 or higher . If SAP NetWeaver Business Process Management is
using an MS SQL DB, SAP LT Replication Server needs to be installed over a Microsoft Windows operating
system.
One or more of the following provider systems:
●
Business Workflow as part of SAP Business Suite SAP_BASIS 702 SP13 or SAP_BASIS 731 SP05 or higher
●
SAP Business Process Management as part of SAP NetWeaver 7.3 EHP1 SP05 or higher
●
SAP NetWeaver Process Integration 7.3 EHP1 SP07 or higher
●
Process Observer as part of:
○
6
SAP Business Suite 7 (SAP_BS_FND 701 SP 12 )
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP Operational Process Intelligence Installation and Upgrade Guide
Hardware and Software Requirements
○
SAP ERP 6.0 EhP 4, SAP CRM 7.0, SAP SCM 7.0, SAP SRM 7.0
○
SAP Business Suite 7i2010 (SAP_BS_FND 702 SP 10 / SAP_BASIS 702 SP 08 (or note 1488051))
○
SAP ERP 6.0 EhP 5, SAP CRM 7.0 EhP 1, SAP SCM 7.0 EhP 1, SAP SRM 7.0 EhP 1
○
SAP Business Suite 7i2011 (SAP_BS_FND 7.31 SP 05 )
○
SAP ERP 6.0 EhP 6, SAP CRM 7.0 EhP2, SAP SCM 7.0 EhP 2, SAP SRM 7.0 EhP
Note
In addition, check SAP Note ??? for release information and 2029252
SAP Operational Process Intelligence Installation and Upgrade Guide
Hardware and Software Requirements
for compatibility information.
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
7
3
Installing SAP Operational Process
Intelligence
To install SAP Operational Process Intelligence, you use the hdbalm command line tool, which is part of the SAP
HANA application lifecycle management. SAP HANA application lifecycle management supports you in all phases
of an SAP HANA application lifecycle, from modeling your product structure, through application development,
transport, assemble, and install.
Prerequisites
●
You have performed the SAP HANA client installation.
If you have left the default installation options unchanged hdbalm is located in the c:\Program Files\sap
\hdbclient directory on Windows and /hana/shared/<SID>/hdbclient/hdbalm directory on Linux.
For more information, see the SAP HANA Client Installation and Update Guide and the SAP HANA Application
Lifecycle Management section in the SAP HANA Developer Guide.
●
You have the permissions required to use hdbalm: You have an SAP HANA database user with the SAP HANA
sap.hana.xs.lm.roles::Administrator user role assigned to it.
Note
You cannot use a newly created user that still has the initial password, since hdbalm will not ask you to
change it. Change the password for this user in SAP HANA studio, before using hdbalm.
Procedure
1.
8
Download the delivery units of SAP Operational Process Intelligence.
○
Alternative 1: Download the delivery units from the SAP Software Download Center using the following
substeps:
a.
Open the SAP Software Download Center with the following URL: https://support.sap.com/swdc
b.
Choose
c.
Click O and then click OPERAT. PROCESS INTELLIGENCE.
d.
Select OPERATION. PROCESS INTELL. 1.0 and choose Installation.
e.
Select the SP04 version and download the ZIP file containing all necessary files.
○
Alternative 2: Download the delivery units from SAP Solution Manager with the Maintenance Optimizer
(MOPZ) using the following substeps:
a.
Download the delivery units of SAP Operational Process Intelligence as an add-on to the latest available
SAP HANA stack including the latest available SAP HANA stack from Solution Manager with the
Maintenance Optimizer (MOPZ). For more information about the Solution Manager and the MOPZ, see
Maintenance Optimizer, Upgrade.
Installations and Upgrades
.
A-Z .
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP Operational Process Intelligence Installation and Upgrade Guide
Installing SAP Operational Process Intelligence
b.
2.
Place the downloaded files into a directory.
Start a command line client and navigate to the directory where hdbalm is located, or add this directory to
your path.
You use the following command: hdbalm install [<command options>] [<archive>|
<directory>]*
You can specify an archive file (for example a ZIP file as you downloaded from the SAP Software Download
Center) or a directory location that contains unpacked archive files (usually shipped on DVDs).
Command options are command-specific. For more information about the install command, enter hdbalm
help <command> in hdbalm. Some command options depend on the archive type. For example, you can only
use the --instances option for product archives.
3.
Enter the following command to install SAP Operational Process Intelligence: C:\Program Files\SAP
\hdbclient>hdbalm --user=<user name> --host=<host> --port=<port> install <location
of the SAP Operational Process Intelligence 1.0 SP04 installation DVD location>
If you download the four delivery units as separate files and not as one archive including all delivery units, and
you are going to install the delivery units individually, you need to consider the following order of installation:
1.
Task Management (HCOBCTASKMGT)
2.
HANA Operational Process Intelligence Process Visualization (HCOOPIPV), HANA Rules Framework
(HCORULEFW), HANA Workflow (HCOBCHWF)
It is important, to install the Task Management delivery unit before the Operational Process Intelligence
Process Visualization delivery unit.
Example (with an archive file containing all delivery units): C:\Program Files\SAP\hdbclient>hdbalm
--user=SYSTEM --host=somehostname --port=8004 install D:\Downloads
\<OPInt_installation DVD>.ZIP
4.
Post installation steps for the HANA rules framework (HRF):
a.
Create a technical user with name USER_RESOURCE_CREATOR.
b.
For the user to execute the necessary SQL statement (SYSTEM) assign the following roles:
OPINTDEVELOPER and OPINTUSER
c.
For the user to execute the necessary SQL statement (SYSTEM), add the object privileges “Create” and
“Execute” for SYS_PROCESS_VISIBILITY by adding SYS_PROCESS_VISIBILITY to the Object Privileges
tab.
d.
Run the following SQL procedure CALL
"SYS_PROCESS_VISIBILITY"."sap.opi.pv::SPVR_POST_INSTALLATION"('USER_RESOURCE_CRE
ATOR') to perform SAP HANA rules framework post installation steps. This procedure takes the user
name as input parameter. This automated procedure assigns required HRF roles to the user and the XS
connection configuration used for generation.
You need to run the manual scripts that need to be executed following the DU import. For more
information on activating the HRF runtime plugin, see the Enabling the Runtime Plug-In of SAP HANA
Rules Framework SAP HANA Rules Framework 1.0 SPS02 Installation & Upgrade Guide on SAP Service
Marketplace at SAP HANA Rules Framework
.
SAP Operational Process Intelligence Installation and Upgrade Guide
Installing SAP Operational Process Intelligence
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
9
4
Authorizations and Roles
Authorizations and roles define the objects users can access and the actions they can perform. In SAP
Operational Process Intelligence there are several roles that need to be assigned to users to perform operations
on business scenarios or admin tasks or to create business scenarios.
Operator or line-of-business user (with full access)
Required Roles
Description
sap.opi.pv.roles::OPINTUSER
Access space.me, which is the workspace for SAP
Operational Process Intelligence
<package_name>.gen_<scenario_name>::<scenario_name>_ Access the specific scenarios and all the relevant data in
OPERATOR
space.me
sap.bc.taskmgt.roles::TASKMGT_CORE
Access to tasks; enables task management in space.me
sap.bc.hwf.security::HWF_EndUser
Allows to complete tasks (execution of
sap.bc.hwf.api.usertask::COMPLETE_USER_TASK)
Operator or line-of-business user (with restricted access)
Table 1:
Required Roles
Description
sap.opi.pv.roles::OPINTUSER
Access space.me, which is the workspace for SAP Operational
Process Intelligence
<package_name>.gen_<scenario_name>::<custom_role_nam
e>_OPERATOR
Access the specific scenarios and the restricted data in
space.me
sap.bc.taskmgt.roles::TASKMGT_CORE
Access to tasks; enables task management in space.me
sap.bc.hwf.security::HWF_EndUser
Allows to complete tasks (execution of sap.bc.hwf.api.user
task::COMPLETE_USER_TASK)
Requester
Table 2:
Required Roles
Description
sap.opi.pv.roles::OPINTUSER
Access space.me, which is the workspace for SAP Operational
Process Intelligence
10
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP Operational Process Intelligence Installation and Upgrade Guide
Authorizations and Roles
Required Roles
Description
<package_name>.gen_<scenario_name>::<scenario_name>_
REQUESTER
Access the specific scenarios in space.me as a requester
Solution Expert
Table 3:
Required Roles
Description
sap.opi.pv.roles::OPINTDEVELOPER
Access to specific scenarios
MODELING
Access to work with the SAP HANA studio, create packages/
calculation views/attribute views and other HANA artifacts.
This role is required by SAP Operational Process Intelligence
to create or generate a business scenario.
The MODELING role grants permissions for the root package
and also grants the _SYS_BI_CP_ALL analytic privilege, which
is a surplus to requirements.
Tip
We recommend to modify the content of your custom roles
by changing the package privileges. Below are the basic
privileges that need to be provided:
●
Packages
○
sap.opi and sap.bc.taskmgt - Rights on the pack
ages: REPO.READ
○
package where you would like the business sce
narios to be created - Rights on the packages:
REPO.READ, REPO.EDIT_NATIVE_OBJECTS,
REPO.ACTIVATE_NATIVE_OBJECTS,
REPO.MAINTAIN_NATIVE_OBJECTS
●
Object Privileges
○
●
_SYS_BI with SELECT
System Privileges
○
CREATE SCENARIO
○
CREATE STRUCTURED PRIVILEGE
○
STRUCTUREDPRIVILEGE ADMIN (Optional - If
you want the solution expert to provide access to
the business scenario)
●
Analytical Privileges (Optional)
○
_SYS_BI_CP_ALL - If you want the solution expert
to view data and test the calculation views
SAP Operational Process Intelligence Installation and Upgrade Guide
Authorizations and Roles
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
11
Required Roles
Description
Grant select, create any on schema <schema_name> to
<user_name or role_name>
Grant select and create any authorizations on the schema
where the source of your event/process context and opera
tional data exists. This is needed to access data from source
systems and to generate your business scenario successful.
Optionally, you can grant select, create any, insert, update,
delete, drop, execute, trigger authorizations on the schema
where the source of your event/process context and opera
tional data exists.
HRF rule consumer
sap.bc.hwf.security::HWFDeveloper
Permits assigned users to run determination services based
on the rules and rule services created in the system. To enable
a user based on this role, you must grant permission for the
application schema to the user. The consumption of determi
nation services can be done in one of the following ways:
●
REST API rule service execution
●
Simulation rule service execution
●
ODBC consumption, by running the service procedure di
rectly
Allows to generate workflow templates (execution of
SET_TEMPLATE_TO_GENERATED)
HANA Workflow Administrator
Table 4:
Required Role
Description
sap.bc.hwf.security::HWFAdmin
Allows to activate the workflow template (execution of
sap.bc.hwf.api::SET_TEMPLATE_TO_ACTIVE and
sap.bc.hwf.api::SET_TEMPLATE_TO_INACTIVE
READ (generated role)
Grants unrestricted access to
12
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
●
workflow calculation view
●
workflow template calculation view
●
all generated context calculation views
SAP Operational Process Intelligence Installation and Upgrade Guide
Authorizations and Roles
HANA Workflow Technical Administrator
Table 5:
Required Role
Description
sap.bc.hwf.security::HWFSuperAdmin
Grants unrestricted access to
●
workflow calculation view
●
workflow template calculation view
Allows to activate the workflow template (execution of
sap.bc.hwf.api:SET_TEMPLATE_TO_ACTIVE and
sap.bc.hwf.api::SET_TEMPLATE_TO_INACTIVE
Allows to enable and disable the developer mode (execution
of sap.bc.hwf.api::DEVELOPER_MODE_ENABLE and
sap.bc.hwf.api::DEVELOPER_MODE_ENABLE
Read (generated role)
Grants unrestricted access to
●
workflow calculation view
●
workflow template calculation view
●
all generated context calculation views
Technical User
_SYS_REPO
_SYS_REPO is a technical database user and does not correspond to real people.
Table 6:
Required Roles
Description
Grant select, create any on schema <schema_name> to
_SYS_REPO
Grant select and create any authorizations on the schema
(used by SAP SAP Operational Process Intelligence) where
the source of your event/process context and operational
data exists. This is needed to access data from source sys
tems and to generate your business scenario successful.
Note
<schema_name> is TASKMGT,
SYS_PROCESS_VISIBILITY, and source system schema.
USER_RESOURCE_CREATOR
Table 7:
Required Roles
Description
Grant HRF Resource Creator
Allows assigned users to activate all resources related to SAP
HANA rules framework (HRF).
SAP Operational Process Intelligence Installation and Upgrade Guide
Authorizations and Roles
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
13
HANA Workflow Technical User
Table 8:
Required Roles
Description
sap.bc.hwf.security::HWFJobUser
Allows to check and update workflow templates (execution of
SET_TEMPLATE_TO_GENERATED).
Grants access to
Job (generated role)
●
the token calculation view
●
the configuration SQL view
Allows to generate all wrapper and end procedures
System User
Table 9:
Required Roles
Description
INIFILE ADMIN
Allows to enable the validation of HANA workflow files
(.hprworkflow)
Service User
Table 10:
Required Roles
Description
sap.opi.pv.roles::OPINTSERVICE
Allows to schedule jobs for correlation and notifications in
SAP Operational Process Intelligence
sap.bc.taskmgt.roles::TASKMGT_SERVICE_CONNECTION
Allows to execute tasks
Grant select, create any on schema <schema_name> to
<user_name or role_name>
Grant select and create any authorizations on the schema
where the source of your event/process context and opera
tional data exists. This is needed to access data from source
systems and to execute correlation and notification jobs.
Optionally, you can grant select, create any, insert, update,
delete, drop, execute, trigger authorizations on the schema
where the source of your event/process context and opera
tional data exists.
14
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP Operational Process Intelligence Installation and Upgrade Guide
Authorizations and Roles
4.1
Assigning Roles to SAP Operational Process Intelligence
Users
You use this procedure to assign the necessary roles to the SAP Operational Process Intelligence users.
Prerequisites
Users are created. For more information on creating users, see the SAP HANA Administration Guide, topic
Managing SAP HANA Users.
Procedure
1.
In the SAP HANA Systems view, select the required system.
2.
Under the system, choose Security/Users.
3.
Select the user ID to which you want to assign a role.
4.
From the context menu of the selected user ID, choose Open.
5.
On the Granted Roles tab page, choose the + icon.
6.
Select the required role.
7.
Choose OK.
8.
Repeat steps 5 through 7 to add more roles.
Note
For service users and users running background jobs, the password expires every six months. This results
in failure of the jobs. To avoid this situation, disable the password lifetime by using the command, ALTER
USER <user_name> DISABLE PASSWORD LIFETIME.
SAP Operational Process Intelligence Installation and Upgrade Guide
Authorizations and Roles
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
15
5
Configuring SAP Operational Process
Intelligence
Context
You use this procedure to configure SAP Operational Process Intelligence on the SAP HANA system.
Procedure
1.
Specify the time dimension based on which system must generate the data or records.
For more information, see Generating Time Data [page 16] .
2.
Configure the SAP Operational Process Intelligence scheduler.
For more information, see Configuring the SAP Operational Process Intelligence Scheduler [page 18].
3.
Define a service connection for the HANA task management.
For more information, see Setting Up Service Connection for Task Management [page 23]
4.
HANA workflow-specific step: Configure the HANA workflow repository integration
For more information, see Enable HANA Workflow Repository Integration [page 24]
5.
HANA workflow-specific step: Configure the developer mode for HANA workflow models.
For more information, see Configuring the Developer Mode for HANA Workflow Models [page 24]
5.1
Generating Time Data
Context
Before you start to model business scenarios, you need to set the time dimension for which data is generated.
This is a one-time activity; once done, it applies to all business scenarios created thereafter. You do this by
generating time data in the SAP HANA. The system populates the generated time data in the
M_TIME_DIMENSION table in the _SYS_BI schema. Each row of the table is one record. For example, if you define
the granularity of your records as one day, each row will be the record for one day.
By generating time data, you enable the business user to later filter all process and performance data in the
space.me workspace.
16
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP Operational Process Intelligence Installation and Upgrade Guide
Configuring SAP Operational Process Intelligence
For more information, see the Generating Time Data topic on SAP Help Portal at http://help.sap.com/
hana_appliance,
Modeling Information
SAP HANA Modeling Guide .
Procedure
1.
In the SAP HANA studio, select the required SAP HANA system.
2.
Open the Modeler perspective.
3.
If the Quick Launch view is not already open, navigate to
4.
In the Data section, choose Generate Time Data.
5.
From the Calendar Type dropdown menu, choose Gregorian.
Help
Quick Launch .
Note
The calendar type is Gregorian, so you have the option of choosing the granularity for recording time data.
6.
Specify the time period for which you want to generate time data by entering a year in the From Year and To
Year fields, respectively.
7.
From the Granularity dropdown menu, choose the desired granularity of the data.
Note
We strongly recommend that you choose 1 Day for the optimal granularity of data. This will give you
sufficiently detailed time data to use the time filters in the space.me workspace.
If you choose a finer granularity, for example 1 Hour, there will be too many time records and this will hinder
the performance of the queries. On the other hand, if the granularity is too coarse, the time records will not
be detailed enough to use the time filter in the space.me workspace.
8.
Choose Generate.
Results
You can now proceed with assembling and configuring your business scenarios.
For more information, see http://help.sap.com/hana-opint,
section Modeling a Business Scenario.
SAP Operational Process Intelligence Installation and Upgrade Guide
Configuring SAP Operational Process Intelligence
Development Information
Developers Guide ,
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
17
5.2
Configuring the SAP Operational Process Intelligence
Scheduler
Prerequisites
The following prerequisites must be fulfilled:
●
Task Management delivery unit has been installed.
●
SAP Operational Process Intelligence delivery unit has been installed.
●
HANA workflow delivery unit has been installed
●
HANA rules framework delivery unit has been installed
For more information about downloading and installing the Task Management and the SAP Operational Process
Intelligence delivery units, see Installing SAP Operational Process Intelligence [page 8].
Context
The SAP Operational Process Intelligence Scheduler is used to schedule the following jobs:
●
Correlation job - Uses the correlation scheduling interval of each business scenario to import the events and
context from replicated source tables and make the content available for analysis.
●
Notification jobs - Check the notification conditions on indicators.
5.2.1
Scheduling the Correlation Job
Prerequisites
The following roles are assigned to you:
●
sap.hana.xs.admin.roles::JobAdministrator
●
sap.hana.xs.admin.roles::RuntimeConfAdministrator
●
sap.hana.xs.lm.roles::Administrator
Context
You use this procedure to schedule the correlation job.
18
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP Operational Process Intelligence Installation and Upgrade Guide
Configuring SAP Operational Process Intelligence
Note
The correlation job is located in the /sap/opi/pv/master package.
Procedure
1.
Launch SAP HANA studio.
2.
If the required SAP HANA system is not yet added, proceed as follows:
a.
Open the Systems view, and in the context menu, choose Add System.
b.
Enter the host name and the instance number of the SAP HANA system, and choose Finish.
3.
In the Systems view, select the required SAP HANA system.
4.
From the context menu of the SAP HANA system, select
Configuration and Monitoring
Open
Administration .
5.
Choose the Configuration tab page.
6.
Select xsengine.ini scheduler , and check whether the value of enabled is set to true. If you do not have a
scheduler entry, create a scheduler section as follows:
a.
In the context menu of xsengine.ini, choose Add Section.
b.
In the Add Section Wizard, enter the name scheduler and choose Next.
c.
Enter the key enabled and the value true, and choose Finish.
7.
Start the SAP HANA XS administration tool by using the URL http://<host><port>/sap/hana/xs/admin/,
where <host> is your SAP HANA server host, and <port> is 80 followed by your SAP HANA server instance
number.
8.
From the Application Objects section, select the correlation job
sap.opi.pv.master::OP_INT_MASTER_CORRELATION_PROCEDURE.
9.
In the User field, enter the service user.
For service users and users running background jobs, the password expires every six months. This results in
failure of the jobs. To avoid this situation, disable the password lifetime by using the command, ALTER USER
<user_name> DISABLE PASSWORD LIFETIME. For more information, see Authorizations and Roles [page
10].
10. In the Locale field, enter the required language code.
11. Select Active.
12. Save the changes.
Results
After each scheduled job is run, entries are generated in the sap.opi.pv/
SPVR_SCENARIO_DEFINITION_SCHEDULER table.
The runtime checks identify erroneous situations in the sap.opi.pv::SPVR_APPLICATION_LOG, sap.opi.pv/
SPVR_ERROR_LOGS, and sap.opi.pv::SPVR_APPLICATION_LOG_MESSAGE tables. The
SAP Operational Process Intelligence Installation and Upgrade Guide
Configuring SAP Operational Process Intelligence
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
19
sap.opi.pv::SPVR_APPLICATION_LOG table displays the status and details of the runtime checks. The
sap.opi.pv::SPVR_APPLICATION_LOG_MESSAGE table displays the details of result messages of runtime checks.
Name
Description
SCENARIO_NAME
Business scenario name
SQL_SP_NAME
Correlation stored procedure that is responsible for
correlating events from the replicated sources to business
scenario-specific events
SQL_ERR_TEXT
Explains why the correlation failed
SQL_ERR_CODE
10750
TIMESTAMP
Time when the error occurred
If an error occurs during correlation, the correlation will not happen until the business scenario has been
regenerated.
For more details about the error log and exception handling, see SAP Note 1775708
5.2.2
.
Scheduling the Notification Job
Prerequisites
The following roles are assigned to you:
●
sap.hana.xs.admin.roles::JobAdministrator
●
sap.hana.xs.admin.roles::RuntimeConfAdministrator
●
sap.hana.xs.lm.roles::Administrator
A user must be specified under which the notification jobs are executed. The user needs to be a dedicated user
having the role OPINTSERVICE, which provides the necessary authorizations for the KPI evaluation and
notification creation.
Context
You use this procedure to schedule the notification job. You need to activate the notification xsjob file so that
users receive notifications that they have subscribed to.
Note
The notification xsjob file is located in the /sap/opi/pv/workspace/xsjobs package.
20
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP Operational Process Intelligence Installation and Upgrade Guide
Configuring SAP Operational Process Intelligence
Procedure
1.
Launch SAP HANA studio.
2.
If the required SAP HANA system is not yet added, proceed as follows:
a.
Open the Systems view, and in the context menu, choose Add System.
b.
Enter the host name and the instance number of the SAP HANA system, and choose Finish.
3.
In the Systems view, select the required SAP HANA system.
4.
From the context menu of the SAP HANA system, select
Configuration and Monitoring
Open
Administration .
5.
Choose the Configuration tab page.
6.
Select xsengine.ini scheduler , and check whether the value of enabled is set to true. If you do not have a
scheduler entry, create a scheduler section as follows:
a.
In the context menu of xsengine.ini, choose Add Section.
b.
In the Add Section Wizard enter the name scheduler and choose Next.
c.
Enter the key enabled and the value true, and choose Finish.
7.
Start the SAP HANA XS administration tool by using the URL http://<host>:<port>/sap/hana/xs/admin/
where <host> is your SAP HANA server host, and <port> is 80 followed by your SAP HANA server instance
number.
8.
In the SAP HANA XS administration tool, in the Application Objects section, go to /sap/opi/pv/workspace/
xsjobs.
9.
For the notification job triggerNotifications.xsjob, enter the service user account under which the job is
executed (User field) and select the Active checkbox to activate the job. The user that is specified, here, needs
to be a dedicated user having the role OPINTSERVICE, which provides the necessary authorizations for the
KPI evaluation and notification creation. For service users and users running background jobs, the password
expires every six months. This results in failure of the jobs. To avoid this situation, disable the password
lifetime by using the command, ALTER USER <user_name> DISABLE PASSWORD LIFETIME. For more
information, see Authorizations and Roles [page 10].
You do not need to enter a specific locale or start and end time.
10. Save the changes.
Results
The single xsjob file triggerNotifications.xsjob contains one dedicated schedule for each possible frequency
(hourly, daily, weekly, monthly) for the KPI evaluation.
Errors occurring during the execution of the notification job are written to the XS engine trace and to the XS job
log, which can be reviewed for each execution of the job in the SAP HANA XS administration tool.
To get additional information about the job such as the start time, end time, the polling period of the job, and the
number of notifications that have been triggered, increase the trace level of the component
xsa:sap.opi.pv.workspace to INFO.
Example trace file extract:
[23023]{-1}[-1/-1] 2014-01-14 14:48:00.029870 i xsa:sap.opi.pv.w
sap.opi.pv.workspace.xsjobs:triggerNotifications.xsjs(00011) : Polling period:
SAP Operational Process Intelligence Installation and Upgrade Guide
Configuring SAP Operational Process Intelligence
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
21
HOURLY - Job
started
[23023]{-1}[-1/-1] 2014-01-14 14:48:03.896535 i xsa:sap.opi.pv.w
sap.opi.pv.workspace.xsjobs:triggerNotifications.xsjs(00028) : Polling period:
HOURLY - 1
notification(s) created
[23023]{-1}[-1/-1] 2014-01-14 14:48:03.896550 i xsa:sap.opi.pv.w
sap.opi.pv.workspace.xsjobs:triggerNotifications.xsjs(00030) : Polling period:
HOURLY - Job
ended successfully
5.2.3
Changing the Schedule of the Job
You can change the schedule of a job, for example, when using count measure-based indicators. In this case, you
change the job schedule so that the jobs are executed at the end of your reporting interval.
Prerequisites
The following roles are assigned to you:
●
sap.hana.xs.admin.roles::JobAdministrator
●
sap.hana.xs.admin.roles::RuntimeConfAdministrator
●
sap.hana.xs.lm.roles::Administrator
Context
By default the jobs are scheduled at the beginning of a certain period.
●
hourly - every hour on the hour
●
daily - every day at 00:00 UTC
●
weekly - every Monday at 00:00 UTC
●
monthly - on the 1st of each month at 00:00 UTC
Note
Times defined in xsjob file schedules are always considered to be in UTC.
Procedure
1.
In the SAP HANA XS administration tool (http://<host>:<port>/sap/hana/xs/admin/), deactivate the job
whose schedule you want to change.
<host> is your SAP HANA server host, and <port> is 80 followed by your SAP HANA server instance number.
22
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP Operational Process Intelligence Installation and Upgrade Guide
Configuring SAP Operational Process Intelligence
2.
Check out the corresponding xsjob and change the schedule according to your needs.
For more information about defining schedules, see the SAP HANA Developer Guide, section Scheduling XS
Jobs.
3.
Check in and activate the file.
4.
Reactivate the job.
5.3
Setting Up Service Connection for Task Management
To enable users to execute tasks that are generated from templates, you need to define a service connection.
Prerequisites
The following roles are assigned to you:
●
sap.hana.xs.admin.roles::JobAdministrator - to access the SAP HANA XS administration tool (http://
<host>:<port>/sap/hana/xs/admin/)
●
sap.hana.xs.admin.roles::SQLCCAdministrator
Procedure
1.
Start the SAP HANA XS administration tool by using the URL http://<host>:<port>/sap/hana/xs/admin/
where <host> is your SAP HANA server host, and <port> is 80 followed by your SAP HANA server instance
number.
2.
Choose the XS APPLICATIONS tab to display the screen where you can manage the runtime configurations
for the various applications in your package hierarchy.
3.
In the Application Objects list, locate and select the SQL connection configuration sap.bc.taskmgt.task/
taskgmt.xssqlcc.
4.
In the User field, assign the service user.
For service users and users running background jobs, the password expires every six months. This results in
failure of the jobs. To avoid this situation, disable the password lifetime by using the command, ALTER USER
<user_name> DISABLE PASSWORD LIFETIME. For more information about users and roles, see
Authorizations and Roles [page 10].
For more information about SQL connection configuration, see the SAP HANA Administration Guide, topic
Edit an SQL Connection Configuration.
Results
Business users can now access and execute the tasks of a checklist in the space.me workspace.
SAP Operational Process Intelligence Installation and Upgrade Guide
Configuring SAP Operational Process Intelligence
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
23
5.4
Enable HANA Workflow Repository Integration
HANA Workflow artifacts with extension .hprworkflow are validated on activation by the HANA repository.
Prerequisites
The system privilege INIFILE ADMIN is assigned to you.
Context
Before the HANA workflow files can be validated, you need to enable the respective support by executing a
statement.
Procedure
Execute the following statement: ALTER SYSTEM ALTER CONFIGURATION ( 'indexserver.ini',
'SYSTEM' ) SET ( 'repository', 'jsplugin_sap/bc/hwf/repoplugin/hwfrepoplugin.xsjs' ) =
'true' WITH RECONFIGURE;
If files with the extension .hprworkflow had been imported or created in the system before you executed the
statement, activation errors will occur and respective files cannot be activated.
5.5
Configuring the Developer Mode for HANA Workflow
Models
The developer mode is an integral part of the HANA workflow versioning concept.
The developer mode enables developers to deliberately override existing versions of a workflow in a system. It is a
safe net mechanism, which prevents accidental corruption of workflow instances by re-activating and/or regenerating a workflow model.
A developer needs to explicitly switch on the developer mode by changing the runtime configurations.
●
Developer mode is enabled (developer_mode = true): activation and generation is not restricted
●
Developer mode is disabled (developer_mode = false): patching existing HANA workflow by regenerating or
by deploying HANA DU, containing a different set of generated artifacts, will be:
○
24
revoked, if the workflow template is not in Suspended status - HANA workflow instances of that workflow
template are being processed
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP Operational Process Intelligence Installation and Upgrade Guide
Configuring SAP Operational Process Intelligence
○
allowed, if the workflow template is in Suspended status - all HANA workflow instances of that workflow
template are not being processed anymore
To enable the developer mode, execute the following procedure:
"SAP_HWF"."sap.bc.hwf.config::DEVELOPER_MODE_ENABLE"
To disable the developer mode, execute the following procedure:
"SAP_HWF"."sap.bc.hwf.config::DEVELOPER_MODE_DISABLE"
SAP Operational Process Intelligence Installation and Upgrade Guide
Configuring SAP Operational Process Intelligence
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
25
6
Configuring Source System
6.1
Configuring the SAP LT Replication Server
The SAP LT Replication Server enables you to replicate process data from a provider system to the SAP HANA
system. The configuration itself consists of defining the following in the SAP LT Replication Server system:
●
●
One or more source systems:
○
ERP system (containing data for Process Observer or Business Workflow)
○
SAP Business Process Management system
○
SAP Process Integration system
○
Third-party systems
Target SAP HANA system where the data is replicated
For more information about configuring the SAP LT replication server, read the information and follow the
procedures in SAP Note 1709225 .
Once this configuration is complete, you can replicate all required tables in the SAP HANA system.
The table below provides the tables you need to replicate for various systems in order to generate scenarios with
process definitions from the respective provider systems.
Table 11:
Provider System
Tables
Process Observer
POC_D_PRC_BIND
POC_D_PRC_IN
POC_D_PRC_STP_IN
POC_C_PROC_STEP
POC_C_PS_EXT
POC_C_PS_BND
POC_D_BA_LOG
ADRP
USR21
26
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP Operational Process Intelligence Installation and Upgrade Guide
Configuring Source System
Provider System
Tables
Business Workflow
SWF_PF_REL_EVT
SWWLOGHIST
SWWWIHEAD
SWW_WI2OBJ
ADRP
USR21
SAP Business Process Management
BC_BPEM_EL_ENTRY
BC_BPEM_EL_EVT_MAP
BC_BPEM_EL_RDS
BC_BPEM_UM_MAP
SAP Process Integration
NIMM Model tables
●
BC_IV_E2E_MSG_FLOW
●
BC_IV_MESSAGE_FLOW
●
BC_IV_MSG_FLW_STEP
●
BC_IV_SERVICE
●
BC_IV_DISC_CONFIG
JAVA DC tables
●
BC_IV_DC_EVNT
●
BC_IV_DC_EVNT_ACK
ABAP DC tables
Third-party system
●
/SDF/IVISEVTMAIN
●
/SDF/IVISEVTPATR
●
/SDF/IVISEVTFLOW
●
/SDF/IVISEVTPRED
●
/SDF/IVISEVTSUCC
●
/SDF/IVISEVTREL
●
/SDF/IVISEVTALT
Appropriate event log table
For generation to work when using SAP Business Process Management on MsSQL, you have to create three
additional SAP LT Replication Server transformations. You do this because the timestamp format of the Microsoft
SQL DB Server needs to be changed to work properly with SAP Operational Process Intelligence.
These three transformations need to be created for the following tables or columns:
●
BC_BPEM_EL_ENTRY and EVENT_TIMESTAMP
*&---------------------------------------------------------------------*
*& Include
ZIUUC_POC_TIMESTAMP_TRANS
*&---------------------------------------------------------------------*
data result type string.
SAP Operational Process Intelligence Installation and Upgrade Guide
Configuring Source System
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
27
result = i_event_timestamp_1.
replace all occurrences of '-' in result with ''.
replace all occurrences of ':' in result with ''.
replace all occurrences of '.' in result with ''.
condense result no-gaps.
concatenate result '000' into result.
e_event_timestamp = result.
●
BC_BPEM_EL_RDS and DATA_VAL_DATETIME
*&---------------------------------------------------------------------*
*& Include
ZIUUC_POC_TIMESTAMP_TRANS
*&---------------------------------------------------------------------*
data result type string.
IF NOT i_data_val_datetim_1 IS INITIAL.
result = i_data_val_datetim_1.
replace all occurrences of '-' in result with ''.
replace all occurrences of ':' in result with ''.
replace all occurrences of '.' in result with ''.
condense result no-gaps.
concatenate result '000' into result.
e_data_val_datetime = result.
ELSE.
e_data_val_datetime = i_data_val_datetim_1.
ENDIF.
●
BC_BPEM_EL_RDS and DATA_VAL_TIME
*&---------------------------------------------------------------------*
*& Include
ZIUUC_POC_TIMESTAMP_TRANS
*&---------------------------------------------------------------------*
data result type string.
IF NOT i_data_val_time_1 IS INITIAL.
result = i_data_val_time_1.
result = result+11(8).
replace all occurrences of ':' in result with ''.
e_data_val_time = result.
ELSE.
e_data_val_time = i_data_val_time_1.
ENDIF.
6.2
(Optional) Configuring the Process Gateway to Provider
Systems
To be able to use the search console to discover process definitions from the provider systems, and use these
definitions when modeling your business scenarios, you need to configure the connection between the Process
Gateway system and the provider systems.
For more information about configuring the Process Gateway, see Configuring Business Process Content
Services.
28
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP Operational Process Intelligence Installation and Upgrade Guide
Configuring Source System
6.3
Configuring Provider System
SAP Operational Process Intelligence supports several provider systems. To make the relevant data coming from
different systems visible, you need to configure the respective provider systems.
Note
The ERP system needs to have the software component SAP_BS_FND satisfying the below mentioned support
package levels for various releases.
●
731: support package level 5
●
730: support package level 4
●
702: support package level 10
●
701: support package level 12
Below is a list of the possible correlation scenarios between provider systems.
Process Observer on SAP Business Suite
To discover and consume process definitions from Process Observer on SAP Business Suite, you need to follow
the configuration steps in the Process Monitoring Setup section in the Process Observer Documentation.
SAP Business Workflow
After completing the Process Observer configuration steps, to enable Process Gateway to expose Business
Workflow data, you need to assign the data provider to the data model. Proceed as follows:
1.
Call transaction SPRO.
2.
Follow the navigation path
SAP Customizing Implementation Guide
Channel Development with IW_BEP
3.
SAP NetWeaver
Gateway
OData
Registration .
Assign a Data provider to the Data model.
Result: Business Workflow process definitions can be searched and discovered in the SAP HANA studio.
Business Workflow Observable Events
Table 12:
Step Type
Technical Step Type
Process Gateway Monitoring Activity
Activity
FUNC
BWFActivityType
Document from Template
TMPL
BWFActivityType
Form
FORM
BWFActivityType
Send Mail
MAIL
BWFBackgroundActivityType
SAP Operational Process Intelligence Installation and Upgrade Guide
Configuring Source System
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
29
Step Type
Technical Step Type
Process Gateway Monitoring Activity
Subworkflow
FUNC
BWFSubflowType
User Decision
MSEL
BWFActivityType
Wait
WAIT
BWFIntermediateEventType
Web Activity
WEB
BWFBackgroundActivityType
Workaround for Non-Observable Step Types
Other event types do not have a subnode bpmn2:monitoring id, so they cannot be observed in a business
scenario. As a workaround, add a “dummy” observable activity (for example, Activity) in Business Workflow after
the non-observable step type and observe this "dummy" observable activity.
Additional Security Configuration
If you want business users to be able to view their own requests, create a user in SAP HANA that has the same
user ID as the user ID replicated by the provider system (source system) and grant this user the corresponding
SQL and analytic privileges. For more information, see SAP Operational Process Intelligence Security Guide .
●
A user named exactly like the user that creates processes in the Business Workflow system
Note
Every process definition instance from Business Workflow is started by the WF-BATCH user. However, the
dash symbol "-" is not allowed to be used as a character in the user name in the SAP HANA database, so
you cannot create a WF-BATCH user in SAP HANA. To enable a SAP HANA user to see the business
scenarios initiated by the WF-BATCH user in the My Requests view, you can create external identity WFBATCH@<domain> for the SAP HANA user.
●
A user OPERATOR who is the Business Process Operator
SAP NetWeaver Process Integration
There are many different ways to establish a landscape and different ways to configure the message exchange in
PI. Integration Visibility supports landscapes where multiple PI domains exist. It is a technical foundation that
discovers message flows and enables consumer applications to subscribe and consume monitoring events for a
selected set of discovered message flows. This includes all A2A and B2B scenarios in the monitored landscape.
Integration Visibility works with the following integration landscape assumptions:
●
One system landscape directory as of SAP NetWeaver 7.1 including enhancement package 1 SP06.
●
One or more PI domains (dual-stack and/or Java-only, with an optional non-central Adapter Engine) as of
SAP NetWeaver PI 7.3 including enhancement package 1 SP07.
●
One or more connected SAP backend systems.
Supported middleware components and sender/receiver backend systems are:
●
SAP NetWeaver PI ABAP IS as of SAP NetWeaver 7.3 including enhancement package 1 (discovery and data
collection).
●
SAP NetWeaver PI Java AE (AEX, dual-stack Central Adapter Engine, non-central Adapter Engine) as of SAP
NetWeaver 7.3 including enhancement package 1 (discovery and data collection).
30
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP Operational Process Intelligence Installation and Upgrade Guide
Configuring Source System
●
Backend systems with ABAP Proxy as of SAP NetWeaver PI 7.1 including enhancement package 1 SP06
(discovery only).
●
Backend systems with ALE and ABAP Proxy (data collection only). For more information about the release
dependencies, see the relevant SAP Solution Manager documentation.
To observe message flows, you need to configure the Integration Visibility system. For more information, see the
Integration Visibility documentation on SAP Help Portal at http://help.sap.com/nw731,
Function-Oriented View
Process Integration
Integration (PI) Dual Stack
Administering Process Integration (PI)
Application Help Administering Process
Integration Visibility .
SAP NetWeaver Business Process Management
Note
If you are using SAP NetWeaver Business Process Management on SAP NetWeaver 7.31 SP05, you need to
make sure your process events are logged in the event log table. To do so, make sure that in SAP NetWeaver
Administrator you turn on the EventLog switch. For more information, see SAP NetWeaver Documentation,
under Application Help and SAP NetWeaver Administration Guide.
Table 13:
Observable Step
Required SAP NetWeaver BPM Release
Human activity (user task)
SAP NetWeaver 7.3 EHP 1 SP05 or higher
Subprocess (call activity)
SAP NetWeaver 7.3 EHP 1 SP05 or higher
Human activities as part of subprocesses
SAP NetWeaver 7.3 EHP 1 SP05 or higher
The subprocess definition needs to be discovered and im
ported into the business scenario.
Intermediate event
SAP NetWeaver 7.3 EHP 1 SP07 or higher
Automated activity (service task)
SAP NetWeaver 7.3 EHP 1 SP07 or higher
Automated activities as part of subprocesses
SAP NetWeaver 7.3 EHP 1 SP07 or higher
The subprocess definition needs to be discovered and im
ported into the business scenario.
Workaround for Non-Observable Step Types
To observe any other non-observable steps, you need to include these steps in SAP Business Process
Management subprocesses.
Additional Security Configuration
The SAP HANA user who discovers SAP Business Process Management process definitions needs to have
authorization as an SAP NetWeaver Gateway user. To consume process definitions from the SAP Business
Process Management system through the SAP NetWeaver Gateway, the user that is authenticated in the SAP
Business Process Management system needs to be assigned a UME action SAP_BPM_EXPORT_MODEL. We also
recommend the following:
SAP Operational Process Intelligence Installation and Upgrade Guide
Configuring Source System
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
31
●
SAP_BPM_EXPORT_MODEL action is assigned to the SAP_BPM_SuperDisplay role
●
SAP_BPM_EXPORT_MODEL action is assigned to the Support user
To enable the user to see business scenario definitions in the space.me workspace, you need to assign the user
the respective SQL and Analytic privileges. For more information, see SAP Operational Process Intelligence
Security Guide .
SAP Business Suite Process Observer to SAP Business Suite Process Observer
(Asynchronous)
Prerequisites: You need core ABAP knowledge to complete this procedure.
Procedure: To configure Process Observer to Process Observer process definition correlation with iDocs, follow
the procedure in the Process Observer documentation: Configuring End-To-End Federation.
Due to the asynchronous nature of the ALE framework, the built-in automatic algorithm for cross-system process
correlation of Process Observer (based on passport ID or transaction ID) cannot be used. The reasons are as
follows:
●
Transaction ID of source and target systems are different.
●
Transaction ID at the target system is one and the same because there is only one ID for the scheduled job of
processing the incoming iDoc.
To enable correlation, you need to implement a BAdl. To do so, proceed as follows:
1.
Call transaction POC_CUSTOMIZING.
2.
In the Business Add-ons node, implement Enrichment of Task Log Data.
Result: You set the ba_log of the transaction ID to a unique identifier in accordance with the specifics of the
business process, for example, sales order number, request ID, and so on.
SAP Business Workflow to SAP Business Workflow
The Business Workflow to Business Workflow (with explicit subflow) correlation does not require additional
configuration. You just need to import both process definitions as scenario participants, as a main flow and a
subflow in the business scenario editor.
32
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP Operational Process Intelligence Installation and Upgrade Guide
Configuring Source System
7
Upgrading SAP Operational Process
Intelligence to 1.0 SP04
You use this procedure to upgrade your system from SAP Operational Process Intelligence 1.0 SP02 or 1.0 SP03
to SAP Operational Process Intelligence 1.0 SP04.
Prerequisites
You have SELECT, EXECUTE, DELETE, ALTER, and UPDATE authorizations on the "SYS_PROCESS_VISIBILITY"
schema.
Procedure
1.
2.
Stop the scheduling jobs running from SAP XS administration by performing the following substeps:
a.
Open the SAP HANA XS administration page (http://<host>:<port>/sap/hana/xs/admin/ where <host>
is your SAP HANA server host, and <port> is 80 followed by your SAP HANA server instance number).
b.
From Application Objects, navigate to / sap opi
OP_INT_MASTER_CORRELATION_PROCEDURE.
c.
Deactivate the job by unchecking the option, Active.
d.
Save the changes.
e.
From the Application Objects, navigate to
triggerNotifications.
f.
Deactivate the job by unchecking the option, Active.
g.
Save the changes.
/
sap
pv
opi
master , and select
pv
workspace
xsjobs , and select
Uninstall the SAP Operational Process Intelligence 1.0 SP03 plugin from SAP HANA studio.
If you have a new installation of the SAP HANA Studio and the SAP Operational Process Intelligence 1.0 SP03
plugin is not installed, you could skip the following steps.
a.
3.
Open SAP HANA studio.
b.
Go to
c.
In the About HANA Studio dialog, choose Installation Details.
Help
About SAP HANA Studio
.
d.
On the Installed Software tab page, select Business Scenario Editor, Business Scenario Project, Phase
Editor, and Process Search Console and choose Uninstall .
e.
In the Uninstall dialog, select the above-mentioned features again, and choose Finish.
f.
Restart SAP HANA studio to make the uninstallation effective.
Upgrade SAP HANA Studio and SAP HANA Server from HANA 1.0 SPS08 to SAP HANA 1.0 SPS09 revision
90.
For more information, see the SAP HANA Upgrade Guide on SAP Help Portal at http://help.sap.com/
hana_appliance,
Installation and Upgrade Information
SAP Operational Process Intelligence Installation and Upgrade Guide
Upgrading SAP Operational Process Intelligence to 1.0 SP04
SAP HANA Update Guides .
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
33
4.
If you are upgrading from SAP OPInt 1.0 SP02 to SAP OPInt 1.0 SP04 or higher, perform the following
substeps:
a.
In the HANA system, create the following stored procedure:
create procedure "SYS_PROCESS_VISIBILITY"."UPGRADE_SP4_SCRIPT" ( )
language SQLSCRIPT sql security definer default schema "SYSTEM" as CURSOR
c_scn_data
FOR SELECT DISTINCT TABLE_NAME FROM "PUBLIC"."COLUMNS" WHERE SCHEMA_NAME =
'SYS_PROCESS_VISIBILITY'
AND (TABLE_NAME LIKE '%_EVT' OR TABLE_NAME LIKE '%_BUF')
AND COLUMN_NAME = 'EVENT_KEY'
AND "DATA_TYPE_NAME" <> 'BIGINT';
BEGIN FOR
cur_rec as c_scn_data DO exec('ALTER TABLE "SYS_PROCESS_VISIBILITY"."' ||
cur_rec."TABLE_NAME" || '" ALTER ("EVENT_KEY" BIGINT)');
END FOR;
exec('ALTER TABLE "SYS_PROCESS_VISIBILITY"."sap.opi.pv::SPVD_PHASE_METADATA"
ALTER ("EVENT_KEY" BIGINT)');
exec('ALTER TABLE "SYS_PROCESS_VISIBILITY"."sap.opi.pv::SPVD_EVENT_METADATA"
ALTER ("EVENT_KEY" BIGINT)');
exec('ALTER TABLE "SYS_PROCESS_VISIBILITY"."sap.opi.pv::SPVD_SCENARIO_METADATA"
ALTER ("EVENT_KEY" BIGINT)');
END;
b.
5.
Call the stored procedure, "SYS_PROCESS_VISIBILITY"."UPGRADE_SP4_SCRIPT".
Import the SAP Operational Process Intelligence 1.0 SP04 delivery units into the SAP HANA System.
For more information, see Installing SAP Operational Process Intelligence [page 8].
6.
In the SAP HANA Studio, install the SAP Operational Process Intelligence 1.0 SP04 plugins from the SAP
Operational Process Intelligence update site: http://<host>:<port>/sap/opi/pv/updatesite, where <host> is
your SAP HANA server host, and <port> is 80 followed by your SAP HANA server instance number
7.
Open the package that contains your business scenarios, and generate the scenarios in SAP Operational
Process Intelligence 1.0 SP04.
For more information, see the Generating a Business Scenario topic on Developers Guide.
8.
Configure the SAP Operational Process Intelligence scheduler.
For more information, see Configuring the SAP Operational Process Intelligence Scheduler [page 18].
9.
34
Start the jobs you scheduled during the scheduler configuration (see Scheduling the Notification Job [page
20]).
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP Operational Process Intelligence Installation and Upgrade Guide
Upgrading SAP Operational Process Intelligence to 1.0 SP04
8
Product Restrictions
Lifecycle Management of Scenarios
●
If the process implementation in a provider system changes, then the business scenario model can be reimported. Some associated definitions, such as the scenario cycle time and phase cycle time, need to be
redefined to suit the re-imported definition.
●
Generating artifacts of a business scenario might fail if generation for more than one business scenario is
triggered simultaneously, and for each business scenario the source system is mapped to a different
schema. Note that this issue exists only sporadically, and also when the generation is done by two solution
developers or solution architects at the same time. Not all created artifacts are rolled back if the generation
fails.
Workaround: If you experience this error, ensure that no other generation is taking place at the same time and
try to generate the scenario again.
●
Business scenarios with business situations using HRF rules for detection cannot be transported directly to
another target SAP HANA system.
Workaround: Import the delivery unit without activating the objects within. Activate and generate the HRF
vocabulary and rule artifacts after the import. Then, activate all other artifacts from the imported package.
General Constraints
●
Free text search - Wild card search is not supported (*, ?, and %, for example).
●
Not all types of events from process definitions from provider systems are observable. For more information
about which process events are observable for each provider system type, see Configuring Provider System
Scenarios [page 29].
●
Recommended screen resolution for the space.me workspace of SAP Operational Process Intelligence is
1200x800 or higher.
Supported Browsers
●
Microsoft Internet Explorer 9 and higher
●
Mozilla Firefox 10 and higher
●
Safari 5.1 (for Apple iOS)
●
Google Chrome 20 and higher
SAP Operational Process Intelligence Installation and Upgrade Guide
Product Restrictions
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
35
Supported Operation Systems
SAP HANA Studio 1.0 SPS07 is supported on the following:
●
Microsoft Windows XP - 32-bit and 64-bit
●
Microsoft Windows Vista - 32-bit and 64-bit
●
Microsoft Windows 7 - 32-bit and 64-bit
●
SUSE Linux Enterprise Server SLES 11: x86 64-bit version
The SAP HANA platform is supported on SUSE Linux Enterprise Server SLES 11: x86 64-bit version.
36
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP Operational Process Intelligence Installation and Upgrade Guide
Product Restrictions
9
Reference
Table 14:
Description
Link
Release Information about SAP Operational Process Intelli
gence 1.0 SP04
SAP Note ??? (not yet created)
SAP HANA Installation and Upgrade information
http://help.sap.com/hana_appliance
Compatibility information for SAP HANA and SAP Operational
Process Intelligence revisions
SAP Note 2029252
SAP Operational Process Intelligence - error log and exception SAP Note 1886292
handling information
SAP Operational Process Intelligence 1.0 documentation on
the help portal
SAP Operational Process Intelligence Installation and Upgrade Guide
Reference
http://help.sap.com/hana-opint
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
37
Important Disclaimers and Legal Information
Coding Samples
Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system
environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and
completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP
intentionally or by SAP's gross negligence.
Accessibility
The information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a
binding guideline on how to ensure accessibility of software products. SAP in particular disclaims any liability in relation to this document. This disclaimer, however, does
not apply in cases of wilful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of SAP.
Gender-Neutral Language
As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales
person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not
exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.
Internet Hyperlinks
The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not
warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages
caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for transparency
(see: http://help.sap.com/disclaimer).
38
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP Operational Process Intelligence Installation and Upgrade Guide
Important Disclaimers and Legal Information
SAP Operational Process Intelligence Installation and Upgrade Guide
Important Disclaimers and Legal Information
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
39
www.sap.com/contactsap
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any
form or for any purpose without the express permission of SAP SE
or an SAP affiliate company. The information contained herein may
be changed without prior notice.
Some software products marketed by SAP SE and its distributors
contain proprietary software components of other software
vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company
for informational purposes only, without representation or warranty
of any kind, and SAP or its affiliated companies shall not be liable for
errors or omissions with respect to the materials. The only
warranties for SAP or SAP affiliate company products and services
are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein
should be construed as constituting an additional warranty.
SAP and other SAP products and services mentioned herein as well
as their respective logos are trademarks or registered trademarks
of SAP SE (or an SAP affiliate company) in Germany and other
countries. All other product and service names mentioned are the
trademarks of their respective companies.
Please see http://www.sap.com/corporate-en/legal/copyright/
index.epx for additional trademark information and notices.