XI 3.0 components in SAP Web AS 6.40:
The XI takes advantage of both the Java and ABAP stacks of the SAP Web Application Server.
Components that reside on the J2EE engine include the Integration Builder (Integration Repository,
Integration Directory), the Runtime Workbench, the Mapping Runtime, and the Adapter Engine.
The Integration Engine is implemented in ABAP Objects. This provides a robust, flexible, scalable,
manageable, and powerful engine for message exchange.
This course is not intended for administrators; in this unit we will take a very high-level view of
administrative tasks and responsibilities in the XI. We will focus on tracing and logging settings
particularly, as these are important to developers as well as administrators.
Web AS 6.40 - key architecture points:
J2EE stack
SQLJ layer for database connectivity
All objects stored in database
SLD is delivered with the J2EE Engine
UME for user management
Middleware
JRFC replaces JCo for J2EE to ABAP connectivity
ABAP stack
Integration Engine is part of BASIS (and corresponding sup.
Many XI components are integral components of the SAP Web Application Server version 6.40.
The SAP Web AS has both Java and ABAP components, plus integrated middleware to facilitate
communication between the two.
Java components that are particularly relevant to the XI include the SQLJ layer; SQLJ is a standard for
using Java and SQL together. It has been developed by a consortium of companies comprising IBM,
Informix, Microsoft, Sun, Sybase and Oracle.
Another Java component that is particularly relevant to XI is the SLD, which is now an integral part of the
Web AS.
On the ABAP side, the Integration Engine is an integral part of the Web AS; it is configured as a “Central
Integration Engine” in an XI system, and an “Application System” in a mySAP solution based on the Web
AS.
Integration Engine Administration:
Administration:
•Tuning capabilities for queues:
• Special queue for large
messages
• Balancing between parallel
queues
•Schedule Jobs
Configuration:
•Time-controlled message
processing
•“Switch procedure“ for
message deletion
•Pipeline Definition/Settings.
Many administration tasks in the XI are performed from transaction SXMB_ADM; this transaction
contains launchers to access administrative functionality.
There are two branches in the transaction: Administration and Configuration.
Administrative tasks include managing and tuning the queues for message processing; scheduling
archiving and delete jobs; and making error analysis settings (increasing the debug/trace level for certain
interfaces).
Configuration includes settings for time-controlled message processing (message sending can be triggered
by a background job), configuring the integration engine and the pipeline, controlling the method for
deleting messages (messages build up in the database and must be deleted regularly; XI 3.0 introduces a
new, faster, “switch” method for deleting messages, and the administrator can choose which method to
use), and setting the retention periods and interfaces for message archiving.
J2EE Engine – Administration overview:
The SAP J2EE engine must be configured, managed, and tuned.
There are three tools for configuring the J2EE environment of the SAP Web AS; the offline configuration
editor, the configuration tool, and the J2EE Administrator; of the three, the Administrator is used most
often.
SAP J2EE engines hosts various services that are used by the XI (for instance, a common logging service).
The J2EE Engine Administrator interface provides a common framework for configuring the services that
are used by the XI.
Tracing and Logging
J2EE-based components of XI use standard logging of J2EE Engine
Setup via Log Configurator Service in Visual Administrator tool.
Using the Log Configurator Service runtime available in the Visual Administrator, you can manage the logging and tracing
configurations of the J2EE Engine components of the XI. To ease the configuration process, two configuration modes are
provided – simple and advanced. Using both modes you can:
add, edit and remove log formatters, log destinations, and log controllers.
change states of controllers
archive logs
The Log Viewer provides a runtime control for displaying log messages. These messages assist you to monitor for problems and
search through messages to diagnose problems. It also helps you to tune attributes of applications to optimize processing time, use
of resources, etc.
>>The Log Viewer does the following:
Displays application and system logs. The messages in log files provide hints to the cause of problematic application behavior.
Displays different logs side by side
Gives insight into system problems
Helps with debugging
Improves performance by providing insights into the inner workings of applications
Displays information in a useful form, because Log Viewer understands the information in a log
Brings logs together from the J2EE server and related systems in one place (Integrated Log Viewer)
Searches logs. You can run a query across many logs with a specific severity level selected, while searching for information in
specific logs.
Merges logs that have compatible sequence information across servers, based on time stamps in each record
Allows control of the amount of log data created with log severity thresholds
Creates CCMS templates so that the logs can be monitored in an SAP system. Alerts are then generated in the CCMS.
Can add logs from client and server machines for viewing
The SAT logs show execution times for user transactions. The SQL trace provides details on the database interactions through
the OpenSQL interface.
Standalone Log Viewer UI:
Connect to any number of WebAS servers (ABAP/J2EE).
The standalone version of the Log Viewer server provides the ability to monitor logs in the system when the J2EE engine is not running properly, does not start up at all, or is not available on the system to
monitored.
The standalone installation file is located under the J2EE server admin directory and includes both a Log Viewer Server and Client. The client can connect the user to the Log Viewer service via the P4 port on the
J2EE engine, or via the RMI port to the standalone Log Viewer server. Once installed, the client is run using a batch file.
Integrated Log Viewer UI:
Accessible via J2EE Visual Administrator tool.
The Integrated Log Viewer runs in the SAP Web AS Java. Each time a new log is created the log server is
informed. The Log Viewer client accesses the logs available on the SAP Web AS Java. No separate
configuration is required.
Trace and Log Files for the XI J2EE components:
Under
Trace and log files are essential for analyzing problems. They are offered for all components of SAP
Exchange Infrastructure.
Tracing is not activated by default. In order to activate tracing, perform the following steps:
1. Go to the Log Configurator service.
2. Switch To advanced mode.
3. Choose tab page Location.
4. Select a location.
5. Change the Severity from None to the required value, for example, Debug.
Logging is activated by default. In order to change the preset log level, perform the following steps:
1. Go to the Log Configurator service.
2. Choose tab page Categories.
3. Choose Applications → Exchange Infrastructure.
4. Change the Severity to the required value.
You can view traces and log files by the Log Viewer service in the Visual Administrator.
Trace and Log Files for the XI J2EE components
>>>Under
repository.log
directory.log
mapruntime.log
rwb.log
xi.log
repository.trc
directory.trc
mapruntime.trc
rwb.trc
xi.trc
>>>Default trace file for entire J2EE Engine:
Trace and log files are essential for analyzing problems. They are offered for all components of SAP
Exchange Infrastructure.
Tracing is not activated by default. In order to activate tracing, perform the following steps:
1. Go to the Log Configurator service.
2. Switch To advanced mode.
3. Choose tab page Location.
4. Select a location.
5. Change the Severity from None to the required value, for example, Debug.
Logging is activated by default. In order to change the preset log level, perform the following steps:
1. Go to the Log Configurator service.
2. Choose tab page Categories.
3. Choose Applications → Exchange Infrastructure.
4. Change the Severity to the required value.
You can view traces and log files by the Log Viewer service in the Visual Administrator.
Trace and Log Files in the ABAP Part:
The tracing and logging behavior of the SAP XI is controlled inside transaction SXMB_ADM. Form the
main screen, choose Integration Engine Configuration. From the application toolbar, choose Specific
Configuration.
Parameter LOGGING: The parameter LOGGING enables you to locally activate the logging of messages
for all pipelines of an Integration Engine.
Usage: You set this parameter when you want to analyze message processing as it enables you to
document either individual steps, or all steps in a pipeline.
Possible Values: 0 (deactivated) or 1 (activated)
Parameter LOGGING_PROPAGATION: The parameter LOGGING_PROPAGATION enables you to set
locally in the Integration Engine whether the logging of a pipeline is passed on to the message.
Usage: The parameter is used to pass on the logging settings to a message.
Possible Values: 0 (deactivated) or 1 (activated)
Parameter TRACE_LEVEL: The parameter TRACE_LEVEL enables you to locally set the trace level for
all pipelines in an Integration Engine. However, the diagnostic header of a message can specify the trace
level at which it is to be processed. Runtime then uses the maximum local trace level and message trace
level.
Usage: The parameter is used to pass on the trace level settings to a message.
Possible Values:
- 0 No Trace
- 1 Low Trace Level
- 2 Medium Trace Level
- 3 High Trace Level
Parameter TRACE_LEVEL_PROPAGATION: The parameter TRACE_LEVEL_PROPAGATION
enables you to set locally in the Integration Engine whether the trace level of a pipeline is passed on to the
message.
Usage: The parameter is used to pass on the trace level settings to a message.
Possible Values: 0 (deactivated) or 1 (activated)
