SAP Note 894279 - Background processing in SAP Solution Manager (Part I)

Symptom

This note relates to documentation for background processing in SAP Solution Manager.


Other terms
SAP SOLUTION_MANAGER, SOLUTION_MANAGER, DSWP, DSMOP, SM:SCHEDULER, DSWPJOB, SMCONFIGJOBS, SM:EXEC SERVICES


Reason and Prerequisites
Documentation is missing in background processing.


Solution
Below, you can find details about background processing, which is required to operate the Solution Manager.


Background processing in the Solution Manager System

Old job framework of the SAP Solution Manager (SM:SCHEDULER, valid up to and including Support Package 21)

• SAP Solution Manager background processing does not require any administrative work by the customer.

• All of the programs required by your Solution Manager system are automatically executed by the job SM:SCHEDULER (the program RDSWPJOBSCHEDULER), which runs hourly. The job is created automatically (under the current user) when you create the first solution landscape ("Solution" or "Solution Landscape") in SAP Solution Manager. SM:SCHEDULER manages all programs that are flagged as active in the table DSWPJOB according to their relevant configurations.

• The configuration delivered by SAP (Customizing) is available in the table DSWPJOB. The table is delivered with a suitable default setting and should not be changed.

• Once a day, SM:SCHEDULER starts an important job that automatically executes service sessions (for example, EarlyWatch Alert processing). This job is called SM:EXEC SERVICES. You can set the time at which this job is started in SAP Solution Manager "Global Settings". The default setting is 6 am.

• Use the Solution Manager automatic diagnosis to obtain information about the status of the background processing. If jobs terminate or are not executed, you will find the relevant information here. The table DSWPJOBSTATUS contains information about the last run of individual programs.

• Note: Continue to use your SAP system's underlying infrastructure, that is, transactions SM37 and SM36, for configuration-intensive programs (for example, customer-specific variants). Do not add any customer-specific programs.

New job framework 'Solution Manager Job Configuration' of the SAP Solution Manager

• By definition, the SolMan job configuration delivers the required SolMan standard jobs with predefined start conditions.  The scheduling is performed by the user in transaction SM_CONFIG_JOBS (relevant up to and including ST Support Package 17) or as of ST Support Package 18 in transaction SOLMAN_SETUP in the automatic configuration (in "Basic Configuration" scenario, under "Configure Automatically" step, "Schedule Background Jobs" activity). However jobs contained in the old configuration table (DSWPJOB) and not in the new one (SMCONFIGJOBS) will continue to be scheduled from the SM:SCHEDULER job, which is still active in the new job framework.

• This SolMan jobs configuration is stored in SMCONFIGJOBS table and offers more flexibility than the old framework. The ISIMMEDIATE flag allows an immediate scheduling of the corresponding jobs when the "Schedule Background Jobs" activity in executed. Moreover the COMM2SAP flag is used to distinguish the jobs in communication with a SAP system. Starting from ST400 SP26 those kind of jobs which are declared as non immediate are started with a random time offset to ensure a randomly distributed access to SAP systems for all SAP customers of the same time zone. For more details about this global randomization and how to unschedule the existing jobs with a fixed start time causing problems to SAP systems, please see SAP notes 1538950 and 1604572.

(Check Next Post)