SAP J2EE version

Hi all
I am in the process of installing EP 6.0 from Netweaver04 DVDs. As prerequisite I installed SAP Web Application Server Java 6.40 on Windows. But when launched J2ee server it shows it as SAP J2EE Engine 6.30 . As per my guess I should see SAP J2EE 6.40. I thought Netweaver 04 comes with SAP J2EE 6.40. Correct me if I am wrong.
2. How to check SP level for J2EE. As per the administrator tool parameter SAP_J2EE_Engine_Version shows 6.30 Patch Level 66061.37. What does it mean? How to interpret this? I need to upgrade from Sp3 to Sp4 before installing portal.
Thanks

Hi RG,
About the Java part of the SAP NetWeaver there is no fundamental difference between 6.30 and 6.40 (in contrast to the APAP part).
So, SAP J2EE Engine up to SP3 is version 6.30 and from SP4 becomes 6.40.
There is a note where you can find what SP is your engine knowing the patch level the note number is 701385.
You can read the information about the version from this file:
"...j2ee/cluster/server0/version.txt" which is located into the J2EE Engine installation directory.
If you cannot see the note 701385, here is a snipped:
The SP number on the market place is just a counter assigned at publication time, i.e. later. That's why the patch number is not written into version.txt.
SP____BuildNumber___TimeStamp________ReleaseDate
00.........48385...........16.04.03 20:43/GMT.....06.10.2003
02.........56692.32......24.07.03 13:16/GMT.....08.10.2003
02-PL1..67206.39......12.01.04 02:21/GMT.....23.01.2004
03.........66061.37......11.01.04 21:06 GMT.....11.01.2004
04.........71379.311.....25.02.04 23:16 GMT.....26.02.2004
05.........75145.313.....19.04.04 19:49 GMT.....19.04.2004
06.........77737.313.....03.06.04 19:38 GMT.....09.06.2004
06-PL1..80393.311.....17.06.04 19:34 GMT.....18.06.2004
07.........83087.313.....29.07.04 19:46 GMT.....05.08.2004
08.........84589.313.....06.09.04 19:48 GMT.....09.09.2004
09.........87037.313.....19.10.04 19:52 GMT.....22.10.2004
(The notation "xx-PLx" in the column "SP" stands for SPxx Patch Level x)
I hope this helps
Best regards,
Lyubomir

Similar Messages

Where can I download a light SAP J2EE version?

Hi,
Is there a light J2EE version?
Where can I download it?
Thanks,
Eylon
Message was edited by: Eylon Steiner
http://www.eshmore.com
Message was edited by: Eylon Steiner

Hi Eylon,
please check the following URL for downloads within SDN
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/downloaditem?rid=/library/uuid/cfc19866-0401-0010-35b2-dc8158247fb6">sap NetWeaver Sneak Preview and Trial</a>
Kind Regards
Thomas

Starting and stoping SAP J2EE engine without using SAPMMC

Hi All,
How can we start SAP J2EE engine without using SAPMMC.
My SAP J2EE version is 6.40.
Kindly, help.
Regards,
Devender V

hi Devender,
if your SID = J01 system no# 00, host = hostabc
open a command prompt,..cd to this exe folder... (/usr/sap/J01/SYS/exe) just cross check if startsap existing or not.
then run
startsap.exe name=J01 nr=00 SAPDIAHOST=hostabc
if the PATH env variable already has a value C:\usr\sap\J01\SYS\exe then you may directly run the command from any folder.. no need to specifically go to the exe folder.
(if you need help how to set env variable in windows, http://www.cs.usask.ca/~wew036/latex/env.html)
Regards,
Debasis.
Edited by: Debasis Sahoo on Apr 29, 2009 8:56 PM

Soap Version supported by SAP J2EE Engine 7.0

Hi,
Cna somebody tell me that which version of SOAP is supported by SAP J2EE Engine 7.0?
Thanks in advance,
manish

Hi Manish,
Have you checked the other link, that I have supplied, check it up, the page says that:
"If you have any problems with the SOAP Processor within the SAP Web AS, our customer support can help you. Please create a problem message on the SAP Service Marketplace under the component BC-MID-SRT (SOAP Run Time). "
So you might want to parallelly post your query over there too, cause i don't see any other note describing the version.
Regards,
Siddhesh

Trial version of SAP J2EE engine and Development environment for Windows

Hello,
I am looking for a trial version of the SAP J2EE Development Environment and the corresponding SAP J2EE Engine for windows environment. I looked at the link https://www.sdn.sap.com/irj/sdn/nw-downloads. But the downloads are for the Linux environment. Are there any downloads for the Windows Environment.
Thanks for your help in advance.
Sumit Agarwal.

Hi Sumit,
Currently trial versions of SAP NetWeaver 2004 and 2004s (7.0) are only available for Linux.
Java EE development environment (the latest Java EE version - 5) trial versions for Windows are available in the [SAP NetWeaver CE download section|https://www.sdn.sap.com/irj/sdn/nw-ce-downloads].
HTH!
-- Vladimir

RFC Connection error in SM59 for SAP J2EE

Hi All,
i am getting the following error description while testing the connection for
SAP J2EE ...
Connection Test SAPJ2EE
Connection Type TCP/IP Connection
Logon Connection Error
Error Details Error when opening an RFC connection
Error Details ERROR: program sapfallback not registered
Error Details LOCATION: SAP-Gateway on host filip / sapgw00
Error Details DETAIL: TP sapfallback not registered
Error Details COMPONENT: SAP-Gateway
Error Details COUNTER: 1483
Error Details MODULE: gwr3cpic.c
Error Details LINE: 1694
Error Details RETURN CODE: 679
Error Details SUBRC: 0
Error Details RELEASE: 700
Error Details TIME: Tue Mar 31 02:44:35 2009
Error Details VERSION: 2
Help me resolve this
Regards,
Mahesh.

Hi,
Please follow this steps:
Creating RFC Destinations in the ABAP and Java Environment
You need to create the following RFC destinations in transaction SM59 (ABAP) and the Visual Administrator (Java):
u2022 AI_RUNTIME_JCOSERVER
u2022 AI_DIRECTORY_JCOSERVER
u2022 LCRSAPRFC
u2022 SAPSLDAPI
Depending on your client settings, it may be necessary to be logged on your SAP Exchange Infrastructure host as SAP system user with the authorization to maintain customizing tables and to release transport orders. Note, that user "SAP*" or "DDIC" does not have these authorizations.
Maintaining the RFC Connections (Transaction SM59)
1. Log on to your SAP Exchange Infrastructure central instance host.
2. Call transaction SM59.
3. Choose Create.
4. Enter at least the following:
RFC destination: AI_RUNTIME_JCOSERVER
Connection type: T
Description: <your description>
5. Choose ENTER
6. Choose the tab Technical settings and do the following:
a. Select Registered Server Program
b. In the Program ID field, enter: AI_RUNTIME_<SID> where <SID> is the SAP system ID of your Integration Server host. Use uppercase letters only.
c. Enter Gateway host and Gateway service of your Integration Server host. To find out the required parameters:
a. On the Integration Server host, call transaction SMGW
b. Choose Goto u2192 Parameters u2192 Display (see entries for gateway hostname and gateway service)
7. Choose tab Special Options and select the flag Unicode in the box Character Width in Target System.
8. Save your settings.
9. Repeat the steps 3 u2013 8 for the remaining destinations:
Destination
Values
AI_DIRECTORY_JCOSERVER
Program ID: AI_DIRECTORY_<SID>, where <SID> is the SAP system ID of your SAP XI host
LCRSAPRFC
Program ID: LCRSAPRFC_<SID>, where <SID> is the SAP system ID of your SAP XI host.
SAPSLDAPI
Program ID: SAPSLDAPI_<SID>, where <SID> is the SAP system ID of your SAP XI host.
10. Leave the transaction SM59 open for later tests.
J2EE Configuration for the Destinations (Visual Administrator)
1. On your SAP Exchange Infrastructure central instance host, start the J2EE Engine administration tool.
2. Choose Cluster u2192 Server u2192 Services u2192 JCo RFC Provider
3. In the section RFC destination, enter exactly the same program ID and gateway options for AI_RUNTIME_JCOSERVER that you used in the step Maintaining the RFC connection above. Additionally, set the number of processes to 10.
4. In the section Repository, do the following:
a. Enter the parameter for the SAP XI host: Application Server, System Number, Client and Language.
b. For User and Password maintain the login parameters for the user SAPJSF.
c. Select the flag Unicode.
6. Choose Set.
7. Repeat the steps 3 u2013 6 for the remaining destinations:
Destination
Values
AI_DIRECTORY_JCOSERVER
u2022 Corresponding values from SM59
u2022 Number of processes: 10
LCRSAPRFC
u2022 Corresponding values from SM59
u2022 Number of processes: 3
SAPSLDAPI
u2022 Corresponding values from SM59
u2022 Number of processes: 3
Testing the RFC Destination
After you have maintained all RFC destinations in both the ABAP and Java environment, you can check all the connections above as follows:
1. Call transaction SM59 again.
2. Open your RFC destination.
3. Choose Test Connection. No error should be displayed.
This will solve your problem.
Thanks
Laxmi Bhushan

SAP J2EE Engine JTA Transaction Xml for table TABLE could not be ana

I'm having a weird case. I created 3 entity bean. In my R/3 will call this JCO.Function to do the insert to database. But out of 3 entity bean, only 1 entity bean got error where it unable to insert to database and have this error in the log.
The case is quite weird where i created the same entity but only 1 entity is not working as expected. Wondering what cause this problem.
Thanks.
org.xml.sax.SAXException: Fatal Error: URI=:main: Line=1: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Name expected: 0x20(:main:, row:1, col:218)#
at com.sap.dictionary.database.dbs.XmlExtractor$XMLErrorHandler.fatalError(XmlExtractor.java:279)#
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144)#
at com.sap.dictionary.database.dbs.XmlExtractor.map(XmlExtractor.java:130)#
at com.sap.dictionary.database.catalog.DbGeneralStructure.<init>(DbGeneralStructure.java:86)#
at com.sap.dictionary.database.catalog.XmlCatalogReader.getTable(XmlCatalogReader.java:90)#
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:124)#
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:87)#
at com.sap.sql.sqlparser.CheckColAndTabVisitor.checkTables(CheckColAndTabVisitor.java:299)#
at com.sap.sql.sqlparser.CheckColAndTabVisitor.performCatalogChecks(CheckColAndTabVisitor.java:176)#
at com.sap.sql.sqlparser.CommonSQLStatement.checkSemantics(CommonSQLStatement.java:169)#
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:35)#
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:101)#
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:87)#
at com.sap.sql.jdbc.common.AbstractCommonStatement.parseStatement(AbstractCommonStatement.java:472)#
at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonConnectionImpl.java:375)#
at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(ConnectionHandle.java:81)#
at net.tnb.model.ReasonCodeEntityBean3_0Persistent.ejb_iInsert(ReasonCodeEntityBean3_0Persistent.java:306)#
at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.ejbFlush(UpdatablePersistent.java:92)#
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flushAll(TransactionContext.java:429)#
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flush(TransactionContext.java:378)#
at com.sap.engine.services.ejb.entity.pm.TransactionContext.beforeCompletion(TransactionContext.java:506)#
at com.sap.engine.services.ejb.entity.SynchronizationList.beforeCompletion(SynchronizationList.java:136)#
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:226)#
at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:546)#
at net.tnb.model.ReasonCodeEntityHome_Stub.create(ReasonCodeEntityHome_Stub.java:57)#
at net.tnb.model.EToGatewayBean.insertIntoTable(EToGatewayBean.java:223)#
at net.tnb.model.EToGatewayBean.processFunction(EToGatewayBean.java:166)#
at net.tnb.model.EToGatewayLocalLocalObjectImpl3_0.processFunction(EToGatewayLocalLocalObjectImpl3_0.java:175)#
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.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277)#
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219)#
at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260)#
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)#
at java.security.AccessController.doPrivileged(Native Method)#
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)#
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)#
##0#0#Error##Java###{0}.commit(), Cannot commit due to unexpected exception in beforeCompletion():
[EXCEPTION]
{1}#2#SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b]#java.lang.IllegalStateException: Xml for table <TABLE> could not be analysed
 at com.sap.dictionary.database.catalog.XmlCatalogReader.getTable(XmlCatalogReader.java:100)
 at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:124)
 at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:87)
 at com.sap.sql.sqlparser.CheckColAndTabVisitor.checkTables(CheckColAndTabVisitor.java:299)
 at com.sap.sql.sqlparser.CheckColAndTabVisitor.performCatalogChecks(CheckColAndTabVisitor.java:176)
 at com.sap.sql.sqlparser.CommonSQLStatement.checkSemantics(CommonSQLStatement.java:169)
 at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:35)
 at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:101)
 at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:87)
 at com.sap.sql.jdbc.common.AbstractCommonStatement.parseStatement(AbstractCommonStatement.java:472)
 at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonConnectionImpl.java:375)
 at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(ConnectionHandle.java:81)
 at net.tnb.model.ReasonCodeEntityBean3_0Persistent.ejb_iInsert(ReasonCodeEntityBean3_0Persistent.java:306)
 at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.ejbFlush(UpdatablePersistent.java:92)
 at com.sap.engine.services.ejb.entity.pm.TransactionContext.flushAll(TransactionContext.java:429)
 at com.sap.engine.services.ejb.entity.pm.TransactionContext.flush(TransactionContext.java:378)
 at com.sap.engine.services.ejb.entity.pm.TransactionContext.beforeCompletion(TransactionContext.java:506)
 at com.sap.engine.services.ejb.entity.SynchronizationList.beforeCompletion(SynchronizationList.java:136)
 at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:226)
 at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:546)
 at net.tnb.model.ReasonCodeEntityHome_Stub.create(ReasonCodeEntityHome_Stub.java:57)
 at net.tnb.model.EToGatewayBean.insertIntoTable(EToGatewayBean.java:223)
 at net.tnb.model.EToGatewayBean.processFunction(EToGatewayBean.java:166)
 at net.tnb.model.EToGatewayLocalLocalObjectImpl3_0.processFunction(EToGatewayLocalLocalObjectImpl3_0.java:175)
 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.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277)
 at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219)
 at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#1.5 #001A6467CDF400590000004E000018D8000459BB785F496C#1224561620123#com.sap.engine.services.ts#sap.com/ESolutionsEGatewayEAR#com.sap.engine.services.ts#J2EE_GUEST#0####95b74d409f2411dd86c4001a6467cdf4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error#1#/System/Server#Java#ts_0004##Exception in beforeCompletition of ( SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b] ).#1#SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b]#
#1.5 #001A6467CDF400590000004F000018D8000459BB785F4BC5#1224561620123#com.sap.engine.services.ts#sap.com/ESolutionsEGatewayEAR#com.sap.engine.services.ts#J2EE_GUEST#0####95b74d409f2411dd86c4001a6467cdf4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error#1#/System/Audit#Java###Exception {0}#1#com.sap.engine.services.ts.exceptions.BaseRollbackException: Exception in beforeCompletition of ( SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b] ).
 at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:236)
 at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:546)
 at net.tnb.model.ReasonCodeEntityHome_Stub.create(ReasonCodeEntityHome_Stub.java:57)
 at net.tnb.model.EToGatewayBean.insertIntoTable(EToGatewayBean.java:223)
 at net.tnb.model.EToGatewayBean.processFunction(EToGatewayBean.java:166)
 at net.tnb.model.EToGatewayLocalLocalObjectImpl3_0.processFunction(EToGatewayLocalLocalObjectImpl3_0.java:175)
 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.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277)
 at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219)
 at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.lang.IllegalStateException: Xml for table ZREASON_CODE could not be analysed
 at com.sap.dictionary.database.catalog.XmlCatalogReader.getTable(XmlCatalogReader.java:100)
 at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:124)
 at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:87)
 at com.sap.sql.sqlparser.CheckColAndTabVisitor.checkTables(CheckColAndTabVisitor.java:299)
 at com.sap.sql.sqlparser.CheckColAndTabVisitor.performCatalogChecks(CheckColAndTabVisitor.java:176)
 at com.sap.sql.sqlparser.CommonSQLStatement.checkSemantics(CommonSQLStatement.java:169)
 at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:35)
 at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:101)
 at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:87)
 at com.sap.sql.jdbc.common.AbstractCommonStatement.parseStatement(AbstractCommonStatement.java:472)
 at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonConnectionImpl.java:375)
 at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(ConnectionHandle.java:81)
 at net.tnb.model.ReasonCodeEntityBean3_0Persistent.ejb_iInsert(ReasonCodeEntityBean3_0Persistent.java:306)
 at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.ejbFlush(UpdatablePersistent.java:92)
 at com.sap.engine.services.ejb.entity.pm.TransactionContext.flushAll(TransactionContext.java:429)
 at com.sap.engine.services.ejb.entity.pm.TransactionContext.flush(TransactionContext.java:378)
 at com.sap.engine.services.ejb.entity.pm.TransactionContext.beforeCompletion(TransactionContext.java:506)
 at com.sap.engine.services.ejb.entity.SynchronizationList.beforeCompletion(SynchronizationList.java:136)
 at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:226)
 ... 16 more
#1.5 #001A6467CDF4005900000050000018D8000459BB785F4E8F#1224561620123#com.sap.engine.services.ejb.entity.Container#sap.com/ESolutionsEGatewayEAR#com.sap.engine.services.ejb.entity.Container#J2EE_GUEST#0####95b74d409f2411dd86c4001a6467cdf4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Java###null
[EXCEPTION]
{0}#1#com.sap.engine.services.ejb.exceptions.BaseRemoteException: Transaction system failure in method net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(net.tnb.model.ReasonCodeBean).
 at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:573)
 at net.tnb.model.ReasonCodeEntityHome_Stub.create(ReasonCodeEntityHome_Stub.java:57)
 at net.tnb.model.EToGatewayBean.insertIntoTable(EToGatewayBean.java:223)
 at net.tnb.model.EToGatewayBean.processFunction(EToGatewayBean.java:166)
 at net.tnb.model.EToGatewayLocalLocalObjectImpl3_0.processFunction(EToGatewayLocalLocalObjectImpl3_0.java:175)
 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.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277)
 at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219)
 at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.ts.exceptions.BaseRollbackException: Exception in beforeCompletition of ( SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b] ).
 at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:236)
 at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:546)
 ... 15 more
Caused by: java.lang.IllegalStateException: Xml for table ZREASON_CODE could not be analysed
 at com.sap.dictionary.database.catalog.XmlCatalogReader.getTable(XmlCatalogReader.java:100)
 at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:124)
 at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:87)
 at com.sap.sql.sqlparser.CheckColAndTabVisitor.checkTables(CheckColAndTabVisitor.java:299)
 at com.sap.sql.sqlparser.CheckColAndTabVisitor.performCatalogChecks(CheckColAndTabVisitor.java:176)
 at com.sap.sql.sqlparser.CommonSQLStatement.checkSemantics(CommonSQLStatement.java:169)
 at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:35)
 at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:101)
 at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:87)
 at com.sap.sql.jdbc.common.AbstractCommonStatement.parseStatement(AbstractCommonStatement.java:472)
 at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonConnectionImpl.java:375)
 at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(ConnectionHandle.java:81)
 at net.tnb.model.ReasonCodeEntityBean3_0Persistent.ejb_iInsert(ReasonCodeEntityBean3_0Persistent.java:306)
 at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.ejbFlush(UpdatablePersistent.java:92)
 at com.sap.engine.services.ejb.entity.pm.TransactionContext.flushAll(TransactionContext.java:429)
 at com.sap.engine.services.ejb.entity.pm.TransactionContext.flush(TransactionContext.java:378)
 at com.sap.engine.services.ejb.entity.pm.TransactionContext.beforeCompletion(TransactionContext.java:506)
 at com.sap.engine.services.ejb.entity.SynchronizationList.beforeCompletion(SynchronizationList.java:136)
 at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:226)
 ... 16 more
#1.5 #001A6467CDF4005900000051000018D8000459BB785F5FA9#1224561620123#System.err#sap.com/ESolutionsEGatewayEAR#System.err#J2EE_GUEST#0####95b74d409f2411dd86c4001a6467cdf4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Plain###RemoteException insertOk=false#
#1.5 #001A6467CDF4005900000052000018D8000459BB785F6094#1224561620123#System.err#sap.com/ESolutionsEGatewayEAR#System.err#J2EE_GUEST#0####95b74d409f2411dd86c4001a6467cdf4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Plain###Tue Oct 21 12:00:20 SGT 2008 java.rmi.RemoteException: com.sap.engine.services.ejb.exceptions.BaseRemoteException: Transaction system failure in method net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(net.tnb.model.ReasonCodeBean).
 at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:573)
 at net.tnb.model.ReasonCodeEntityHome_Stub.create(ReasonCodeEntityHome_Stub.java:57)
 at net.tnb.model.EToGatewayBean.insertIntoTable(EToGatewayBean.java:223)
 at net.tnb.model.EToGatewayBean.processFunction(EToGatewayBean.java:166)
 at net.tnb.model.EToGatewayLocalLocalObjectImpl3_0.processFunction(EToGatewayLocalLocalObjectImpl3_0.java:175)
 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.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277)
 at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219)
 at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.ts.exceptions.BaseRollbackException: Exception in beforeCompletition of ( SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b] ).
 at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:236)
 at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:546)
 ... 15 more
Caused by: java.lang.IllegalStateException: Xml for table <TABLE> could not be analysed
 at com.sap.dictionary.database.catalog.XmlCatalogReader.getTable(XmlCatalogReader.java:100)
 at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:124)
 at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:87)
 at com.sap.sql.sqlparser.CheckColAndTabVisitor.checkTables(CheckColAndTabVisitor.java:299)
 at com.sap.sql.sqlparser.CheckColAndTabVisitor.performCatalogChecks(CheckColAndTabVisitor.java:176)
 at com.sap.sql.sqlparser.CommonSQLStatement.checkSemantics(CommonSQLStatement.java:169)
 at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:35)
 at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:101)
 at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:87)
 at com.sap.sql.jdbc.common.AbstractCommonStatement.parseStatement(AbstractCommonStatement.java:472)
 at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonConnectionImpl.java:375)
 at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(ConnectionHandle.java:81)
 at net.tnb.model.ReasonCodeEntityBean3_0Persistent.ejb_iInsert(ReasonCodeEntityBean3_0Persistent.java:306)
 at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.ejbFlush(UpdatablePersistent.java:92)
 at com.sap.engine.services.ejb.entity.pm.TransactionContext.flushAll(TransactionContext.java:429)
 at com.sap.engine.services.ejb.entity.pm.TransactionContext.flush(TransactionContext.java:378)
 at com.sap.engine.services.ejb.entity.pm.TransactionContext.beforeCompletion(TransactionContext.java:506)
 at com.sap.engine.services.ejb.entity.SynchronizationList.beforeCompletion(SynchronizationList.java:136)
 at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:226)
 ... 16 more
; nested exception is:
 javax.transaction.RollbackException: com.sap.engine.services.ts.exceptions.BaseRollbackException: Exception in beforeCompletition of ( SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b] ).
 at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:236)
 at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:546)
 at net.tnb.model.ReasonCodeEntityHome_Stub.create(ReasonCodeEntityHome_Stub.java:57)
 at net.tnb.model.EToGatewayBean.insertIntoTable(EToGatewayBean.java:223)
 at net.tnb.model.EToGatewayBean.processFunction(EToGatewayBean.java:166)
 at net.tnb.model.EToGatewayLocalLocalObjectImpl3_0.processFunction(EToGatewayLocalLocalObjectImpl3_0.java:175)
 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.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277)
 at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219)
 at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.lang.IllegalStateException: Xml for table ZREASON_CODE could not be analysed
 at com.sap.dictionary.database.catalog.XmlCatalogReader.getTable(XmlCatalogReader.java:100)
 at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:124)
 at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:87)
 at com.sap.sql.sqlparser.CheckColAndTabVisitor.checkTables(CheckColAndTabVisitor.java:299)
 at com.sap.sql.sqlparser.CheckColAndTabVisitor.performCatalogChecks(CheckColAndTabVisitor.java:176)
 at com.sap.sql.sqlparser.CommonSQLStatement.checkSemantics(CommonSQLStatement.java:169)
 at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:35)
 at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:101)
 at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:87)
 at com.sap.sql.jdbc.common.AbstractCommonStatement.parseStatement(AbstractCommonStatement.java:472)
 at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonConnectionImpl.java:375)
 at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(ConnectionHandle.java:81)
 at net.tnb.model.ReasonCodeEntityBean3_0Persistent.ejb_iInsert(ReasonCodeEntityBean3_0Persistent.java:306)
 at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.ejbFlush(UpdatablePersistent.java:92)
 at com.sap.engine.services.ejb.entity.pm.TransactionContext.flushAll(TransactionContext.java:429)
 at com.sap.engine.services.ejb.entity.pm.TransactionContext.flush(TransactionContext.java:378)
 at com.sap.engine.services.ejb.entity.pm.TransactionContext.beforeCompletion(TransactionContext.java:506)
 at com.sap.engine.services.ejb.entity.SynchronizationList.beforeCompletion(SynchronizationList.java:136)
 at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:226)
 ... 16 more

Hi Stefan and Everyone,
I have solved my problem. Just want to let everyone know if u have to install the SP's for WEB AS 6.30/6.40.
You start from the installation from CD 6.30/6.40. Everything will be working at this point. You can login to Visual Admin, Config tool and SDM.
Before you apply any SP's, do the following:
a) Create an emergency user with the Administrator rights: Ref OSS Note:669848
Try to follow this route for SP's:
From CD 6.30/6.40 -> SP04 -> SP07
Apply SP04 first before applying SP07 (Recommended Approach).
Refer the installation guide: SAP Web AS Support Package Guide 630SP2 to 640SP4.
Use JDK1.4.2_05 to install SP04. You must reference the following OSS Notes and apply to your system accordingly, this is the key to an error free installation:
a) OSS Note: 697535
b) OSS Note: 709140
c) OSS Note: 716604
d) OSS Note: 706378
You have to be really careful with SP04 installation, because it changes the version from 6.30 -> 6.40.
Once you are able to install SP04 without any problems, you can directly apply SP07 or the highest 6.40 SP.
Kind Regards,
Buddha.

Time out error on deploying to SAP-J2EE engine.

I got a problem while deploying to SAP-J2EE engine using ant. It takes a lot of time and then throws a time out error.
The problem is with the web.xml file pointing to a DTD in the internet, I have pasted some part of the web.xml below,
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE web-app
PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN"
"http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
<web-app>
 <display-name>MyPay</display-name>
 <description>MyPay</description>
Once I write down the DTD description in the web.xml itself, it works fine.
I have pasted the error trace below,
j2eedeploy:
 [echo] Deploying to Local environment...
 [echo] C:\Java\Projects/MyPay/dist/MyPay.ear
BUILD FAILED
C:\Java\Projects\MyPay\build.xml:445: java.lang.RuntimeException: ERROR: ID90507: Error occured during getting EARDescriptor : Failed to load resource from the context classloader of the current thread! Loading from classloader was caused by: java.net.ConnectException: Connection timed out: connect
Exception is :
java.io.IOException: Failed to load resource from the context classloader of the current thread! Loading from classloader was caused by: java.net.ConnectException: Connection timed out: connect
 at com.sap.engine.lib.xml.parser.URLLoaderBase.resolveEntity(URLLoaderBase.java:148)
 at com.sap.engine.lib.xml.parser.XMLParser.scanDTD(XMLParser.java:1271)
 at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2795)
 at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2830)
 at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229)
 at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
 at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160)
 at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261)
 at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280)
 at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342)
 at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:101)
 at com.sap.engine.lib.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:127)
 at com.inqmy.lib.xml.StandardDOMParser.parse(StandardDOMParser.java:127)
 at com.inqmy.lib.xml.StandardDOMParser.parse(StandardDOMParser.java:120)
 at com.inqmy.services.servlets_jsp.descriptor.jar.WebWar.getWebDescriptor(WebWar.java:98)
 at com.inqmy.deploy.tool.deployer.ExtendedEarReader.loadDescriptorFromFile(ExtendedEarReader.java:175)
 at com.inqmy.deploy.tool.deployer.ExtendedEarReader.getFullEarDescriptor(ExtendedEarReader.java:104)
 at com.inqmy.deploy.manager.DeployManagerImpl.setEar(DeployManagerImpl.java:355)
 at com.inqmy.deploy.manager.DeployManagerImpl.setEar(DeployManagerImpl.java:325)
 at com.pg.sap.deploy620.SAPDeploy620Manager.process(SAPDeploy620Manager.java:84)
 at com.pg.ant.tasks.j2ee620.J2ee620EngineDeployTask.execute(J2ee620EngineDeployTask.java:40)
 at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
 at org.apache.tools.ant.Task.perform(Task.java:364)
 at org.apache.tools.ant.Target.execute(Target.java:341)
 at org.apache.tools.ant.Target.performTasks(Target.java:369)
 at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
 at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
 at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
 at org.eclipse.ant.internal.ui.antsupport.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:32)
 at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
 at org.eclipse.ant.internal.ui.antsupport.InternalAntRunner.run(InternalAntRunner.java:423)
 at org.eclipse.ant.internal.ui.antsupport.InternalAntRunner.main(InternalAntRunner.java:137)

Thanks for your reply Kalyan,
The problem seems to be with my system, because I had run the same ant script in another system and it deployed successfully.
The problem does not seem to be with the dtd, whereas it seems that the SAP-J2EE engine is not able to open the link to the dtd giving a time out error.
Is it possible to switch off the validation process of the SAP-J2EE engine of an xml with the dtd?

Error message when starting SAP J2EE Engine 6.20

When i am starting SAP J2EE Engine 6.20 i am not able to get the homepage at its startup.
I have checked the Cluster_Log and it says
[OS: Windows XP] [VM vendor: Sun Microsystems Inc.] [VM version: 1.3.1_16-b06] [VM type: Java HotSpot(TM) Client VM]
SAP J2EE Engine Version 6.20 PatchLevel 100897.20 is starting...
Loading: LogManager ...
Loading: R3StartupManager ...
Loading: ThreadManager ...
Loading: TimeoutManager ...
Loading: MemoryManager ...
Loading: PoolManager ...
Loading: PolicyManager ...
Loading: ConnectionsManipulator ...
Loading: IpVerificationManager ...
Loading: ClusterManager ...
Loading: ClassLoaderManager ...
Loading: PortsManager ...
Loading: LockManager ...
Loading: ServiceManager ...
Loading core services:
Starting core service p4 ... done. (297 ms)
Starting core service security ... done. (78 ms)
Starting core service log ... done. (656 ms)
Starting core service admin ... done. (204 ms)
Starting core service monitor ... done. (235 ms)
Core services loaded successfully.
Loading additional services:
Starting service httptunneling ... done. (109 ms)
Starting service jms ... done. (0 ms)
Starting service telnet ... done. (94 ms)
Starting service shell ... done. (250 ms)
ID000544: Error starting service http. Can't start the service due to java.io.IOException: Can't open HTTP server socket on port 80
[ServiceManager]: ID000544: Error starting service http. Can't start the service due to java.io.IOException: Can't open HTTP server socket on port 80
Additional services loaded successfully.
[Framework -> criticalShutdown] [Tue Jul 22 13:44:16 IST 2008] Service http startup error!
Here i can notice "Cant open HTTP server socket on port 80".
How can i do this setting so that everything works fine.

Hi
Check that your port 80 is not occupied by other running application (eg. IIS or ITS etc.)
Also check that it may be disabled by antivirus software.
Check the services file that this port is not assigned to other application then
http 80/tcp www www-http

Issue in Communication of SAP R/3 6.4C with SAP J2EE Engine 6.40.

Hello,
We have an application deployed in SAP J2EE engine 6.20. From SAP R3 (SAP R/3 version is 6.4C), We are communicating to the application deployed in SAP J2EE Engine 6.20 using RFC protocol. EJB module (Deployed in SAP J2EE Engine 6.20) which is being invoked from a Function Module using RFC protocol has the same name as the Function Module name. We were able to communicate to SAP J2EE Engine 6.20 this way.
Currently, I have deployed the same application in SAP J2EE Engine 6.40. I have followed the same procedure which i have used while depolying and working with SAP J2EE Engine 6.20. But, it is not working, and i was not able to communicate to SAP J2EE 6.40, the same way i did in SAP J2EE Engine 6.20.
Please let me know whether the procedure for communicating to SAP J2EE Engine 6.40 has changed in comparison with SAP J2EE Engine 6.20.
Also,Any pointers regarding RFC and JCO implementation in SAP J2EE Engine 6.40 willl be helpful.
Thank you.
Regards,
-Shabir Rahim.

Hi,
compare to 4.7
1.New ABAP editor added like if u write code in abap editor ,using if coditions and select statments it automatically shows the link endif, like if .. endif,select ...endselect.
2.New abap debugger compare to the classic debugger.
3.DBACOCKPIT
Missing indexes of various database tablesu2019 and the transaction to reactivate all the missing indexes is u2018DBACOCKPITu2019. Below is the screenshot of the transaction DBACOCKPIT.
Regards,
Madhu

SAP J2EE Engine : does not work !!!

Hi everyone,
I have installed SAP NW2004s Java SP9 Trial (on Windows XP and Sapdb as database). The installation finished without problems.
But when I start my SAP system, the SAP J2EE engine (process jcontrol) is still stopped
[... I have already searched in the forum, but I have not found a solution to my problem ...]
Here is the contents of files dev_jcontrol & dev_sdm :
File dev_jcontrol : *************************************
trc file: "D:\usr\sap\J2E\JC01\work\dev_jcontrol", trc level: 1, release: "700"
node name : jcontrol
pid : 1384
system name : J2E
system nr. : 01
started at : Mon Dec 03 15:23:56 2007
arguments :
 arg[00] : D:\usr\sap\J2E\JC01\exe\jcontrol.EXE
 arg[01] : pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_ahassaine
[Thr 2356] Mon Dec 03 15:23:56 2007
[Thr 2356] *** ERROR => Can't open property file [D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties] [jstartxx.c 725]
[Thr 2356] *** ERROR => Can't open property file [D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties] [jstartxx.c 1952]
[Thr 2356] *** ERROR => JStartupReadArgumentsEx: can't enumerate nodes [D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties;D:\usr\sap\J2E\JC01\SDM\program\config\sdm_jstartup.properties] (rc = -1) [jstartxx.c 524]
File dev_sdm : *************************************
trc file: "D:\usr\sap\J2E\JC01\work\dev_sdm", trc level: 1, release: "700"
node name : sdm
pid : 1360
system name : J2E
system nr. : 01
started at : Fri Nov 30 10:38:29 2007
arguments :
 arg[00] : D:\usr\sap\J2E\JC01\exe\jlaunch.exe
 arg[01] : pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_ahassaine
 arg[02] : -DSAPINFO=J2E_01_sdm
 arg[03] : pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_ahassaine
JStartupReadInstanceProperties: read instance properties [D:\usr\sap\J2E\JC01\SDM\program\config\sdm_jstartup.properties]
-> ms host : ahassaine
-> ms port : 3900
-> OS libs : D:\usr\sap\J2E\JC01\exe
-> Admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
Used property files
-> files [00] : D:\usr\sap\J2E\JC01\SDM\program\config\sdm_jstartup.properties
Instance properties
-> ms host : ahassaine
-> ms port : 3900
-> os libs : D:\usr\sap\J2E\JC01\exe
-> admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
Bootstrap nodes
Worker nodes
-> [00] sdm : D:\usr\sap\J2E\JC01\SDM\program\config\sdm_jstartup.properties
[Thr 3544] Fri Nov 30 10:38:29 2007
[Thr 3544] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 3544] JLaunchRequestQueueInit: create pipe listener thread
[Thr 2240] JLaunchRequestFunc: Thread 2240 started as listener thread for np messages.
[Thr 3352] WaitSyncSemThread: Thread 3352 started as semaphore monitor thread.
[Thr 3544] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
[Thr 3544] CPIC (version=700.2005.12.02)
[Thr 3544] INFO: Invalid property value [Debbugable=yes]
[Thr 3544] [Node: SDM] java home is set by profile parameter
 Java Home: C:\Java\
[Thr 3544] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\J2E\JC01\exe\jvmx.jar
JStartupIReadSection: read node properties [sdm]
-> node name : SDM
-> node type : sdm
-> node execute : yes
-> java path : C:\Java\
-> java parameters :
-> java vm version : 1.4.2_09-b05
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type : server
-> java vm cpu : x86
-> heap size : 512M
-> root path : D:\usr\sap\J2E\JC01\SDM\program
-> class path : D:\usr\sap\J2E\JC01\SDM\program\bin\SDM.jar
-> OS libs path : D:\usr\sap\J2E\JC01\exe
-> main class : SDMInternal
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : D:\usr\sap\J2E\JC01\exe\jstartup.jar;D:\usr\sap\J2E\JC01\exe\jvmx.jar
-> shutdown class : com.sap.sdm.jstartup.shutdown.InternalShutDown
-> parameters : server sdmhome=D:\usr\sap\J2E\JC01\SDM\program
-> debuggable : yes
-> debug mode : no
-> debug port : 50000
-> shutdown timeout : 120000
[Thr 3544] JLaunchISetDebugMode: set debug mode [no]
[Thr 2480] JLaunchIStartFunc: Thread 2480 started as Java VM thread.
JHVM_LoadJavaVM: VM Arguments of node [SDM]
-> stack : 262144 Bytes
-> arg[ 0]: exit
-> arg[ 1]: abort
-> arg[ 2]: vfprintf
-> arg[ 3]: -Dsys.global.dir=D:\usr\sap\J2E\SYS\global
-> arg[ 4]: -Dapplication.home=D:\usr\sap\J2E\JC01\exe
-> arg[ 5]: -Djava.class.path=D:\usr\sap\J2E\JC01\exe\jstartup.jar;D:\usr\sap\J2E\JC01\exe\jvmx.jar;D:\usr\sap\J2E\JC01\SDM\program\bin\SDM.jar
-> arg[ 6]: -Djava.library.path=C:\Java
jre\bin\server;C:\Java
jre\bin;C:\Java
bin;D:\usr\sap\J2E\JC01\exe;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\ATI Technologies\ATI Control Panel;D:\usr\sap\J2E\SYS\exe\uc\NTI386
-> arg[ 7]: -Dmemory.manager=512M
-> arg[ 8]: -Xmx512M
-> arg[ 9]: -DLoadBalanceRestricted=no
-> arg[ 10]: -Djstartup.mode=JCONTROL
-> arg[ 11]: -Djstartup.ownProcessId=1360
-> arg[ 12]: -Djstartup.ownHardwareId=G1610100576
-> arg[ 13]: -Djstartup.whoami=sdm
-> arg[ 14]: -Djstartup.debuggable=yes
-> arg[ 15]: -DSAPINFO=J2E_01_sdm
-> arg[ 16]: -DSAPSTARTUP=1
-> arg[ 17]: -DSAPSYSTEM=01
-> arg[ 18]: -DSAPSYSTEMNAME=J2E
-> arg[ 19]: -DSAPMYNAME=ahassaine_J2E_01
-> arg[ 20]: -DSAPDBHOST=ahassaine
-> arg[ 21]: -Dj2ee.dbhost=ahassaine
CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
CompilerOracle: exclude iaik/security/md/SHA a
CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
[Thr 2480] JHVM_LoadJavaVM: Java VM created OK.
JHVM_BuildArgumentList: main method arguments of node [SDM]
-> arg[ 0]: server
-> arg[ 1]: sdmhome=D:\usr\sap\J2E\JC01\SDM\program
[Thr 2240] Fri Nov 30 10:38:33 2007
[Thr 2240] JLaunchRequestFunc: receive command:17, argument:0 from pid:2600
[Thr 2240] JLaunchIShutdownInvoke: set shutdown interval (stop:1196419113/end:1196419233/TO:120)
[Thr 2240] JLaunchProcessCommand: Invoke VM Shutdown
[Thr 2240] JHVM_FrameworkShutdownDirect: invoke direct shutdown
[Thr 2240] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 2240] JLaunchISetState: change state from [Initial (0)] to [Stopping (5)]
[Thr 640] Fri Nov 30 10:38:34 2007
[Thr 640] JLaunchIExitJava: exit hook is called (rc = 0)
[Thr 640] JLaunchCloseProgram: good bye (exitcode = 0)
Thank you very much in advance for your help.
Hassan

Hi!
If instance.properties is not there your installation has not finished correctly. This file is the central point of information for the bootstrap, which retrieves the info on how to connect to the database to collect the infos for the system startup (which will then overwrite your instance.properties file with the most recent values from the DB).
Please check if instance.properties has been deleted and can maybe be restored from tape or if there was an error in the installation.
Regards,
Jörg

Regarding RFC Communication from SAP R/3 to SAP J2EE Engine 6.40

Hello,
     We have an application deployed in SAP J2EE engine 6.20. From SAP R3 (SAP R/3 version is 6.4C), We are communicating to the application deployed in SAP J2EE Engine 6.20 using RFC protocol. EJB module (Deployed in SAP J2EE Engine 6.20) which is being invoked from a Function Module using RFC protocol has the same name as the Function Module name. We were able to communicate to SAP J2EE Engine 6.20 this way.
     Currently, I have deployed the same application in SAP J2EE Engine 6.40. I have followed the same procedure which i have used while depolying and working with SAP J2EE Engine 6.20. But, it is not working, and i was not able to communicate to SAP J2EE 6.40, the same way i did in SAP J2EE Engine 6.20.
   Please let me know whether the procedure for communicating to SAP J2EE Engine 6.40 has changed in comparison with SAP J2EE Engine 6.20.
Also,Any pointers regarding RFC and JCO implementation in SAP J2EE Engine 6.40 willl be helpful.
Thank you.
Regards,
-Shabir Rahim.

Hello ,
      The Connection in sm59 is established successfully> there were no Error thorwn in SAP when testing the connnection. But when i am making background call using a Function Module in SAP R3, the calls reaches Application deployed in SAP J2EE Engine 6.40, But it is failing with the error as,
#1.5#005056A24413003C000000240000126000042853BD899290#1170240034258#/System/Server##com.sap.engine.services.dsr####sstra902_IPC_2629150#Guest#6813e650a93f11dba9f5005056a24413#Thread[JCO.ServerThread-1,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/System/Server#Plain####
#1.5#005056A244130042000000000000126000042853CFDB80F8#1170240341655#/System/Server##com.sap.engine.services.dsr#Guest#2####322aaa71b11811db85e1005056a24413#SAPEngine_Application_Thread[impl:3]_36##0#0#Error#1#com.sap.engine.services.dsr#Java#DSR_36#com.sap.engine.services.dsr.res.DSRResourceBundle#Error while taking over external passport null#1#null#
#1.5#005056A244130042000000030000126000042853CFDB86BD#1170240341671#/System/Server##com.sap.engine.services.jndi#Guest#2####322aaa71b11811db85e1005056a24413#SAPEngine_Application_Thread[impl:3]_36##0#0#Info#1#com.sap.engine.services.jndi#Plain###Incorrect name parameter rfcaccessejb//DCEUR/Z_AIS_IPC_CFG_PRICE in naming operation.#
#1.5#005056A244130042000000040000126000042853CFDB8745#1170240341671#/System/Server##com.sap.engine.services.jndi#Guest#2####322aaa71b11811db85e1005056a24413#SAPEngine_Application_Thread[impl:3]_36##0#0#Info#1#com.sap.engine.services.jndi#Plain###Incorrect name parameter java:rfcaccessejb//DCEUR/Z_AIS_IPC_CFG_PRICE in naming operation.#
#1.5#005056A24413003C000000280000126000042853CFDBC4AA#1170240341686#/System/Server##com.sap.engine.services.dsr####sstra902_IPC_2629150#Guest#6813e650a93f11dba9f5005056a24413#Thread[JCO.ServerThread-1,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/System/Server#Plain####
Here, //DCEUR/Z_AIS_IPC_CFG_PRICE is the Funcrtion module name in SAP R/3 6.4C.
Also Please let me know whether is there any Operating Differences between WAS 6.20 and WAS 6.40, for JCO/RFC based Communication( ie Comunicating with WAS 6.40 from SAP r/3 using RFC Protocol). Any materials and Information on how to work on SAP J2EE Engine 6.4 will also be very helpful.
Thank you.

Problem while extending and modifying the ISA B2B app on SAP J2EE 6.4

We are facing some problem with extending and modifying the ISA B2B 4.0 application.
First Let me clarify you the whole scenario.
Previously we had ISA B2B 4.0 SP03 deployed on SAP J2EE 6.20 Engine.
We had used eclipse 3.0 to extend and modify the application as NWDS does not support SAP J2EE 6.20.
We had used ant buildtool to build the modified application which comes along with the ISA Software Archive.
We had successfully done all the modifications and application was running fine...
Now we have upgraded the overall J2EE infrastructure and using J2EE 6.4 Engine which supports NWDS.
We have successfully deployed the ISA B2B application which comes along with the Support Package.
We are using Support Package ISAWAC40SP11P_7-20000529.SAR E-Selling 640. The application is working fine after all
the configuration done in XCM and SAP CRM 4.0 system.
Now for modification and extension i have created another b2b enterprise archive with name "b2b_client.ear" using ant buildtool.
I've done the modification and extension .. added some Z classes and JSP pages. Now when i try to deploy the application using
SDM 6.40, I got an error message stating
"com.sap.sdm.util.sduread.IllFormattedSduFileException: The archive must be deployed with a 6.20 SDM, which has a SDM-SDA compatible version 1 or greater."
I think this error is due to the incompatible sda_build.xml used in the build process but we have used the same xml file bundled with the above mentioned ".sar" file..
Please help or suggest someone who can help me out from this...
Thanks & Regards.
Sandeep Solanki

Hi Alkis.
First, you need to specify the fully qualified class name of your based-RequestProcessor class in the config.xml file like
<controller contentType="text/html;charset=UTF-8" locale="true" nocache="true"
processorClass="com.mycompany.struts.framework.MyRequestProcessor"/>
If you review the source code of the ActionServlet and RequestProcessor classes, you can see that overwritten methods (by you) are executed every time the client makes a request to the struts based application.
I hope you can run your approach. And it will be excellent you can shared how you will do it.
Kindest regards.

Communication issue btw applications on SAP J2EE Engine6.20 & Websphere 6.0

We have a customized SAP IPC application running on SAP J2EE Engine 6.20 and it is communicating with another application called Common Configurator or C2 running on WebSphere 4.0.5.
Communication between customized SAP IPC application and C2 application is over RMI IIOP. SAP IPC application calls methods on stateless session beans in C2 application.
Going forward, we want to connect to C2 running on Websphere 6.0 from this customized SAP IPC.
When I am trying to connect to C2 on Websphere 6.0 I am getting the following
exception :
org.omg.CORBA.BAD_PARAM: minor code: 0 completed: No
 at org.omg.CosNaming.NamingContextHelper.narrow(NamingContextHelper.java:48)
 at com.sun.jndi.cosnaming.CNCtx.setOrbAndRootContext(CNCtx.java:278)
 at com.sun.jndi.cosnaming.CNCtx.initUsingUrl(CNCtx.java:251)
 at com.sun.jndi.cosnaming.CNCtx.initOrbAndRootContext(CNCtx.java:188)
 at com.sun.jndi.cosnaming.CNCtx.<init>(CNCtx.java:68)
 at com.sun.jndi.cosnaming.CNCtxFactory.getInitialContext(CNCtxFactory.java:30)
 at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:660)
 at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
 at javax.naming.InitialContext.init(InitialContext.java:217)
 at javax.naming.InitialContext.<init>(InitialContext.java:193)
But the same setup is working fine for SAP J2EE Engine 6.20 and Websphere 4.0.5.
Has anybody faced similar issue before ?
Could anyone tell me what could be the possible reasons and how can I preceed on this.
Additionally,
SAP J2EE Engine 6.20 uses ORB implementation of the Sun JDK (1.3). And Websphere 6.0 is based on JDK 1.4 version.
Thanks in advance.
Harman

This is what class org.omg.CORBA.BAD_PARAM all about :
Exception thrown when a parameter passed to a call is out of range or otherwise considered illegal. An ORB may raise this exception if null values or null pointers are passed to an operation (for language mappings where the concept of a null pointers or null values applies). BAD_PARAM can also be raised as a result of a client generating requests with incorrect parameters using the DII.
It contains a minor code, which gives more detailed information about what caused the exception, and a completion status. It may also contain a string describing the exception.
And Websphere 6.0 is based on JDK 1.4 version. The JDK of websphere is an IBM implementation and differs a lot from the sun implementation. As well, WAS6.0 supports J2EE 1.4 also...may be you should check the release notes / documentation of WAS for compatibility issues if any.
Regards,
Amol

Starting and stopping SAP J2EE Engine

Hi guys,
         I have downloaded and installed trial version of SAP Web Application Server (SAP Web AS) Java 6.40 for Microsoft Windows XP.
   I wanted to launch SAP J2EE Engine and Software Deployment Manager (SDM) to run my web dynpro application. The Netweaver Developer studio getting started guide has a link for starting and stopping the SAP J2EE Engine but its not working for me. I get an error with the link.
Is it possible for someone to let me know how to launch J2EE engine and SDM. Also what server settings I need to make in the menu path Window -> Preferences -> SAP J2EE Engine.
Any help will be appreciated.
Thanks,
Mandar

Hi Ivaylo and Thomas,
    Thanks for your help, It works fine. For some reason after starting my J2EE server, when I start my Netweaver developer studio, it gives the following error
   JVM Terminated Exit code=1
   c:\j2sdk1.4.2_05\bin\javaw.exe
   -Xmx512m
   -Xms128m
   -XX:PermSize=128m
   DallUserDir='C:\Documents and Setting\All users\Application Data'
   -cp C:\Program Files\SAP\JDT\eclipse\SAPStartup.jar com.sap.ide.eclipse.startup.Main
   -os win32
   -ws win32
   -arch x86
   -feature com.sap.java.ide
   -showsplash C:\Program Files\SAP\JDT\eclipse\SAPIde.exe -showsplash 600
Any idea why I get this error and how to fix it. My Netweaver Developer studio did startup few times and I did write some code in it. But now when I try to start NDS, I get the above error.
Any help will be appreciated.
regards,
Mandar

SAP J2EE version

Similar Messages

Maybe you are looking for