xMII 12.0 on NW 7.1 CE?

[Former Member]

I installed the NW 7.1 CE developer preview and installed xMII 12.0 via JSPM. I created my 3 groups, XMII Administrators, XMII Users, and XMII Developers and assigned them to my user. I upgraded my JCO DLLs (Windows XP SP-latest). I restarted NW 7.1 CE. When I go to URL http://myhost:50100/XMII (or .../XMII/Menu.jsp), I get the following stack dump:

Details: com.sap.engine.services.jmsconnector.exceptions.BaseDeploymentException: Class loading error: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Error getting the server-side naming service functionality during getInitialContext operation.

at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:251)

at com.sap.engine.system.naming.provider.DefaultInitialContext._getDefaultInitCtxt(DefaultInitialContext.java:64)

at com.sap.engine.system.naming.provider.DefaultInitialContext.<init>(DefaultInitialContext.java:45)

at com.sap.engine.system.naming.provider.DefaultInitialContextFactory.getInitialContext(DefaultInitialContextFactory.java:41)

at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)

at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)

at javax.naming.InitialContext.init(InitialContext.java:223)

at javax.naming.InitialContext.<init>(InitialContext.java:197)

at com.sap.engine.services.jmsconnector.container.JmsContainerImpl.loadFactory(JmsContainerImpl.java:1325)

at com.sap.engine.services.jmsconnector.container.JmsContainerImpl.prepareStart(JmsContainerImpl.java:585)

at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:211)

at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)

at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:393)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:480)

at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:537)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:230)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:374)

at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:2955)

at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:736)

at com.sap.engine.services.servlets_jsp.server.deploy.impl.ApplicationManager.start(ApplicationManager.java:175)

at com.sap.engine.services.servlets_jsp.server.deploy.impl.ApplicationManager.analyseAppStatusMode(ApplicationManager.java:279)

at com.sap.engine.services.servlets_jsp.server.DeployContext.startLazyApplication(DeployContext.java:334)

at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:86)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)

at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)

at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)

at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)

at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)

at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)

at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)

at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:308)

at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:221)

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:137)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:229)

Caused by: com.sap.engine.services.jndi.persistent.exceptions.NoPermissionException: Exception during getInitialContext operation. Wrong security principle/credentials. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.]

at com.sap.engine.services.jndi.implclient.LoginHelper.serverSideLogin(LoginHelper.java:70)

at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:143)

... 41 more

Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.

at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:177)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.services.security.login.FastLoginContext.login(FastLoginContext.java:217)

at com.sap.engine.services.jndi.implclient.LoginHelper.serverSideLogin(LoginHelper.java:60)

... 42 more

Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Authentication did not succeed.

at com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule.login(BasicPasswordLoginModule.java:149)

at com.sap.engine.services.security.login.LoginModuleLoggingWrapperImpl.login(LoginModuleLoggingWrapperImpl.java:189)

at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:71)

... 45 more

com.sap.engine.services.jndi.persistent.exceptions.NamingException: Error getting the server-side naming service functionality during getInitialContext operation.

at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:251)

at com.sap.engine.system.naming.provider.DefaultInitialContext._getDefaultInitCtxt(DefaultInitialContext.java:64)

at com.sap.engine.system.naming.provider.DefaultInitialContext.<init>(DefaultInitialContext.java:45)

at com.sap.engine.system.naming.provider.DefaultInitialContextFactory.getInitialContext(DefaultInitialContextFactory.java:41)

at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)

at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)

at javax.naming.InitialContext.init(InitialContext.java:223)

at javax.naming.InitialContext.<init>(InitialContext.java:197)

at com.sap.engine.services.jmsconnector.container.JmsContainerImpl.loadFactory(JmsContainerImpl.java:1325)

at com.sap.engine.services.jmsconnector.container.JmsContainerImpl.prepareStart(JmsContainerImpl.java:585)

at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:211)

at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)

at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:393)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:480)

at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:537)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:230)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:374)

at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:2955)

at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:736)

at com.sap.engine.services.servlets_jsp.server.deploy.impl.ApplicationManager.start(ApplicationManager.java:175)

at com.sap.engine.services.servlets_jsp.server.deploy.impl.ApplicationManager.analyseAppStatusMode(ApplicationManager.java:279)

at com.sap.engine.services.servlets_jsp.server.DeployContext.startLazyApplication(DeployContext.java:334)

at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:86)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)

at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)

at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)

at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)

at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)

at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)

at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)

at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:308)

at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:221)

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:137)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:229)

Caused by: com.sap.engine.services.jndi.persistent.exceptions.NoPermissionException: Exception during getInitialContext operation. Wrong security principle/credentials. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.]

at com.sap.engine.services.jndi.implclient.LoginHelper.serverSideLogin(LoginHelper.java:70)

at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:143)

... 41 more

Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.

at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:177)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.services.security.login.FastLoginContext.login(FastLoginContext.java:217)

at com.sap.engine.services.jndi.implclient.LoginHelper.serverSideLogin(LoginHelper.java:60)

... 42 more

Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Authentication did not succeed.

at com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule.login(BasicPasswordLoginModule.java:149)

at com.sap.engine.services.security.login.LoginModuleLoggingWrapperImpl.login(LoginModuleLoggingWrapperImpl.java:189)

at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:71)

... 45 more

.

at com.sap.engine.services.jmsconnector.container.JmsContainerImpl.loadFactory(JmsContainerImpl.java:1339)

at com.sap.engine.services.jmsconnector.container.JmsContainerImpl.prepareStart(JmsContainerImpl.java:585)

at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:211)

at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)

at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:393)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:480)

at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:537)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:230)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:374)

at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:2955)

at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:736)

at com.sap.engine.services.servlets_jsp.server.deploy.impl.ApplicationManager.start(ApplicationManager.java:175)

at com.sap.engine.services.servlets_jsp.server.deploy.impl.ApplicationManager.analyseAppStatusMode(ApplicationManager.java:279)

at com.sap.engine.services.servlets_jsp.server.DeployContext.startLazyApplication(DeployContext.java:334)

at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:86)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)

at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)

at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)

at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)

at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)

at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)

at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)

at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:308)

at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:221)

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:137)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:229)

Any ideas?

-tim

[Former Member]

I still cannot get an xMII 12.0 IDOC/JCO message listener running in NW 7.1.

(sorry for the redundant post, but I wanted to mark this thread as "unanswered" and I was required to enter a comment.)

Message was edited by:

Tim Drury

[former_member193328]

Hi Tim

First thing I would suggest is not to run xMII 12.0 on NW CE 7.1. This is because NW 7.1 CE is not the upgraded version of NW 2004s but a new J2EE engine from SAP.

So surely lot of things dont work from 2004s to CE.

One of them is JCo Message Listeners that you have mentioned. They are no longer supported in CE. There is no fix and no workaround for the error you are getting.

Regards

Partha

[Former Member]

Parta, thanks for the response. I've basically come to the same conclusion that xMII 12's JCO interfaces are not going to work in NW 7.1.

When you say the "JCo Message Listeners" are not supported in CE are you saying the xMII 12's bundled JCO libraries won't work in NW 7.1 CE? Can you elaborate on why? My guess is there's a resource conflict with NW 7.1's built-in JCO listener resource. Is this your experience too? Do you know how xMII 12.x is planning to deal with this? Will it defer to NW 7.1's JCO resource and simply let you use a JCO listener you've created in NW? I'm just curious. Thanks again,

-tim

[former_member193328]

Hi Tim

Ya more or less your guess is correct. There is a conflict with the version in CE with the xMII bundled (SAP Standalone JCo). So the classes cannot be loaded properly.

At the moment I am not sure how the implementation will be in xMII 12.x in CE environment.

Regards

Partha

[jcgood25]

Tim,

I guess you'll just have to patiently await the 12.1 release like the rest of us

Regards,

Jeremy

[Former Member]

Hi Tim,

There is no way to get a fully functioning version of 12.0 running on CE. Platform differences exist in the location or required libraries, etc. The JCO/RFC differences is one of the largest since the new implementation is completely different on the NW 7.1 side.

Also service libraries are no longer supported in 7.1. Which means the references to the XMII LIbraries and XMII JCO Libraries from the main applicaiton no longer work. The only reason your XML parsing works is because the XML libraries are now bundled with JDK 1.5, otherwise you wouldn't be able to get anything to even load.

As Jermey said you will have to wait to go to CE. 12.1 is just starting development now. Our first major effort is getting 12.0 to work on 7.1 correctly before we can get to the new good stuff! Though running on JDK 1.5 will be very nice.

Fran

[Former Member]

I solved the problem. From Sam's suggestions I suspected something went wrong with deployment so I undeployed then redeployed. This time I deployed with the Deploy View in Developer Studio (7.1 CE) which provided a simpler deployment summary and there was one warning about a MDB failing because it couldn't find "XMIICatalogReloadTopic". Sure enough, there was no XMIICatalogReloadTopic. I tried to manually create it, but it wouldn't let me set the Application name to the same name that xMII is using and I thought that may cause problems. So, instead, I exploded the SCA and found jms-destinations.xml down in <XMII-nnn.SCA>/DEPLOYARCHIVES/<XMII.sda>/META-INF. XMIICatalogReloadTopic was missing so I added it:

	<destination>
		<connection-factory>XMIITopicConnectionFactory</connection-factory>
		<destination-name>XMIICatalogReloadTopic</destination-name>
	</destination>	

and repackaged the SCA and redeployed. Presto! xMII 12.0 is now running on NW 7.1 CE. I ran the BLE a little and created a simple HelloWorld transaction and all seemed to work nicely.

-tim

[Former Member]

Let us know your experiences...2004s is a real PITA to install, whereas 7.1 CE installs a WHOLE lot quicker, from what I've seen.

If you can reliably get it running, that would be awesome. If you have time to write up a step-by-step summary of what you did to deploy, that would be helpful as well.

[salvatore_castro]

Tim,

First off I would like to say that I'm impressed by your thirst for pain! Secondly if you do run into any issues they are most likely related to incorrect class paths referenced by xMII that have changed from NW 7.0 to 7.1 so most likely things such as logging and UME will be most heavily affected. My suspicion is that anything referenced by name such as JMS and WebService/URL interface to BLS will remain unaffected. As a result the test that I suggest running is to create new roles/users/navigation and also to use the Event Logger action and see what happens with those. Good luck.

-Sam

[Former Member]

Update of progress:

I had a bit more time to spend on this yesterday. Firstly, I found the Simulator Editor did not work because the jsp used ArrayList but did not import the class. I updated the jsp, rebuilt the SCA, and reployed and it worked.

As for logging, the Event Logger source still defaults to the User log, but I have no idea how to find that log in xMII 12.0.

I noticed that the online help for the Event Logger says that source defaults to "Xacute" and changing it will cause the action to fail. That seemed odd, so I looked at the 11.5 online help and it says the same thing. I suspect that must be a documentation bug that's been there since 11.0 or earlier. Once I figure out where the event log is in 12.0, I can determine if logging works.

SAP connectivity is the biggest issue right now. I can create a message listener, but when I try to start it, a get a message that it failed. Checking the logs, I see an error complaining about the JCO version. I had downloaded the JCO libs SAR listed within the xMII 12.0 platform-specific section and the enclosed DLLs (librfc32.dll and sapjcorfc.dll) are the same versions I already had in /windows/system32. I dropped them into /windows/system32 anyway but it made no difference. I did notice another issue with the JCO SAR - it included a third file called Installation.doc which is not a document file. It's a SAR file also - I noticed the "CAR" magic-number as the first few bytes of the file by loading the file into my editor. Upon renaming is .SAR and running sapcar on it, it turns out to include the same two DLL files. This seems to be a build-system bug.

Anyhow, while looking into the JCO problem, I came across JRA which is the preferred method of accessing JCO from a J2EE container. I also noticed that NW 7.1CE included a version of JRA but it was not started. I started it from the Repository view of Developer Studio and I got past the JCO version error when trying to start my message listener - however the listener start-up still failed. The new error is complaining that the listener is already in the JCO listener pool. This seems to either be a bug in the xMII code which is not checking to see if the listener is already in the pool before adding it, or xMII 12.0 depends on a version of JRA that already has this failsafe. Is there a specific JRA version I can deploy to get past this? If not, there's little chance I can get past this error without some very intrusive modifications.

-tim

[Former Member]

Update on logging:

I think I figured out NW logging. The Developer Studio logs seem to lag quite a bit so I had to use the web-based log viewer. Found this entry:

info 2007-10-05 09:18:29:640 [UserEvent] : "HelloWorld!" 

so Event Logging to the User log appears to work fine.

-tim

[Former Member]

Here's more detail on the JCO error I'm getting in case anyone has a suggestion:

An error occurred trying to start server DMO210-TIM

[EXCEPTION]

com.sap.mw.jco.JCO$Exception: (102) JCO_ERROR_COMMUNICATION: A pool with the identifier 'DMO210-TIM' already exists

at com.sap.mw.jco.JCO$PoolManager.addPool(JCO.java:6072)

at com.sap.mw.jco.JCO.addClientPool(JCO.java:8402)

at com.sap.xmii.databuffer.util.JCoServerManager.startServer(JCoServerManager.java:302)

at com.sap.xmii.Illuminator.gui.handlers.JCoServerHandler.processConfiguration(JCoServerHandler.java:249)

at com.sap.xmii.Illuminator.gui.handlers.JCoServerHandler.process(JCoServerHandler.java:123)

at com.sap.xmii.servlet.Admin.service(Admin.java:65)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)

at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:163)

at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:82)

at com.sap.xmii.system.SecurityFilter.doFilter(SecurityFilter.java:97)

at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:74)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:425)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:288)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)

at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)

at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)

at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)

at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)

at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)

at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)

at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)

at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)

at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:308)

at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:221)

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:137)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:229)

Date: 2007-10-04

Time: 18:32:22:953

Category: com.sap.xmii.Illuminator.gui.handlers.JCoServerHandler

Location: com.sap.xmii.Illuminator.gui.handlers.JCoServerHandler

Application: sap.com/XMII_EnterpriseApplication

Thread: HTTP Worker [4]

Data Source: j2ee\cluster\server0\log\defaultTrace_00.trc

Message ID: 190632500000048277

Argument Objects:

Arguments:

DSR Component:

DSR Transaction: acedc99072c911dcca9d0015c55394ba

DSR User:

Message Code:

Session: 40

Transaction:

User: Administrator

Host: Timdruryxp

System: TD1

Instance: J01

Node: server0

[Former Member]

I may be getting closer to a solution here. Upon searching around the NW 7.1CE installation, I found two jars that contain com.sap.mw.jco.JCO:

1. C:\usr\sap\TD1\J01\j2ee\cluster\bin\ext\com.sap.mw.jco\sap.com_tcbl_jrfcimpl.jar

MANIFEST.MF has no Specification Version; it says Edition = 710SP1

and

2. C:\usr\sap\TD1\J01\j2ee\cluster\bin\ext\XMII JCo Library\sapjco.jar

MANIFEST.MF states the Specification Version is 2.1.8

The first appears to be the JCO library included in the NW 7.1CE installation and the second was likely created when I installed xMII 12.0.

Here's something that always amazes me about SAP - NW includes a classloader viewer. Sweet! I can see that XMII JCo Library is a parent to XMII_EnterpriseApplication, so I'm fairly certain that xMII is using jar #2 above which would seem to be the correct jar.

However, in addition to the first exception that I posted earlier I noticed there was another exception that I missed seeing before:

Unable to load servers

[EXCEPTION]

java.lang.ExceptionInInitializerError

at com.sap.xmii.databuffer.util.JCoServerManager.startServer(JCoServerManager.java:309)

at com.sap.xmii.databuffer.util.JCoServerManager.loadServers(JCoServerManager.java:414)

at com.sap.xmii.system.ContextListener.contextInitialized(ContextListener.java:68)

at com.sap.engine.services.servlets_jsp.server.application.WebEvents.contextInitialized(WebEvents.java:74)

at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:198)

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:137)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:229)

Caused by: com.sap.mw.idoc.IDoc$Exception: (8) IDOC_ERROR_INITIALIZATION: Could not initialize SAP Java Connector IDoc Class Library. Found SAP Java Connector version 6.42.20 but version 2.1.6 or a higher patch level is required.

at com.sap.mw.idoc.jco.JCoIDoc.<clinit>(JCoIDoc.java:142)

... 9 more

In addition to sapjco.jar in the directory C:\usr\sap\TD1\J01\j2ee\cluster\bin\ext\XMII JCo Library, there is also sapidoc.jar and sapidocjco.jar. However the versions Strings that sapidoc.jar and sapidocjco.jar report back are:

sapidoc.jar version="1.0.4 (2006-10-10)";

sapidocjco.jar version="1.0.6 (2006-05-17)";

sapjco.jar version="2.1.8 (2006-12-11)"

If I look at JCO jar #1 above, I see this:

sap.com_tcbl_jrfcimpl.jar version="6.42.20 (2007-02-26)";

So, it appears that I was wrong when I stated above that xMII seemed to be picking up the "XMII JCo Library" jars because this latest exception is clearly showing that xMII is loading the NW 7.1 JCO library. Which means either (1) the Classloader viewer isn't correct or (2) I have no idea how to use the Classloader viewer - the later being the more likely answer.

-tim

[Former Member]

Hi, Tim.

If I remember correctly, as long as you update both the DLL's and the JARs to the matching set for the latest version amongst the ones that are in conflict, you should be OK.

Rick

[Former Member]

Thanks Rick, but I don't think that's the issue. I believe both libraries are properly installed. The JRA is using JCO version 6.42.20 and the XMII JCo Library is version 2.1.8. What I don't understand is why the xMII Enterprise Application is finding the JRA first - before it sees the xMII JCo Library. It's been a while since I looked at the JCA spec, but I would think an application would need to explicitly request access to a JCA resource via the container before the container gives the application access to the resource. Perhaps in my enthusiasm to get xMII 12.0 running, I set/unset/changed something I shouldn't have - I just don't know what. I'll keep looking...

Thanks,

-tim

[Former Member]

In any case, I don't think you can have two versions of the DLL's loaded (including the JCO DLL's and LIBRFC DLL's), and since the JCO JAR's make a bunch of native calls, they're tightly bound to specific DLL version(s).

I would ferret out all versions of the JCO JARS that get deployed, and make sure they're the same.

This same issue use to pop up when someone had SAP Business Connector and SAP xMII installed on the same server.

[Former Member]

Oh, I understand what you're saying now. Since only one DLL can be loaded at any one time, make sure any and all JCO jars deployed (both in xMII and in JRA) are the jars that match that loaded DLL. Right?

I'll work on that. I thought I could simply uninstall the JRA, but then NW wouldn't even start since some application relies on it.

-tim

[Former Member]

Yep. That's what I was suggesting. Run a search through the deployed web app for all JCO jars and see what you find.

[Former Member]

I replaced sapjco.jar in XMII_JCO_Libs.sda with the NW 7.1 JCO jar (sap.com_tcbl_jrfcimpl.jar) and updated provider.xml:

(snip)
<jars>
	<jar-name>sapidoc.jar</jar-name>
	<jar-name>sapidocjco.jar</jar-name>
	<jar-name>sap.com~tc~bl~jrfc~impl.jar</jar-name>
</jars>
(snip)

and rebuilt the xMII 12.0 SCA and deployed. I didn't see the JCO version mismatch error, but I still get this exception when trying to start the message listener:

<b>

An error occurred trying to start server DMO210-XMII_TIM

[EXCEPTION]

com.sap.mw.jco.JCO$Exception: (102) JCO_ERROR_COMMUNICATION: A pool with the identifier 'DMO210-XMII_TIM' already exists

at com.sap.mw.jco.JCO$PoolManager.addPool(JCO.java:6072)

at com.sap.mw.jco.JCO.addClientPool(JCO.java:8402)

at com.sap.xmii.databuffer.util.JCoServerManager.startServer(JCoServerManager.java:302)

at com.sap.xmii.Illuminator.gui.handlers.JCoServerHandler.processConfiguration(JCoServerHandler.java:249)

at com.sap.xmii.Illuminator.gui.handlers.JCoServerHandler.process(JCoServerHandler.java:123)

...

</b>

I've tried deleting message listener "DMO210-XMII_TIM" from xMII and re-creating it but to no avail. I have verified that I do not have any JCO RFC Destinations defined in NW itself and the only other message listener in xMII is the default "XMIIMESSAGELISTENER". I also peeked into the XMII_JCOSERVER table in the database and it only shows "XMIIMESSAGELISTENER" and "DMO210-XMII_TIM".

Can anyone provide any help on this error?

-tim

[Former Member]

Maybe there's a double entry in the configuration database?

[salvatore_castro]

Tim,

Did you have any errors during deployment as well? From what I can see in the stack trace is that the JMS classes are not found in the JNDI lookup. If you log into Visual Administrator -> Server0 -> Services -> JMS Provider

Select default and then look under the Topic and Queue tabs....under Topic there should be 3 starting with the name XMII and under Queue there should be 2 starting with XMII. If these are not present or the naming is different then this is your problem. As Rick mentioned already this is not a supported release but it's always nice to know what the underlying problem is. Happy hunting

-Sam

[salvatore_castro]

Tim,

Just to add something else to this thread....as of now the v12.1 release of xMII is unofficially planned to support NW 7.1 CE so nothing concrete, as always

-Sam

[Former Member]

Salvatore, thanks for the reply. I had no errors during deployment. I had forgotten to mention the JMS queues in my earlier posts. All the JMS providers/factories for XMII are present, but all are stopped. I thought that starting XMII_EnterpriseApplication would get them started. Are you implying that they need to be started first? That would seem to explain some of the error messages.

Here is what the admin tool says about XMIIQueueConnectionFactory:

-

---

Application Name: * -> sap.com/XMII_EnterpriseApplication

SAP Factory Type: * -> JNDI Context

Link Factory Name: * -> jmsfactory/default/QueueConnectionFactory

(all fields not specified are blank)

java.naming.provider.url=localhost

java.naming.security.principal=Administrator

java.naming.factory.initial=com.sap.engine.services.jndi.InitialContextFactoryImpl

-

---

The Topic factory is nearly identical except it links to the TopicConnectionFactory. Both the jmsfactory/default/QueueConnectionFactory and .../TopicConnectionFactory exist.

-tim

[salvatore_castro]

Tim,

My assumption is that the JMS provider would have to be started first since the xMII data buffering and other various background processes use this functionality. As for your class definitions for the Queue they also appear correct when I compare them to mine in my 2004s setup. I would say to setup the JMS Service to startup automatically and restart your NW environment and see if the error message changes. I honestly do not know if you will be able to hack v12.0 into 7.1 since the change in NW from 7.0 to 7.1 is somwhat equivalent to a shift from Windows to Linux. Aparently there are a lot of backend changes to the class/package names. I do know that the release of xMII v12.0 to v12.1 will probably contain a migration as well to account for this shift. So once again good luck

-Sam

[erik_schrampf]

Tim,

I believe Rick is right on this one I do not think xMII is supported on NW 7.1 CE.

[Former Member]

AFAIK, it isn't supported on NW CE, only 2004s.

[Former Member]

Rick, I suspect xMII 12.0 is not certified for NW 7.1 CE but that doesn't stop us from trying... Just like xMII 11.5 isn't certified to run on JDK 1.6, right?

-tim

[Former Member]

You're a glutton for punishment......

[erik_schrampf]

Tim,

What service release of xMII 12.0 are you using? In SP1 and above you need to adds xMII Administrators, Users and Developers under the Roles and not Groups. Try that and see if that fixes your problem. Can you get to all other NW screens such as the Admnistration page?

Erik

[Former Member]

Thanks for the response Erik. I'm <i>not</i> running xMII 12.0 SP1 - just 12.0. I can get to all the other screens without any problems.

If I go to the Start/Stop Applications page and filter on "xmii" I see 3 entries:

sap_xmiidbinit

XMII_EnterpriseApplication

XMII_Database

I can start sap_xmiidbinit and XMII_Database, but XMII_EnterpriseApplication will not start. When I try to start it, I get the following two errors in the server log:

-

---

Version: 1.5

Guid: 0015C55394BA00070000000200001A8802A5433FAD259C7F

Time: 2007 10 03 09:18:35:953

SourceName: /System/Server/Services/Deploy

Application:

Location: com.sap.engine.services.deploy

User:

Session:

Transaction:

DSRComponent:

DSRUser:

DSRTransaction: 25ae321071b311dcb06f0015c55394ba

ThreadName: System [30]

GroupId:

GroupLevel: 0

GroupIndent: 0

Severity: Error

Relatives: com.sap.engine.services.deploy

MsgType: Plain

MsgCode: Exception in operation startApp with application sap.com/XMII_EnterpriseApplication.

ResourceBundle: com.sap.engine.services.monitor.mbeans.MonitorResourceBundle

Text:

-

---

Version: 1.5

Guid: 0015C55394BA00070000000500001A8802A5433FAD259C7F

Time: 2007 10 03 09:18:35:953

SourceName: /System/Server/Services/Deploy

Application:

Location: com.sap.engine.services.deploy

User:

Session:

Transaction:

DSRComponent:

DSRUser:

DSRTransaction: 25ae321071b311dcb06f0015c55394ba

ThreadName: System [30]

GroupId:

GroupLevel: 0

GroupIndent: 0

Severity: Error

Relatives: com.sap.engine.services.deploy

MsgType: Plain

MsgCode: Error occurred while parsing file "data-source-aliases.xml".

ResourceBundle: com.sap.engine.services.monitor.mbeans.MonitorResourceBundle

Text:

-

---

-tim