Beruflich Dokumente
Kultur Dokumente
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.
The installation host for the central SAP BPA server system must meet the following requirements:
To get consistent job handling on the satellite systems, you should upgrade the satellite systems in question to the
latest Support Package Stack.
1
Preparation for SAP NetWeaver
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.
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.
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.
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:
4
Installation on SAP NetWeaver
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.
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.
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.
5
Installation on SAP NetWeaver
Assigning Privileges
See the Creating Roles in SAP NetWeaver topic for instructions.
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
2. From the Console Root, choose the system you want to administer.
4. In the right-hand pane, select the ICM and choose AS Java Telnet from the context-menu.
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.
6
Installation on SAP NetWeaver
Process Flow
1. You check to see if you installed the JOB-SCHED usage type.
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.
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.
7
Installation on SAP NetWeaver
Assigning Privileges
See the Creating Roles in SAP NetWeaver topic for instructions.
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
2. From the Console Root, choose the system you want to administer.
4. In the right-hand pane, select the ICM and choose AS Java Telnet from the context-menu.
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.
8
Installation on SAP NetWeaver
scheduler-bae-only-user - indicates that the user account is restricted to logging on via the SAP Inbound
interface, only.
scheduler-user - has access to SAP BPA only, cannot see any objects (always required, even for admin-
istrators)
The user access roles are bound to features that require a specific license key:
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.
9
Installation on SAP NetWeaver
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.
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.
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:
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.
Procedure
Creating a role to map to a SAP BPA role
1. Connect to the UME in SAP NetWeaver where SAP BPA was installed.
3. Choose Create Role and enter a name of one of the SAP BPA roles into the Unique Name field.
5. Search for scheduler and choose the action name AccessScheduler, choose Add and Save.
1. Connect to the UME in SAP NetWeaver where SAP BPA was installed.
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 .
5. Search for scheduler and choose the action names AccessScheduler and ManageSchedulerIsolation.
11
Installation on SAP NetWeaver
3. On the Assign Privileges tab, choose an Object definition and then Next.
1. Connect to the UME in SAP NetWeaver where SAP BPA was installed.
4. Search for one of the roles previously created, and choose Add.
Values
Assign Privileges
Grantable - If this option is selected, the user can grant this role to any other user.
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
3. Choose Create Role and enter scheduler-event-operator into the Unique Name field.
5. Search for scheduler and choose the action name AccessScheduler, choose Add and Save.
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
Users are part of the Security section in the navigation bar. The following standard users are provided with SAP
BPA:
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 the default actions are available in SAP UME.
14
Installation on SAP NetWeaver
The following table lists the default roles are available in SAP UME.
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.
3. Add this user to at least one of the roles created during the installation of SAP BPA.
Enable a user
2. Choose Enable Login from the context-menu of the user; you might be prompted for a username.
Delete a user
Values
Name - The name of the user.
15
Installation on SAP NetWeaver
Last Modification time - The last time the user ID was modified.
See Also
Roles
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
3. Enter a name for the isolation group. Names should be all upper case.
16
Installation on SAP NetWeaver
3. Use the search dialog to locate users from the Authentication system, wildcards * and ? are allowed.
5. Close the window when you are finished importing users into the isolation group.
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
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.
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 These materials are subject to change without notice.
No part of this publication may be reproduced or These materials are provided by SAP AG and its affiliated
transmitted in any form or for any purpose without the companies ("SAP Group") for informational purposes only,
express permission of SAP SE. The information contained without representation or warranty of any kind, and SAP
herein may be changed without prior notice. Group shall not be liable for errors or omissions with
Some software products marketed by SAP AG and its respect to the materials. The only warranties for SAP
distributors contain proprietary software components of Group products and services are those that are set forth in
other software vendors. the express warranty statements accompanying such
products and services, if any. Nothing herein should be
Microsoft, Windows, Outlook, and PowerPoint are
construed as constituting an additional warranty.
registered trademarks of Microsoft Corporation.
These materials are provided as is without a warranty of
IBM, DB2, DB2 Universal Database, OS/2, Parallel
any kind, either express or implied, including but not
Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390,
limited to, the implied warranties of merchantability,
OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP,
fitness for a particular purpose, or non-infringement.
Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix,
i5/OS, POWER, POWER5, OpenPower and PowerPC are SAP shall not be liable for damages of any kind including
trademarks or registered trademarks of IBM Corporation. without limitation direct, special, indirect, or consequential
damages that may result from the use of these materials.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader
are either trademarks or registered trademarks of Adobe SAP does not warrant the accuracy or completeness of the
Systems Incorporated in the United States and/or other information, text, graphics, links or other items contained
countries. within these materials. SAP has no control over the
information that you may access through the use of hot
Oracle is a registered trademark of Oracle Corporation.
links contained in these materials and does not endorse
UNIX, X/Open, OSF/1, and Motif are registered
your use of third party web pages nor provide any warranty
trademarks of the Open Group.
whatsoever relating to third party web pages.
Citrix, ICA, Program Neighborhood, MetaFrame,
SAP NetWeaver How-to Guides are intended to simplify
WinFrame, VideoFrame, and MultiWin are trademarks or
the product implementation. While specific product
registered trademarks of Citrix Systems, Inc.
features and procedures typically are explained in a
HTML, XML, XHTML and W3C are trademarks or practical business context, it is not implied that those
registered trademarks of W3C, World Wide Web features and procedures are the only approach in solving a
Consortium, Massachusetts Institute of Technology. specific business problem using SAP NetWeaver. Should
Java is a registered trademark of Sun Microsystems, Inc. you wish to receive additional information, clarification or
JavaScript is a registered trademark of Sun Microsystems, support, please refer to SAP Consulting.
Inc., used under license for technology invented and Any software coding and/or code lines / strings (Code)
implemented by Netscape. included in this documentation are only examples and are
MaxDB is a trademark of MySQL AB, Sweden. not intended to be used in a productive system
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP environment. The Code is only intended better explain and
NetWeaver, and other SAP products and services visualize the syntax and phrasing rules of certain coding.
mentioned herein as well as their respective logos are SAP does not warrant the correctness and completeness of
trademarks or registered trademarks of SAP AG in the Code given herein, and SAP shall not be liable for
Germany and in several other countries all over the world. errors or damages caused by the usage of the Code, except
All other product and service names mentioned are the if such damages were caused by SAP intentionally or
trademarks of their respective companies. Data contained grossly negligent.
in this document serves informational purposes only. Disclaimer
National product specifications may vary. 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.