Need help getting local J2EE engine to run

[Former Member]

Hello,

I have installed Netweaver Developer Workplace with MaxDB and a local J2EE engine.

I cannot figure out what all I need to do in order to have all the proper pieces of J2EE engine running locally so I can deply and run some simple servlets/JSPs locally.

I have gone into Administrative Tools|Services and made sure that SAPJ2E_00 and SAPJ2E_01 are both set to Automatic.

Even after doing that and rebooting I still don't see the J2E node as green in the management console. So I rightclick on it and choose start.

When I do that, a bunch of dos(console) windows open and run some commands and after awhile one of the nodes under J2E on management console shows up as green but the other one never does.

Is there some documentation somewhere that shows how to do this locally? I don't want to do it on a server yet.

Thanks in advance for any help.

David

[Benny · Accepted solution]

As far as I remember a development installation does only have a single node and is not possible to update to additional nodes. Did you install a full server locally?

Additionally, what are the RAM values of your machinery?

Regards,

Benny

[Former Member · Accepted solution]

Benny,

I may be using the wrong terminology so let me try again.

When I open the Management console I see the following in the "Tree" tab:

- SAP Systems

- J2E

MyComputerName

- MyComputerName 1

+ Process List

+ Syslog

- MyComputerName 0

+ Process List

+ Process Table

If I right-click on the J2E entry and choose Start from the context menu it opens a bunch of DOS command windows and after awhile 2 separate processes show up under what I was calling the "first node". That's the one referred to as "MyComputerName 1" in the above diagram. The processes show up yellow for a long time and eventually turn green.

The 2nd node (referred to as "MyComputerName 0" in above diagram) starts a process but eventually that process turns back from yellow to gray.

Oh, and NDS is running on my Win 2000 pc with 1.5GB of RAM.

Thanks

David

[Benny · Accepted solution]

David,

first you should check whether your DB is running. That should be directly under the J2E in a blue icon. If you click there it usually shows a DB icon with a colored bullet next to it. That should be green otherwise you got your problem.

Earlier versions did not start the DB automatically, may be this is what you have?

The processes you can see are the SCS instance, (message and enq servers) that is DB independant and therefore able to run without DB.

Hope that helps.

Regards,

Benny

[Former Member · Accepted solution]

Benny,

Thanks much for getting back to me. That's exactly what was happening.

So, to summarize for others looking at this later:

1-I had to click on the blue icon in the Management Console that represents the DB.

2-Then in the right pane, I clicked on the online button and waited until the database showed as online.

3-Then I right-clicked on the "J2E" node in the Management Console I chose "All Taks|Start"

Now the only question I have is how I can get the DB to come up online automatically without having to do steps 1&2 above.

Thanks!

David

Then

[Benny · Accepted solution]

Newer version do this automatically.

Regards,

Benny

[former_member185954]

Hi,

Check the J2EE Administration Manual at the following link.

It should give you some idea on where to check for errors etc.

http://help.sap.com/saphelp_erp2004/helpdata/en/a2/bb0a412a06f023e10000000a155106/frameset.htm

Hope that helps.

Regards,

Siddhesh

[Former Member]

Siddesh,

Thanks for your reply. That was a helpful link in that it got me pointed in the right direction. I found a document that told me to look in the dev_jcontrol file.

There I found the following...

[Thr 2904] Tue Apr 12 09:42:30 2005
[Thr 2904] *** ERROR => invalid return code of process [bootstrap] (exitcode=66) [jstartxx.c   1433]
[Thr 2904] JControlExecuteBootstrap: error executing bootstrap node [bootstrap] (rc=66)
[Thr 2904] JControlCloseProgram: started (exitcode = 66)
[Thr 2904] JControlCloseProgram: good bye... (exitcode=66)

So I did a search in this forum for "exitcode = 66" and found a couple of posts. This one seems to be the most like what I'm experiencing

Halfway thru that post it mentions checking the jvm_bootstrap.out file for errors. I did and it had the following in it:

Exception occured:
com.sap.engine.bootstrap.SynchronizationException: Database initialization failed! Check database properties!
	at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:422)
	at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:144)
	at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:813)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:324)
	at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
----------==[ Caused by: ]==----------
com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.
	at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:344)
	at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:123)
	at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.<init>(PersistenceHandler.java:38)
	at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init>(ConfigurationCache.java:147)
	at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:236)
	at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationManagerBootstrapImpl.java:49)
	at com.sap.engine.bootstrap.Synchronizer.<init>(Synchronizer.java:66)
	at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:419)
	at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:144)
	at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:813)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:324)
	at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
Caused by: com.sap.dbtech.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC: Cannot connect to jdbc:sapdb://TAG132371/J2E [Restart required].
	at com.sap.dbtech.jdbc.DriverSapDB.connect(DriverSapDB.java:183)
	at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:219)
	at com.sap.sql.connect.OpenSQLDataSourceImpl.createPooledConnection(OpenSQLDataSourceImpl.java:570)
	at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:263)
	at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:294)
	... 14 more


[Bootstrap module]> Problem occured while performing synchronization.

Not quite sure what to do. Where do I check the database properties and how do I know which are wrong?

Also, in a subsequent post of that same thread it mentions running the following command in a command window:

dbmcli db_enum

I searched the sap install directory (c:usr) and its subdirectories for a file starting with dbmcli and couldn't find one. Is that installed automatically when you install NDS Workplace?

Any help would be greatly appreciated.

Thanks

David.