SAP BPA Quick Install Guide

Version 9.0.12.1
Table of Contents
1. Preparation for SAP NetWeaver ................................................................................................................. 1
1.1 Checking Hardware and Software Requirements ................................................................................. 1
Required Support Package Stack ................................................................................................... 1
1.2 Preparing the Installation Files ......................................................................................................... 1
2. Prerequisites for SAP NetWeaver ............................................................................................................... 3
Installation Prerequisites ...................................................................................................................... 3
3. Installation on SAP NetWeaver .................................................................................................................. 4
Purpose ............................................................................................................................................ 4
Process Flow ..................................................................................................................................... 4
Deliverables ...................................................................................................................................... 4
Prerequisites ..................................................................................................................................... 5
Procedure ......................................................................................................................................... 5
Determine if Usage Type JOB-SCHED is installed ........................................................................... 5
Installing SAP BPA .................................................................................................................... 5
Assigning Privileges ................................................................................................................... 6
Determine Upgrade Path .............................................................................................................. 6
Upgrading ETPRJSCHEDULER<SP Level>_<Patch Level>-XXXXXXXX.SCA using Telnet Adminis-
tration Console .......................................................................................................................... 6
Starting & Stopping SAP BPA ...................................................................................................... 6
3.1 Installation on SAP NetWeaver Version 7.30 and Later ......................................................................... 7
Purpose .................................................................................................................................... 7
Process Flow ............................................................................................................................. 7
Prerequisites ............................................................................................................................. 7
Procedure ................................................................................................................................. 7
3.2 Creating Roles in SAP NetWeaver .................................................................................................... 8
Use ......................................................................................................................................... 8
Prerequisites ............................................................................................................................ 11
Procedure ............................................................................................................................... 11
Example ................................................................................................................................. 12
3.3 Creating Users in SAP NetWeaver .................................................................................................. 14
Use ........................................................................................................................................ 14
Prerequisites ............................................................................................................................ 15
Procedure ............................................................................................................................... 15
See Also ................................................................................................................................. 16
3.4 Assigning Isolation Groups in SAP NetWeaver ................................................................................. 16
Use ........................................................................................................................................ 16
Prerequisites ............................................................................................................................ 16
Procedure ............................................................................................................................... 16
3.5 Installing a License ...................................................................................................................... 17
Use ........................................................................................................................................ 17
Prerequisites ............................................................................................................................ 17
Procedure ............................................................................................................................... 17
4. Copyright and Trademarks ...................................................................................................................... 19
...................................................................................................................................................... 19

iii
Chapter 1. Preparation for SAP
NetWeaver
Before you start the installation and configuration of the central SAP BPA server system, you have to complete
the following steps:

1. Check the requirements for the central SAP BPA server system. See Checking Hardware and Software Re-
quirements.

2. Prepare the installation files. See Preparing the Installation Files.

1.1 Checking Hardware and Software Require-

ments
The following table lists the requirements.

The installation host for the central SAP BPA server system must meet the following requirements:

Requirement Type Requirement

Hardware requirements
Software requirements
Database requirements
Disk space: 150 MB
For the supported operating system releases, see the Product Availability
Matrix on SAP Service Marketplace at service.sap.com/pam.
Support Package Stack (SPS) applied to the SAP Systems. See the Required
Support Package Stack section of Chapter 3.
All databases supported by SAP NetWeaver are supported.

Required Support Package Stack

You should upgrade the SAP System on the central SAP BPA server installation host to the necessary SPS level
as outlined in the table below:

Required SPS Level (Central Scheduling System)

Release Number SPS Number

730 0

To get consistent job handling on the satellite systems, you should upgrade the satellite systems in question to the
latest Support Package Stack.

1.2 Preparing the Installation Files

1. Download the installation file.
The file is available on SAP Service Marketplace at: service.sap.com/swdc -> Download -> Support Packages
and Patches -> Entry by Application Group -> SAP NetWeaver -> SAP NETWEAVER -> SAP NETWEAVER
7.0 -> SAP Central Process Scheduling by Redwood -> SAP BPA for NW 7.0

2. Download the following file:

1
 Preparation for SAP NetWeaver

a. ETPRJSCHEDULER<SP Level>_<Patch Level>-XXXXXXXX.SCA

Note
Login credentials are required to access the website.

2
Chapter 2. Prerequisites for SAP
NetWeaver
Installation Prerequisites
A fully functional and supported SAP NetWeaver 7.30 or higher installation; see the Choose Your Installation
Hosts topic ( see the Administration Guide ) for more information.

Hostname and HTTP port number for NetWeaver applications. The default HTTP port number is 50000.

SAP username/password for the NetWeaver application server with privileges to deploy Software and cre-
ate/modify SAP users and roles.

The following deliverable:

File Description
ETPRJSCHEDULER<SP Level>_<Patch Level>- Scheduler software with GUI
XXXXXXXX.SCA

3
Chapter 3. Installation on SAP NetWeaver
Purpose
This section tells you how to install and configure the central SAP BPA server system on Windows and UNIX.
You need direct access to the NetWeaver system to perform the deployment procedure described below.

Process Flow
1. You download and deploy the ETPRJSCHEDULER<SP Level>_<Patch Level>-XXXXXXXX.SCA.

2. You assign administrative privileges to a user, via a role, in UME.

3. You request and install a license for SAP BPA.

Deliverables
File Description Required
ETPRJSCHEDULER<SP Level>_<Patch Level>- Scheduler software with GUI Always
XXXXXXXX.SCA.

You deploy the SCA file using the Java Support Package Manager (JSPM). You have to deploy the SCA file as
a new software component.

You deploy SDA files using Software Deployment Manager (SDM).

For more information on starting JSPM, please see Starting JSPM [http://help.sap.com/saphelp_nwpi71/helpdata/-
en/87/4797422930c56ae10000000a155106/frameset.htm].

To deploy a file using JSPM, you need to know the location of the JSPM Inbox Directory, perform the following
command to detect it:
sappfpar pf=<install_directory>:\usr\sap\<SID>\SYS\profile\<SID>_<Central instance name>_<host> DIR_EPS_ROOT

Note
Ensure this directory only contains packages that you want to install at this moment as JSPM will install all
packages in contained in this directory, by default. You can choose to skip one or more packages, the SAP
BPA package is named redwood.com/&package;.

You use the SCA file to deploy the following actions in AS Java:

AccessScheduler - access SAP BPA

ManageScheduler - administrative privileges in SAP BPA

ManageSchedulerIsolation - isolation group administrator (same as scheduler-isolation-

administrator role) used in combination with AccessScheduler; you are not allowed to grant the ManageS-
cheduler action to the same role.

AccessSchedulerBusiness - Access SAP BPA as a Business user

4
 Installation on SAP NetWeaver

AccessSchedulerOperations - Access SAP BPA as a technical user

AccessSchedulerGlobalMonitor - Access SAP BPA as a Global monitor User

AccessSchedulerBusinessApplicationEnabler - Access SAP BPA as a BAE user

These actions contain the permissions for SAP BPA that need to be granted to roles.

You use the SDA file to deploy a scripting environment which allows you to use RedwoodScript ( see the Admin-
istration Guide ); a Java-based scripting language with a subset of Java classes. RedwoodScript can be used in a
Shell as well as in jobs to interact with the central SAP BPA server. Please refer to the Administration Guide for
more details.

The Scripting Module is delivered with extensive API documentation, which is available when you have the
Chargeable version. If you have the Chargeable version but no API documentation, please contact SAP.. Please
contact your Sales Representative if you require the Scripting Module, which is shipped with the Chargeable version.

Note that the following actions should not be used:

scheduler-ear/scheduler-administrator

scheduler-ear/scheduler-isolation-administrator

scheduler.ear/scheduler-user

Prerequisites
JSPM Inbox Directory

<SAPSID>adm credentials

SDM needs to be started and available, only one connection to the SDM is allowed at any given time.

SUM 1.0 SP09 or later for upgrading with JOB-SCHED usage type installed

Procedure
Determine if Usage Type JOB-SCHED is installed
1. Navigate to http://<server>:<port>/utl/UsageTypesInfo.

2. Locate the line with UT Code JOB-SCHED. If there is no such line, then the usage type is not installed and
you proceed to Installing SAP BPA. If JOB-SCHED is installed, you proceed to Upgrading ETPRJSCHED-
ULER<SP Level>_<Patch Level>-XXXXXXXX.SCA when JOB-SCHED is Installed.

Installing SAP BPA

1. Copy the file to the desired target directory.

2. Start SUM and in the Specify Credentials roadmap step, log in as user <SAPSID>adm.

3. In the Select Target roadmap step, specify the location to the target directory.

4. Proceed to the Execution roadmap step

5
 Installation on SAP NetWeaver

5. Finally, make sure the deployment was successful

Assigning Privileges
See the Creating Roles in SAP NetWeaver topic for instructions.

Determine Upgrade Path

1. If SUM version is older than SUM 1.0 SP09 and JOB-SCHED usage type is installed, use Telnet Administration
Console as outlined below

2. If SUM version is older than SUM 1.0 SP09 and JOB-SCHED usage type is not installed, use Installing SAP
BPA

3. If SUM 1.0 SP09 or later is installed, use SUM as outlined in Installing SAP BPA above

Upgrading ETPRJSCHEDULER<SP Level>_<Patch Level>-

XXXXXXXX.SCA using Telnet Administration Console
1. Open the SAP Management Console (SAP MC).

2. From the Console Root, choose the system you want to administer.

3. Navigate to the to the Process Table node.

4. In the right-hand pane, select the ICM and choose AS Java Telnet from the context-menu.

a. The Telnet administration console is opened.

5. Authenticate yourself with valid credentials (user name and password).

6. Issue deploy /path/to/app/<file> on_deploy_error=stop

Note
Alternatively, you can issue the deploy command in a telnet client; issue telnet localhost
5<inst_nr>08. Some Windows releases no longer have a telnet client.

Starting & Stopping SAP BPA

When setup and configuration of SAP BPA have been finished, SAP BPA starts and stops together with the hosting
SAP NetWeaver AS Java. Starting and stopping SAP NetWeaver AS Java is described in great detail in SAP Help
Portal. For more details, please see:

Starting and Stopping SAP NetWeaver ABAP and Java [http://help.sap.com/saphelp_nw70/helpdata/en/71/-

1c9a4267f9c66ae10000000a155106/frameset.htm]

Database Administration [http://help.sap.com/saphelp_nw70/helpdata/en/29/7d4ed11dc11d45a73850df6e8a1bac/-

frameset.htm]

6
 Installation on SAP NetWeaver

3.1 Installation on SAP NetWeaver Version 7.30

and Later
Purpose
This section tells you how to install and configure the central SAP BPA server system on Windows and UNIX.
You need direct access to the NetWeaver system to perform the deployment procedure described below.

Process Flow
1. You check to see if you installed the JOB-SCHED usage type.

2. You deploy the deliverable.

3. You assign administrative privileges to a user, via a role or group, in UME. See Chapter 5.4 Creating Roles
in SAP NetWeaver.

4. You request and install a license for SAP BPA. See Chapter 5.6 Installing a License.

5. You connect the central SAP BPA server system to remote systems. See Chapter 6.2 Connecting to Remote
SAP Systems ( see the Administration Guide ).

Prerequisites
SAP NetWeaver 7.30

SUM 1.0 SP09 or later for upgrading with JOB-SCHED usage type installed

Procedure
Determine if Usage Type JOB-SCHED is installed
1. Navigate to http://<server>:<port>/utl/UsageTypesInfo.

2. Locate the line with UT Code JOB-SCHED. If there is no such line, then the usage type is not installed and
you proceed to Installing SAP BPA. If JOB-SCHED is installed, you proceed to Upgrading ETPRJSCHED-
ULER<SP Level>_<Patch Level>-XXXXXXXX.SCA when JOB-SCHED is Installed.

Installing SAP BPA

1. Copy the file to the desired target directory.

2. Start SUM and in the Specify Credentials roadmap step, log in as user <SAPSID>adm.

3. In the Select Target roadmap step, specify the location to the target directory.

4. Proceed to the Execution roadmap step

5. Finally, make sure the deployment was successful

7
 Installation on SAP NetWeaver

Assigning Privileges
See the Creating Roles in SAP NetWeaver topic for instructions.

Determine Upgrade Path

1. If SUM version is older than SUM 1.0 SP09 and JOB-SCHED usage type is installed, use Telnet Administration
Console as outlined below

2. If SUM version is older than SUM 1.0 SP09 and JOB-SCHED usage type is not installed, use Installing SAP
BPA

3. If SUM 1.0 SP09 or later is installed, use SUM as outlined in Installing SAP BPA above

Upgrading ETPRJSCHEDULER<SP Level>_<Patch Level>-

XXXXXXXX.SCA using Telnet Administration Console
1. Open the SAP Management Console (SAP MC).

2. From the Console Root, choose the system you want to administer.

3. Navigate to the to the Process Table node.

4. In the right-hand pane, select the ICM and choose AS Java Telnet from the context-menu.

a. The Telnet administration console is opened.

5. Authenticate yourself with valid credentials (user name and password).

6. Issue deploy /path/to/app/<file> on_deploy_error=stop

Note
Alternatively, you can issue the deploy command in a telnet client; issue telnet localhost
5<inst_nr>08. Some Windows releases no longer have a telnet client available by default.

Starting & Stopping SAP BPA

When setup and configuration of SAP BPA have been finished, SAP BPA starts and stops together with the hosting
SAP NetWeaver AS Java. Starting and stopping SAP NetWeaver AS Java is described in great detail in SAP Help
Portal. For more details, please see:

Starting and Stopping SAP NetWeaver ABAP and Java [http://help.sap.com/saphelp_nw70/helpdata/en/71/-

1c9a4267f9c66ae10000000a155106/frameset.htm]

3.2 Creating Roles in SAP NetWeaver

Use
A role is a set or group of privileges that can be granted to users or other roles. Roles are part of the Security section
in the navigation bar.

The following core roles are provided with SAP BPA:

8
 Installation on SAP NetWeaver

Core roles (always required):

scheduler-administrator - can perform all actions, except manage isolation groups

scheduler-bae-only-user - indicates that the user account is restricted to logging on via the SAP Inbound
interface, only.

scheduler-isolation-administrator - can create/edit/delete isolation groups and add users to

these.

scheduler-screen-reader - indicates that you are using a screen reader

scheduler-user - has access to SAP BPA only, cannot see any objects (always required, even for admin-
istrators)

scheduler-viewer - read only access to all objects

The user access roles are bound to features that require a specific license key:

scheduler-business-user - can access the business-user-centric user interface

scheduler-it-user - can access the it-user-centric user interface

scheduler-global-monitor-user - can this user use the global monitor

Predefined roles (optional):

scheduler-event-operator - can raise events

scheduler-job-administrator - can create/edit/delete event definitions, process definitions, process

chains and modify processes

Note
The roles scheduler-business-user and scheduler-it-user are used by the Financial Process
Automation module.

Note
If you get an HTTP error 403 - Access Denied after logging in, your user may be lacking the
scheduler-user role.

These are the standard roles, it is not possible to edit the standard roles. You create a role with the corresponding
name in the UME, assign it the AccessScheduler action and grant it to SAP BPA users. Once you grant these roles
to users in the UME, the users will get the corresponding SAP BPA roles granted and have the privileges granted
to these roles as soon as they log in or the isolation administrator adds them to an isolation group.

The UME also allows you to grant SAP BPA privileges directly to roles via the following actions:

AccessScheduler - read-only access, all roles that you want to use in SAP BPA must have this action as-
signed.

ManageScheduler - scheduler Administrator (same as scheduler-administrator role) used in

combination with AccessScheduler

9
 Installation on SAP NetWeaver

ManageSchedulerIsolation - isolation group administrator (same as scheduler-isolation-

administrator role) used in combination with AccessScheduler; you are not allowed to grant the ManageS-
cheduler action to the same role.

AccessSchedulerBusiness - Access SAP BPA as a Business user

AccessSchedulerOperations - Access SAP BPA as a technical user

AccessSchedulerGlobalMonitor - Access SAP BPA as a Global monitor User

AccessSchedulerBusinessApplicationEnabler - Access SAP BPA as a BAE user

SAP strongly recommends you start by creating the above roles in the UME and assign them the AccessScheduler
action. Once that is done, you grant these roles to users. If the roles do not exactly suit your needs, create custom
roles (with names that do not match the above roles) in the UME and assign them the same action; these roles will
be editable in SAP BPA and allow you to extend privileges of users.

Note that the following actions should not be used:

scheduler-ear/scheduler-administrator

scheduler-ear/scheduler-isolation-administrator

scheduler.ear/scheduler-user

Accessibility
SAP BPA has been tested with the JAWS screen-reader for the visually impaired. When you want to use a screen-
reader, you have the following options, depending on your application server:

SAP NetWeaver - SAP UME allows you to set a property for visually impaired users, this property is supported
by SAP BPA

Other supported application servers - you use the scheduler-screen-reader role or append &sap-
accessibility=X in the URL. Note that the use of the role is highly recommended. Despite what the name
might suggest, the URL parameter is supported on all supported application servers, and is designed for testing
purposes.

Restricting BAE Users

You have the Business Automation Enabler Module and would like to prevent a user created specifically for the
BAE interface from logging-on from other interfaces (for example the web interface).

You grant that user the following roles and this user will only be able to access SAP BPA via the BAE interface
(SAP Inbound objects):

scheduler-user - has access to SAP BPA only, cannot see any objects.

scheduler-bae-only-user - indicates that the user account is restricted to logging on via the SAP Inbound
interface, only.

Granting Privileges
You can grant privileges to custom roles. Custom roles are recognizable by the name (it is not allowed to be one
of the above) as well as the description and comment fields, which contain Created automatically on first login.

Some privileges are not dependent on a partition or isolation group, these are known as global Privileges.

10
 Installation on SAP NetWeaver

You grant specific privileges to roles for each object type; available privileges are dependent on the object. These
privileges are known as system privileges and are granted via the role object. There are two levels at which you
can grant system privileges, Access and Admin. Privileges granted with the Admin level allow the grantee to grant
the privileges to other users.

You can also grant privileges for specific objects on object-level to users or roles, these are known as object privileges
and are granted via the Security tab on the object.

The following topics in the Security Guide and Administration Guide provide more information on privileges and
how you grant them:

System Privileges ( see the Administration Guide )

Object Privileges ( see the Administration Guide )

Granting and Revoking System Privileges ( see the Administration Guide )

Granting or Revoking Object Privileges ( see the Administration Guide )

Prerequisites
The URL to the NetWeaver UME. Usually http://<host>:<port>/useradmin

An account with sufficient privileges to create a role and add members to the role.

The username and password of a user you add to the role.

A Scheduler Manager user account for SAP BPA

Procedure
Creating a role to map to a SAP BPA role

1. Connect to the UME in SAP NetWeaver where SAP BPA was installed.

2. Choose Role in the drop-down box for Search Criteria.

3. Choose Create Role and enter a name of one of the SAP BPA roles into the Unique Name field.

4. Choose the Assigned Actions tab.

5. Search for scheduler and choose the action name AccessScheduler, choose Add and Save.

6. Log out of the UME.

Creating a custom role to manage isolation groups in the UME

1. Connect to the UME in SAP NetWeaver where SAP BPA was installed.

2. Choose Role in the drop-down box for Search Criteria.

3. Choose Create Role and enter a role name in the Unique Name field, SAP recommends to prefix the role
name with scheduler as it will be easier to distinguish the role fro other roles in the UME .

4. Choose the Assigned Actions tab.

5. Search for scheduler and choose the action names AccessScheduler and ManageSchedulerIsolation.

11
 Installation on SAP NetWeaver

6. Choose Add and Save.

7. Log out of the UME.

Editing a custom role in SAP BPA

1. Navigate to Security > Roles.

2. Choose Edit from the context-menu of an editable role.

Editable roles have a description: Created automatically on first login.

3. On the Assign Privileges tab, choose an Object definition and then Next.

4. Choose the desired range of the privileges.

5. Choose a Rank with the desired privileges.

Admin privileges allow the user to perform the action and to grant the privilege to others as well.
Access privileges allow the user to perform the actions.

Assigning a user to a role

1. Connect to the UME in SAP NetWeaver where SAP BPA was installed.

2. Fill in the Search Criteria field and locate the user.

3. Choose the user, and choose the Assigned Roles tab.

4. Search for one of the roles previously created, and choose Add.

5. Choose Add and Save.

6. Log out of the UME.

Values
Assign Privileges

Object Definition - The role name.

Grantable - If this option is selected, the user can grant this role to any other user.

Assigned Global Privileges

Granted Subject - The privilege name.

Grantable - If this option is selected, the user can grant this privilege to any other user.

Example
Create a Role to access SAP BPA
The URL to the NetWeaver UME http://sapnwprd.masalan.com:50200/useradmin

The account with sufficient privileges to create a role and add members to the role is Administrator

The username and password of the user to add to the role is masalan and process1 respectively, created previ-
ously.

12
 Installation on SAP NetWeaver

The Scheduler Manager user account is ProcAdmin.

Creating a role that maps to the scheduler-event-operator SAP BPA role

1. Connect to http://sapnwprd.masalan.com:50200/useradmin using the Administrator login

2. Choose Role in the drop-down box for Search Criteria.

3. Choose Create Role and enter scheduler-event-operator into the Unique Name field.

4. Choose the Assigned Actions tab.

5. Search for scheduler and choose the action name AccessScheduler, choose Add and Save.

6. Log out of the UME.

Custom Roles
Custom roles must allow users to see all properties of objects they are supposed to. This means that if you want
the user to be able to see processes, the user needs to be able to see the process definition, queue and process
server as well as have View privileges for DatumDefinition on system-level.

Note that shared objects reside in the GLOBAL partition and might also require privileges, for example, all users
should be able to see the GLOBAL.Custom library, as this is used by processes as well as period functions, for
example.

Example
The typical viewer user could have the following privileges (note that Rank is always View in this example):

Object Level
Application Partition
Credential Partition
CredentialProtocol Partition
DatumDefinition System
EventDefinition Partition
Export > Export Partition
Export > Export with related objects Partition including referenced objects
Promote > Promote to system Promote the object to a remote system
Promote > Edit further then promote Exit the export rule set prior to promoting
ExportRuleSet Partition
Format Partition
ImportRuleDefinition Partition
ImportRuleSet Partition
ImportSource Partition
JobDefinition Partition
JobLock Partition
Job Partition
Library

13
 Installation on SAP NetWeaver

NavigationBar Partition
PeriodFunction Partition
ProcessServer Partition
Queue Partition
Report Partition
Resource Partition
SAPSystem Partition
SubmitFrame Partition
TableDefinition Partition
Table Partition
TimeWindow Partition

3.3 Creating Users in SAP NetWeaver

Use
User objects represent users of the system and can have roles granted to them in order to have privileges to perform
actions.

Users are part of the Security section in the navigation bar. The following standard users are provided with SAP
BPA:

Redwood System - a user that represents the system.

Users are imported automatically from the SAP User Management Engine (UME) as soon as they log in for the
first time and kept in sync with UME at each login. This synchronization only occurs one way, from UME to SAP
BPA. Users are created in UME and cannot be created in SAP BPA. They must have the following action assigned
to at least one of their roles to get access:

AccessScheduler

Administrator users additionally have the UME role scheduler-administrator or the following action
assigned to one of their roles:

ManageScheduler

The following table lists all scheduler-related actions in the UME:

The following table lists the default actions are available in SAP UME.

Action Description Core Role

AccessScheduler
ManageScheduler
ManageSchedulerIsolation
AccessSchedulerBusiness
AccessSchedulerOperations
AccessSchedulerGlobalMonitor
Access Scheduler scheduler-user
Manage the Scheduler scheduler-administrator
Manage Scheduler Isolation scheduler-isolation-administrator
Access Scheduler as a Business user scheduler-business-user
Access Scheduler as a IT user scheduler-it-user
Access Scheduler as a Global monitor scheduler-globalMonitor-user
User

14
 Installation on SAP NetWeaver

AccessSchedulerBusinessApplication- Access Scheduler as a BAE user scheduler-bae-user

Enabler

The following table lists the default roles are available in SAP UME.

Role Assigned Actions

Administrator AccessScheduler ManageScheduler ManageSchedulerIsolation

To view all the available users, choose Security > Users in the Navigation bar.

You can enable and disable login for a user; when you disable login for a user, the user will be notified at the next
login attempt that the user has no access to the system.

Prerequisites
A user account and password with appropriate privileges for managing users in the SAP NetWeaver system
where SAP BPA was installed.

The URL to the User Management interface of the SAP NetWeaver system where SAP BPA was installed.

Procedure
Create a user in SAP NetWeaver UME

1. Connect to the User Management interface in SAP NetWeaver where SAP BPA was installed.

2. Choose Create User and fill in the data.

3. Add this user to at least one of the roles created during the installation of SAP BPA.

4. Log on with this user in SAP BPA.

Disable a user from logging into SAP BPA

1. Navigate to Security > Users.

2. Choose Disable Login from the context-menu of the user

Enable a user

1. Navigate to Security > Users.

2. Choose Enable Login from the context-menu of the user; you might be prompted for a username.

Delete a user

1. Navigate to Security > Users.

2. Choose Delete User from the context-menu of the user

Values
Name - The name of the user.

Description - The description of the user.

15
 Installation on SAP NetWeaver

Documentation - A comment about the user.

Creation Time - The time the user ID was created.

Last Modification time - The last time the user ID was modified.

See Also
Roles

3.4 Assigning Isolation Groups in SAP NetWeaver

Use
With an isolation group, a user is limited to interacting with objects of the same isolation group as well as objects
from the GLOBAL isolation group. You assign users to isolation groups ( see the Administration Guide ) in the
Security section in the navigation bar. The user must either have the role scheduler-isolation-adminis-
trator or a custom role granted which has the ManageSchedulerIsolation action to be able to add users to an
isolation group. Users can have multiple isolation groups; in this case, the user needs to choose an isolation group
for the session during login.

Note
In the OEM version, only one SAP client can be in an isolation group. This is governed by the value of the
ProcessServerService.SAP.limit license key ( see the Administration Guide ).

Tip
SAP does not recommend the use of isolation groups in the Chargeable version; these have been implemented
to adhere to the limitations of the OEM version and demand a high level of configuration. You can use par-
titions without isolation groups and rely on partition access privileges for isolation. A user cannot view objects
residing in a partition if the user cannot view the partition.

Prerequisites
the user needs the role scheduler-isolation-administrator or a custom role granted which has the AccessScheduler
and ManageSchedulerIsolation actions.

Procedure
Create an isolation group

1. Navigate to Security > Isolation Groups.

2. Choose New Isolation Group from the context-menu.

3. Enter a name for the isolation group. Names should be all upper case.

4. Choose Save & Close to exit edit dialog.

Assign an isolation group to users

1. Navigate to Security > Isolation Groups.

16
 Installation on SAP NetWeaver

2. Choose Import Users

3. Use the search dialog to locate users from the Authentication system, wildcards * and ? are allowed.

4. Select the users to import and choose Import.

5. Close the window when you are finished importing users into the isolation group.

3.5 Installing a License

Use
After a successful installation and login, you will be presented with the licensing page.
To request a license, follow the instructions on the screen: please create an OSS ticket and copy the license request
including ## BEGIN REQUEST ## and ## END REQUEST ## into the OSS ticket. Next, assign to component
XX-PART-REDWOOD-LKY and submit the ticket. You will receive your license via the OSS ticket.

Note
A OEM license is only available for installations on SAP NetWeaver.

You can also use the OEM license, which does not require you to send an email to Redwood Software. On the li-
censing page, you need to fill in your company name and choose Generate OEM License. Note that a lot of features
are disabled with the OEM license and your SAP instances are isolated from each other in SAP BPA; you can only
schedule jobs in one SAP System per session with a OEM license.
You can also use the OEM license, which does not require you to request a license. On the licensing page, you
need to fill in your company name and choose Generate OEM License. Note that a lot of features are disabled with
the OEM license. You can only schedule SAP systems and your SAP instances are isolated from each other in
SAP BPA; you can only schedule jobs in one SAP System per session.

Prerequisites
The full URL to the SAP BPA installation

An email account to request the license, which will be sent inline to that account.

Procedure
Generate a license request and install the license

1. Log on to SAP BPA

If the licensing page does not appear, or you want to install a new license, go to http://<serv-
er>:<port>/scheduler/ui/licence/request1.jsp

2. Fill in a company name and proceed to the following screen.

3. To request a license, follow the instructions on the screen: please create an OSS ticket and copy the license
request including ## BEGIN REQUEST ## and ## END REQUEST ## into the OSS ticket. Next, assign to
component XX-PART-REDWOOD-LKY and submit the ticket. You will receive your license via the OSS
ticket.

4. Once you have received the license, you can paste it into the following window.
If you closed the window, you may proceed to http://<server>:<port>/scheduler/ui/li-
cence/request3.jsp

17
 Installation on SAP NetWeaver

5. Paste the license into the License Key field and choose Activate License.

Use the OEM license

1. Log on to SAP BPA

If the licensing page does not appear, or you want to install a new license, proceed as follows; if you are on
the licensing page proceed to the last step.

a. Navigate to Configuration > License Keys

b. Choose Start License Manager from the context-menu

c. Choose Generate License Request

2. Fill in a company name and choose Generate OEM License.

18
Chapter 4. Copyright and Trademarks
Copyright 1993-2015 Redwood Technology B.V., Houten, The Netherlands. All rights reserved.

No part of this document may be reproduced by any mechanical, photographic or electronic process, photographic
recording, nor may it be stored in a retrieval system, transmitted or otherwise copied for public or private use,
without written permission from the publisher.

The information in this manual is subject to change without notice. Companies, names and data used in examples
herein are fictitious unless otherwise noted. If you find any problems in the documentation, please report them to
us in writing. Redwood Technology does not warrant that this document is error-free.

Redwood, Redwood Explorer, Cronacle, CronacleBeans, and Report2Web are trademarks of Redwood Technology
B.V.

SAP, SAP NetWeaver and all other SAP product and service names are trademarks or registered trademarks of
SAP AG in Germany and several other countries around the world. Oracle and SQL*Plus are registered trademarks
of Oracle Corporation. Oracle8i, Oracle 9i, Oracle 10g and PL/SQL are trademarks of Oracle Corporation. PostScript
and Portable Document Format are registered trademarks of Adobe Systems, Inc. Microsoft, MS-DOS, Windows,
ActiveX, Win32, and Win32s are either registered trademarks or trademarks of Microsoft Corporation in the U.S.A.
and/or other countries. Other trademarks and registered trademarks are the property of their respective owners.

19
Copyright 2015 SAP SE. 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. The information contained
herein may be changed without prior notice.
Some software products marketed by SAP AG and its
distributors contain proprietary software components of
other software vendors.
Microsoft, Windows, Outlook, and PowerPoint are
registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel
Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390,
OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP,
Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix,
i5/OS, POWER, POWER5, OpenPower and PowerPC are
trademarks or registered trademarks of IBM Corporation.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader
are either trademarks or registered trademarks of Adobe
Systems Incorporated in the United States and/or other
countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered
trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame,
WinFrame, VideoFrame, and MultiWin are trademarks or
registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or
registered trademarks of W3C, World Wide Web
Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems,
Inc., used under license for technology invented and
implemented by Netscape.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP
NetWeaver, and other SAP products and services
mentioned herein as well as their respective logos are
trademarks or registered trademarks of SAP AG in
Germany and in several other countries all over the world.
All other product and service names mentioned are the
trademarks of their respective companies. Data contained
in this document serves informational purposes only.
National product specifications may vary.
These materials are subject to change without notice.
These materials are provided by SAP AG and its affiliated
companies ("SAP Group") for informational purposes only,
without representation or warranty of any kind, and SAP
Group shall not be liable for errors or omissions with
respect to the materials. The only warranties for SAP
Group 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.
These materials are provided as is without a warranty of
any kind, either express or implied, including but not
limited to, the implied warranties of merchantability,
fitness for a particular purpose, or non-infringement.
SAP shall not be liable for damages of any kind including
without limitation direct, special, indirect, or consequential
damages that may result from the use of these materials.
SAP does not warrant the accuracy or completeness of the
information, text, graphics, links or other items contained
within these materials. SAP has no control over the
information that you may access through the use of hot
links contained in these materials and does not endorse
your use of third party web pages nor provide any warranty
whatsoever relating to third party web pages.
SAP NetWeaver How-to Guides are intended to simplify
the product implementation. While specific product
features and procedures typically are explained in a
practical business context, it is not implied that those
features and procedures are the only approach in solving a
specific business problem using SAP NetWeaver. Should
you wish to receive additional information, clarification or
support, please refer to SAP Consulting.
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 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, except
if such damages were caused by SAP intentionally or
grossly negligent.
Disclaimer
Some components of this product are based on Java. Any
code change in these components may cause unpredictable
and severe malfunctions and is therefore expressively
prohibited, as is any decompilation of these components.
Any Java Source Code delivered with this product is only
to be used by SAPs Support Services and may not be
modified or altered in any way.