Redwood Documentation

Product Documentation

 

›Adaptive Computing

RunMyJobsSAP Connector

Introduction

  • The SAP Connector
  • HANA Platforms

Configuration

  • Configuring the Central and Satellite Systems
  • Installing SAP JCo
  • Configuring an SAP System for Process Automation
  • SAP RFC User Privileges
  • Assigning SAP Authorizations to the RFC User
  • Connecting to SAP Systems
  • Connecting to SAP Systems with the Wizard
  • Connection Details for the ABAP Stack
  • Intercepting SAP Jobs
  • SAP Job Interception Configuration
  • Interacting with SAP Events
  • Configuration Details on Interacting with SAP Events
  • Parsing Log Files to set Status of SAP Jobs
  • Understanding the Different XBP Interface Releases

Importing SAP Objects

  • Importing Objects from SAP Systems
  • Importing ABAP Programs
  • Importing ABAP Program Parameter Definitions
  • Importing Archive Objects
  • Importing Batch Events
  • Importing SAP BusinessObjects Processes
  • Importing SAP Calendars
  • Importing SAP CCMS Jobs
  • Importing Communication Channels via PI/XI
  • Importing External Commands
  • Importing and Running Mass Activities
  • Importing Output Devices
  • Importing Process Chains
  • Importing Process Chain Definitions
  • Importing Recipients
  • Importing Variants
  • Importing Variant Definitions

SAP ABAP

  • Handling ABAP Programs
  • Controlling Batch Input Sessions
  • Handling Variants
  • Creating and Modifying Variants in Redwood Server
  • Maintaining Variants Manually
  • Maintaining Variants Automatically
  • Maintaining Variants Automatically (Advanced)
  • Using Temporary Variants
  • Default SAP Process Definitions

Business Objects

  • Main
  • Interface Configuration
  • Crystal Reports
  • Web Intelligence
  • Data Services
  • Triggering Events
  • Crystal Reports REST
  • Web Intelligence REST

Process Chains

  • Handling Process Chains
  • Running Process Chains
  • Monitoring Process Chains
  • Restarting Process Chains

SAP PI/XI

  • SAP Communication Channels with PI/XI
  • Controlling Communication Channels with Redwood Server via PI/XI

Adaptive Computing

  • SAP Adaptive Computing
  • Controlling SAP Adaptive Computing

SAP Monitoring

  • Integrating SAP Monitors
  • Configuration Details for Integrating SAP Monitors
  • Sending Monitoring Data to SAP Systems
  • Configuration Details for Sending Monitoring Data to SAP Systems
  • Monitoring Redwood Server Availability in CEN
  • Active XMB Monitoring
  • Active IDoc Monitoring

Advanced Configuration

  • Connect to an ABAP System via SAProuter
  • SNC connection to an SAP System
  • The SAP Cryptographic Library
  • Tuning Redwood Server

Legacy Systems Support

  • Enable XBP 2.0 or 3.0 Functionality
  • Enhanced SAP Interfaces with Redwood Transports
← Controlling Communication Channels with Redwood Server via PI/XIControlling SAP Adaptive Computing →

SAP Adaptive Computing Environments and Redwood Server

Data centers are becoming more and more virtualized, allowing greater optimization of resources and processes. Applications can be started, stopped and moved on demand to other servers. SAP has introduced SAP Adaptive Computing to address the needs of its customers. Redwood Server uses SAP Adaptive Computing Controller (SAP ACC) to automate starting, stopping and relocating SAP ACC services. You use the SAP_ACC_Controller process definition for this purpose.

You always need to provide the following parameters:

  • Url - URL to the SAP ACC server web service http://:/ACCGW/ACC(for example: http://sapacc.example.com:50200/ACCGW/ACC)
  • Username - username of a user that is authorized to manage SAP ACC services
  • Password - password of the user
  • Command - the command to perform, can be STOP, START and RELOCATE
  • Service ID - the ID of the service to manage

Stopping Services

To stop a service, you do not need to provide any more parameters, the SAP ACC will identify the host the service is running on and request the shutdown of the service.

Starting and Relocation Services

The behavior of the SAP ACC for the commands START and RELOCATE depends on the value of the parameter Hostname. The SAP ACC checks if the target host is available, not running any other services, and provides enough resources for running the new service. You can force the service to run on a server that does not provide enough resources according to the SAP ACC by using ForceSmallServer parameter. When this parameter is set to true, the SAP ACC will start the service on the target host regardless of resources.

Hostname is set

  • START - The SAP ACC will start the requested service on the host <hostname>, provided is meets the requirements.
  • RELOCATE - The SAP ACC will stop the requested service and start it on the host <hostname>, provided the new target server meets the requirements.

Hostname is not set

The host where to start the service is determined by the internal assignment rules of the SAP ACC.

See Also

  • CCI Request Format
← Controlling Communication Channels with Redwood Server via PI/XIControlling SAP Adaptive Computing →
  • Stopping Services
  • Starting and Relocation Services
  • Hostname is set
  • Hostname is not set
  • See Also
Docs
Getting StartedInstallationFinance InstallationConcepts
TroubleshootingArchiving
Learn and Connect
Support Portal
BlogEventsResources
ISO/ IEC 27001 Information Security Management
Automate to be human

2023 All Rights Reserved |

Terms of Service | Policies | Cookies | Glossary | Third-party Software | Contact | Copyright | Impressum |