Skip to Content
author's profile photo Former Member
Former Member

Control M Scheduling the Scenario on XI

Summary of Control-M SAP XI Integration Proof of Concept

Our aim was to develop and proof a mechanism to use Control-M to trigger SAP-XI Jobs to run on a Schedule, say once a day, or once every 2 hours.

Our initial design was to try installing Control-M SAP Control Module on top of SAP XI, then find a way to schedule an Event to trigger the XI Integration Scenario. We would use Control-M to schedule an Event (a file drop, an ABAP Proxy Call), which would cause the XI Integration Scenario to kick-off.

Our key findings are as follows:

1. Yes, we confirmed that Control-M SAP Control Module can run on SAP XI

2. Any particular SAP XI Client can either be a Business System (Source/Target), or an Integration Server (the middleware), but not both. This means that while we can have the Trigger Event and the Integration Server on the same box, they cannot use the same SAP client. We need to use two SAP clients on the SAP XI box.

Set Up – One Server Two Clients, Asynchronous

We have been able to create the following set-up on our Environment, where:

· XI Client 545 is the Integration Engine

· XI Client 520 acts as a Client of the Integration Engine

· Control-M waits on a File-Drop on the XI box to signal completion of the Job Stream

With the above scenario completed and working, we have the following issues:

· Using 2 SAP clients to enable scheduling in each environment (Dev, QA, Prod) is cumbersome, and feels like we are abusing the concept of separate clients

· Using File Drops is not ideal. In addition, use of File Drops requires the Control-M UNIX account to have permissions to delete files that are created by the XI Application User – while not a problem, it will require additional assistance from the UNIX team.

Alternate Set-Up #1 – Two Servers, Asynchronous

To address the issue of using two clients for each environment, we can use SAP R/3 as the Client of the Integration Server, instead of using the SAP XI second client.

This approach has the issue of an additional application server to monitor, i.e. more moving parts. We would also have to monitor network connectivity between SAP R/3 to SAP XI. This also does not address the File Drop issue.

Alternate Set-Up #2 – One Server Two Clients, Synchronous

(Best Solutions we found, so far)

Using two clients on the XI Server, but uses a Synchronous ABAP Proxy Call – this has the advantage of not requiring a file-drop, and allows Control-M to monitor the process with a single job, instead of two. This solution will work if SAP supports our approach of using two clients on the XI Server.

Note: We do not want to implement the above approach using a separate R/3 server as the client – the performance impact of a synchronous ABAP Proxy Call would be very high for a long-running job.

We are looking forward if someone can confirm our two-client approach falls under best practices. The SAP Developer Network has an example that employs this two-client approach (/people/siva.maranani/blog/2005/05/22/schedule-your-bpm), but we need to confirm that there isn’t a better solution available.

We are planning to open a note with SAP anyways, if someone knows upfront who will be saving us lot of time, i would really appreciate it.

Thanks in Advance

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Dec 05, 2005 at 10:10 AM

    Hi Hari,

    Do you already use Control-M? If not, you might want to check out the new Job Scheduling capabilities of SAP NetWeaver. You can find more information about this on SAP Service Marketplace under quick-link job-scheduling (

    Kind regards,

    Edwin Esser

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.