faq automated dvm-ewa self-service v3corrected

7/23/2019 FAQ Automated DVM-EWA Self-service V3corrected

http://slidepdf.com/reader/full/faq-automated-dvm-ewa-self-service-v3corrected 1/23

Frequently Asked Questions (FAQs):

Automated DVM Self-Service and new DVM

chapter in EWA



Table of Contents

1 General Information .......................................................................................................................4

1.1 What is the DVM Guided Self Service (GSS)? ........................................................................4

1.2 What is the Automated DVM Self Service? ............................................................................4

1.3 What is the new DVM chapter in EWA? .................................................................................4

1.4 Process overview chart and job/document names ....................................................................4

2 Automated DVM Self-Service Setup ..............................................................................................5

2.1 What the software prerequisites? .............................................................................................5

2.2 What are the required authorizations for the user setting up? ...................................................5

2.3 What are the required authorizations in the managed systems? ................................................5

2.4 How is the service setup? ........................................................................................................6

3 Automated DVM Self-Service Service Document Browsing ......................................................... 103.1 How do I browse over the created service documents? .......................................................... 10

3.2 How do I distinguish between those documents created automatically and those that arecreated manually? ................................................................................................................................ 10

3.3 I have located a service document. How do I see the service report for it? ............................. 11

3.4 I have located the service document, but it does not have the Attachment tab. Is that an error?

12

4 New DVM chapter in EWA.......................................................................................................... 13

4.1 What the software prerequisites? ........................................................................................... 13

4.2 What are the required authorizations for the user setting up? ................................................. 134.3 What are the required authorizations in the managed systems? .............................................. 13

4.4 How is the service setup? ...................................................................................................... 14

4.5 Where is the new chapter located in the EWA document? ..................................................... 16

4.6 Will I get this new chapter for all my EWA documents? ....................................................... 16

5 Status Monitoring ......................................................................................................................... 17

5.1 Automated DVM Self-Service documents ............................................................................. 17

5.1.1 Browsing the self-service document area ........................................................................... 17

5.1.2 Technically monitoring the background jobs ..................................................................... 17

5.1.3 Monitoring the analyses .................................................................................................... 18

5.2 EWA analysis monitoring ..................................................................................................... 19

5.2.1 Technically monitoring the background jobs ..................................................................... 19

5.2.2 Monitoring the analyses .................................................................................................... 20

5.2.3 Troubleshooting ................................................................................................................ 21

6 Technical Details / troubleshooting ............................................................................................... 22

6.1 How are the Analysis jobs scheduled in the managed system(s)? ........................................... 22

6.2 If I see an error in the log, does it mean it is a software error (bug)? ...................................... 22

6.3 I have an ST14 dataset but no analysis results in the DVM chapter in my EWA document .... 22



1 General Information

1.1 What is the DVM Guided Self Service (GSS)?

It is standard functionality in the DVM workcenter to manually execute the creation of the DVM GSS

(Guided self-service) documents, which is done from the DVM workcenter in the Service Document area.

1.2 What is the Automated DVM Self Service?

As of ST SP12, there is the possibility to automate the creation of DVM GSS documents. As such, there is

a new step 9 in the DVM section of the Solution Manager setup transaction (SOLMAN_SETUP).Once the setup is done, the service will be executed in fully automated mode without any further user interaction.

1.3 What is the new DVM chapter in EWA?

As of ST SP12, a new DVM specific section may be included in the Early Watch Alert (EWA) report. This

means a basic DVM session will be run only for EWA that requires no user interaction.However, this also requires an initial setup which is done in the new step 5.3 in the EWA section of theSolution Manager set-up transaction (SOLMAN_SETUP).

1.4 Process overview chart and job/document names

Below you can find a chart that describes what the process and job/document names are for both, the Automated DVM Self Service and the new DVM chapter in EWA:



2 Automated DVM Self-Service Setup

2.1 What the software prerequisites?

SAP Solution Manager 7.1 support pack 12 or higher (component ST)

Note 2030234.

2.2 What are the required authorizations for the user setting up?

In order to be able to run the DVM SOLMAN_SETUP, the following role should be assigned:

SAP_DVM_CONFIG

2.3 What are the required authorizations in the managed systems?

The required TWM connection should be set up from the Solution Manager for the managed system (*). Inorder to be able to do this, the user should have admin rights in the solution manager.

For the TMW RFC connection, the required role SAP_SOLMAN_TMW should be assigned or a copyautomatically generated for this RFC connection when the setup is done.

(*) To get to the managed systems configuration, follow this path:

è Transaction SOLMAN_SETUP

è Managed Systems Configuration

è Select system to be configured

è Click on button Configure Systemè From the context menu, select Full Service Configuration incl. Service Delivery/EWA

è In the pop up window, go to Step 3: Maintain RFCsè Select the desired clientè Create / maintain the TMW and BACK RFCs and save (see screenshot below).



2.4 How is the service setup?

For setting up the DVM self-service, the following steps should be followed:

a) Go to transaction SOLMAN_SETUP (/nSOLMAN_SETUP)

b) Select the menu Data Volume Management

c) Select step 4: Scope Selection and pick the system ID (SIDs) to be setup

d) Select step 5: Select Client and from the drop down choose the client

e) Select step 9: Automated Self Service. The SID/client combinations selected in steps 4 and 5

are now available

f) Click on the Edit button. The section Currently Scheduled Options can now be changed



g) Click on the field Processing Mode and click on the search help button or press F4

h) A pop-up window with the available processing modes appears. Only those modes with agreen light under the column Immediate Availability should be selected.

i) Select the Worklist Refresh Frequency. This is how often the object list passed to the DVM

service should be refreshed from the DVM available data. The drop-down available values are:Weekly

MonthlyBi-Monthly

Quarterly



j) Reprocessing Frequency: this field tells the system how often an object can be processed again. The drop-down available values are:WeeklyMonthlyBi-MonthlyQuarterly

k) Objects per run: this determines how many objects are processed per report or servicedocument. Enter a number.

l) Reports to keep per Object: this field serves for housekeeping purposes and allows the systemto keep only the number of reports per object set. Enter a number.

m) Job Scheduling Frequency: Sets up the first run of the configured SID/Client and its

frequency. First you have to click on the possible values button for the field:

A pop up comes. For the Job Scheduling Frequency field, choose one of the drop-downavailable values: NoneDailyWeekly

By-weeklyMonthly

Quarterly

For the Start Date field, the current date is proposed, but it can be changed to any date in thefuture.

For the Start Time field, the current time is proposed, but it can be changed to any time in thefuture.



3 Automated DVM Self-Service Service Document Browsing

3.1 How do I browse over the created service documents?

The service documents are available in the DVM workcenter.To display the DVM workcenter, go to transaction SM_WORKCENTER and then select the tab Data

Volume Management. Then, click on Service Documents.

3.2 How do I distinguish between those documents created automatically and

those that are created manually?

Two things distinguish the automated reports from others: in the solution column, it says Solution Independent and in the session column the naming convention is

Aut DVM Service <SID>/<Client>/<Date>.

You can use the filtering / sorting capabilities to find a document based on its name or delivery date

(creation date).See example in screenshot below.



3.3 I have located a service document. How do I see the service report for it?

When you click on the document, its details are displayed below under a tab named Details. Also, a second tab named Attachments appears. Clicking on the document number triggers the opening of the service

report in PDF format.



3.4 I have located the service document, but it does not have the Attachment tab.

Is that an error?

Not necessarily. The service document can be found in the browser as soon as the session (technicalcontainer) is created. After that, a job has to be scheduled in the managed system. Once that job in themanaged system is finished, data is retrieved to the Solution Manager system. After that, the data stillneeds to be processed and finally the PDF document is created.

If you try to check on a service document between the times when the session is created until just beforethe PDF document is created, no attachment tab will be visible, as there PDF document does not exist yet.

In addition, the status in the Details tab will be displayed as Session initial.



4 New DVM chapter in EWA

4.1 What the software prerequisites?

SAP Solution Manager 7.1 support pack 12 or higher (component ST)

Implement the Note 2030234Component ST-SER (Solution Manager Service Tools) release 701_2010_1 with support pack 24 or

Service Content Update activated.Implement the Note 2115837 in Solution Manager System and Managed System to be configured.

Refer to the Note 2036442 for the Pre-requisites you should have

4.2 What are the required authorizations for the user setting up?

In order to be able to run the EWA SOLMAN_SETUP, the following role should be assigned:

SAP_SM_BASIC_SETTINGS

4.3 What are the required authorizations in the managed systems?

The required TWM and BACK RFC connections should be set up from the Solution Manager for themanaged system (*). In order to be able to do this, the user should have admin rights in the solution

manager.

For the TMW RFC connection, the required role SAP_SOLMAN_TMW should be assigned or a copyautomatically generated for this RFC connection when the setup is done.

A BACK RFC connection should be set up from the Solution Manager to allow calls from the managed

system back to the Solution Manager.The required role SAP_SOLMAN_BACK should be assigned or a copy automatically generated for thisRFC connection set up is done.

(*) To get to the managed systems configuration, follow this path:

è Transaction SOLMAN_SETUP

è Managed Systems Configuration

è Select system to be configured è Click on button Configure Systemè From the context menu, select Full Service Configuration incl. Service Delivery/EWA

è In the pop up window, go to Step 3: Maintain RFCs

è Select the desired clientè Create / maintain the TMW and BACK RFCs and save (see screenshot below).



4.4 How is the service setup?

By entering this step please notice that:

All the listed systems are ABAP systems with their corresponding clients excluding clients 000and 066, and have either TMW RFC or BACK RFC or both of them. Also systems for which theEWA is yet not activated are listed. To check EWA activation, start with step 1. Also systems for

which the EWA is yet not activated are listed. To check EWA activation, start with step 1.

The ‘DVM Active’ filed allows activation or de-activation of DVM content for EWA. Theactivation is only possible for one single client of a system.

For activating the new DVM chapter in EWA, the following steps should be followed:

a) Go to transaction SOLMAN_SETUP (/nSOLMAN_SETUP)

b) Select the menu Early Watch Alert Management

c) Go straight to step 5 Configure EWA Content



d) Select step 5.3 Data Volume Management. Only systems with the TMW RFC Status and Back RFC columns in green can be selected.

e) Click on the Edit button

f) Select the System Id and Client combination. You can use the filtering capability toquickly find the right system.

g) Select the check button under the column DVM Active

h) Job Scheduling Frequency: Sets up the first run of the configured SID/Client and itsfrequency. The drop-down available values are:

Weekly

Monthly

i) Choose a start date and start time j) Select the table line

k) Click on the button Save Configuration



4.5 Where is the new chapter located in the EWA document?

The new Data Volume Management chapter is located before the Database Performance chapter.

4.6 Will I get this new chapter for all my EWA documents?

The new chapter will only be available for those system / client combinations setup in step 5.3. See point

4.4 above



5 Status Monitoring

5.1 Automated DVM Self-Service documents

There are different ways to monitor the status of an automated DVM self-service document, as follows:

5.1.1 Browsing the self-service document area

This is the easiest, less technical way to check. Instructions on how to do this can be found in point 3:

Automated DVM Self-Service Service Document Browsing

5.1.2 Technically monitoring the background jobs

Control job: AGSDVMAS_CONTROL5.1.2.1

To display these jobs, you have to use the job selection transaction SM37.The control job name is AGSDVMAS_CONTROL and it is valid for all systems.In the job log, check the lines starting with a bullet (n), as those are the starting point for each SID/Client

and service combination.For the automated DVM self-service document creation process, the service type is DVM.Below a sample of how a job log looks like:

Execution job: AGSDVMAS_EX_<SID>_<CLIENT>_<SESSION NUMBER>5.1.2.2

To display these jobs, you have to use the job selection transaction SM37.The control job name AGSDVMAS_EX_<SID>_<CLIENT>_<SESSION NUMBER> à there will be a

job for each SID/Client combination configured in step 9 of the SOLMAN_SETUP for DVM.In the job log, check the lines starting with a bullet (n), as those are the starting point for each SID/Clientand service combination.



This job will be only restricted to a single SID, client and session number combination.Below a sample of how a job log looks like:

5.1.3 Monitoring the analyses

The actual analyses can be monitored, both on the managed system (before the transfer to SolutionManager) and on the Solution Manager.There are two ways to check them, which actually take you to the same place:

a) Transaction /SSF/AB, or b) Transaction ST13àTool Name: ANALYSISBROWSER

Here you will look for analyses with the following naming convention:

<Session No> DVM Auto Service – Mode <MODE><SID><CLIENT>

A sample of how the job details are displayed can be seen below:



Note: these analyses are technically triggered by a scheduled job visible in the job selection transactionSM37. This job has the naming convention BO APPLICATION ANALYSIS <Number>, whose name is notvery detailed and would be very difficult to correlate to a specific process.

However, it is important to note that this main job BO APPLICATION ANALYSIS <Number> triggers twoadditional jobs that are related to the final result transferred in the actual analysis data:

· TAANA (SM37 name DVM_TAANA_ANALYSIS or TAANA ANALYSIS)

and

· DANA (SM37 name DANA ANALYSIS).

5.2 EWA analysis monitoring

Since the EWA analyses are technically the same as the analyses created for DVM, the monitoring is donein the same way, with some differences as follows:

5.2.1 Technically monitoring the background jobs

Control job: AGSDVMAS_CONTROL5.2.1.1

To display these jobs, you have to use the job selection transaction SM37.The control job name is AGSDVMAS_CONTROL and it is valid for all systems.In the job log, check the lines starting with a bullet (n), as those are the starting point for each SID/Clientand service combination.For the DVM analysis to be included in Early Watch Alert, the service type is EWA.

Below a sample of how a job log looks like:



5.2.2 Monitoring the analyses

The actual analyses can be monitored, both on the managed system (before the transfer to SolutionManager) and on the Solution Manager.There are two ways to check them, which actually take you to the same place:

a) Transaction /SSF/AB, or b) Transaction ST13àTool Name: ANALYSISBROWSER

Here you will look for analyses with the following naming convention:

DVM for EWA Analysis <SID><CLIENT>

A sample of how the job details are displayed can be seen below:



Note: these analyses are technically triggered by a scheduled job visible in the job selection transactionSM37. This job has the naming convention BO APPLICATION ANALYSIS <Number>, whose name is notvery detailed and would be very difficult to correlate to a specific process.However, it is important to note that this main job BO APPLICATION ANALYSIS <Number> triggers twoadditional jobs that are related to the final result transferred in the actual analysis data:

· TAANA (SM37 name DVM_TAANA_ANALYSIS or TAANA ANALYSIS)and

· DANA (SM37 name DANA ANALYSIS).

5.2.3 Troubleshooting

Most error messages will not be due to a software error, as they may be related to an issue in themanaged system, being it an authorization or job error in the managed system side.

Therefore, it is recommended to look into the probable causes of the error message before opening anincident with SAP.

For instance, an error in the ST14 linking (see screenshot below) is normally due to an authorizationissue in the managed system for the user configured for the TMW RFC.

You can overcome this by implementing the note 2115837.



6 Technical Details / troubleshooting

6.1 How are the Analysis jobs scheduled in the managed system(s)?

As soon as there is a DVM (step 9) or EWA (step 5.3) system set up a job is automatically scheduled to run

hourly. The name of the job is AGSDVMAS_CONTROL and it controls that all the required steps areexecuted for each system that is configured.

If you wonder what is the status for a specific system, check the job log in SM37 and look for the specificSID / Client / Service Type (EWA or DVM) combination.

Below is an example for a system set up for DVM:

6.2 If I see an error in the log, does it mean it is a software error (bug)?

Most error messages will not be due to a software error, as they may be related to an issue in the managed system, being it an authorization or job error in the managed system side.

Therefore, it is recommended to look into the probable causes of the error message before opening anincident with SAP.For instance, an error in the ST14 linking (see screenshot below) is normally due to an authorization issuein the managed system for the user configured for the TMW RFC.

6.3 I have an ST14 dataset but no analysis results in the DVM chapter in my

EWA document

You set up the customizing for a particular system / client combination, all jobs run, the ST14 dataset wascreated, but you still don't have the new DVM chapter in your EWA documents. Most likely an incomplete



ST14 dataset is the cause for this issue which is not populated with all required data.To check the reason for this please do the following:Run report RTCCTOOL with option " Prepare for DVM (Data Volumt Mgmt) service" on the managed system (use button "Settings" to select this). Implement all required SAP Notes and perform all stepsdisplayed after using button "Addons&Upgr.".

If the next EWA documents still don't show any analysis results in the new DVM chapter please logon to

the managed system and check the job logs with transaction SM37 for jobs with name ' BOAPPLICATION ANALYSIS*', 'TAANA Analysis' and 'DANA Analysis'. All three jobs should have beenstarted and finished successfully. If not, please check the job logs of all jobs and try to find out whichissues happened during the job run.If you can't solve this issue please contact your system administrator for assistance or create a ticket under component SV-SMG-DVM. In case you create a ticket please secure that R/3 support and HTTP Connectconnections to the SAP Solution Manager system and to the managed system are open. Please insert the

logon credentials for both systems in the secure area of this ticket.