Where are the J2EE services?

[Terry_KPMG]

I have successfully installed the SAP NetWeaver 7.0 2004s trial version on my Linux system.

Thanks to this forum, I got my license file installed and my system is up and somewhat functional. However, I don't think the Java stack was correctly installed or functioning. ....or I'm making a really big assumption.

I used transaction SICF to switch on the /sap/xi hierarchy of applications and the ping application. I can successfully ping resources like http://hostname:8001/sap/xi/adapter_plain http://host:8001/sap/public/ping

Ok, that's a good start, but what happened with the other common URL's like host:50100/nwa and :50100/useradmin :50100/sld

None of those URL's are available. I made the assumption that the NetWeaver trial came with both the ABAP and Java stacks. So when checked the file system I fond my directory structure to include:

/usr/sap/N4S/DVDEBMSG01

/usr/sap/N4S/SCS00

/usr/sap/N4S/SYS

I expected to find a /usr/sap/N4S/JC01 directory.

Looks like I need to install some more software. I guess I need the WAS 6.40 now?

Or did I make a mistake during the installation process?

[brian_walker]

Terry,

Is there not a /usr/sap/N4S/DVDEBMSG01/j2ee directory? The /usr/sap/N4S/JC01 directory would be there ONLY if you did a java-only installation. ABAP+Java uses /usr/sap/N4S/DVDEBMSG01

Are there any files in the work directory (/usr/sap/N4S/DVDEBMSG01/work) like dev_server0?

Brian

[Terry_KPMG]

Thanks for the reply Brian! I didn't realize that JC01 was only available under a java only installation.

Are there any files in the work directory (/usr/sap/N4S/DVDEBMSG01/work) like dev_server0?

Yes, there lots of files in the work directory, but none following that naming convention. I'm trying to log into the Visual Administrator, but its not connecting - yet!

[brian_walker]

Do you have a profile parameter in the instance profile like:

rdisp/j2ee_start=1

If not, it won't start java on a dual stack system.

Brian

[Terry_KPMG]

Yes, that setting is in there - I should have mentioned that it was one of the first things that I checked.

It's clear to me that the Java stack just isn't starting. Now I need to find the right log file to see why!

I can run configtool and poke around. There's no J2EE stack for Visual Administrator to connect to.

Assuming that the J2EE server is crashing on start, which log files should I be checking?

[hannes_kuehnemund]

Hi Terry,

I'd check the following folders and files.

/usr/sap/<SID>/DVEBMGS01/work/dev_jcontrol*
/usr/sap/<SID>/DVEBMGS01/work/dev_dispatcher*
/usr/sap/<SID>/DVEBMGS01/work/std_bootstrap.*
/usr/sap/<SID>/DVEBMGS01/work/std_server.*

also, find the j2ee log folder via:

find /usr/sap/<SID>/DVEBMGS01/j2ee -type d -iname \*log\*

alternatively, you should use

jcmon pf=<path/to/j2ee/instanceprofile>

to get an overview about the j2ee engine itself.

Thanks,

Hannes

[Terry_KPMG]

We're getting somewhere now! I'm starting to suspect that the JAVA_HOME parameter is incorrect throughout the configuration. The path to the "Java for SAP Customers" is /opt/IBMJava2-amd64-142 throughout these log files I see references to an empty directory /usr/lib/java.

But let's break it down one on piece at a time.

Here's the instance profile /usr/sap/N4S/SYS/profile/N4S_DVEBMGS01_n4shost

SAPSYSTEMNAME = N4S
SAPSYSTEM = 01
INSTANCE_NAME = DVEBMGS01
DIR_CT_RUN = $(DIR_EXE_ROOT)/run
DIR_EXECUTABLE = $(DIR_INSTANCE)/exe
jstartup/trimming_properties = off
jstartup/protocol = on
jstartup/vm/home = /usr/lib/java
jstartup/max_caches = 500
jstartup/release = 700
jstartup/instance_properties = $(jstartup/j2ee_properties):$(jstartup/sdm_properties)
j2ee/dbdriver = /sapdb/programs/runtime/jar/sapdbc.jar
exe/saposcol = $(DIR_CT_RUN)/saposcol
rdisp/wp_no_dia = 4
rdisp/wp_no_btc = 1
exe/icmbnd = $(DIR_CT_RUN)/icmbnd
rdisp/j2ee_start_control = 1
rdisp/j2ee_start = 1
rdisp/j2ee_libpath = $(DIR_EXECUTABLE)
exe/j2ee = $(DIR_EXECUTABLE)/jcontrol$(FT_EXE)
rdisp/j2ee_timeout = 600
rdisp/frfc_fallback = on
icm/HTTP/j2ee_0 = PREFIX=/,HOST=localhost,CONN=0-500,PORT=5$$00
icm/server_port_0 = PROT=HTTP,PORT=80$$
#-----------------------------------------------------------------------
# SAP Messaging Service parameters are set in the DEFAULT.PFL
#-----------------------------------------------------------------------
ms/server_port_0 = PROT=HTTP,PORT=81$$
rdisp/wp_no_enq = 1
rdisp/wp_no_vb = 1
rdisp/wp_no_vb2 = 0
rdisp/wp_no_spo = 1
rsdb/dbid = N4S
dbs/ada/schema = SAPN4S
ipc/shm_psize_10 = 136000000
ipc/shm_psize_40 = 112000000


#------------------------------------------------------------
# Jcontrol: Migrated Profile Parameter
#            create at Tue Jun 13 00:41:51 2006
#------------------------------------------------------------
j2ee/instance_id = ID0147049
#------------------------------------------------------------

At first glance, I think this parameter:

jstartup/vm/home = /usr/lib/java

should be

jstartup/vm/home = /opt/IBMJava2-amd64-142

As for the other log files you suggested I check - these two don't exist:

/usr/sap/N4S/DVEBMGS01/work/std_server.*

/usr/sap/N4S/DVEBMGS01/work/dev_dispatcher*

...and the /usr/sap/N4S/DVEBMGS01/work/std_bootstrap.* logs are essentially empty - just some header data.

*EDIT* I was going to post the dev_jcontrol log file here, but it complete screwed up the formatting of the message, so I cut it out and will try to post it in a different message. After reading the dev_jcontrol log, it became apparent that I needed to have a look at the J2EE instance properties file.

In the interests of brevity, I snipped out what I thought were the relevant bits of /usr/sap/N4S/DVEBMGS01/j2ee/cluster/instance.properties

.
.
.
ID14704950.JavaPath=/usr/lib/java
ID14704950.LogName=server0
ID14704950.MainClass=com.sap.engine.boot.Start
ID14704950.MaxHeapSize=1024
ID14704950.Name=server0
ID14704950.Parameters=
ID14704950.RootPath=/usr/sap/N4S/DVEBMGS01/j2ee/cluster/server0
ID14704950.Type=server
.
.
.
bootstrap_ID14704900.JavaPath=/usr/lib/java
bootstrap_ID14704900.MainClass=com.sap.engine.offline.OfflineToolStart
bootstrap_ID14704900.MaxHeapSize=256
bootstrap_ID14704900.Name=dispatcher bootstrap
bootstrap_ID14704900.Parameters=com.sap.engine.bootstrap.Bootstrap ./bootstrap ID014704900
bootstrap_ID14704900.RootPath=/usr/sap/N4S/DVEBMGS01/j2ee/cluster
bootstrap_ID14704900.Type=bootstrap
bootstrap_ID14704950.ClassPath=./bootstrap/launcher.jar
bootstrap_ID14704950.JLaunchParameters=
bootstrap_ID14704950.JavaParameters=-Djco.jarm=1
bootstrap_ID14704950.JavaPath=/usr/lib/java

Those JavaPath statements look suspect to me. What do you think? Did the installation process pickup the wrong java path?

Edited by: Terry Riedel on May 8, 2009 8:45 AM

[Terry_KPMG]

The contents of /usr/sap/N4S/DVEBMGS01/work/dev_jcontrol file gave the message parser fits! ...and really screwed the formating up - so I had to edit it to render correctly.

[Thr 140015118817008] [Node: bootstrap] java home is set by profile parameter
        Java Home: /usr/lib/java

JStartupIReadSection: read node properties [bootstrap]
-> node name          : bootstrap
-> node type          : bootstrap
-> node execute       : yes
-> java path          : /usr/lib/java
-> java parameters    : -Djco.jarm=1
-> java vm version    : J2RE 1.4.2 IBM J9 2.2 Linux amd64-64 j9xa64142ifx-20051125 (JIT enabled)
-> java vm vendor     : IBM J9SE VM (IBM Corporation)
-> java vm type       : <default>
-> java vm cpu        : amd64
-> heap size          : 256M
-> root path          : /usr/sap/N4S/DVEBMGS01/j2ee/cluster
-> class path         : ./bootstrap/launcher.jar
-> OS libs path       : /usr/sap/N4S/DVEBMGS01/j2ee/os_libs
-> main class         : com.sap.engine.offline.OfflineToolStart
-> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path     : /usr/sap/N4S/SYS/exe/run/jstartup.jar:/usr/sap/N4S/SYS/exe/run/jvmx.jar
-> parameters         : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID0147049
-> debuggable         : yes
-> debug mode         : no
-> debug port         : 60000
-> shutdown timeout   : 120000

JControlStartJLaunch: program = /usr/sap/N4S/DVEBMGS01/exe/jlaunch

-> arg[00] = /usr/sap/N4S/DVEBMGS01/exe/jlaunch

-> arg[01] = pf=/usr/sap/N4S/SYS/profile/N4S_DVEBMGS01_n4shost

-> arg[02] = -DSAPINFO=N4S_01_bootstrap

-> arg[03] = -nodeId=-1

-> arg[04] = -file=/usr/sap/N4S/DVEBMGS01/j2ee/cluster/instance.properties

-> arg[05] = -syncSem=19071080

-> arg[06] = -nodeName=bootstrap

-> arg[07] = -jvmOutFile=/usr/sap/N4S/DVEBMGS01/work/jvm_bootstrap.out

-> arg[08] = -stdOutFile=/usr/sap/N4S/DVEBMGS01/work/std_bootstrap.out

-> arg[09] = -locOutFile=/usr/sap/N4S/DVEBMGS01/work/dev_bootstrap

-> arg[10] = -mode=BOOTSTRAP

-> arg[11] = pf=/usr/sap/N4S/SYS/profile/N4S_DVEBMGS01_n4shost

-> arg[12] = -DSAPSTART=1

-> arg[13] = -DCONNECT_PORT=45703

-> arg[14] = -DSAPSYSTEM=01

-> arg[15] = -DSAPSYSTEMNAME=N4S

-> arg[16] = -DSAPMYNAME=helmsdeep_N4S_01

-> arg[17] = -DSAPPROFILE=/usr/sap/N4S/SYS/profile/N4S_DVEBMGS01_n4shost

-> arg[18] = -DFRFC_FALLBACK=ON

-> arg[19] = -DFRFC_FALLBACK_HOST=localhost

-> lib path = LD_LIBRARY_PATH=/usr/lib/java/jre/bin:/usr/lib/java/bin/../jre/bin:/usr/lib/java/jre/bin/j9vm:/usr/lib/java/jre/bin:/usr/sap/N4S/DVEBMGS01/exe:/usr/sap/N4S/DVEBMGS01/exe:/usr/sap/N4S/DVEBMGS01/exe:/tmp/sapinst_exe.11133.1149865079:/usr/sap/N4S/SYS/exe/run:/sapdb/programs/lib:/usr/lib:/usr/sap/N4S/DVEBMGS01/j2ee/os_libs:/usr/sap/N4S/DVEBMGS01/exe:/usr/sap/N4S/DVEBMGS01/exe:/usr/sap/N4S/DVEBMGS01/exe:/usr/sap/N4S/SYS/exe/run:/sapdb/programs/lib:/usr/lib64:/usr/lib

-> exe path = PATH=/usr/lib/java/bin:/usr/sap/N4S/DVEBMGS01/j2ee/os_libs:/sapdb/programs/bin:/opt/IBMJava2-amd64-142/bin:.:/home/n4sadm:/usr/sap/N4S/SYS/exe/run:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin

[Thr 140015118817008] JStartupICreateProcess: fork process (pid 32731)

[Thr 140015118817008] Thu May 7 17:25:11 2009

[Thr 140015118817008] *** ERROR => invalid return code of process [bootstrap] (exitcode = 254) [jstartxx_mt. 1642]

[Thr 140015118817008] JControlExecuteBootstrap: error executing bootstrap node [bootstrap] (rc = 254)

[Thr 140015118817008] JControlCloseProgram: started (exitcode = 254)

[Thr 140015118817008] JControlCloseProgram: good bye... (exitcode = 254)

[brian_walker]

Sounds like the JAVA_HOME directory was not set correctly or at all when you installed?

Brian

[Terry_KPMG]

That's a possibility, so I blew away the installation and started over again.

Here's proof that JAVA was set correctly.

# echo $JAVA_HOME
/opt/IBMJava2-amd64-142

# java -fullversion
java full version "J2RE 1.4.2 IBM build j9xa64142-20090306 (SR13)"

...and that I was using the correct Java for SAP Customers from IBM.

[Terry_KPMG]

I finally "gave up" on getting the system to use the right version of J2EE. No matter what, it expects JAVA_HOME to be /usr/lib/java.

So I gave in and just made a symbolic link for it.

ln -s /opt/IBMJava2-amd64-142/. /usr/lib/java

I can see this causing some problems in the future with other J2EE products on the computer, but for the time being it gets me up and running.