Sunday, 11 September 2016

SM01 functionality


REQUIREMENT
Lock or unlock a transaction code in SAP system, which will temporarily prevent the users from accessing specific transaction code

PROCEDURE
Transaction code SM01 is used either to lock or unlock the transaction codes.
Enter the transaction code for which we have to lock (for example ST12) in the search box and then press Enter button. Select the square box which is provided next to the transaction code and chose the button Lock/Unlock.

NOTE
  1. It is possible to Lock/Unlock the Multiple transaction codes at a time.   
  2. Apart from Lock/Unlock functionality, in SM01 we can also search for the transaction codes available in the SAP system with its description and associated ABAP program.  
  3. Executing this associated program from SE38 (Most of the cases, particularly if it is executable program) is same is accessing the transaction code.   
  4. In some cases, users won't be able to access specific transaction code due to the authorization issue. But it may be possible to open the same transaction code by executing the associated program (shown in SM01) from SE38 transaction code.

What is JCMON tool


The JCmon is a monitoring program, mainly used to
·         Display list of the processes
·         Enable, disable, restart and debugging the specific process
·         Shutdown a specific J2EE instance
1.   To start the JCmon, login with <SID>adm and execute the below command:
·         jcmon pf=/usr/sap/<SID>/sys/profile/<SAPSID><INSTANCE_ID><HOST>
2.   It will display the below 4 choices on the JControl Main Menu
===================================================
JControl Monitor Program - Main Menu
===================================================

 :  exit
------------------------------------------------------------
10 : Cluster Administration Menu
------------------------------------------------------------
20 : Local Administration Menu
------------------------------------------------------------
30 : Shared Memory Menu (Solid Rock, experimental)
------------------------------------------------------------

command => 20
From Basis Administrative perspective, most important command is 20, which displays the status of the below:

1.   dispatcher
2.   Server0
3.   SDM
Idx
Name              
PID    
State               
Error
Restart
0
dispatcher        
   8028
Running             
   0
yes   
1
server0           
   7508
Running             
   0
yes   
2
SDM               
    15804
Running             
   0
yes   































JCMon Monitoring tool can be used to administrate the processes and JCmon main menu provides the following functions.
0: Exit
Returns back to the main menu

1: Refresh list
Refreshes the process list and the menu

2: Shutdown instance
Invokes the shutdown of the specified J2EE instance

3: Enable process
Enables and starts a process, which is switched off. (Restart == no)

4: Disable Process
Stops a running process and switches off the restart flag

5: Restart Process
Restarts the specified process

6: Enable bootstrapping on restart

7: Disable bootstrapping on restart

8: Enable Debugging
Checks if the specified process is running in debug mode. If not and the process is configured for debugging, JControl will restart the process in debug mode

9: Disable Debugging
If the process is running in debug mode, JControl will restart the process and switch off the debug mode

10: Dump stack trace
The specified process gets an event to invoke the dump of the stack trace of the Java VM. The stack trace is stored in the stderr<n> output file in the work directory

11: Process list
Displays the status and additional information about all the processes

12: Port list
Displays a list with detailed information about the ports used by the J2EE Engine

13: Activate debug session
Activates the debug session for the specified process. To activate a debug session:
·         The process must be running in debug mode.
·         The process must be “Load Balance Restricted”

14: Deactivate debug session
Deactivates the debug session. The process will be restarted or stopped – this depends on the process configuration

15: Increment trace level
This increments the trace level for the developer trace file of the specified process (dev_<component name>)

16: Decrement trace level
This decrements the trace level for the developer trace file of the specified process (dev_<component name>)

17: Enable process restart

18: Disable process restart


          - - - - - - - -- - - -- - - -Continue- - - -- - - -- - - -- - - -

40 : Enable bootstrapping for all processes with specified process type

41 : Enable bootstrapping for all processes excluding specified process type

          - - - - - - - -- - - -- - - -Continue- - - -- - - -- - - -- - - -

98: Synchronize instance properties

99: Extended process list on/off

Schedule process Chain in BW

REQUIREMENT:
Process Chain needs to be scheduled for the data collection and distribution in BW system.

We will discuss how to schedule the Process Chain in BW system.

  • Logon to BW system
  • Go to Transaction code RSA1/RSPC
  • Search the mentioned Process chain
  • Activate the Process chain and schedule the same.
  • Scheduled process chain can confirmed with Green Ticket in the left of the window.

Run Transaction code RSPC
Click on Change Mode
ފ°







The Process Chain will be successfully scheduled in the system