SAP Basis/Netweaver Tutorials, Monitoring, Administration(Certification) and FAQs Headline Animator

SAP Basis/Netweaver Tutorials, Monitoring, Administration(Certification) and FAQs


Thursday, 9 June 2011

How to configure Early Watch Alert report

To configure Early watch alert some specific settings to be done at managing system (Solution manager system) and satellite system( or managed system – for which EWA report to be generated)
Following are the steps to configure EWA in a satellite system :

1) Check whether latest versions of ST-A, ST-PI, ST-A/PI packages are installed in the managed/satellite system
(This check can be done going to system->status -> Component information display in any sap screen)

2) If they are installed, run RTCCTOOL report from SE38 transaction code of satellite system.

Check the output of the report. If there are some errors or warnings in the output of the report, please take corrective actions and run the report again and ensure there are no errors

3) Setup RFC connection between your satellite system and the solution manager system
An RFC connection can be made between 2 systems using Transaction code SM59
4) Setup RFC connection between your solution manager and the SAP service market place

5) Assign the solution monitoring roles to the users

6) Setup your satellite system in a solution landscape of the solution manager(SMSY)

7) Make sure SLD is configured and working fine for satellite system (using Rz70 and SLDCHECK transactions)

8) Activation of SDCCN in satellite system (Goto SDCCN transaction. Then click on Utilities -> Activate)  then confirm for SDCC_OSS destination creation

9) In satellite system, goto SDCCN transaction and navigate to Goto -> Settings -> Task specific.
In the resulted screen, select RFC destination and provide the solution manager RFC from the satellite system and set solution manager RFC as the master system.

10) Addition of satellite system in solution manager system in SDCCN :

Goto SMSY transaction in solman system and then navigate to Environment -> Solution Manager Operations -> Adminstration SDCCN to add the new service data control centre to the solution manager.

Click on add system button to add the new SDCC to the solution manager. When prompted, please select the respective system and client from the resulting screen and confirm

11) Early watch service session activation for satellite system:

In the solution manager system, execute transaction code solution_manager  and navigate to operations -> Earlywatch Alert and press create button. This prompts you to confirm the date and time to run the report. Please provide the details and confirm to trigger the generation of the report

12) Login to satellite system, goto transaction code SDCCN and press create button which displays a screen to select a task to be executed. Select request session data task  and click continue. You will be prompted to enter the schedule time to run the report. Click now to execute it immediately. After that you can see an early watch session running in SDCCN.

13) After completion of this session run successfully, an Earlywatch Alert will be generated and this can be viewed in Solution_manager of Solution manager system.



Related articles:



How to delete an SAP lock ?

This article answers following queries :

  • What is a SAP lock ?
  • Different types of SAP locks ?
  • Difference between Write lock(E) and Enhanced write lock(X) ?
  • How to monitor SAP locks ?
  • How to delete SAP locks ?

****************************************************************

SAP lock is set by the executing workprocess when a user/job wants a change access to data.

Whenever a lock to be set the respective workprocess checks in the locktable whether a respective lock conflicts the existing entries in the locktable. If so, a lock is refused. If there is no conflict, then a lock is set.

There are different types of locks :

Write locks (E) : This is also known as exclusive lock mode as the lock data can be edited by only one user. Any other requests from workprocesses to set another write lock or read lock are rejected. A cumulate lock can be applied on the lock data by the same lock owner again.

Read locks (S) : This is also known as shared lock mode as several users can have read access to the locked data at the same time. Additional read lock requests are entertained even if they are from different users. However a write lock is rejected.

Enhanced write locks (X) : This is also known as exclusive non-cumulative lock mode. An enhanced write lock can be requested only once even if it is by the same transaction.

Difference between write locks(E) and Enhanced write lock(X) is write locks can be set and released by the same transaction several times but X type locks can also be set once even by the same transaction.

Optimistic locks (O) : These locks are set up when the users displays the data in change mode. Several optimistic locks can be setup on the same data. Optimistic locks are read locks(S) at first and converted to write lock (E) when the users wants to save the data. If an optimistic locks on a data is changed to write lock(E), all other optimistic locks on that data will be deleted.

Locks that are set by an application program are released by the program itself or they are released by the update program once the database has been changed.

Transaction code SM12 can be used to monitor SAP locks.




Here you have option of selecting locks based on following parameters
  • tablename
  • lock argument
  • client
  • username


















In case, as part of monitoring, if you encounter some old sap locks and after thorough analysis, you would like to delete these, it can be done in the following ways :
  • Select the locks and delete the lock from SM12
  • Identify the user who has set the respective lock and end the user session using SM04 transaction code









Wednesday, 8 June 2011

What is the difference between dynamic and static parameter

This article answers following queries :

  • What is a SAP parameter?
  • Different types of SAP Parameters?
  • How to identify whether a parameter is dynamic or static ?

***************************************************************

In SAP, parameters are used to set the configuration and define the functionality of an sap system like number of workprocesses, buffer size, locktable size etc.

Basically there are 2 types of parameters :

  • Static
  • Dynamic
Static are the parameters those won't take effect immediately the value is set. Restart of an sap system is required for them to take effect.

Dynamic are the parameters those will take effect immediately in the run time. Restart of an sap system is not required for them to take effect.

Parameter can be differentiated whether it is dynamic or static by checking in RZ11 transaction of SAP.









 In Rz11, type the parameter and display it. In the screen , there will be a check box with description as "Dynamically switchable". If that check box is ticked, it means that it is dynamic parameter and value can changed in run time without restart of the system. If it is not ticked, then it is static parameter and it needs restart of a sap system for the changes to take effect. 



How to change the number of workprocesses

This article answers the following queries:

  • What is a workprocess ?
  • What are the different types of workprocesses and their functionality ?
  • How to increase/decrease the number of workprocesses?


****************************************************************


A work processes is used to execute a particular type of job in an sap system.

There are different types of workprocesses as mentioned below :

DIA   (Dialog workprocess) : Used for execution of dialog steps triggered by active users. For every dispatcher atleast 2 dialog workprocesses to be configured

UPD  (Update workprocess) : Used for execution of update tasks. Atleast one update workprocess to be configured per SAP system. Also, more than one UPD can be configured for a dispatcher

BTC  (Background workprocess): Used for executing background jobs. Atleast 2 background workprocesses to be configured for an SAP system

SPO   (Spool workprocess) : Used for passing sequential data to printers. Atleast one spool workprocess to be configured for an sap system.

UP2   (Update2 workprocess) : This is similar to UPD workprocess. There is small difference in functionality based on criticality of the update.

ENQ  (Enqueue workprocess) : This is required to administer locktable in the shared memory. Locktable contains database locks for ABAP stack of an sap system. Only one enqueue process to be configured for an SAP system.


To increase/decrease the number of workprocesses, value to be changed accordingly for the following parameters as per workprocess in RZ10 Transaction.

rdisp/wp_no_dia  (for dialog workprocess)
rdisp/wp_no_btc  ( for background workprocess)
rdisp/wp_no_spo  (for spool workprocess)
rdisp/wp_no_enq  (for enqueue workprocess)
rdisp/wp_no_vb    (for update workprocess)
rdisp/wp_no_vb2  (for update2 workprocess)

In RZ10 transaction, select the profile of the instance, for which workprocess number to be changed and edit the profile through extended maintenance and save the changes done and activate the profile.

Please note that as this parameter is not dynamic one, restart of the application server is required for the changes to become effective.