on 05-06-2008 1:24 AM
I realize this topic has been brought up in multiple threads, however my symptoms seem to be a bit different.
If I select 'Generate Documentation' from the transaction menu, I am prompted for the destination, which I direct toward the appropriate web/project directory. I click 'OK' and all seems fine, except that the .pdf file never shows up in the directory.
In the Netweaver logs I see the following:
com.sap.security.core.server.vsi.api.exception.VSIServiceException: No default virus scan profile available.
at com.sap.security.core.server.vsi.service.VSIServiceImpl.getInstance(VSIServiceImpl.java:173)
at com.sap.xmii.Illuminator.util.VirusScanner.scan(VirusScanner.java:54)
at com.sap.xmii.Illuminator.util.VirusScanner.scan(VirusScanner.java:101)
at com.sap.xmii.Illuminator.content.ContentManager.update(ContentManager.java:167)
at com.sap.xmii.Illuminator.content.ContentManager.save(ContentManager.java:196)
at com.sap.xmii.servlet.Catalog.doSave(Catalog.java:883)
at com.sap.xmii.servlet.Catalog.handleSaveBinary(Catalog.java:833)
at com.sap.xmii.servlet.Catalog.service(Catalog.java:116)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:117)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:62)
at com.sap.xmii.system.SecurityFilter.doFilter(SecurityFilter.java:100)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:58)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:384)
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)
I have PDF Actions installed as per SAP note 1109054. iText.jar 1.4.5 etc...
My server is running JRE 1.4.2_16 and Netweaver 2004s Java AS SP13.
All appears well with the PDF actions in BLS, however I am not doing any development with them at this point so I couldn't say for sure. I have checked to be sure the objects can be configured.
Regards,
Rod Hoffman
Hi Rod,
Are you using web:// for addressing the correct folder? Make sure you do not include the WEB folder in the path or use db:// instead (my preference as you use the full path instead of dropping WEB). Also remember that the path is case sensitive.
Not sure if this will help as I have not tried the generate documentation feature in 12.0.2 yet.
Good luck,
Mike
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In my experience it should work with the default path.
In your case the path essentially means generate documentation for the transaction txnGetLeadTimeForFamily existing in the project azXMII under the folders AZ/LeanSC/LeadTime.Correct?
The default path is usually displayed as
azXMII/WEB/AZ/LeanSC/LeadTime/txnGetLeadTimeForFamily_1.pdf, where the_1 is the version of the document. As soon as you say OK a browser pops up displaying the generated doc and you probably are not experiencing this behavior.
I would suggest first verify completely if the PDF Actions deployment is successful by using the Actions and creating a simple pdf doc.
User | Count |
---|---|
8 | |
7 | |
3 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.