CPS1

Central Process Scheduling on SAP Netwaever 2012
Table of Contents
1. General Description......................................................................................................................... 2
1.1 CPS Overview............................................................................................................................................. 2
1.2 SAP Partnership with Redwood.................................................................................................................. 2
1.3 Operational Excellence and Business Support........................................................................................... 2
2. Installation Procedure...................................................................................................................... 3
2.1
2.2
2.3
2.4
2.5
2.6
2.7
Pre-Requisites............................................................................................................................................ 3
Installation Options..................................................................................................................................... 4
Architecture Overview................................................................................................................................. 5
Versions and Scope.................................................................................................................................... 6
Installation Preparation Steps..................................................................................................................... 7
Standard Configuration Steps in SPRO.................................................................................................... 15
Integration Steps in SPRO........................................................................................................................ 25
3. Key Features of the Application....................................................................................................34

3.1
3.2
3.3
3.4
3.5
3.6
3.7
3.8
User Interface........................................................................................................................................... 34
Scripts ..35
Job Chains................................................................................................................................................ 36
Events .. 37
Calendars.................................................................................................................................................. 38
Jobs and Queues...................................................................................................................................... 41
SAP Business Objects Integration............................................................................................................ 42
Web Services Integration.......................................................................................................................... 43
4. Comparison with CCMS Scheduling.............................................................................................44

5. Features and Benefits.................................................................................................................... 44
6. Specific Business Scenarios.........................................................................................................45
6.1
6.2
6.3
6.4
Parallel Processing................................................................................................................................... 45
Many to One Relationship......................................................................................................................... 46
Lock Mechanism....................................................................................................................................... 47
Restart Behavior....................................................................................................................................... 48
7. Frequently Asked Questions......................................................................................................... 49

8. References...................................................................................................................................... 50
Created By: r.jhalani@accenture.com
Page 1
1.
General Description
The SAP Central Process Scheduling application by Redwood leverages the SAP Solution Manager application
management solution platform to centralize process scheduling, resulting in powerful functionality for crossapplication automation and process management and control.
1.1
CPS Overview
Central Process Scheduling is an adaptive and scalable application that provides the real-time, eventdriven scheduling and process automation.
Centrally manages and orchestrates processes across multiple applications and organizations.
Provides seamless integration with SAP and non-SAP applications.
Provides integration with the native SAP management tools like Solution Manager and CCMS.
Aligns IT Processes to business needs
1.2
1.3
SAP Partnership with Redwood
SAP CPS is the only Enterprise Process Scheduling solution sold and supported by SAP.
Redwood and SAP software engineers work together in Walldorf and The Netherlands for creating the
new process automation standard for SAP customers and providing Strategic direction for SAP
application automation and management.
CPS enables SAP components to cross system boundaries in order to implement end-to-end Business
Process Automation
CPS holds a unique position as a core and default component of SAP NetWeaver platform
It can be upgraded by licenses from SAP for wider capabilities
Support calls
o
Dedicated OSS component for SAP CPS
SAP Active Global Support is first level support.
SAP support connection is used for troubleshooting.
In case development support is needed, SAP passes call to Redwood.
The software, patches and documentation are delivered by SAP and can be downloaded from SAP
Service Market Place.
Operational Excellence and Business Support
The following picture shows the operational benefits and Business Support of using SAP CPS tool.
Page 2
Figure 1-1: Business Support and Operation Excellence
2.
2.1
Installation Procedure
Pre-Requisites
The installation host for the SAP CPS system must meet the following requirements:
To manage a base line workload of 100k jobs per day, with 10 million jobs retained in the history data, more than
95% of jobs producing average log file size of 10k and no large output files, the following table shows the sizing
requirements:
Page 3
Table 2-1: Sizing Requirements on SAP host

The installation of SAP CPS requires a Netweaver 7.00 Application Server System containing a Java stack (see
the below list for required SPS). If this prerequisite is not satisfied then you should upgrade the SAP System on
the Central Scheduler installation host to the necessary SPS levels:
Table 2-2: Required SPS Level (Central Scheduling System)
2.2
Installation Options
There are various options available for the installation of SAP CPS. Each of these options will be covered as the
scope of this implementation guide is only limited to deployment of the tool on SAP Solution Manager System:
1. Installation into a standalone Netweaver system (single Java stack, single node) which has no additional
software deployed
2. Installation into an existing Netweaver system which contains a dual stack
3. Installation into an existing Netweaver system e.g. Solution Manager which contains a Java stack
Page 4
Redwood strongly recommends option 1, especially when you are installing the production instance of SAP
CPS.
The main reason for this is the fact that because SAP CPS is a mission critical component of the Scheduling
landscape it is important that the availability of the environment is not compromised by any other software
deployed in the Netweaver stack. The same goes for the choice for a single Java stack system because there will
be no reason to have an ABAP stack available as no ABAP jobs will be executed. A multiple node configuration is
also not required as this causes additional overhead for the scheduler that is not recommended.
ADVISE: Choose option 2 or 3 for a test/development environment if required but only option 1 for a production
environment. But if the landscape allows the installation on SAP Solution Manager then few additional settings
are required to be activated which will be covered in detail in this guide.
2.3
Architecture Overview
The product is a J2EE web application that runs on SAP Netweaver Web Application Server Java. It stores its
data in the default database for the application server, and supports all databases listed in the SAP NW Product
Availability Matrix.
Figure 2-1: CPS Architecture on Standalone Java Engine
Page 5
Figure 2-2: CPS Architecture on Netweaver Integrated Java Engine

It can connect to SAP systems using XBP and JXBP, run OS jobs and connect to other systems and applications.
The basic version includes functionality to connect to SAP systems using XBP and JXBP. Other functionality is
available by purchasing the enterprise version.
Table 2-3: XBP version information
2.4
Versions and Scope
SAP Central Process Scheduling by Redwood exists as:

1. Standalone Java Version:
Current Version: M33.49
Page 6
2. SAP Netweaver deployed version

Current Version: SAP CPS V8 (Patch 49)
Both versions have two flavors described below:
1. Basic:
a. Define, control, and manage jobs and processes from a central point of administration
b. Both ABAP and Java stacks are supported
c.
Limited to one (V8: two!) process server(s)
2. Full:
a. Also manages non-SAP applications, OS level, database, infrastructure (storage, backup)
b. Multiple process servers supported
2.5
Installation Preparation Steps
This step will tell you the most important steps to activate the SAP Process Scheduling Adapter.
2.5.1
Download the Add-On Software
The following figure shows the complete path to download the ST-PSM Add-On from SAP Service Market Place.
Page 7
Figure 2-3: Add-On Download path on SAP Service Market Place
2.5.2
Install Add-On with SAINT
You need to follow the below steps to install the Add-On:
Start the Add-On Installation Tool SAINT.
Load packages from Front-end or Application Server
Choose Start to start the installation
For more information on the installation of ST_PSM see SAP Note 1122497
Page 8
Figure 2-3: Add-On Installation using SAINT
2.5.3
Activate the Adapter
The Process Scheduling Adapter has to be activated following the below steps:
Start transaction SPRO
Navigate to the path: SAP Solution Manager Cross-Scenario Settings Activate Solution Manager
Enhancements
Page 9
Figure 2-4: SPRO path to activate the Process Scheduling Adapter
Activate the Business Function SM_CRON under Enterprise Extensions
Figure 2-5: Activate the Process Scheduling Adapter
2.5.4
Activate XBP 2.0 Interface
To activate the XBP 2.0 Interface follow the below steps:
Page 10
Run the report INITXBP2 using transaction SE38.
Activate at least switch XBP 2.0 and switch Parent-Child Functions on, and then Execute.
Figure 2-6: Activate XBP 2.0 switch
2.5.5
Create Roles for Job Scheduling Management
You should copy the following roles to Z roles, maintain authorization data and generate profiles:
SAP_BC_BATCH_ADMIN_REDWOOD
SAP_BC_REDWOOD_COMM_EXT_SDL
SAP_SM_REDWOOD_COMMUNICATION
SAP_SM_SCHEDULER_ADMIN
SAP_SM_SCHEDULER_EXE
SAP_SM_SCHEDULER_DIS
SAP_SMWORK_JOB_MAIN
SAP_SUPPDESK_ADMIN
SAP_SUPPDESK_CREATE
SAP_SV_FDB_NOTIG_BC_ADMIN
. These copies of roles will be required later on.
2.5.6
Netweaver Settings to be checked
The following NetWeaver settings should be checked:
Page 11
2.5.6.1
Maximum Database connections
The value can be found using the Netweaver administrator:
Figure 2-7: Maximum no of RFC Connections in NWA

The value can also be found using the Config tool:
Page 12
Figure 2-8: Maximum no of RFC Connections (Config. Tool)

The value should be set to a minimum of 50.
NOTE: If you increase this parameter you may need to increase the number of sessions that can connect to the
database on the database level as well (for Oracle look at the init parameters sessions and processes).
2.5.6.2
Maximum Application Threads
The value can be found using the Netweaver administrator:
Page 13
Figure 2-9: Maximum Thread Count (NWA)

The value for the MaxThreadCount property of the ApplicationThreadManager service should be set to a
minimum of 50
2.5.6.3
HTTP Worker Threads
You need to allocate 2n HTTP worker threads where n is the number of concurrent users that you want to
support. This is because the user interface uses 2 HTTP connections per user, see SAP Note 1169442. A lack of
HTTP Worker threads will manifest itself as very poor performance.
2.5.6.4
SAP RFC Connections
For connecting SAP systems to CPS we recommend setting the environment variable CPIC_MAX_CONV as
described in SAP note 314530 on all Java servers of the NetWeaver installation where SAP CPS is installed to
5000. SAP CPS takes a maximum of 50 (default) RFC connections to per connected SAP system and then there
will be additional connections for clients and other tools as well.
2.5.6.5
JVM Settings
Page 14
At least 2 GB of memory in the JVM but 4 GB highly recommended for production environments; these values
should be doubled for 64bit/EM64T/AMD64 systems (4GB and 8GB, respectively).
See SAP Note 710146 for information on setting JVM parameters.
Use of compressed references (IBM JVM version 6), compressed oops (as of Oracle JVM 1.6), or the equivalent
of your JVM vendor is recommended; it allows you to decrease the amount of memory required by the JVM.
To enable compressed oops, you must specify the -XX:+UseCompressedOops JVM parameter. Note that
compressed oops are available on Oracle/Sun JDK 1.6 and later. Note that compressed references are enabled
by default on IBM JVM 6 and later when the heap size is smaller than 25GB on supported platforms (64Bit,
EM64T, and AMD64). To disable compressed references, you use the -Xnocompressedrefs JVM parameter.
2.5.6.6
Business Automation Enabler (BAE) Requirements
Increase the profile value gw/max_conn and gw/max_sys on the SAP gateway to support more parallel
connections:
gw/max_conn: 2000
gw/max_sys: 1200
gw/max_overflow_size: 40000000
gw/max_shm_req: 200
Increase the profile values rdisp/tm_max_no and rdisp/max_comm_entries on the application server:
rdisp/tm_max_no: 5000
rdisp/max_comm_entries: 200
2.6
Standard Configuration Steps in SPRO
This section describes the following steps:
Activate Solution Manager Services for Job Scheduling Management
Create Default User for Job Request
Create External Alias for Job Request
Setup Work center for Job Scheduling Management
These activities can be accessed via SPRO SAP Solution Manager Scenario Specific Settings Job
Scheduling Management Standard Configuration
Page 15
2.6.1
Activate Solution Manager Services for Job Scheduling Management
Navigate to the below shown path in SPRO and execute the activity Activate Solution Manager Services:
Figure 2-10: Activate Solution Manager Services in SPRO

Select (double click) the option Activate Service
Page 16
Figure 2-11: Activate Service

Browse & Execute - SM_JOB_SCHEDULING
Figure 2-12: SM_JOB_SCHEDULING

Select Back
Figure 2-13: SM-JOB_SCHEDULING Activated

Select (double click) Check Service Activation:
Page 17
Figure 2-14: Check Activation

This will take us to SICF transaction screen, Execute
Figure 2-15: SICF transaction Screen

Browse to the path: default_host sap bc webdynpro sap and activate the service
wd_ags_ejr_overview
Figure 2-16: SICF Service
Page 18
Close the Internet Explorer window which is opened and select Back
Figure 2-17: Service Check
2.6.2
Create Default User for Job Request
Create a user in User Maintenance transaction (SU01) in your production client, for example JOBREQUEST
On the Logon Data tab choose user type Service and enter a password, do not ever change this password.
Assign your copies of the following roles to your JOBREQUEST user:
SAP_SM_SCHEDULER_ADMIN
SAP_SUPPDESK_ADMIN
SAP_SUPPDESK_CREATE
SAP_SV_FDB_NOTIG_BC_ADMIN
Figure 2-18: User maintenence
2.6.3
Create External Alias for Job Request
Page 19
In transaction SPRO, execute Set-up alias for Job Request:
Figure 2-19: Set-up Job Alias from SPRO

Give Hierarchy Type: Alias and Execute
Page 20
Figure 2-20: SICF transaction Screen

Select default_host and click on create new Alias:
Figure 2-21: Maintain Alias
Page 21
Give External Alias Name: /sap/bc/solman/jobrequestuser and provide proper description. Also provide the
Logon Data of the previously created user JOBREQUEST:
Figure 2-22: Alias Definition

In the Trg Elements tab, assign the target handler by double clicking wd_ags_ejr_job_request_app and save
Page 22
Figure 2-23: Assign Target Handler

Now test the newly created external alias as below.
Note: Apply SAP Note - 1230387 if the program terminates on displaying the context menu.
Page 23
Figure 2-24: Test Alias

Close the Internet Explorer screen which is opened.
Page 24
Figure 2-25: Test Alias
2.6.4
Setup Work center for Job Scheduling Management

Assign workcenter navigation role
o
Assign your copy of SAP_SMWORK_JOB_MAN to your job management users
Assign workcenter basic role

o
Choose the roile SAP_SMWORK_BASIC
Copy the role
Go to Authorizations tab
Apply the authorizations by double-clicking on the yellow traffic light
Generate the profile
Go to the Users tab
Enter the users to which you have assigned work center roles
Compare users with Compare Users
Adjust Workcenter role

o
Adjust the web address of SAP CPS on the Menu tab, by entering
http://<host>:<port>/scheduler of you SAP CPS
Page 25
2.7
Integration Steps in SPRO
This section describes the following steps:
Setup Technical User
Create Connection to SAP CPS
Setup Business Automation Enabler
These activities can be accessed via: SPRO SAP Solution Manager Scenario Specific Settings Third
Party Integration SAP Central Process Scheduling by Redwood.
2.7.1
Setup Technical User
Create a communication user (e.g. CPSCOMM) between SAP Solution Manager and SAP CPS. This can be
done using the SAP transaction SU01 or SPRO menu path shown below:
Figure 2-26: Set-up Technical User - SPRO

The user has to be created as Dialog user initially to be able to login to SAP CPS once. The roles for Dialog user
is the copy of the below roles:
SAP_SM_SCHEDULER_EXE
SAP_J2EE_ADMIN
You should login to SAP CPS with this dialog user at least once via the following menu role (or CPS URL directly):
Job Management Process Scheduling Adapter SAP Central Process Scheduling by Redwood
Figure 2-27: SAP CPS access from Menu Role
Page 26
You will be asked for the license keys when logging in for the first time, click on Request Key for Enterprise
License.
Figure 2-28: Request CPS License

Once the License keys are received, click on Enter License Keys and paste the license information click on
Activate License in the next screen.
Page 27
Figure 2-29: Enter CPS License Information
Figure 2-30: Activate the CPS License
Page 28
Figure 2-31: CPS Home Page

Please close the CPS session, come back the user maintenance transaction and perform following actions:
Change the user CPSCOMM from Dialog to Communications Data.
Remove the roles assigned already and assign the copy of below roles:
2.7.2
SAP_SM_REDWOOD_COMMUNICATION
Create Connection to SAP CPS
To setup a connection between SAP Satellite System and SAP CPS follow the below steps:
Login to CPS using an Administrator user of type Dialog
Select Environment SAP Systems New (SMP in our case).
Provide the below details in SAP System tab:

o
System Name = System ID
ASHOST = Application Server Name
SYSNR = System Number
J2EE_URL = URL of the CPS System (This is required only if this system is itself hosting CPS)
Page 29
Job Handling = Disabled for CPS Host, Enabled for Satellite System and All if job handling is
required on all Systems.
Figure 2-32: Create CPS Connection
Provide the CPS-XBP user credentials in XBP and XAL tab and Check Connection Settings.
Figure 2-33 Create CPS Connection
Page 30
Figure 2-34: Create CPS Connection
Edit Security settings of this particular SAP System:
Figure 2-35: SAP System Security Settings in CPS
Edit the Partition Global:
Page 31
Figure 2-36: Global Partition Security Settings
To enable the RFC on Process Servers, select Environment Process Servers Select Process
Server Edit Parameters
Figure 2-37: Process Server parameters
Start the Process Servers.
This completes the connection settings and the connection can be tested to from ABAP stack using the program
RSEXTSDL.
Page 32
2.7.3
Setup Business Automation Enabler
Business Automation Enabler (BAE) is an interface between SAP-applications and SAP CPS for scheduling jobs
and job chains and integrating of business and infrastructure events.
Setup in the ABAP System (BAE)

o
Assign copy of below roles to every CPS-XBP user:
Assign copy of below roles to all the BAE-ABAP user:
Setup in NW J2EE Stack User Management UME (CPS System)

o
Create and assign roles for CPS users using the UME as explained below:
Create a new role with name scheduler-administrator.
Assign the following actions to the role:
redwood.com/Scheduler.AccessScheduler
redwood.com/Scheduler.ManageScheduler
Assign this role to your CPS users.
Figure 2-38: Create CPS Role (UME)
Setup in NW J2EE Stack Scheduler

o
Add every BAE-CPS-User to BAE System. This is already completed in creating a new SAP
System connection.
Assign rank Business Automation User.
Select Environment SAP Systems Select SAP System Edit Security
Page 33
Figure 2-39: BAE User Assignment

This completes the integration of SAP CPS System with SAP Solution Manager and SAP Satellite Systems.
3.
Key Features of the Application
This section describes few of the key features of the SAP CPS application.
3.1
User Interface
SAP CPS GUI is the key administrative and operational interface for the management and control of crossenterprise workload. Designed with an intuitive look and feel, this single point of control enables user and rolespecific access to the process automation environment for administrators, operators, and end users.
Few of the key features of the user interface are mentioned below:
1. Job Chain Editor
2. Flow oriented design-and run-time views
3. Single click and slide bar zoom controls
4. Mini-map control
5. Customizable navigation bar
6. Drag and drop configuration
7. Dashboard with dials and graphs
Page 34
8. Extended metrics
Figure 3-1: Job Chain
Figure 3-2: CPS Dashboard
3.2
Scripts
A script is a definition of a work item to be done and all SAP tasks are available as scripts out of the box. Each job
is an invocation of a script and SAP CPS supports multiple script-types.
Page 35
Figure 3-3: CPS Scripts
3.3
Job Chains
Job chains are grouped execution of related scripts (jobs). The job chains support following features:
Each steps can have one or more scripts for execution
Scripts in the same step run as parallel jobs
Scripts in different steps run in sequence
Pre- and Post-condition events and parameters control execution
Dependencies can exist between different job chains
Figure 3-4: Job Chain Definition
Page 36
3.4
Events
The job execution can be controlled using events. Events can be set at script level or at runtime and scripts (jobs)
can raise or wait for defined events. The following are types of events which can be raised:
Events raised by Job Execution

o
Return code
Function call in script
Job status change
File Events
o
Check if file exists
Move files to target directory
Check for file locks
Operation Intervention
o
Manually raise / clear events
Page 37
Figure 3-5: Event Definition
Figure 3-6: Event Raise/Clear
3.5
Calendars
SAP CPS provides the following features as a part of Calendars:
Single centralized calendar for all scheduled processes
Page 38
Time zone handling
Figure 3-7: Time Zones
Time window: Window with allowed start times for a job

e.g. 08:00 - 20:00 on workdays
Page 39
Figure 3-8: Time Window Definition
Submit frame: Cycle for a job, or a frequency

e.g. every hour
Figure 3-9: Submit Frame Definition
Page 40
3.6
Jobs and Queues
All scripts (jobs) in SAP CPS are processed in Queues and each queue is served by one or more Process
Servers.
Queue definition can be used to balance workload and provide HA by

o
Maximum number of active jobs in queue (throttling)
Hold jobs with lower priority or when CPU and page rate exceed threshold
Specify varying Time Windows for Queues
Figure 3-10: CPS Queue Definition
Dynamic queue reconfiguration

o
Concurrency limit
Bringing process servers on- and off-line
Page 41
Figure 3-11: Different CPS Queues
3.7
SAP Business Objects Integration
SAP CPS also supports Business Onjects and Crystal Reports Integration .
Figure 3-12: CPS-BO Integration
Page 42
3.8
Web Services Integration
Web Services are callable services that take advantage of ubiquity of the internet and perform specific tasks.
These services are central to most of the SOA environments.
Web Services are integrated in SAP CPS as:

o
Web services are increasingly used for mainstream applications
Organizations moving to SOA need to maintain legacy environments
Capabilities
o
Publish any SAP CPS job as a Web Service (inbound).
Import web service from third party application and run it from SAP CPS (outbound)
Dynamic scheduling for any web service enabled application
Asynchronous Web Service execution
Figure 3-13: Web Services Integration
Page 43
4.
Comparison with CCMS Scheduling
The following chart shows the comparison between CCMS Job Scheduling in SAP Systems with SAP CPS Job
Scheduling tool. This includes the comparison between free and chargeable version for SAP CPS as well.
Figure 4-1: CCMS Job Scheduling Comparison
5.
Features and Benefits
The table shown below lists all the features of SAP CPS which help in areas like reducing TCO, increase
productivity and improved response and flexibility.
Page 44
Table 5-1: Features and benefits overview
6.
6.1
Specific Business Scenarios

Parallel Processing
CPS provides parallel processing functionality which can be used to run multiple independent scripts in
combination of parallel and sequential steps. This helps in reducing end to end processing time of a job chain.
Page 45
Figure 6-1: Parallel Processing
6.2
Many to One Relationship
CPS provides many to one Relationship between job events which is not there in SAP Job Scheduler. The SAP
CCMS Scheduler only provides functionality to trigger multiple jobs based on status of a single job (using events).
But this feature in SAP CPS helps us to trigger a single or multiple jobs on status of multiple jobs as well.
In typical jobs such as period end closing jobs this can help reduce the total closing time by 40-60%.
Page 46
Figure 6-2: Many to One Relationship
6.3
Lock Mechanism
CPS provides Lock concept in jobs which can be used to prevent multiple copies of jobs to run at the same time
in case previous copy of a periodic job is still running. This is done by defining a lock and incorporating that lock in
the job definition.
Figure 6-3: Lock Definition
Page 47
Figure 6-4: Lock in SAP Script

The same lock can be used to control the scheduling of multiple jobs.
Once the new copy of the job is released, it will wait for the previous copy of the job (or any other active job
having this lock) to finish (in status Lock Wait).
Figure 6-5: Job Status with Lock
6.4
Restart Behavior
Most of the organizations require few background jobs such as Real Time Monitoring jobs to run on regular
basis so that they provide most recent data. This functionality can be implemented using the Restart Behavior in
the jobs.
Page 48
Figure 6-6: Restart behavior in Job Chain

Using this functionality the jobs can be triggered on regular basis (delay can also be set) based on the status of
the previous job.
7.
Frequently Asked Questions
Q: What is SAP CPS 8.0 by Redwood?

A: SAP CPS 8.0 by Redwood is the latest version of SAP CPS by Redwood. This version is a successor to SAP
CPS for NetWeaver 7.0
Q: Do I need a license to get SAP CPS 8.0?
A: As with all versions of SAP CPS by Redwood, there is a basic version with limited functionality included in the
standard SAP NetWeaver license. To unlock the full potential of SAP CPS by Redwood, an additional license
purchase is necessary. Please contact your SAP account executive for details.
Q: Are there prerequisites for moving to the new version with regards to the underlying SAP NetWeaver version?
Page 49
A: SAP CPS 8.0 by Redwood has been released for all SAP NetWeaver AS Java versions 7.0 and higher. There
is no upgrade of the underlying application server necessary.
Q: Do I have to upgrade from my current SAP CPS version to SAP CPS 8.0?
A: No, the upgrade is optional. The previous versions will continue to be maintained along the communicated
timelines
Q: Where can I get SAP CPS 8.0 by Redwood?
A: You can get the new version from the SAP Service Marketplace
Q: Where can I ask additional questions?
A: Please use the established forums on SDN to get answers to additional questions you may have and check
out the SAP Release Note 1524650 for additional information.
8.
References
EcoHub.SAP.com
https://ecohub.sdn.sap.com/irj/ecohub/solutions/centralprocessscheduling
SAP Service Marketplace
http://service.sap.com/process-scheduling
Page 50

CPS1

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

CPS1

Загружено:

Авторское право:

Доступные форматы

Central Process Scheduling on SAP Netwaever 2012

3. Key Features of the Application....................................................................................................34

4. Comparison with CCMS Scheduling.............................................................................................44

7. Frequently Asked Questions......................................................................................................... 49

Created By: r.jhalani@accenture.com

Central Process Scheduling on SAP Netwaever 2012

Provides seamless integration with SAP and non-SAP applications.

Aligns IT Processes to business needs

SAP Partnership with Redwood

It can be upgraded by licenses from SAP for wider capabilities

Dedicated OSS component for SAP CPS

SAP Active Global Support is first level support.

SAP support connection is used for troubleshooting.

In case development support is needed, SAP passes call to Redwood.

Operational Excellence and Business Support

Created By: r.jhalani@accenture.com

Central Process Scheduling on SAP Netwaever 2012

Figure 1-1: Business Support and Operation Excellence

Created By: r.jhalani@accenture.com

Central Process Scheduling on SAP Netwaever 2012

Table 2-1: Sizing Requirements on SAP host

Table 2-2: Required SPS Level (Central Scheduling System)

Created By: r.jhalani@accenture.com

Central Process Scheduling on SAP Netwaever 2012

Figure 2-1: CPS Architecture on Standalone Java Engine

Created By: r.jhalani@accenture.com

Central Process Scheduling on SAP Netwaever 2012

Figure 2-2: CPS Architecture on Netweaver Integrated Java Engine

Table 2-3: XBP version information

Versions and Scope

SAP Central Process Scheduling by Redwood exists as:

Created By: r.jhalani@accenture.com

Central Process Scheduling on SAP Netwaever 2012

2. SAP Netweaver deployed version

Limited to one (V8: two!) process server(s)

Installation Preparation Steps

Download the Add-On Software

Created By: r.jhalani@accenture.com

Central Process Scheduling on SAP Netwaever 2012

Figure 2-3: Add-On Download path on SAP Service Market Place

Install Add-On with SAINT

You need to follow the below steps to install the Add-On:

Start the Add-On Installation Tool SAINT.

Load packages from Front-end or Application Server

Choose Start to start the installation

Created By: r.jhalani@accenture.com

Central Process Scheduling on SAP Netwaever 2012

Figure 2-3: Add-On Installation using SAINT

Activate the Adapter

Start transaction SPRO

Created By: r.jhalani@accenture.com

Central Process Scheduling on SAP Netwaever 2012

Figure 2-4: SPRO path to activate the Process Scheduling Adapter

Activate the Business Function SM_CRON under Enterprise Extensions

Figure 2-5: Activate the Process Scheduling Adapter

Activate XBP 2.0 Interface

To activate the XBP 2.0 Interface follow the below steps:

Created By: r.jhalani@accenture.com

Central Process Scheduling on SAP Netwaever 2012

Run the report INITXBP2 using transaction SE38.

Figure 2-6: Activate XBP 2.0 switch

Create Roles for Job Scheduling Management

. These copies of roles will be required later on.

Netweaver Settings to be checked