0% found this document useful (0 votes)
100 views5 pages

The Focused Run Job Monitoring

The Focused Run Job Monitoring will provide advanced monitoring and analytics features for large customers and service providers. It will allow configuration of job monitoring for selected systems through a single tile in the SAP Fiori launchpad. Users will be able to select the scope of monitoring by system, client, or group. The application will also allow configuration of monitoring schedules, metrics, alerts, and default settings for new job groups.

Uploaded by

Mustameer Khan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
100 views5 pages

The Focused Run Job Monitoring

The Focused Run Job Monitoring will provide advanced monitoring and analytics features for large customers and service providers. It will allow configuration of job monitoring for selected systems through a single tile in the SAP Fiori launchpad. Users will be able to select the scope of monitoring by system, client, or group. The application will also allow configuration of monitoring schedules, metrics, alerts, and default settings for new job groups.

Uploaded by

Mustameer Khan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

The Focused Run Job Monitoring

will address the needs of the Large Service Providers, Large and Very Large customers with advanced
needs, which can‘t be satisfied by SAP Solution Manager.

The Focused Run Job Monitoring will provide advanced features for configuration, monitoring and
analytics. The features, options and possibilities are discussed in the following sections below :

Personas:
1. IT Administrators / Managers
2. Business Users

Launch of the Application:


1. The configuration as well as monitoring shall be possible via a single tile in the fiori launch pad.
2. The tile must be part of the tray ‘Job Management’ (Will be renamed based on alignment).
3. On click – the job monitoring application shall be launched.
4. OPEN: Authorization concept.
5. Acceptance:
a. There shall be a new tile with the naming and the navigation as suggested above.
6. How to test:
a. Login to the FRUN application and add the tile from the appropriate group.
b. The tile can be added to the favorites.
c. On click, The tile opens the job monitoring application .

Configuration:
Based on the roles and authorization, there shall be an option for configuring the job monitoring for
selected systems/clients.

Context Selection:
1. On launch of the Job monitoring application, there shall be an option to select the scope. There
are two ways to select the scope
a. System / client
i. The search should consider the following fields – Customer ID, Data Center, Ext
Sys ID, Life Cycle Status, IT Admin Role, Customer Network. Additionally, there
shall be an option to select based on System and Client
ii. The result list should consist of the following fields – System, Client, Ext Syst ID,
System Display name, Lifecycle status, IT admin role, Customer Network.
iii. There shall be filter and sort options available in the result list to enable the end
users to easily select the systems he wants to work with.
b. Group
i. List of all the groups and group descriptions.
ii. Only the group for which the user is completely authorized should be displayed
in the list.
Data Usage:

Group:

Group List:
1. The group list shall display all the group which consists of systems for which the end user is
completely authorized.
2. The group list will consist of the Name and the description
3. The group header shall display the total number of groups: Group(4).
4. OPEN: Toggle button(ON/OFF) for mass activation.
5. OPEN: Additional text that is needed in the group list.
6. Group actions:
a. Refresh: Refresh the Group list
b. Edit: Opens the dialog for performing additional actions of the groups.
7. Search Bar: It shall be possible to search for the group. The group bar is placed above the list
and shall be left aligned.

Group Overview List :


1. The group overview dialog shall consist of the following
a. Table with the fields : Group name, Description , No of Systems, No of Active jobs, Last
changed, Last changed by, Standard Group .
b. The group header shall display the total number of groups: Group(4).
c. Refresh button
d. Search Bar: It shall be possible to search for the group. The group bar is placed above
the list and shall be left aligned.
e. Actions :
i. Add : Add a new Group and Group description .
ii. Delete : Delete a group . On delete a pop-up asking for confirmation and also
warning suggesting that all the Jobs will be deactivated and removed from
monitoring has to be shown.
f. Close button : There shall be a close button on the bottom right corner of the screen
that lets the end user to close the screen.

Add New Group :


The add new group screen will consists of guided procedure consisting of the following steps.

1. Systems:
a. Group Name and Description:
b. Indicator for Standard ABAP Jobs :
i. This indicator is a onetime activity and cannot be changed after at-least one job
in the group is activated.
ii. Toggle Standard ->Application
1. All the standard jobs in the subsequent steps will be lost and not
available for the end users
iii. Toggle Application -> Standad
1. All the application jobs in the subsequent steps will be lost and will be
replaced by the standard jobs for the selected systems/clients
c. System / Client: The tray will consist of the following
i. Table with the fields – System and Client. Note There can be multiple clients for
the same system. The EDIT of the entries are based on the click of the
system(hyperlink).
System Client(s)
FBT 200, 000, 100, 300
FA7 100
FQ7 200, 100
ii. The following actions are allowed on the table
1. Add : A dialog to enter the CN, System , Client -> Save and Cancel.
2. Delete : Delete the entry with a confirmation message.
3. Refresh: The entries in the table are refreshed.
2. Group Default Settings: The group default setting will provide the possibility to
default(template) the values for all the jobs that are created as part of the group.
a. Monitoring Schedule
i. Job Schedule :
1. Time Based:
2. Start Based:
ii. Schedule Data:
1. A table consisting of the days of week.
2. The planned start and the periodicity should have one of the options –
either take from the actual job or based on job periodicity. Feedback is
welcome.
iii. Stop Monitoring: Optional Field with Date and Time zone. If entered the
monitoring of the jobs in the group/job will be stopped on the arrival of this
time.
b. Metric Configuration : The following metrics will be available
i. Status :
1. A toggle ON/OFF .
2. Drop down with options : RED , YELLOW
ii. Duration :
1. A toggle ON/OFF .
2. Radio-button with two options
a. User defined : the following values are permissible
i. Lower red, Lower Yellow, Upper Red, Upper Yellow
ii. A bar indicating the values – Ratings and numbers.
b. Propose Values: The proposal of values should consider the
following parameters.
i. Min , Max, Avg, Last Run
ii. Absolute, Percentile
iii. +,-
iv. Value (Value to be considered )

c. Alert Configuration
i.
ii.
iii.
d. Alert Notification
e. Job Information

Monitoring :

You might also like