Professional Documents
Culture Documents
The use of Java EE in SAP technology has the following advantages for SAP NetWeaver
Application Server:
The open integration architecture SAP NetWeaver integrates perfectly into the openness
of Java EE.
Java EE is further proof of the strategy of platform-independence pursued by SAP.
The Java EE Connector architecture allows standardized integration of
external applications.
Web Services technologies are supported directly by Java.
The quickly-growing Java community provides simple access to experienced developers.
GO to /usr/sap/<SID>/DVEBMGS00/j2ee/cluster/bootstrap/scripts
as sidadm 99> ./batchdeployer.csh -sdu /usr/sap/trans/EPS/in/ENGINEAPI10_0-
20002603.SCA
ENGINEAPI and SERVERCORE must be in the same level (queue) to deploy
Note : Please be careful if you want to run this command.
If you open OSS Notes 1017526, you can only find general cause which somehow a little bit
confusing, which state : For SAP J2EE Engine SP15 (NW04), add the Java option “-
DP4ClassLoad=P4Connection” in the “go” script and make sure the J2EE Application
“com.sap.engine.class.download” is started .
To solve this problem you need to copy sldserv.jar file
from/usr/sap/<SID>/<InstID>/j2ee/cluster/server<x>/bin/services/sld/to usr/sap/<SID>/
<InstID>/j2ee/admin/lib/
You may try to look for the other services under /bin/services folder and move it to
admin/lib. good luck.
-Go to Configuration –> cluster_data –> server -> cfg -> services
-Click on Propertysheet com.sap.security.core.ume.service
-Change the password in ume.r3.connection.master.passwd
Make sure that this password configuration is defined also in ABAP system (transaction
SU01).
In general there are two roles which should be assigned in SAPJSF user in ABAP system
depends on the configuration. Those are :
– SAP_BC_JSF_COMMUNICATION_RO
– SAP_BC_JSF_COMMUNICATION
And make sure that you generate profile for those roles and assigned correctly to user
SAPJSF.
By default , SAPJSF is set to service user type.
A typical installation has a central instance (CI), a central service instance (SCS), a Java
instance, and a database. The CI is identified by its dispatcher, a server, and Software
Deployment Manager (SDM). Java instance can also has dispatcher and one or more server
processes but not the SDM. Note that Central Instance, Central Service Instance and Java
Instance can be installed on different machine, and these supports High availability and
scalability. Central Service Instance contains message service and enqueue service installed
together in one machine.
May be some of you getting confused about the name which used here. So here’s the
description about Web AS Java :
Java Instance : Java instance contains one dispatcher and one or more server
processses. Sever processes can be defined depends on the memory available since these
processes will consume a memory once it’s started. These java intances can be installed on
one or distributed across multiple hosts which is known as the central or distributed
installation.
Message Service : message server is a program in OS level which will be used for
communicating between Java cluster such as dispatcher and server processes. It will
maintain all dispatcher and server process nodes that are running on J2EE engine, provide
information for Web dispatcher for load balancing, notify the other nodes if some nodes are
up or down.
Enqueue Server : enqueue server is responsible for maintaining the locks for all objects
which is used by Portal application, component and services. One different with enqueue
service in ABAP system is used by Portal application, component and services. One different
with enqueue service in ABAP system is that in Java system also synchronize data in the
Java cluster.
The thing is not all people can read what is inside the log files since this is generated
roughly from Java process, but those texts are very helpful to predict the portal application.
The logs also display some Java class which is used by application. for example :
#1.5#001185E9BA0D0090000031F90000524C00046B19DB1815A0#1243658700982#com.
sapportals.wcm.repository.manager.cm.persistence.BasicPersistenceDB#sap.com/irj#com.s
apportals.wcm.repository.manager.cm.persistence.BasicPersistenceDB#J2EE_GUEST#0#SA
PJ2EE Engine JTA Transaction :
[0384ffffffd20071ffffffb2]#n/a##0ff0c3b04a1111deb8c3001185e9ba0d#Thread[ThreadPool
.Worker1,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###Excep
tion occured during garbage
collection: com.sapportals.wcm.repository.manager.cm.persistence.PersistenceException:
SQLException: Cannot change transaction isolation during distributed transaction and when
the connection is shared. DataSource name: “SAPSR3DB”, current isolation level is
“TRANSACTION_READ_UNCOMMITTED”, new isolation level is
“TRANSACTION_READ_COMMITTED”.#
Yes, of course you need to practice how to solve the issue. There will be a hundreds or even
a thousands of variation of the error. Well , prepare your time to learn then
Answer : If you forgot your SDM password, you can change it in two options,