Creating an Analysis

Show TOC

You want to create a new or an optimized analysis. You set the following attributes when you create an analysis:

The analysis project for which you are creating the analysis
The analysis name
The analysis start time
The systems
Timeline
General settings

Prerequisites

You have called the solution documentation assistant.
You have an analysis project for which you want to create the analysis.

Procedure

Under Common Tasks choose Create Analysis.
You can also create an analysis for a specific analysis project in Analysis Project Overview:
- Choose Analysis Project.
- Select the analysis project for which you want to create an analysis in the Analysis Project area.
- In the Analyses for Analysis Project '<name of analysis project>' area, choose Create.
The Create Analysis guided procedure is displayed, to help you create the analysis.

Defining Profiles

Specify the analysis project for which you are creating the analysis, and the time to start the analysis.

Note Note

If you start creating the analysis in the Analysis Project Overview, specify the analysis project there.

End of the note.

Open the input help for Analysis Project and select an entry; this is not necessary if the analysis project has already been set.
Click the Name field and give the analysis a name.
Open the entry help for Timeline and choose one of the following entries:
- Immediately, to start the analysis immediately after creation (default).
- Planning to set a start time for the analysis as follows:
  - Click in the Planned Start Date field or open the corresponding entry help to specify a Date for starting the analysis.
  - Click in the Planned Start Time field and enter a Time.

Choose Continue to call the next step.

Defining Systems

Specify the systems from which you get data for the analysis. You specify the systems using the logical components that are assigned to the underlying analysis project by check steps, and the system role.

Logical components and the systems and clients for a logical component, and the selected system role, are displayed in the System Selection area.

Note Note

System roles can be either system-wide or individual. Open the input help for System Roles above the System Selection, and choose an entry to set up a system role for all listed logical components. To set up a system role for a logical component, open the input help of the System Role and choose an entry.

End of the note.

The following is displayed for each logical component in the System Selection:

Name of the logical component
System role. You can set up the system roles individually.
System defined by the logical component and the assigned system role.
Client defined by the logical component and the assigned system role.
Status. Displays whether system and client problems can occur for the defined combination of logical components because, for example, a system or a client cannot be found.
Click the value assignment indicator for more details.
Check steps. Displays the number of check steps to be executed.
Workload, SQL and BAdI. If the check boxes Workload, SQL and BAdI are ready for input, you can expect statistics data of the respective types for the analysis. In this case the flag is set by default. The analysis includes the data.
Note
- The analysis only includes those logical components for which the flag is set.
- If the check box is not ready for input, you cannot expect any data for analysis because, for example, the system or client is not defined.
End of the note.
To remove data from the analysis, clear the flag.

Recommendation
SQL check steps can generate a heavy system load. You can therefore improve the performance of the analysis by omitting the SQL step checks from the analysis.

End of the recommendation.

Note Note

You can only create an analysis if systems and client can be found for at least one logical component. Check the logical components in the source of the analysis project that you base your analysis on, and the check steps assignments in the analysis project.

End of the note.

Choose Continue to the next step, or Back to the previous step.

Selecting a Period

Limit the time period for which data can be expected from the specified systems, according to your needs. These time periods are complete months.

Note Note

The planned start of the analysis is relevant for the time period. For an immediate start, the current month is never available for analysis, only completed months.

For a planned start in the future, the month in which the analysis is started is not available for analysis either. However, months that are still in the future at the time of analysis creation might be available.

End of the note.

In the Time Period area, the available time periods are displayed with the following attributes:

Time period is a specific, complete month
Selection. The flag for including the time period is set by default for all available time periods. Clear the flag, to remove a time period from the analysis.
Status displays whether data is available from the specified systems for this time period. The following statuses are displayed with the corresponding status flag for each time period:
- Data is available for all systems.
- Data is not available for all systems. Click on the status flag for details about systems for which there is no data.
Recommendation
To improve the performance of the analysis, restrict the number of periods to be analyzed as much as possible.

End of the recommendation.
Choose Continue to the next step, or Back to the previous step.

Scheduling Systems

In this step you set the period for the execution of the analysis for a particular managed system and define the maximum amount of resources to be used.

Note Note

If the table is empty or does not contain all systems assigned in the Select System step, this is due to the unavailability of check steps of certain check step types (such as SQL).

End of the note.

The following information is displayed and entered in the table:

System: Managed system that has at least one check step for a particular type (for example SQL)
Start date: Start date of the analysis
Start time: Start time of the analysis
End date: Date by which the analysis in the respective managed system must be completed. This date must be agreed with the system administrator.
End time: Time at which the analysis in the respective managed system must be completed. This time must be agreed with the system administrator. The analysis is automatically terminated at the specified time.

Recommendation
To complete the analysis as quickly as possible, use the maximum possible system load allowed by your system administrator. You must ensure that the system has enough background processes, or a sufficient proportion of them, at its disposal, for the analysis to be completed within the specified timeframe.

End of the recommendation.
Max WP: Maximum number of background work processes in the affected managed system. This number must be agreed with the system administrator.
Max % WP: Maximum percentage of background work processes to be used in the affected managed system. This value must be agreed with the system administrator.

Recommendation
To keep the system load low, choose a longer time period for the analysis to be carried out.

Your experience with analyses will be a good guide to how to balance the execution time period and the system load.

End of the recommendation.
Choose Continue to the next step, or Back to the previous step.

Defining Parameters

Specify the following settings for the analysis:

Optimization Optimization means that, for example, analysis of a check item ends as soon as a result for the check item evaluation is sufficient.

Recommendation
Set the flag to keep the load on the system as low as possible during the analysis.

End of the recommendation.
Include Identifying Check Items. The flag is set by default. You must include these check items to get results for the analysis structure node from the analysis.
Include Documentary Check Items. The flag is not set by default.

Recommendation
Documentary check items are not required for the evaluation of the structure nodes. Only include documentary check items in the analysis if you are sure that you need them.

SQL check steps generate a high system load. It is therefore a good idea to include SQL check steps in documentary check items.

End of the recommendation.
Threshold value. Define a global threshold value for the analysis. This global value overwrites all threshold values where the the value for assigned check steps is set to zero.
Get all customer objects. Set the flag to include all customer objects in the analysis and, for example, identify unused customer objects.

Note
Including customer objects requires RFC connections to the corresponding systems.

End of the note.
Task type, for example, dialog, background, spool. All types are included by default. Select one or more entries from the selection list, to change the default setting.
Parameters for SQL Steps. If the analysis includes SQL check steps, the Very expensive SQL statements check box is ready for input. The flag is not set by default.
If you don not select the check box, the system only checks whether structure objects are active or inactive.
Recommendation
SQL check steps can generate a heavy system load.
- Check whether it is necessary for the analysis to execute SQL statements (for example to check the contents of database tables).
- Ensure that the time and resources allocated by your system administrator are sufficient for complete execution of the SQL statements. How precisely you are able to estimate the expected system load will depend on your experience with executing SQL statements.
End of the recommendation.

Choose Continue to the next step, or Back to the previous step.
To end the process, choose Close.

Result

The analysis is created.
The summary displays the name of the analysis, the planned start time, the selected systems, and the time periods of the analysis are displayed.