J2EE at Os level...

Hello,
How can I make sure that J2EE is running? It is regarding ABAP+J2EE for BW 3.5 NW04.
I went to SMICM - Services and it will show the list of HTTP ports and there status. How will I be sure that J2EE is active. Because J2EE will be down but these will active in SMICM. J2EE ports are different than HTTP ports. You can view tham in SMICM - Go To - HTTP Server - Display Data.
I think - You can only start-stop J2EE from SMICM and can look at their port numbers using different option but not Services in SMICM.
Does it have to done at OS level or there is a SAP transaction.
Your help will be greately appreciated.
Thank you very much.
Thank you.
SC

Hi,
A couple of ways to check the status of the J2EE Engine..
Open up an Internet Explorer and enter the URL http://<was server>:5<sysnr>00 (for example - http://mywasserver/50000)...you should get the page with SAP Web application server....This shows that the server is running(does not mean that all applications might be running)....
If you have netweaver developer studio installed...open the NWDS...give the j2ee engine details in the settings of the NWDS...Now open the J2EE view ...here you can see the statuses of the J2ee engine (of the server, sdm...etc)...
Thanks & Regards,
Renjith.

Similar Messages

Error while generating PDF - in Bex Web

Hi Experts,
I am currently having the issue that I receive the error "Error while generating PDF" when using the "Print Version" functionality. This problem only occurrs for the Bex Web Query. I know that the ADS service is configured correctly- The webservice test is successful and other applications (Guided Procedures, MSS) also use it successfully.
Please see below the excerpt from the default trace:
A message was generated:
ERROR
Error while generating PDF
com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode PageExportRenderingRootNode_0001
Message: 28
Stack trace: java.lang.ArrayIndexOutOfBoundsException: 28
at com.sap.ip.bi.export.xfa.impl.SizeCalculator.getColumnSizes(SizeCalculator.java:178)
at com.sap.ip.bi.export.impl.ExportController.setSizes(ExportController.java:220)
at com.sap.ip.bi.export.impl.ExportController.calculateAndSetSizes(ExportController.java:611)
at com.sap.ip.bi.export.impl.ExportController.doExportPrep(ExportController.java:408)
at com.sap.ip.bi.export.impl.ExportController.convert(ExportController.java:336)
at com.sap.ip.bi.export.controller.ExportResult.createExport(ExportResult.java:58)
at com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode.createPDF(PageExportRenderingRootNode.java:453)
at com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode.doExport(PageExportRenderingRootNode.java:105)
at com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode.processRendering(PageExportRenderingRootNode.java:252)
at com.sap.ip.bi.webapplications.runtime.impl.Page.buildRenderingTree(Page.java:3809)
at com.sap.ip.bi.webapplications.runtime.impl.Page.processRenderingRootNode(Page.java:3867)
at com.sap.ip.bi.webapplications.runtime.impl.Page.processRendering(Page.java:3510)
at com.sap.ip.bi.webapplications.runtime.impl.Page.doProcessRequest(Page.java:3470)
at com.sap.ip.bi.webapplications.runtime.impl.Page.processRequest(Page.java:2489)
at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.doProcessRequest(Controller.java:892)
at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.processRequest(Controller.java:813)
at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService.handleRequest(BIRuntimeService.java:456)
at com.sap.ip.bi.webapplications.runtime.jsp.portal.components.LauncherComponent.doContent(LauncherComponent.java:21)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
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)
If you have any idea or clue it would be greatly appreciated.
Thanks in advance for every support,
Jan

Hi Jan,
Most possible causes for encountering this issue are:
Possible cause:
- The ADS is installed on a plattform, that is currently not supported by SAP for ADS. Please check the avaliablity at: Product Availability Matrix
- Mixing of different Netweaver releases (NW04 and NW04s) -> This is unfortunatelly not possibble the J2EE engine release has to match with the ABAP stack release in order connect them properly.
- The ADS SP level does not match the J2EE engine SP level. -> Please update the software components to have the same support package level.
Hope this helps!!
Regards,
Arafat

Taking Java a little lower

This post is not a help request.
It's just a sort of poll or curiousity question.
Would you agree to let java (by means of new api and jvm support of them, obviously) have lower level features?
Java VM works on every system, through native code, or better interfacing to a specific code of a specific Operating System.
That's why every os needs a dedicated vm.
Well, if that low level access is reached for operations like, drawing on the screen, playing sounds, io streams, networking, hidden memory management, and so on, what's the problem in giving java the possibility to do things like shutting down a system or formatting a unit (real formatting).
I know the latter is possible, in terms of file system manipulation.
But as for things like the first one? Every OS has a call which lets you shut it down.
Runtime.exec() is not cross-platform and it's not even always considered pure java.
JNI is not java (the part regarding native code).
What's the matter in having a System.shutdown()?
Or File.format(File root)?
Obviously such calls should be protected by a SecurityManager, as are other features in Java.
Java has a great API and you hardly feel the necessity for a closer contact with the hardware, but sometimes you do.
It'd get to be the most powerful, all-purposes, ultimate language.
Luckily, thanks to JNI and exec, you can find a way around most of those necessities, but it's not like the java I'd really like.
The 2 examples I've given are just the first things I could think of, but I'm sure many people would like to have other characteristics implemented.
Don't get me wrong.
I think Java is already the best all-purpose language around, and I really like it.
I like it so much I'd like I could do everything just using Java, no need for other external resources.
I just hope Sun will consider possibilities like those I mentioned.
So if you want to post your considerations, I'd really appreciate them, but please let's not start a flame out of it ^__^
Nobody criticized JAVA!!!

You seriously exepect the OS to let an application
tell it when to shut down? What happnes if you're
running this on some critical server thats running a
load of other apps?
I think you need to think your argument through a bit
more!I don't see any problem with that. Windows, Linux, MacOS,... native applications can easily shut the system down and nothing bad has ever happened...
As I said, that feature could be protected by security managing, meaning you need prehemptive user authorization.
Many native applications don't even let you authorize it.
Don't tell me you've never had a download manager or a cd-burner tool which had a check box like this : "Shut system down when operation is finished"...
So as you can see... it is accomplished regularily on every application. Java could easily be no exception.
I agrees to the idea but not the solution. instead I want to suggest > to have another package or development kit like j2me, j2ee for low
level hardware programming. Yes, why not. The problem though is not whether the APIs for that are standard or an expansion. The important thing should be the jvm accepting low level commands.
On SUN/OS (or Linux etc.) for example there is the shutdown command -
but it is available only with appropriate privileges, that is, for
the super user.YES, EXACTLY! On windows also, and probably on MacOS.
So, this is an example of low level feature available in every OS.
No portability issues in this one!
My guess why this does not yet exist is that either there are
technical difficulties (which you will probably discover when you
write the reference implementations), or there was no need for it yet
(which is a hint that it should better be an extension library
instead of part of the standard classes).I think the second one is the reason.
Probably there wouldn't be many tech diff. Java has much tougher features already there.
Very likely, Sun don't see specific low level access suitable in Java original conception.

Business logic in a Java Class

Hi,
In case of RPC web services why it is necessary to have a stateless
session bean ? can i have a simple java class instead ?
thanks and regards
Vedant

Hi Vedant,
WLS 6.1 does not currently support using POJOs (Plain Old Java Objects) as a service
implementation. I think the reasoning behind this was that WebLogic Web Services
where designed to "complement" Web Services technology, using "stateless" J2EE
components and J2EE packaging (i.e. war file, ear file). Seeing as the principle
network protocol for them (the web services' technologies) is HTTP, which is inturn
stateless ;-) There's also the factor that J2EE provides enterprise-level capabilities
(i.e. scalability, transactions, failover, clustering, etc.), that just aren't
there with a POJO. To me, this is a bit different than the approach being taken
with Java-based SOAP implementations, like Apache SOAP, that support using POJOs,
but don't take into consideration the "enterprise-level" aspects (or architectual
needs/best practices) for Web Services. If you think about the following requirements
for a given SOAP service, you'll see how using "lightweight" J2EE components has
merit 1) will be called thousands of times per second, and 2) must have <3 sec
avg response time, and 3) must have 99.9% uptime/availablity, and 3) must transparently
failover to another instance of the SOAP service on failure.
Regards,
Mike Wooten
"Vedant" <[email protected]> wrote:
Hi,
In case of RPC web services why it is necessary to have a stateless
session bean ? can i have a simple java class instead ?
thanks and regards
Vedant

OC4J Log Error Interpretation

Hi, I am trying to debug an authentication issue using a system based on the information in this article: http://www.oracle.com/technology/products/jdev/howtos/1013/oc4jjaas/oc4j_jaas_login_module.htm
IE database/datasource based authentication.
I am getting the following error in the applications OC4J log every time a login attempt is made, no error is seen from the application, authentication simply fails.
When I had the recommended code for fine logging in the j2ee-loggin.xml file (<logger name="oracle.j2ee.security.oc4j" level="FINE" useParentHandlers="false">
<handler name="oc4j-handler"/>
<handler name="console-handler"/>
</logger>) there was no information at all recorded in the OC4J log, not until I removed the extra logger code from that file did entries such as the following begin appearing in the log file. What could be going wrong here? Why is the login process generating a null pointer error and why would the log file not be written too when the fine logging code was added to the config file? Any idea's? All I can really gain from this error message is that the DBTableOraDataSourceLoginModule is at some stage atleast being referenced or called.
Log Message: September 3, 2007 10:59:51 AM EST
Component Name OC4J Component ID j2ee
Host Network Address 172.etc Message Level 1
Module ID security User ID SYSTEM
Execution Context ID 172.etc Execution Context Sequence 0
Host Name usatl01 Thread ID 12
Message Type Warning
Message Text
java.lang.NullPointerException
at javax.naming.InitialContext.getURLScheme(InitialContext.java:228)
at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:277)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at oracle.security.jazn.login.module.db.DBTableOraDataSourceLoginModule.performDbAuthentication(DBTableOraDataSourceLoginModule.java:484)
at oracle.security.jazn.login.module.db.DBTableOraDataSourceLoginModule.login(DBTableOraDataSourceLoginModule.java:335)
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:585)
at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
at javax.security.auth.login.LoginContext.login(LoginContext.java:579)
at oracle.security.jazn.oc4j.OC4JUtil.doJAASLogin(OC4JUtil.java:241)
at oracle.security.jazn.oc4j.GenericUser$1.run(JAZNUserManager.java:818)
at oracle.security.jazn.oc4j.OC4JUtil.doWithJAZNClsLdr(OC4JUtil.java:173)
at oracle.security.jazn.oc4j.GenericUser.authenticate(JAZNUserManager.java:814)
at oracle.security.jazn.oc4j.FilterUser.authenticate(JAZNUserManager.java:1143)
at com.evermind.server.http.EvermindHttpServletRequest.getUserPrincipalInternal(EvermindHttpServletRequest.java:3601)
at com.evermind.server.http.AJPHttpServletRequest.getUserPrincipalInternal(AJPHttpServletRequest.java:261)
at com.evermind.server.http.HttpApplication.checkAuthenticationAndAuthorize(HttpApplication.java:6332)
at com.evermind.server.http.HttpApplication.getRequestDispatcher(HttpApplication.java:3009)
at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:736)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:302)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:190)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:595)
Supplemental Text
javax.security.auth.login.LoginException: java.lang.NullPointerException
at javax.naming.InitialContext.getURLScheme(InitialContext.java:228)
at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:277)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at oracle.security.jazn.login.module.db.DBTableOraDataSourceLoginModule.performDbAuthentication(DBTableOraDataSourceLoginModule.java:484)
at oracle.security.jazn.login.module.db.DBTableOraDataSourceLoginModule.login(DBTableOraDataSourceLoginModule.java:335)
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:585)
at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
at javax.security.auth.login.LoginContext.login(LoginContext.java:579)
at oracle.security.jazn.oc4j.OC4JUtil.doJAASLogin(OC4JUtil.java:241)
at oracle.security.jazn.oc4j.GenericUser$1.run(JAZNUserManager.java:818)
at oracle.security.jazn.oc4j.OC4JUtil.doWithJAZNClsLdr(OC4JUtil.java:173)
at oracle.security.jazn.oc4j.GenericUser.authenticate(JAZNUserManager.java:814)
at oracle.security.jazn.oc4j.FilterUser.authenticate(JAZNUserManager.java:1143)
at com.evermind.server.http.EvermindHttpServletRequest.getUserPrincipalInternal(EvermindHttpServletRequest.java:3601)
at com.evermind.server.http.AJPHttpServletRequest.getUserPrincipalInternal(AJPHttpServletRequest.java:261)
at com.evermind.server.http.HttpApplication.checkAuthenticationAndAuthorize(HttpApplication.java:6332)
at com.evermind.server.http.HttpApplication.getRequestDispatcher(HttpApplication.java:3009)
at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:736)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:302)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:190)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:595)
at javax.security.auth.login.LoginContext.invoke(LoginContext.java:872)
at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
at javax.security.auth.login.LoginContext.login(LoginContext.java:579)
at oracle.security.jazn.oc4j.OC4JUtil.doJAASLogin(OC4JUtil.java:241)
at oracle.security.jazn.oc4j.GenericUser$1.run(JAZNUserManager.java:818)
at oracle.security.jazn.oc4j.OC4JUtil.doWithJAZNClsLdr(OC4JUtil.java:173)
at oracle.security.jazn.oc4j.GenericUser.authenticate(JAZNUserManager.java:814)
at oracle.security.jazn.oc4j.FilterUser.authenticate(JAZNUserManager.java:1143)
at com.evermind.server.http.EvermindHttpServletRequest.getUserPrincipalInternal(EvermindHttpServletRequest.java:3601)
at com.evermind.server.http.AJPHttpServletRequest.getUserPrincipalInternal(AJPHttpServletRequest.java:261)
at com.evermind.server.http.HttpApplication.checkAuthenticationAndAuthorize(HttpApplication.java:6332)
at com.evermind.server.http.HttpApplication.getRequestDispatcher(HttpApplication.java:3009)
at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:736)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:302)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:190)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:595)

Well, still struggling with this one.. although i've managed to get fine oc4j security logging enabled through the console, the error stream now follows this sequence of events at each login attempt :
[DBTableOraDataSourceLoginModule]login called on DBTableLoginModule
[DBTableOraDataSourceLoginModule]Calling callbackhandler ...
[DBTableOraDataSourceLoginModule]Username returned by callback = TATKINS
[DBTableOraDataSourceLoginModule]Username changed to case as defined by null to TATKINS
[DBTableOraDataSourceLoginModule]Abort called on LoginModule
java.lang.NullPointerException
at javax.naming.InitialContext.getURLScheme(InitialContext.java:228)
at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:277)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at oracle.security.jazn.login.module.db.DBTableOraDataSourceLoginModule.performDbAuthentication(DBTableOraDataSourceLoginModule.java:484)
at oracle.security.jazn.login.module.db.DBTableOraDataSourceLoginModule.login(DBTableOraDataSourceLoginModule.java:335)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
etc etc...
JAAS-OC4J: Authentication failure for user: TATKINS
JAAS-OC4J: Membership check for group: USER failed for user: anonymous
What i cant work out is what is causing the login module to abort and raise a null pointer exception. Could this be due to a configuration mistake in the console manager or one of the xml files prior to deployment? I just have no idea how to approach fixing this issue.
I really would appreciate some assistance, 5+ days trying to get this working. I had this working on jdeveloper embedded oc4j, and all the tute's on standalone deployment pass off the configuration of standalone as simple compared to embedded, yet don't go into enough detail to get it working, atleast from my perspective.

Interactive Forms - Context error

Friends,
I am working on an Adobe Interactive form using ABAP Web Dynpro (WDA).
I am encountering errors in the display. I have created a form of ZCI layout type. I have set the displayType to "native" and checked the "enabled" property in the InteractiveForm property in the WDA view.
When i execute the Web Dynpro application in the browser, the fields are in display only mode and are not interactive.
I have not created any attributes in the context.
My question is - does Context creation got to do anything with this error. If not, what else could be the reason.
I am new to Adobe Interactive Forms using ABAP Dynpro.
Please help.
Thanks and Regards.

Hi
Could you send me screenshots of your stuff. Also could you check whether the ADSSAP SP level = J2EE Engine SP level. I dont think that cardinality would affect whether a form is interactive or not. The screenshot with the context node that i sent you was the default cardinality you get when creating a node. Also if you have Active Components Framework installed on your pc then try deleting it. How are you creating the form? are you going into SFP first and then in WDA calling the form or are you using forward navigation in WDA to do it. I used forward navigation for the example screenshots.
Regards
Thashin

Technical system creation problem in SLD

hi
while i'm traying to create a technical system for Web As ABAP(ERP 2004 ECC 5.0) in SLD when I serch for Installed product no product with ECC 5.0 is found.
is there somthing missing ?
regards,
kinjal

HI kinjal
i think UR J2EE server patch level is SP9.
do u read the SLD configuration document carefully?
look at sap note 669669. and import the CR Content according to that. this solves ur issue.
regards,
kaushal

AdobeDocumentServer: Processing exception -- IisProxy

I am getting the following error when I try to render the OnlineInteractiveFormApp tutorial from our IISProxy url (http://iisproxyserver/webdynpro/dispatcher/local/TutWD_OnlineInteractiveForm/OnlineInteractiveFormApp):
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Error during call to AdobeDocumentServer: Processing exception during a "Render" operation.
Request start time: Tue Jan 23 07:46:19 EST 2007
com.adobe.ProcessingError: File not found error writing stream: <Render><Template><Name> "http://iisproxyserver:80/webdynpro/dispatcher/local/TutWD_OnlineInteractiveForm/OnlineInteractiveFormApp/wd_keyh56riy3saTWY7P6Du9c1EA==/sapwebdynpro.xft;jsessionid=(J2EE25797100)ID1136316750DB11302122638220973520End;saplb_*=(J2EE25797100)25797150?sap.session.download=4&sap-wd-cltwndid=b8f0cf60aadf11dbcdc30050568e3487&sap-wd-appwndid=Idb8f0cf60aadf11dbcdc30050568e348771&sap-wd-norefresh=true :
java.io.FileNotFoundException: IO error detected while opening HTTP/HTTPS connection: http://iisproxyserver:80/webdynpro/dispatcher/local/TutWD_OnlineInteractiveForm/OnlineInteractiveFormApp/wd_keyh56riy3saTWY7P6Du9c1EA==/sapwebdynpro.xft;jsessionid=(J2EE25797100)ID1136316750DB11302122638220973520End;saplb_*=(J2EE25797100)25797150?sap.session.download=4&sap-wd-cltwndid=b8f0cf60aadf11dbcdc30050568e3487&sap-wd-appwndid=Idb8f0cf60aadf11dbcdc30050568e348771&sap-wd-norefresh=true :
java.net.ConnectException: Connection timed out: connect
Exception Stack Trace:
com.adobe.ProcessingError: File not found error writing stream: <Render><Template><Name> "http://iisproxyserver:80/webdynpro/dispatcher/local/TutWD_OnlineInteractiveForm/OnlineInteractiveFormApp/wd_keyh56riy3saTWY7P6Du9c1EA==/sapwebdynpro.xft;jsessionid=(J2EE25797100)ID1136316750DB11302122638220973520End;saplb_*=(J2EE25797100)25797150?sap.session.download=4&sap-wd-cltwndid=b8f0cf60aadf11dbcdc30050568e3487&sap-wd-appwndid=Idb8f0cf60aadf11dbcdc30050568e348771&sap-wd-norefresh=true :
java.io.FileNotFoundException: IO error detected while opening HTTP/HTTPS connection: http://iisproxyserver:80/webdynpro/dispatcher/local/TutWD_OnlineInteractiveForm/OnlineInteractiveFormApp/wd_keyh56riy3saTWY7P6Du9c1EA==/sapwebdynpro.xft;jsessionid=(J2EE25797100)ID1136316750DB11302122638220973520End;saplb_*=(J2EE25797100)25797150?sap.session.download=4&sap-wd-cltwndid=b8f0cf60aadf11dbcdc30050568e3487&sap-wd-appwndid=Idb8f0cf60aadf11dbcdc30050568e348771&sap-wd-norefresh=true :
java.net.ConnectException: Connection timed out: connect
at com.adobe.Render.execute(Unknown Source)
When I call the application directly by going to the actual server and port (http://myserver:50000/webdynpro/dispatcher/local/TutWD_OnlineInteractiveForm/OnlineInteractiveFormApp), the application runs correctly without any exceptions.
In the above error, it appears to be adding port 80 to the url which means the iisproxy will not send it onto the correct target. Why is it doing that? Is there a configuration setting that will correct it?

This is the response I received from submitting an OSS message:
Please check the following:
Visual Admin -> server -> configuration adapter
-> webdynpro -> sap.com -> tcwddispwda -> Propertysheet.defualt
sap.ADSCallingMode
change from 'http' to 'SOAP'
After this change, please restart J2EE engine.
If you change this option, reuslt PDF will be passed by Stream, not
using WD resouce URL.
Also make sure the J2EE engine patch level is the same as the ADS
patch level.
Please also make sure the XMLForm module is started in the
Visual Administrator.

PDF Document Creation Error

Hi All,
In one of my webdynpor applications i need to render one PDF document but while i am trying to do the same I am getting this error .
com.sap.tc.webdynpro.services.exceptions.PDFDocumentCreationException: ../../asianpaints.com/hs_rework_wd/ReworkApplication/~wd_key_80eZ1tsPlvcfxodN/ErrorPDF.pdf?sap-wd-download=1&sap-wd-dl_behaviour=1&sap-wd-cltwndid=b8b061b0906411de8a690050569630a5&sap-wd-appwndid=b8b061b1906411deb5a40050569630a5&sap-wd-norefresh=X
    at com.sap.tc.webdynpro.clientserver.uielib.adobe.impl.InteractiveForm.afterHandleActionEvent(InteractiveForm.java:624)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.afterApplicationModification(ClientApplication.java:972)
    at com.sap.tc.webdynpro.clientserver.phases.RespondPhase.execute(RespondPhase.java:60)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:161)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:109)
in the back end or default trace, the message displayed is
com.adobe.ProcessingException: Failed to connect to a <Render> XML Form Module.
Please ensure that the XML Form Module service is running.
I suppose, there is some service with the name "XML Form Module service " and its not running .
Can any one help me with the ways to run this service ?? or any other suggestion about why the error would be coming
thanks in advance

Smriti,
Did you upload a valid credential into the Visual admin? Also check that your ADSSAP SP level is the same as your J2EE Engine SP level.
You can restart the XML Form Module service as follows (if I am not wring) :-.
1.     Logon to Visual Admin
2.     On the Cluster tab, choose server -> Services -> XML Form Module
3.     Right click and stop the service.
4.     Once stopped, right click and start the service
Chintan

Instant Messaging - EP 6.0.2.3.7

I have installed:
EP 6.0 Service pack 2 Patch level 3 Hotfix 7 (6.0.2.3.7)
WebAS 6.20
J2EE Engine patch level 25
On the following system:
Microsoft Windows 2000 Service pack 3
Pentium III 1400 Mhz
2 Gb RAM
During the installation I faced no error messages and the implementation runs without error logs. Unfortunately, the instant messaging does not work. I see the CLP, but the "auto-detect status" is malfunctioning. Online users are shown as offline. Trying to send an instant message there is happening nothing. I did the configurations for the instant messaging as described at help.sap.com:
1) Displaying the Collaboration Link in the Portal Header Area: OK
2) Configuring Collaboration Services in Collaboration Launch Pad: OK
3) Activating the RTC Session Manager: OK
4) Configure the Groupware Framework: Is Not Used and therefore not configured
5) Configure the Synchronous Collaboration Framework: OK
6) Configure Real-Time Collaboration:
ApplicationSharing_ServerName = myhost
ApplicationSharing_ServerPath = streamingserver/servlet/streamingserver
ApplicationSharing_ServerPort = 50000
ApplicationSharing_ServerSecureMode = 1
ApplicationSharing_Version = 1729
When I call the "myhost:50000/streamingserver/servlet/streamingserver" address I get the following output:
URL : /streamingserver/servlet/streamingserver
Server protocol : HTTP/1.1
Server version : 1729
Registered sessions: 0
Do you have an idea what is wrong?
Thank you!

Did you happen to upgrade J2EE from PL < 19 to PL 19? If so, you may have a problem with the JMS. SAP note 716716 addresses this problem.
Regards,
Kyle

How to determine 640/J2EE Startup Framework Binary Patch Level?

Hi All,
We are running BI ABAP with Java Add-in on WAS 640/SUSE/Oracle.
In the ABAP world, there are many options for determining the current kernel patch level. Disp+work -v, SYSTEM->STATUS, etc..
How do I determine the patch level of the J2EE startup framework (ie: jlaunch, jcontrol, etc..)? If I run these commands with '-version', I get a patch level of 0. From System Information, the Cluster Kernel Version is 6.40 PatchLevel 105424.313.
What I am trying to determine is if I have the binaries that map to the latest applied SP (18). Do I need to download J2EERTOS18.SAR and apply the bits or has that already been done? Or is the current patch level for the bits fro the J2EERTOS14.SAR file? Etc...
Any tips/suggestions?
Thanks much,
Greg

Hi
You can check the patch number like this;
D:\usr\sap\FT0\SYS\exe\uc\NTI386>jlaunch -version
Failed to reserve 1610612736 (0x60000000) bytes before loading DLLs (error 8).
jlaunch information
kernel release                700
kernel make variant           700_REL
compiled on                   NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10
compilation mode              UNICODE
compile time                  Jan 23 2008 20:42:28
update level                  0
patch number                  128                         <<< Here is the patch number>>
source id                     0.144
While regarding which file(s) to apply, please notice that the files you are not talking like
J2EERTOS16_1, is part of the J2EE support package stack, which can be applied with JSPM.
Regarding the kernel, you can alway refer to note 19466, and downlaod the lastest kernel from:
http://service.sap.com/swdc
   Support Packages and Patches ->
   Entry by Application Group "
   SAP NetWeaver and complementary products"
   SAP NETWEAVER" SAP NETWEAVER 7.0"
   Entry by Component"
   Application Server Java
   ===> SAP KERNEL 7.00 64-BIT UNICODE
Regards,
Thunder

EJB Isolation levels in ejb-j2ee-engine.xml

Can anyone explain to me why I only seem to have the option of using the 'repeatable read' isolation level in Netweaver Developer Studio?
I'm new to SAP and Netweaver but as a seasoned J2EE developer I would have expected to find read committed, read uncommitted, serializable, as well as repeatable read.
Is there some SAP or Netweaver specific reason why I don't get to choose these options, or do I need to enable them by configuring properties somewhere?

Hi Steve,
The reason is that the J2EE Engine EJB Container supports Read Committed and Repeatable Read isolation levels and Read Committed is the default one. That's why you only have the option of specifying Repeatable Read.
For more information on locking and isolation levels please have a look at these documents:
http://help.sap.com/saphelp_nw04/helpdata/en/37/019b3e25f95f14e10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/a1/d81db94a10bc4b83b3f60b0e3037e7/frameset.htm
Best regards,
Vladimir

How to determine J2EE patch level

If I go to the CMD prompt running the Dispatcher, I can enter "version" and the > prompt and get the following:
SAP J2EE Engine Version 6.20 PatchLevel 78993.20
How does this patch level translate to patch levels 6 throuch 32 on service.sap.com/patches?
Thanks in advance.

Hi Gary,
you can mark your question as self solved to show other users that this toppic has been solved.
Regards
Gregor

Par application - Trace level=all after j2ee restart

Hello,
I'm not sure that is the right place to post this question so, don't hesitate to root me to another thread.
We use the SAP Enterprise Portal EP6 base on NW2004 SPS16.
We have developped some Portal Application. (par). Those applications contain a logger.xml file to describe the trace settings.
In visual Admin\Log configurator, we define the trace level to "Error" for those applications nodes. But, after application deployment, or after j2ee engine restart, the trace level level is automaticaly set to "All". It only appens to our applications and not to other WAS traces.
I think problem is due to the logger.xml but, after lookup on a lot of thread, it seems we use it in the good way.
<u>eg:</u>
<Server>
<Logger       name="corp.mycompany.application.myApplicationName.logger"
              loggerInterface="com.sapportals.portal.prt.logger.ILogger"
              locationName="corp.mycompany.application.myApplicationName"
              pattern="%d # %20t %15s %m #"
                   isActive="true">
     <LoggerClass className="com.sapportals.portal.prt.logger.SimpleFileLogger" level="Error">
     </LoggerClass>
</Logger>
</Server>
Did we miss something ? Do we manage our traces in thge good way ?
Please advice.
Thanks for your support
Laurent

Laurent,
Do have a look at this<a href="https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1794">weblog</a>
check this
<a href="https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5f04b290-0201-0010-1387-d2df53065422">pdf</a>
<a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/e2/75a74046033913e10000000a155106/frameset.htm">Active Tracing</a>
Are all the configurations nd settings done are accordingly?
Thanks,
Swathi

How to find out SAP J2EE Patch Level for 04s

Hi all
I want to find out SAP J2EE Patch Level for 2004s installation i tried to get information from SYSTEM INFORMATION link on WAS homepage but it gave only version :7.00 details and PATCH LEVEL was not mentioned .
I also tried to find out by looking into VERSION.TXT file for server & dispatcher in ....USR\SAP\J2E.....engine installation but again no details about PatchLevel was mentioned can anyone provide some information regarding what is the PatchLevel for WAS 7.0 , J2SE used is 1.4.2_09
Thanks in Advance !!
Asif

Thanks Kenny ,
But as you can see from version.txt file for Server0 it does not mention PatchLevel it is
blank
Specifies the version of the system
Cluster-Version: 7.00 PatchLevel
Build-On:Thursday, March 23, 2006 18:47 GMT
Perforce-Server:
Project-Dir:JKernel/645_VAL_REL
JKernel Change-List:102557
Build machine:SAPInternal
Build java version:1.3.1_12-b03 Sun Microsystems Inc.
SP-Number: 07
Source-Dir: D:\make\engine\645_VAL_REL\builds\JKernel\645_VAL_REL\archive\dbg
i also checked version.txt for dispatcher it is as below
Specifies the version of the system
Cluster-Version: 7.00 PatchLevel
Build-On:Thursday, March 23, 2006 18:47 GMT
Perforce-Server:
Project-Dir:JKernel/645_VAL_REL
JKernel Change-List:102557
Build machine:SAPInternal
Build java version:1.3.1_12-b03 Sun Microsystems Inc.
SP-Number: 07
Source-Dir: D:\make\engine\645_VAL_REL\builds\JKernel\645_VAL_REL\archive\dbg
I tried this on different 2004s server but the Patch Level is not mentioned whereas for 2004
servers it is mentioned
so can u give some inference based on above descriptions about What should be SAP J2EE Patch
Level for the 2004s servers
Regards !!
Asif

J2EE at Os level...

Similar Messages

Maybe you are looking for