It is essential to read this blog before you proceed further.

Since 7.1 SP10, there exist two work centers in technical monitoring namely BI monitoring and Job Monitoring.

There are some inherent design shortcomings with the BI Monitoring application in 7.1 that SAP decided to invest in a renewed work center to overcome these deficiencies. As a part of this approach, we decided to unify the collectors of Business process monitoring and technical monitoring to be based
out of the same infrastructure namely MAI.

However from the runtime and reliability of the solution, Job monitoring offers robustness with regard to alerting mechanism.

What does the MIGRATION report do? & When to execute this?

So when you are actively using BI Monitoring to monitor BW PC (process chains), SBOP and SAP Data services jobs in the past (earlier to SP12) and have
several managed objects configured, we provide a report program to transfer these configurations to managed objects of type Job Monitoring to utilize the
new unified job monitoring collection mechanism and hence overcome the known limitations of BI Monitoring.

What objects are migrated?

If the technical scenario in BI Monitoring has managed objects of type BW PC, SBOP, SAP Data service jobs; this migration report acts on them

Which objects are not migrated?

Bex queries and templates are not migrated

FAQ:

1. What happens to the old BI monitoring objects?

The old BI Monitoring scenario would remain as is. There are options to decide what should happen to the objects in this scenario.

A drop down exist to execute this migration one scenario at a time.

There are two options

a) Migrate BI monitoring Objects :

We create a new Job Monitoring technical scenario. ‘_BIMONIT’ will be added as a suffix to the existing BI Monitoring scenario name. Then in the chosen
scenario, all the objects of type Process chains, SBOP jobs and SAP Data services jobs are referred and the existing configuration (Metrics, Thresholds,
Notification, incident settings) migrated by creating new job monitoring objects of respective sub type in the new job monitoring scenario.

In this case, the bi monitoring is still functioning and now the job monitoring is also functional.

b) Migrate and Deactivate BI Monitoring Objects

We create a new Job Monitoring technical scenario. ‘_BIMONIT’ will be added as a suffix to the existing BI Monitoring scenario name. Then in the chosen
scenario, all the objects of type Process chains, SBOP jobs and SAP Data services jobs are referred and the existing configuration (Metrics, Thresholds,
Notification, incident settings) migrated by creating new job monitoring objects of respective sub type in the new job monitoring scenario.

In this case, only these objects are deactivated from monitoring via BI Monitoring and are now available via the job monitoring.

2. what happens to the old BI Monitoring scenario?

The old BI Monitoring scenario would remain as is. Active and functional and

3. What happens to the other parts of the BI MON scenario, that are not migrated

The old BI Monitoring scenario would remain as is. The other parts of the BI Monitoring scenario like the BW Bex queries & templates, all the systems
included in the scope selection in define scope step 4 would remain in the BI Monitoring Scenario. Depending on the option chosen for migration, the objects
of types BW PC, BO jobs, DS jobs would be deactivated.

4. Where to check the result of the report program that performed the migration

Please check in SLG1,

Object type: E2E_ALERTING

Sub Type: JOB_CONFIG

5. Where to check for the logs of this background job?

Owing to the time intensive operation this program would execute in background. In transaction SM37, check with the job name MIGRATE_BI_JOB_* with
the user who triggered the migration report for the logs and the status of the job

6.Explain the advantages of this migration?

The Job monitoring work center is sophisticated in the collection and would hence avoid grey alerts. Also starting SP12, the BW reporting is available for

job monitoring collected metrics.

7. Explain which feature in BI Monitoring setup is not available in JOB Monitoring

There is also a compromise in this migration. BI Monitoring work center evolved over the last 10 SPs to make a feature rich SOLMAN_SETUP. Certain functionalities that were developed in BI Monitoring configuration typically caters to the mass handling requirements. These are ‘threshold mass maintenance’, ‘Job Details’, ‘Excel import and export’ and ‘take from schedule’. These features are not yet available in the Job Monitoring configuration. But the trade-off exist. The collection is robust. Hence the alerting and monitoring UI are more dependable when using the job monitoring.

Solution

Execute the report program AC_JOBMON_MIGRATION to migrate (BW PC, SBOP, DS jobs) of BI Monitoring to Job Monitoring

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply