Tuesday, October 27, 2009

J2EE Engine : JControl & JCmon

JControl
JControl starts, stops, and monitors the processes of a Java instance - primarily the server and dispatcher processes.
JControl restarts terminated processes, ends hanging processes, and sends a shutdown signal to Java instances.
JControl starts the JLaunch processes, which in turn start Java nodes such as dispatchers or servers.
JControl starts a Java instance bootstrap process with parameters that are defined in the file bootstrap.properties (/usr/sap///j2ee/cluster/bootstrap)

-> Java profiles are stored under \usr\sap\\SYS\profile\DIR_PROFILE

JCmon
The JCmon tool can be used to monitor the JControl process. JCmon is part of the Startup and Control Framework, and is located in the JControl/JLaunch home directory, that is, in the executable directory /usr/sap///j2ee/os_libs.
JCmon can be started with the command JCmon pf=.

Thursday, October 15, 2009

J2EE Engine : Restarting a Single Process

 

       1.      Start JCmon

           The system prompts you to choose a command number.

       2.      Choose command 5 "Restart process" (this command restarts a specified process).

           The system prompts to specify the index of the process that you want to restart.

           You can view the process indexes from the table of processes that is displayed every time you execute a command.

           The  indexes are displayed in the first column of the table (Idx).

       3.      Specify the index of the process that you want to restart and confirm your choice.

 

The JCmon restarts the specified process.

J2EE Engine - Checking That All Processes Are Running

 

Procedure

...

       1.      Start JCmon.

         The system prompts you to choose a command number.

       2.      Choose command 11 "Process list" (this command displays the status of the processes).

The result displayed on the command line will be something like this:

------------------------------------------------------------

SAP System Name   : J2E

SAP System        : 00

MS Host           : testpc-doc

MS Port           : 3601

Process Count     : 3

PID of JControl   : 3108

State of JControl : All processes running

State inside MS   : All processes running

Admin URL         :

------------------------------------------------------------

 

|Idx|Name                |Type                |PID     |State               |Err

or|Restart|Debug|Debug|Debug |

|   |                    |                    |        |                    |Cou

nt|Mode   |Prep.|Mode |Port  |

|---|--------------------|--------------------|--------|--------------------|---

--|-------|-----|-----|------|

|  0|dispatcher          |J2EE Dispatcher     |    2900|Running             |

 0|yes    |no   |no   | 50000|

|  1|server0             |J2EE Server         |    3580|Running             |

 0|yes    |yes  |no   | 50021|

|  2|SDM                 |SDM Server          |    3556|Running             |

 0|yes    |yes  |no   | 50002|

------------------------------------------------------------

 

 

------------------------------------------------------------

SAP System Name   : J2E

SAP System        : 00

MS Host           : testpc-doc

MS Port           : 3601

Process Count     : 3

PID of JControl   : 3108

State of JControl : All processes running

State inside MS   : All processes running

Admin URL         :

------------------------------------------------------------

 

|Idx|Name                |PID     |State               |Error|Restart|

|---|--------------------|--------|--------------------|-----|-------|

|  0|dispatcher          |    2900|Running             |    0|yes    |

|  1|server0             |    3580|Running             |    0|yes    |

|  2|SDM                 |    3556|Running             |    0|yes    |

------------------------------------------------------------

 

 

============================================================

JControl Monitor Program - Administration Menue (Local)

Instance : JC_J2E_00_testpc-doc

============================================================

0  : exit

1  : Refresh list

2  : Shutdown instance

3  : Enable process

4  : Disable process

5  : Restart process

6  : Enable bootstrapping on restart

7  : Disable bootstrapping on restart

8  : Enable debugging

9  : Disable debugging

10 : Dump stacktrace

11 : Process list

12 : Port list

13 : Activate debug session

14 : Deactivate debug session

15 : Increment trace level

16 : Decrement trace level

17 : Enable process restart

18 : Disable process restart

------------------------------------------------------------

98 : Synchronize instance properties

99 : Extended process list on/off

------------------------------------------------------------

command =>

 

The status of each process is displayed in the corresponding tables above.

 

 

JCmon Menu options (features)

 

The 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:

1.      The process must be running in debug mode.

1.      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

-----

98: Synchronize instance properties

99: Extended process list on/off

 

J2EE Engine : Monitoring – JCmon

 

The JCmon is a native monitoring program, part of the startup and control framework, which can be used to:

1.      Display a list of the processes

2.      Enable, disable, and restart the specified processes

3.      Shutdown a specified J2EE instance

4.      Enable/disable debugging for a specified process

5.      Dump stack trace

6.      Display a list of the ports used by the J2EE Engine

7.      Activate/deactivate debug sessions

8.      Increment/decrement the trace level

 To start the JCmon, execute the jcmon script file from the /usr/sap/<SID>/<INSTANCE NAME>/j2ee/os_libs directory, where <SID> is the system ID of the cluster (for example, C11) and <INSTANCE NAME> is the instance name of the J2EE instance (for example, JC00). The instance name consists of a prefix (JC or J) and the two-digit instance number afterwards. As parameter for the jcmon script file specify the SAP instance profile:

jcmon pf=/usr/sap/<SID>/sys/profile/<SAPSID>_<INSTANCE_ID>_<HOST>.

Example:

jcmon pf=/usr/sap/C11/sys/profile/C11_JC00_testpc.

 Enter command '20' to display the main menu.


 

J2EE Engine : Requesting & Installing SAP License

 


You need a valid SAP license to log on to SAP Web AS. After installation, a temporary license is installed, you must replace it with a permanent license.
Note : With a J2EE + ABAP installation (SAP Web Application Server with ABAP and J2EE to the ABAP import license (see SAP license), You can ignore this section.

Before Requesting & Installing licensem SAP J2EE Engine must be installed and Visual Administrator have to be started.

Procedure

        1. Visual Administrator, choose Server 0 -> Services -> Licensing Adapter. You will see the system data, you need to request the license on the SAP Service Marketplace:

○ installation number (if available)

○ System ID,

○ System number (if available)

○ Hardware key

○ News Release


        2. Under the web
https://service.sap.com/licensekeys you to the start page of the license key request in the SAP Service Marketplace. Here you will find all necessary information to request license keys.

        3. Give in to the request your email address. The license key is provided to you via email if available. Alternatively, the license key in the SAP Service Marketplace can be downloaded.

Do not make any manual changes to the license file through! To import the license, it is necessary that the file is used unchanged!

        4. Select Licensing Adapter in the Visual Administrator install license from file.

        5. Select the license file you received from SAP. 


You can see all installed licenses of its SAP system by using the
Visual Administrator choose Server -> Services -> Licensing Adapter tab Runtime -> Installed Licenses

Licensing J2EE Engine

 

 

After installing the SAP J2EE Engine, you can sign up as a temporary license was automatically installed.

You must now request for a permanent SAP license and install it.

If you have installed the SAP Web Application Server with ABAP and J2EE, you use the licensing system, which came with earlier releases of SAP Web AS.

There are 2 types of licenses for SAP: permanent and temporary licenses.

· Permanent License

How do you request a permanent license for SAP and install it on your system, under SAP Request license to install and described.

· Temporary License

If your permanent license has expired, you can install a temporary license for quick remedies.

In the Visual Administrator, choose Server 0 -> Services -> Licensing Adapter. Here you select the tab page Runtime -> General and then install subsequent temporary license.

This is 28 days. Then again, you should have installed a permanent license.

Note that you can not install another temporary license if the license had expired even temporarily.

A newly installed license is effective until you restart the SAP J2EE Engine!

It does not matter whether it is permanent or temporary license.

 

Specifying the J2EE Engine Client to Use for Logon Tickets

 

When issuing logon tickets, it is necessary to make sure that the user's ID for which the logon ticket has been issued is unique. For SAP Web AS, this includes determining the system ID and the client where the user exists. These attributes are necessary when maintaining the access control list in accepting systems and are therefore included in the user's logon ticket.

When the J2EE Engine is the ticket-issuing system, its system ID is used as specified in the installation. Although the J2EE Engine does not have a client, it still needs to provide a client value to use for logon tickets so that the tickets can be accepted by other systems, for example, from an SAP Web AS ABAP. The default client for the J2EE Engine is 000, however, you can explicitly set a different value to use.

 

The system ID and client combination must be unique when tickets are to be accepted by an SAP Web AS ABAP system. Therefore, in an Add-In installation, where the system IDs are the same, you must change the default client for the J2EE Engine (000) to a client that does not exist on the SAP Web AS ABAP system.

 

You can specify the configuration for logon tickets either in the UME properties or in the options for the login module CreateTicketLoginModule. The configuration to use depends on the value of the property ume.configuration.active.

If you use the UME configuration, then to specify the J2EE Engine's client set the property login.ticket_client in the UME property sheet. Otherwise, set the property client in the options for the login module CreateTicketLoginModule. (The reason for these two configuration options is to provide for downward compatibility.)

See the procedures below for information about checking the ume.configuration.active property and where to set the logon ticket client property.

 

Checking the Property ume.configuration.active

To check the value of the property ume.configuration.active for the login module CreateTicketLoginModule, use the Security Provider service. Check for this parameter in both the policy configurations as well as in the user store configuration.

 

Checking the Property in the Policy Configurations

 

 1.      In the Security Provider service, choose Policy Configurations.

 2.      Select each template or application that uses the login module CreateTicketLoginModule, for example, the template ticket.

The login module stack for this component appears.

If you do not know which components use the login module, then check the login module stacks for all of the components.

 

The table below shows the login module stack for the ticket template as it is delivered with the J2EE Engine. In this case, the option ume.configuration.active=true is set in the policy configuration for the ticket template.

Ticket Template Login Module Stack

Login Modules

Flag

Options

com.sap.security.core.jaas.
EvaluateTicketLoginModule

SUFFICIENT

{ume.configuration.active=true}

BasicPasswordLoginModule

REQUISITE

{}

com.sap.security.core.jaas.
CreateTicketLoginModule

OPTIONAL

{ume.configuration.active=true}

 

Checking the Property in the User Store Configuration

1.      In the Security Provider service, choose the User Management tab page.

2.      Choose Manage security stores.

3.      Select the login module CreateTicketLoginModule and choose View / Change Properties.

 

                   Recommendation

If the ume.configuration.active property (or any other property) is set in the policy configurations and not in the login module options in the user store, then we recommend moving the setting(s) to the user store.

 

Reason

 

If properties are set in the login module options in the user store, then these properties are inherited by the policy configurations that use the corresponding login module.

However, if a property is set in the policy configurations, then no inheritance will take affect, even for additional properties that are set in the user store. Therefore, we recommend only setting options in the user store and not in the policy configurations.

 

J2EE Engine : Post-Installation Procedures

· Creating a second administrator user
To prevent locking the administrator in case you do change its password and forget to update the entry secure storage, we also recommend you create a second administrator user after installing the J2EE Engine.

· Add-In installation only:
Single Sign-On using logon tickets requires a client from the ticket-issuing system. For this purpose, the J2EE Engine uses the client 000 per default. However, the system ID and client combination must be unique when tickets are to be accepted by an SAP Web AS ABAP system. Therefore, in an Add-In installation, you have to change the default client (000) to a client that does not exist on the SAP Web AS ABAP system.

(SAP Web AS installation guide is available on SAP Service Marketplace at http://service.sap.com/installNW70 -> Installation.)

Tuesday, October 6, 2009

Frequently used Tcodes in SAP

 

Serial No

Transaction Code

Function

1

ABAPDOCU

Example Library

2

ABAPHELP

Keyword Documentation

3

AL03

Operating system Alert Monitor

4

AL05

Workload Alert Monitor

5

AL08

List of all Users Logged ON (about all Instances/Servers of the System) 

6

DB01

Exclusive waits in Oracle database

7

DB02

Database performance ; tables and index

8

DB03

Parameter changes in database

9

DB05

Analysis of table with respect to indexed fields

10

DB12

Backup logs

11

DB13

DBA planning calendar

12

PFCG

Role Maintenance

13

RZ06

Maintain alert threshold

14

RZ08

CCMS Alert Monitor

15

RZ10

Maintain system profiles

16 

RZ20

Alert Monitor 4.0

17 

RZ21

Maintain settings for Alert Monitor 4.0

18

RZ11

Profile Parameter Maintenance

19

SA38

ABAP Reporting

20

SCAM

CATT Management

21

SCAT

Computer Aided Test Tool

22

SCC1

Client copy transport

23

SCC3

Client copy log

24

SCC4

Client copy administration

25

SCC5

Delete Clients

26

SCC6

Client import

27 

SCC7

Client import--- post processing

28 

SCC8

Client export

29

SCC9

Remote client copy

30

SCCL

Local client copy

31

SCDO

Change Document Object

32

SCMP

Table comparison

33

SCU3

Table History

34

SCI

Code Inspector

35

SE01

Transport Organizer(Extended View)

36

SE06

Set up workbench organizer

37 

SE09

Transport organizer

38 

SE10

Customizing  organizer

39 

SE11

Data dictionary maintenance`

40 

SE12

Data dictionary display

41

SE15

Repository Info System

42

SE16

Display table content

43

SE17

General table display

44

SE37

ABAP Function Modules

45

SE38

ABAP Editor

46

SE41

Menu Painter

47 

SE51

Screen Painter

48 

SE71

Form Painter

49 

SE80

Object Navigator

50

SE93

Maintain Transaction

51

SFT2

Maintain public holiday calendar

52

SFT3

Maintain factory calendar

53

SHDB

Transaction Recorder

54

SICK

Installation check

55

SLIN

Extended Check

56

SM01

Lock Transactions

57 

SM04

Overview of users

58 

SM13

Update terminates

59 

SM21

System Log

60 

SM30

Maintain tables(not all tables can use SM30)

61

SM31

Maintain tables

62

SM35

Batch Input Monitoring

63

SM37

Overview of background jobs

64

SM39

Job analysis

65

SM49

External operating system commands, execute

66 

SM50

Work process overview

67 

SM51

Instance overview

68 

SM58

Error log for asynchronous RFC

69 

SM59

RFC connection, maintain

70

SM63

Operations mode, maintain

71

SM66

Global work process overview

72

SM69

External operating system commands, maintain

73

SP00

Spool

74

SP01

Spool control

75

SP02

Display output requests

76 

SP11

TemSe(temporary sequential objects) contents

77 

SP12

TemSe administration

78 

SPAD

Spool administration (printer setup)

79 

SPAM

SAP Patch Manager

80 

SPAU

Intersection SAP Transport/customer modifications

81

SPIC

Spool; installation check

82

ST01

SAP system trace

83

ST06

Operating system monitor

84

ST07

Application Monitor

85

ST09

Table call statistics

86 

ST11

Display developer trace

87 

ST12

Application monitor

88 

ST22

Dump Analysis

89 

STAT

Local Transaction statistics

90

STUN

Performance monitoring

91

SU01

User maintenance

92

SU02

Maintain authorization profiles

93

SU03

Maintain authorizations

94

SU10

Maintain change to user records

95 

SU12

Delete all users

96 

SU2

Maintain user parameters

97 

SU53

Display authorization checked values

98

SM12

To unlock the locked entries

99

SAAB

Checkpoints that Can Be Activated

100

SALE

ALE customizing transaction

101

CG3Y

Transfer file from application server to front end.

102

CG3Z

transfer file from front end to application server

103

NACE

conditions of output control (to create a link between forms and driver programs)

104

ST05

SQL tracer (for performance tunning)

105

SE30

ABAP runtime analysis(Performance tuning)

106

SE61

SAP Documentation

107

SE62

Industry Utilities

108

SE63

Translation: Initial Screen ( to Translate Short / Long Text )

109

SE64

Terminology

110

SE72

SAPscript Styles

111

SE73

SAPscript Font Maintenance

112

SE74

SAPscript format conversion

113

SE75

SAPscript Settings

114

SE76

SAPscript: Form Translation

115

SE77

SAPscript Styles Translation

116

smartforms

Smartforms

117

Wedi

IDOC and EDI basis

118

we31

Segment creation

119

we30

Idoc Type creation

120

we81

Creation and assigning of Message type