ABAP Transaction Codes Related To Java Administration

ABAP Transaction Codes Related
to Java Administration
Applies to:
SAP R/3 servers from 4.6C onwards to the latest NetWeaver releases. Some TCodes can even be used for
previous releases; however their functionality (and the transaction code screens) may differ. For more
information, visit the Java homepage.
Summary
In a productive landscape, an SAP J2EE server/ SAP Enterprise portal or any other application based on the
JAVA engine is in constant interaction with a variety of backend R/3 servers, be it UME related, internet
application components (IAC’s) like ESS or MSS, TREX etc. This guide describes the main TCodes from the
ABAP end that can be useful to assist troubleshooting in such cases where connection is made from the j2ee
server to the R/3 server or vice versa.
Author: Hemanth Kumar

Company: SAP
Created on: May 4th, 2010
Author Bio
Hemanth is a SAP consultant, working in SAP technology for the last 5½ years.
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

© 2010 SAP AG 1
ABAP Transaction Codes Related to Java Administration
Table of Contents
Introduction ......................................................................................................................................................... 3
1) General System transactions ................................................................................................................ 3
1.1) SM21/ ST22 ........................................................................................................................................... 3
1.2) STAD, ST03G, SKUSR001 ................................................................................................................... 4
1.3) SM04, Al08 ............................................................................................................................................ 5
1.4) SM28/SICK, SLICENSE ........................................................................................................................ 5
1.5) SDMO and SEARCH_SAP_MENU ....................................................................................................... 6
1.6) SITSPMON and SE93 ........................................................................................................................... 6
1.7) SICF ....................................................................................................................................................... 7
1.8) SPAM ..................................................................................................................................................... 8
1.9) STMS ..................................................................................................................................................... 8
2) Operating System and DB transactions ................................................................................................ 9
2.1) SM51 / RZ03 / SMMS ............................................................................................................................ 9
2.2) SM59, TREXADMIN ............................................................................................................................ 10
2.3) SMICM, RZ10, RZ11, RSPFPAR, RSPARAM .......................................................................................... 10
2.4) ST06N,OS01 ....................................................................................................................................... 11
2.5) AL11, ST11 ......................................................................................................................................... 12
2.6) SMGW, RZ70 ...................................................................................................................................... 12
2.7) DBACOCKPIT, DB01, DB13, ST04..................................................................................................... 13
3) Security TCodes .................................................................................................................................. 14
3.1) SU01, SUIM, PFCG, PFUD ................................................................................................................. 14
3.2) STRUST, SSO2 and STRUSTSSO2................................................................................................... 14
3.3) ST01, SM20N, ST05, SM50 ................................................................................................................ 15
3.4) SDCC ................................................................................................................................................... 15
Related Contents .............................................................................................................................................. 16
Copyright........................................................................................................................................................... 17

© 2010 SAP AG 2
Introduction
With the advent of SAP NetWeaver and modern internet, there is constant interaction between various SAP
systems and other applications that necessarily do not belong to the world of SAP ( as shown in the below
NetWeaver fridge diagram). For instance, in an Employee Self Service scenario your portal would require a
system to generate the appropriate calls from your Human Resource Environment. Hence if issues creep up
relating to performance, configuration, connection etc., along with the investigation from the JAVA end (using
java administration tools like visual admin, config tool, telnet etc), it is also useful to check the backend R/3
servers for important leads that may result in faster resolution of the issue. This guide provides main TCodes
for the same and has been segregated into three parts and shows a brief overview about the main Tcodes in
each area.
1) General System transactions

1.1) SM21/ ST22
 Information from the system log can be seen from /n SM21. This should be the starting point
of all investigation. For all servers: Syslog -> choose -> all remote system logs

© 2010 SAP AG 3
In this case the communication user error is shown. Double click for more details.
 /n ST22 shows all the ABAP runtime errors
For example, the user logs in from the portal and (for an ESS/MSS application) there is a dump that is
generated, /nSt22 will show more details of the same.
1.2) STAD, ST03G, SKUSR001

 Transaction /n STAD can be used to call up various statistical data for RFC, in order to find
the status of actions that you have performed. With STAD you can identify the portal URL
which uses the ABAP server as UME backend and other information.
 Report SKUSR001 shows the time the server was functional (same as available.log file)
 Global Workload Monitor (transaction /n ST03G) displays statistical records for entire
landscapes including web clients /specific frontends that have accessed the ABAP engine
/nST03G will show the portals/ j2ee servers and other external connections that have been made to the
ABAP server. This is very useful information as you can also find the total number of connections, data
transferred and lot of other data.

© 2010 SAP AG 4
1.3) SM04, Al08

/n SM04 shows the user list from the actual application server including RFC users.
TCode /n AL08 you will get a list of all currently active users in the whole SAP server. If there are
connections from the portal/ j2ee server, you can check this here.
In this case, the portal on the server dewdfm733.wdf.sap.corp is connecting to the ABAP backend.
Profile parameter rdisp/tm_max_no is useful in this case as it determines the maximum
connections to R/3 server. At times it is possible that many connections are made from the portal
end and no other users are able to login to the R/3 server. In such cases, you can increase this
parameter (from /n RZ11).
1.4) SM28/SICK, SLICENSE

Soon after installation, run TCodes /n SM28 or /n SICK to ensure that the correct database versions
and R/3 kernel versions are used, and to make sure that there are no inconsistencies. If there are
some database patches that are needed for the ABAP or the JAVA schema, this will be shown here
along with the specific SAP note.
Tcode /n SLICENSE (or operating system command “slicense –install ”) is used to install
licenses in case of standalone/add-in installations
Note that incase the server is an ADD-IN installation, there is no need to install another license (via
Visual admin) for the java server. Just /n SLICENSE is needed in this case.

© 2010 SAP AG 5
1.5) SDMO and SEARCH_SAP_MENU

/n SDMO (Searching T Codes) allows you to search for transaction after entering what the
transaction is supposed to do. Example: Lets say that you have forgotten which is the TCode for
administering the internet communication manager. Just navigate to /n SDMO or /n
search_sap_menu and type in the details you know.
/n Search_sap_menu gives the same option
You can see all the TCodes that deal with the ICM now.
1.6) SITSPMON and SE93

Use transaction /n SITSPMON to get a status summary of the integrated ITS and users currently
accessing ITS.

© 2010 SAP AG 6
Transaction /n SE93 governs whether a particular TCode can be accessible via various SAP GUI’s
If you do not want sensitive TCodes to be accessed via HTML etc. then this can be specified here. For
example in a ERP server, you want to restrict TCode /n PA30 (Maintain HR master data) from being invoked
from the portal, then just untick the “sapgui for HTML” option.
1.7) SICF
After the installation of the ABAP server, all Internet Communication Framework (ICF) services are
available in an inactive state for security reasons. After the installation you have to decide which
services must be activated for the applications you want to use. For forms like ADS to work, SICF
nodes must be activated.

© 2010 SAP AG 7
Hence if ADS is not working from the portal end, first check should be done on the /n SICF level to
see if the node is working fine. Also you can test the service from here.
1.8) SPAM
If the UME of the j2ee engine is an ABAP server and if the support pack upgrades are running on the
server, the j2ee too will stop functioning or the performance will go down considerably. In such
cases, TCode /n SPAM needs to be checked (along with background jobs).
The system log will guide you in such cases as well (as the /n SPAM upgrade details will be present
here as well).
1.9) STMS
The enhanced Change and Transport System (CTS+) enables users to transport Java objects (SCA,
EAR, SDA, EPA, PAR files) alongside ABAP objects. Also, it is possible to administer non-ABAP
systems in a CTS transport domain in the R/3 server. You can also maintain SDM details and the
deployments can be done from the /n STMS screen itself.

© 2010 SAP AG 8
2) Operating System and DB transactions

2.1) SM51 / RZ03 / SMMS
 Overview of all running SAP-Servers (/n RZ03 shows the configured SAP servers – not just
the ones that are started)
 With the button RELEASE NOTES you will get the info of the kernel patch level and other
related data in TCode /n SM51
 You can switch to another server, see ABAP message server properties (this data is very
valuable and used in several cases where the J2EE server needs to be connected to the
ABAP backend (like ADS, JCo destination etc.)
 Application servers can be started/stopped without OS access.
/n SM51
/n RZ03

© 2010 SAP AG 9
2.2) SM59, TREXADMIN

 The RFC destination (/n SM59) defines the physical communication to the remote
destination. For the ABAP server to connect to java related services like ADS, TREX etc. an
SM59 destination needs to be created.
 The TCode /n TREXADMIN allows users to check whether the connection to the TREX
server (installed on the java part) is working fine.
2.3) SMICM, RZ10, RZ11, RSPFPAR, RSPARAM

 Transaction /n SMICM can be used to monitor and administer the Internet Communication
Manager, which sends and receives requests to and from the Internet. (ICM) of the ABAP
instance starts and stops the associated Java instance as required.
 Profile parameters rdisp/j2ee_start and rdisp/j2ee_lazy determines whether the j2ee
should be started by the ABAP dispatcher or in a “standalone” mode (more details for the
same are available in /n RZ11)
 Profile files are visible via /n RZ10 and individual parameters can be changed via /n RZ11.
Please note that for a add-in installation, there are no separate profile files for java and abap
part. You can amend java related parameters as well from the TCode /n RZ11. Reports
RSPARAM and RSPFPAR uses the OS command SAPPFPAR and displays all the profile
parameters.

© 2010 SAP AG 10
2.4) ST06N,OS01
 /n ST06, the operating system monitor shows all the OS memory details, status of the
SAPOSCOL. The SAP OS Collector can be started/stopped from /n ST06.
 If the user reports that from the presentation layer (sap gui, web browser) , he is not able to
connect to the java part or abap part, use /n OS01 to check the network connection is fine.
This is useful if a portal link (like ESS/MSS) does not work for a particular user but for others
it works fine.

© 2010 SAP AG 11
2.5) AL11, ST11

 With Tcode /n AL11, administrators should be able to view files on the OS level. Also a new
directory location can be created as per the need.
 /n ST11 TCode shows the work folder in sequence of the files modified.
 TCode /n SM49 and /n SM69 allows users to create their own OS commands and execute
them from within the ABAP server.
 Report RSBDCOS0 gives a telnet like interface inside the ABAP server to execute OS
commands. Now no need to specifically log into the operating system to run commands.
For example, in the above figure, “pwd” command returns the present location.
2.6) SMGW, RZ70

 The gateway monitor shows the gateway properties, the active connections registered on
the gateway and other details. If there are issues with the JCo destinations connecting the
R/3 server, then you can first check whether the connection is visible here in the logged on
clients. For example, in this below screen, the portal pwdf2836 connects to the R/3 server for
ADS related functionalities.

© 2010 SAP AG 12
 The gateway service can also be stopped from /n SMGW

 The Tcode /n RZ70 allows connection of the ABAP server to the SLD installed on a J2EE
engine.
2.7) DBACOCKPIT, DB01, DB13, ST04

 The /n DBACOCKPIT is a platform-independent tool that you can use to monitor and
administer your database. The JAVA schema of the database can also be monitored from
here and activities like adding tablespace can be done. You can see:
1) The free space (/n DB02),
2) Schedule backup (/n DB13)
3) Schedule remote backups (/n DB13C)
4) View backup logs (/n DB14)
5) View database locks (/n DB01)

© 2010 SAP AG 13
3) Security TCodes
3.1) SU01, SUIM, PFCG, PFUD
 TCode /n SU01 allows general user maintenance and addition of roles/profile to the user
master data. If the UME of the java server is an R/3 server (ABAP), then you can do user
administration for the java users from here as well.
 Use TCode /n PCFG to generate profiles and add authorisation objects to profile.
 Mass user comparison can be achieved by /n PFUD
 /n SUIM allows searching of user profiles, roles, authorization objects etc.
3.2) STRUST, SSO2 and STRUSTSSO2

 TCode /n STRUST can be used to add a certificate to the system's list of certificates in the
database.
 TCode /n SSO2 can be used to check the logon tickets being employed.
 TCode /n STRUSTSSO2 is a culmination of both the above transactions.
 Also for SSO connection between a J2EE server and a ABAP server to work, the values of
login/accept_sso2_ticket and login/create_sso2_ticket must be set.

© 2010 SAP AG 14
3.3) ST01, SM20N, ST05, SM50

 When a RFC connection is made to the ABAP server from a portal/j2ee engine, ultimately, it
is the ABAP dialog workprocesses that connects to the DB, retrieves the necessary
information and is responsible for the request. Traces can be activated for:
1) specific workprocess (using /n SM50)
2) for specific users (/n ST01)
3) For specific users logged in specific clients (/n SM20N)
4) Functional trace using /n STATTRACE
3.4) SDCC
TCode /n SDCC allows data transfer from the customer system to SAP so that data /system
measurement is possible and SAP can proactively suggest corrective measures to the customer so that
in future issues do not occur.

© 2010 SAP AG 15
Related Contents
For more information, visit the Java homepage.
For more information, visit the Software Logistics homepage.

© 2010 SAP AG 16
Copyright
© Copyright 2010 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG.
The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9,
iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,
PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes,
BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,
Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems
Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of
Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts
Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by
Netscape.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned
herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and
other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.
All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document
serves informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP
Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the
express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an
additional warranty.

© 2010 SAP AG 17

ABAP Transaction Codes Related To Java Administration

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

ABAP Transaction Codes Related To Java Administration

Caricato da

Copyright:

Formati disponibili

ABAP Transaction Codes Related

Author: Hemanth Kumar

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

1) General System transactions

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

 /n ST22 shows all the ABAP runtime errors

1.2) STAD, ST03G, SKUSR001

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

1.3) SM04, Al08

1.4) SM28/SICK, SLICENSE

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

1.5) SDMO and SEARCH_SAP_MENU

/n Search_sap_menu gives the same option

1.6) SITSPMON and SE93

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

2) Operating System and DB transactions

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

2.2) SM59, TREXADMIN

2.3) SMICM, RZ10, RZ11, RSPFPAR, RSPARAM

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

2.5) AL11, ST11

2.6) SMGW, RZ70

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

 The gateway service can also be stopped from /n SMGW

2.7) DBACOCKPIT, DB01, DB13, ST04

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

3.2) STRUST, SSO2 and STRUSTSSO2

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

3.3) ST01, SM20N, ST05, SM50

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

Potrebbero piacerti anche