Sharing Adobe Document Services Instance

Hello
Our organization has multiple SAP System Landscapes.
I would like to know if ADS can be shared with multiple SAP Systems.
Please advise if there are any Pros and Cons with sharing ADS.
Thanks
Jay

Hi Jay,
We have one ADS instance installed on the Portal server that is also used by our CRM system. Make sure to take this into account when performing your hardware sizing exercise. One CON is the dependency of applications (if the portal goes down it will also effects the Adobe forms in CRM).
Hope this helps,
Harman

Similar Messages

Adobe Document Services Architecture NW04s

All,
I am working at a customer that will be using Adobe Document Services for interactive forms.
The customer has several existing SAP applications but for this project it was recommended to configure the ADS on the SRM server (java stack is required)
What I need to know is the best practice architecture for the customers current needs as well as if they intend to expand its use in the future.
A)Should they have a centralized ADS server?
B) Should they have an ADS on each landscape? ie: one for CRM, one for SRM, one for ERP, in Dev/TST and QA
C)Can they have an ADS on their SRM server and share it with their ERP or other servers? ie: If they want to use ESS/MSS in the future
Any suggestions would be appreciated,

Interesting question, frequently faced in large companies.
The ADS can be shared between various SAP systems, (question c: yes).
So typically the same ADS server can be used for DEV and QAS environments, and one special for productive purposes (questions a, b, c).
Recommandation from SAP side is that the ADS should have the same SPS level as the other components (ABAP or Java) with of course same SP level for all the components for the J2EE engine where the ADS is running.
This the way the newly created forms are tested by SAP (questions a, b, c).
Knowing this, to have a central ADS instance is in practice quite difficult to achieve, so the answer depends on the architecture (number of servers, upgrades plannings etc.)
Keep in mind the sizing of the ADS: your architecture will also then depend of the usage of the ADS by the various SAP systems (questions a, b, c).
Hope this helps,
Best regards,
Francois

Add Subform dynamically,on click of Button, in Interactive form generated by Adobe Document Services

HI,
I have an XDP file designed by Adobe Designer 7.1 with the following hierarchy of elements:
-form1(root)
--Button
--tmpForm (subform - Repeat subform for each data entry )
---ST (Text)
Now, this XDP file generates an Interactive PDF form with Reader Rights enabled by the Adobe Document Services.
On click of button, the following javascript is executed on client side:
var df = _tmpForm.addInstance(1);
df.ST.rawValue = "HI" ;
xfa.host.messageBox( "Instances" + tmpForm.all.length ) ;
On clicking the button, i get the length of the instances of the subform and the size increases on each click, but no element is added "visibly" to the pdf.
But when i try to do the same by saving the XDP file as Dynamic PDF form for Acrobat 8.0,and open it using Adobe Acrobat PRO 8.0, it works fine.
My question is,I s it not possible to add subforms dynamically in PDF's generated by Adobe Document Services with Reader Rights enabled?
Or, is there something that i am missing?
Please guide.
Thanks.
Regards,
Siddhartha

Hi,
you can't change the behavior of the save button in the browser nor in Reader/Acrobat.
You can add a custom button within your form which calls a custom script from a folder level script using the browserForDoc method.
The browseForDoc methos is the only one whcih can change the name in the saveAs dialog.
Here's an example., you can run from Acrobat console.
You need to combine it with the solution from the other thread to make it work with your form.
http://forums.adobe.com/message/2266799#2266799%232266799
var oRetn = app.browseForDoc({
    bSave: true,
    cFilenameInit: "MyForm.pdf",
    cFSInit: "",
if (typeof oRetn !== "undefined") {
    this.saveAs({
        cFS: oRetn.cFS,
        cPath: oRetn.cPath,
        bPromptToOverwrite: false

Adobe Document Services Configuration

Hi Experts,
ERP2004 SP17, EP 6.0 SP20, AS Java 6.40 (web dynpr runtime), As Java 7.0 (for ADS).
I am running ADS on one server (NW 7.0) and web dynpro runtime on server (AS Java 6.40). We are using central SLD. ADS on 64 bit lunux systems is not supported if AS Java 6.40 is installed. I also have followed the note; 925741 Adobe DOcument Service with non supported platforms.
I am trying to configure ADS using the configuration guide for ADS for NW2004. I published the ADS to SLD.
I went to http://<host>.<company.com>:50000/AdobeDocumentServices/Config
and gave ADSUSER/Password,
I get the following response.
RESPONE 1:
HTTP/1.1 200 OK
Connection: close
Set-Cookie: <value is hidden>
Set-Cookie: <value is hidden>
Server: SAP J2EE Engine/7.00
Content-Type: text/xml; charset=UTF-8
Date: Tue, 13 Nov 2007 23:24:25 GMT
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" ><SOAP-ENV:Body><rpl:rpDataResponse xmlns:rpl='urn:AdobeDocumentServicesVi'><rpl:Response xmlns:pns='urn:com.adobe'><pns:rpStrings><pns:RpString><pns:name>Error_Level</pns:name><pns:value>0</pns:value></pns:RpString><pns:RpString><pns:name>Results</pns:name><pns:value>
Required stream: "PDFDocument" not found in request OR its length is zero.</pns:value></pns:RpString><pns:RpString><pns:name>VersionInfo</pns:name><pns:value>710.20061024154505.342190</pns:value></pns:RpString></pns:rpStrings></rpl:Response></rpl:rpDataResponse></SOAP-ENV:Body></SOAP-ENV:Envelope
The document says it should bring the version of the ADS. I got a tree like response in which i see an element which shows the version: 710.20061024154505.342190
I can not execute PCRs that come with MSS business packages. I am getting an error like this below.
ERROR 1:
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Error during call to AdobeDocumentServer: Processing exception during a "Render" operation. Request start time: Tue Nov 13 14:06:46 MST 2007 com.adobe.ProcessingError: Template used in PDF render operation is invalid or cannot be found: url Reason code: http://<host>.<company.com>:50000/webdynpro/dispatcher/sap.com/msspcr/PcrApplication/wd_key56_1194988006244/unknown.pdf;jsessionid=(sapxid_XID_00)ID0612781050DB00927636819783032031End;saplb_=(J2EE1929400)1929450?sap.session.download=4&sap-wd-cltwndid=WID1194974867468&sap-wd-appwndid=kPtnj2P7jeiICdSg1OjikA%3D%3DVFdWFji1I83YX1%2FltSqVHw%3D%3D&sap-wd-norefresh=true - Unable to load dynamic library libcurl.so; [Error Log file "2007.11.13.140646PcrApplicationmss01.pdf" written to /usr/sap/XID/SYS/global/AdobeDocumentServices/renderErrorLog/errorFiles] Exception Stack Trace: com.adobe.ProcessingError: Template used in PDF render operation is invalid or cannot be found: url Reason code: http://<host>.<company.com>:50000/webdynpro/dispatcher/sap.com/msspcr/PcrApplication/wd_key56_1194988006244/unknown.pdf;jsessionid=(sapxid_XID_00)ID0612781050DB00927636819783032031End;saplb_=(J2EE1929400)1929450?sap.session.download=4&sap-wd-cltwndid=WID1194974867468&sap-wd-appwndid=kPtnj2P7jeiICdSg1OjikA%3D%3DVFdWFji1I83YX1%2FltSqVHw%3D%3D&sap-wd-norefresh=true - Unable to load dynamic library libcurl.so at com.adobe.ads.request.RemoteRenderer.renderAllRemote(Unknown Source) at com.adobe.ads.request.RemoteRenderer.renderAll(Unknown Source) at com.adobe.ads.request.RemoteRenderer.renderAll(Unknown Source) at com.adobe.ads.request.Renderer.renderDatalessPdf(Unknown Source) at com.adobe.ads.request.Renderer.renderSpecialPdf(Unknown Source) at com.adobe.ads.request.Renderer.renderWithCache(Unknown Source) at com.adobe.ads.request.Renderer.execute(Unknown Source) at com.adobe.BaseADSRequest.doWork(Unknown Source) at com.adobe.AdobeDocumentServicesWorker.processRender(Unknown Source) at com.adobe.AdobeDocumentServicesWorker.execute(Unknown Source) at com.adobe.AdobeDocumentServicesEJB.processRequest(Unknown Source) at com.adobe.AdobeDocumentServicesEJB.rpData(Unknown Source) at com.adobe.AdobeDocumentServicesLocalLocalObjectImpl0_0.rpData(AdobeDocumentServicesLocalLocalObjectImpl0_0.java:120) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60) at java.lang.reflect.Method.invoke(Method.java:391) at com.sap.engine.services.webservices.runtime.EJBImplementationContainer.invokeMethod(EJBImplementationContainer.java:126) at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:157) at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:79) at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:92) at SoapServlet.doPost(SoapServlet.java:51) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) 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(AccessController.java:207) 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.adobe.document.xmlform.InvalidTemplateException: IDL:com/adobe/document/xmlform/InvalidTemplateException:1.0 at com.adobe.document.xmlform.InvalidTemplateExceptionHelper.read(Unknown Source) at com.adobe.document.xmlform._FormFactoryStub.renderAll(Unknown Source) at com.adobe.ads.request.RemoteRenderer.renderAllRemote(Unknown Source) at com.adobe.ads.request.RemoteRenderer.renderAll(Unknown Source) at com.adobe.ads.request.RemoteRenderer.renderAll(Unknown Source) at com.adobe.ads.request.Renderer.renderDatalessPdf(Unknown Source) at com.adobe.ads.request.Renderer.renderSpecialPdf(Unknown Source) at com.adobe.ads.request.Renderer.renderWithCache(Unknown Source) at com.adobe.ads.request.Renderer.execute(Unknown Source) at com.adobe.BaseADSRequest.doWork(Unknown Source) at com.adobe.AdobeDocumentServicesWorker.processRender(Unknown Source) at com.adobe.AdobeDocumentServicesWorker.execute(Unknown Source) at com.adobe.AdobeDocumentServicesEJB.processRequest(Unknown Source) at com.adobe.AdobeDocumentServicesEJB.rpData(Unknown Source) at com.adobe.AdobeDocumentServicesLocalLocalObjectImpl0_0.rpData(AdobeDocumentServicesLocalLocalObjectImpl0_0.java:120) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60) at java.lang.reflect.Method.invoke(Method.java:391) at com.sap.engine.services.webservices.runtime.EJBImplementationContainer.invokeMethod(EJBImplementationContainer.java:126) at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:157) at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:79) at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:92) at SoapServlet.doPost(SoapServlet.java:51) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) 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(AccessController.java:207) 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 do not know RESPONSE 1 is causing ERROR 1 on portal.
I did not yet install adobe reader credentials.
any ideas why I am seeing the error on portal?

One more observation I have made is:
a HTTP destination is created on AS Java 6.40 as part of the configuration.
5.3 Creating a Destination of the Destination Service in the Java EnvironmentIf you use print forms you have to create the destination service on the server where the Adobe document services are installed. If you use forms in ISR scenarios, for example in the Business Package MSS, you have to create the destination service on the J2EE engine that hosts Web Dynpro.To create the new destination, proceed as follows:
1. Log on to the Visual Administrator. See How to Start the Visual Administrator [on page 48].
2. On the Cluster tab, choose Server <x> → Services → Destinations. Under Runtime, select HTTP. The available destinations are displayed. The information that applies to a selected destination is displayed in the right pane.
3. Choose New in the navigation panel.
4. In the dialog box that follows, enter the name FP_ICF_DATA for the new destination and choose OK.
5. Under Connection Settings enter the message server (or Web Dispatcher) of the SAP Web AS ABAP in the URL field:
http://<hostname>:<HTTP_port>
and in case of SSL,
https://<hostname>:<HTTPS_port> To display the host name of your SAP Web AS ABAP log on to SAP Web AS ABAP and call transaction SICF. In the main menu, choose Goto → Port Information. The information is displayed on a screen; where the HTTP_port is specified under Services.
6. Enter the client number of the system where the user ADS_AGENT exists in the field client. Keep the other fields System ID and Language empty.
7. Select the authentication method to use for the connection, and enter the parameters for the authentication method in the corresponding fields (if applicable).
In the Username field enter ADS_AGENT (must exist as service user in SAP Web AS ABAP)
In the Password field enter the same password as given for SAP Web AS ABAP service user ADS_AGENT.
See Creating a Service User in the ABAP Environment [on page 32].
8. If the connection is to use HTTPS, then specify how the connection should handle SSL server authentication.
9. Save the data.
After this configuration, I picked the button SAVE and TEST,
the system throws an error:
Error during ping operation, Received HTTP response 404

Adobe Document Services - NetWeaver 7.3 - Windows Azure

Hello,
Does SAP support running Adobe Document Services on Microsoft Azure? I am planning to migrate my in-premise ADS JAVA instance to Microsoft Cloud Machine, and looking for guidance, if SAP supports this and if there are SAPNotes around this.
Thanks
Sandeep

Hello RB,
The problem is in these report,
FP_PDF_TEST_00
FP_TEST_IA_01
FP_CHECK_DESTINATION_SERVICE & FP_CHECK_HTTP_DATA_TRANSFER
without check
with check
The password in ABAP user and Java is the same.
Thanks for your support.

Adobe Document Services landscape question

Hello,
We have installed Adobe Document Services (ADS) as part of Netweaver 2004s on a 32 bit Windows server. We have our Development Portal configured to point to this server in the configuration of ADS.
Can we use the same ADS server for our QA Portal? We want to limit the number of servers/instances that we have to install and maintain.
Thank you,
George Barta

Hello,
There is a web service client connection to setup, and that's it (so nothing extraordinary there) !
Guids on how to do this are available on service.sap.com/adobe (configuration guide) and also in the following threads:
ADS connection
Using ADS on other server
Regards,
Francois

Error offline deploying adobe document services

Hi,
I am doing an offline deployment of the adobe document services to my portal implementation. I have portal 2004 SP16. I am deploying ADS which is SP16 as well.
Following is the error. Any recommendations on how to proceed. Any help will be appreciated and rewarded.
Thank You
Sumit
[code]===========================================================================
Deployment started Tue Apr 25 14:31:32 EDT 2006
===========================================================================
Starting Deployment of Binaries
The SDM will now stop SAP Web AS Java cluster instance(s) processes in order to perform offline deployment. After that the deployment will proceed.
It could take some time, so please be patient.
Deployment of Binaries finished successfully (Duration 31969 ms)
Starting Deployment of DataManagerService
Deployment of DataManagerService finished successfully (Duration 2594 ms)
Starting Deployment of DocumentServicesBinaries
Deployment of DocumentServicesBinaries finished successfully (Duration 2344 ms)
Starting Deployment of DocumentServicesBinaries2
Deployment of DocumentServicesBinaries2 finished successfully (Duration 6094 ms)
Starting Deployment of DocumentServicesConfiguration
Deployment of DocumentServicesConfiguration finished successfully (Duration 2422 ms)
Starting Deployment of DocumentServicesDestProtoService
Deployment of DocumentServicesDestProtoService finished successfully (Duration 2281 ms)
Starting Deployment of DocumentServicesLibrary
Deployment of DocumentServicesLibrary finished successfully (Duration 2406 ms)
Starting Deployment of DocumentServicesLicenseDatabase
Deployment of DocumentServicesLicenseDatabase finished successfully (Duration 5156 ms)
Starting Deployment of DocumentServicesLicenseService
Deployment of DocumentServicesLicenseService finished successfully (Duration 2500 ms)
Starting Deployment of DocumentServicesLicenseSupportService
Deployment of DocumentServicesLicenseSupportService finished successfully (Duration 2781 ms)
Starting Deployment of FontManagerService
Deployment of FontManagerService finished successfully (Duration 9610 ms)
Starting Deployment of PDFManipulation
Aborted: development component 'PDFManipulation'/'com.adobe'/'Adobe Systems'/'700.20050711201154.91738', grouped by software component 'ADS_SAPOFF'/'sap.com'/'SAP AG'/'1000.1.00.16.0.20060203041228':
Caught exception during deployment from SAP J2EE Engine's offline deploy API:
com.sap.engine.tools.offlinedeploy.rdb.ODeploymentException: ERROR: Can't deploy component with sda D:\usr\sap\J2E\JC01\SDM\root\origin\com.adobe\PDFManipulation\Adobe Systems\700.20050711201154.91738\adobe-PDFManipulation.sdacom.sap.engine.frame.core.configuration.ConfigurationException: Error occurred during DB access: ,
     at com.sap.engine.core.configuration.impl.persistence.rdbms.UpdateProcessor.flush(UpdateProcessor.java:342)
     at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.commitConfigurationHandler(ConfigurationCache.java:1184)
     at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.commit(ConfigurationHandlerImpl.java:914)
     at com.sap.engine.tools.offlinedeploy.rdb.OfflineComponentDeployImpl.deployComponent0(OfflineComponentDeployImpl.java:408)
     at com.sap.engine.tools.offlinedeploy.rdb.OfflineComponentDeployImpl.deployComponent(OfflineComponentDeployImpl.java:264)
     at com.sap.sdm.serverext.servertype.inqmy.extern.EngineOfflineDeployerImpl.performDeployment(EngineOfflineDeployerImpl.java:209)
     at com.sap.sdm.serverext.servertype.inqmy.extern.EngineDeployerImpl.deploy(EngineDeployerImpl.java:96)
     at com.sap.sdm.serverext.servertype.inqmy.EngineProcessor.executeAction(EngineProcessor.java:224)
     at com.sap.sdm.app.proc.deployment.impl.PhysicalDeploymentActionExecutor.execute(PhysicalDeploymentActionExecutor.java:60)
     at com.sap.sdm.app.proc.deployment.impl.DeploymentActionImpl.execute(DeploymentActionImpl.java:186)
     at com.sap.sdm.app.proc.deployment.controllers.internal.impl.DeploymentExecutorImpl.execute(DeploymentExecutorImpl.java:48)
     at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.executeAction(ExecuteDeploymentHandler.java:83)
     at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.handleEvent(ExecuteDeploymentHandler.java:60)
     at com.sap.sdm.app.proc.deployment.states.StateBeforeNextDeployment.processEvent(StateBeforeNextDeployment.java:127)
     at com.sap.sdm.app.proc.deployment.states.InstContext.processEventServerSide(InstContext.java:73)
     at com.sap.sdm.app.proc.deployment.states.InstContext.processEvent(InstContext.java:59)
     at com.sap.sdm.app.view.controllers.DeployEventProcessor.processEvent(DeployEventProcessor.java:11)
     at com.sap.sdm.client_server.deployserver.DeployCmdProcessor.processEvent(DeployCmdProcessor.java:268)
     at com.sap.sdm.client_server.deployserver.DeployCmdProcessor.process(DeployCmdProcessor.java:112)
     at com.sap.sdm.gui.server.GuiAdminRoleCmdProcessor.process(GuiAdminRoleCmdProcessor.java:72)
     at com.sap.sdm.is.cs.session.server.SessionCmdProcessor.process(SessionCmdProcessor.java:67)
     at com.sap.sdm.is.cs.cmd.server.CmdServer.execCommand(CmdServer.java:76)
     at com.sap.sdm.client_server.launch.ServerLauncher$ConnectionHandlerImpl.handle(ServerLauncher.java:286)
     at com.sap.sdm.is.cs.ncserver.NetCommServer.serve(NetCommServer.java:43)
     at com.sap.sdm.is.cs.ncwrapper.impl.ServiceWrapper.serve(ServiceWrapper.java:39)
     at com.sap.bc.cts.tp.net.Worker.run(Worker.java:50)
     at java.lang.Thread.run(Thread.java:534)
Caused by: com.sap.nwmss.jdbc.base.BaseBatchUpdateException: [NWMss][SQLServer JDBC Driver]Communication error: The stream provided does not contain the number of bytes specified. For batches, please ensure that streams are reset before subsequent addBatch calls. This is a non-recoverable error and the connection has been terminated.
     at com.sap.nwmss.jdbc.base.BasePreparedStatement.executeBatch(Unknown Source)
     at com.sap.sql.jdbc.basic.BasicPreparedStatement.executeBatch(BasicPreparedStatement.java:263)
     at com.sap.sql.jdbc.mss.MssInetPreparedStatement.executeBatch(MssInetPreparedStatement.java:188)
     at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeBatch(DirectPreparedStatement.java:1102)
     at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeBatch(DirectPreparedStatement.java:1066)
     at com.sap.engine.core.configuration.impl.persistence.rdbms.DBAccessDefault.execInsertFileBatch(DBAccessDefault.java:1213)
     at com.sap.engine.core.configuration.impl.persistence.rdbms.UpdateProcessor.flush(UpdateProcessor.java:318)
     ... 26 more
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineOfflineDeployerImpl.performAction(DeploymentActionTypes).ODEXC)
Deployment of PDFManipulation finished with Error (Duration 17078 ms)[/code]

I solved this problem using the suggestion in the thread
Error when deploying PDFManipulation and XMLForm
Basically I increased the startup parameters of SQLServer to 512.
Sumit.

Configuring the Destination URL for the Adobe Document Services

hi all,
I am going through the documentation for "Configuring the Destination URL for the Adobe Document Services " at :
http://help.sap.com/saphelp_nw2004s/helpdata/en/02/560f41ca73d349e10000000a1550b0/frameset.htm
I am not able to understand 7th step
7. Define the user name and password. To find out how to create the user name and password for the Adobe document services, see Creating a User for Basic Authentication in the document Adobe Document Services Configuration Guide. You can find this guide in the SAP Service Marketplace under Quick Link /InstguidesNW04.
In our scenario
We are running NW04s SP11 on 2 machines
1) 32-bit machine with ADS and credentials properly configured on Web AS for Java installation
com.adobe AdobeDocumentServices null (710.20061024154505.342190)
com.adobe AdobeDocumentServicesEjbClientLibrary null (705.20060407121920.289077)
sap.com SAP-JEE 7.00 SP11 (1000.7.00.11.0.20070201154700)
sap.com SAP-JEECOR 7.00 SP11 (1000.7.00.11.0.20070201154700)
com.adobe DocumentServicesBinaries2 null (710.20060629085312.115621)
com.adobe DocumentServicesConfiguration null (710.20061024154505.342190)
com.adobe DocumentServicesDestProtoService null (710.20060821084105.325745)
com.adobe DocumentServicesLibrary null (710.20060629090137.115621)
com.adobe DocumentServicesLicenseDatabase null (705.20051005114147.242570)
com.adobe DocumentServicesLicenseManager null (710.20060929113452.336248)
com.adobe DocumentServicesLicenseService null (710.20060929113452.336248)
com.adobe DocumentServicesLicenseSupportService null (710.20060929113641.336248)

2) 64-bit machine with portal installation on Web AS for Java, with ESS and MSS
sap.com/SAP-JEECOR 7.00 SP11 (1000.7.00.11.0.20070201154700) 20070308153304
sap.com/SAP-JEE 7.00 SP11 (1000.7.00.11.0.20070201154700) 20070308153213
sap.com SAP_ESS 600 SP7 (1000.600.0.7.12.20070314050106)
sap.com SAP_MSS 600 SP7 (1000.600.0.7.4.20070321052655)
sap.com tc/wd/webdynpro null (7.0009.20060804145649.0000) 

Why do we have to create a new user for the server which is consuming the web service? We already have an user "ADSUser" defined for the Web AS server which has ADS services deployed.
I have opened this thread to solve the previous unanswered question I posted on SDN Empty area in place of Interactive form. .
One more thing the adobe print forms of ESS [Total Compensation Statement and Salary Statement] are rendering properly, only the ones with Interactive ability or not.
thanks,
Sanketh

Hello Sanketh,
1. To access the NW04s configuration guide,
 - Go to https://service.sap.com/adobe
 - On the left frame (tree), under Adobe > Media Library > Documentation
 - On the right had pane you will find the link to the NW04s Configuration guide
2. The link that you have mentioned below details the steps required to be carried out on the client machine that consumes the Adobe Document Services. In our case that is the j2ee engine on which your Web Dynpro application is running. It could be the same physical machine with two different j2ee instances hosting Web Dynpro and ADS or it could be two different physical machine or a single machine having a single instance of j2ee engine hosting both the Web Dynpro and the ADS.
You do not have to create a separate username and a password on the consuming machine but you need to configure the Web Service client proxy to point to the ADS (maybe hosted on a different machine) with the username and the password created on the ADS server. As you have mentioned, you have already created such an user on the ADS (ADSUser). This user authentication on the client machine (consuming server - Web Dynpro) would be required at the runtime by the j2ee engine to authenticate itself with the ADS.
Best Regards,
Krish

GRMG Availability for the Adobe Document Services

Hi,
in GRMG I have message:
Scenario: ADS 001 001; status message: Reason for HTTP POST failure:HTTP communication failure.
When I try oren URL [http://<server>:<Java port>/AdobeDocumentServices/Grmg/App]
I had received message:
405 Method Not Allowed
HTTP method GET is not supported by this URL
Could you please help me resolve it?
Thanks a lot,
Alexander

Hello Sanketh,
1. To access the NW04s configuration guide,
 - Go to https://service.sap.com/adobe
 - On the left frame (tree), under Adobe > Media Library > Documentation
 - On the right had pane you will find the link to the NW04s Configuration guide
2. The link that you have mentioned below details the steps required to be carried out on the client machine that consumes the Adobe Document Services. In our case that is the j2ee engine on which your Web Dynpro application is running. It could be the same physical machine with two different j2ee instances hosting Web Dynpro and ADS or it could be two different physical machine or a single machine having a single instance of j2ee engine hosting both the Web Dynpro and the ADS.
You do not have to create a separate username and a password on the consuming machine but you need to configure the Web Service client proxy to point to the ADS (maybe hosted on a different machine) with the username and the password created on the ADS server. As you have mentioned, you have already created such an user on the ADS (ADSUser). This user authentication on the client machine (consuming server - Web Dynpro) would be required at the runtime by the j2ee engine to authenticate itself with the ADS.
Best Regards,
Krish

XMLFormService Error offline deploying adobe document services - 2

Hi,
I am doing an offline deployment of Adobe document Services SP16. I am using the Software Deployment Manager to do this. The installation fails at the XMLFormService.
Any hints or suggestions.
Thank You.
Sumit.
[code]===========================================================================
Deployment started Tue Apr 25 16:14:20 EDT 2006
===========================================================================
Starting Deployment of PDFManipulation
The SDM will now stop SAP Web AS Java cluster instance(s) processes in order to perform offline deployment. After that the deployment will proceed.
It could take some time, so please be patient.
Deployment of PDFManipulation finished successfully (Duration 60281 ms)
Starting Deployment of TrustManagerService
Deployment of TrustManagerService finished successfully (Duration 2297 ms)
Starting Deployment of XMLFormService
Aborted: development component 'XMLFormService'/'com.adobe'/'Adobe Systems'/'700.20051206050005.238137', grouped by software component 'ADS_SAPOFF'/'sap.com'/'SAP AG'/'1000.1.00.16.0.20060203041228':
Caught exception during deployment from SAP J2EE Engine's offline deploy API:
com.sap.engine.tools.offlinedeploy.rdb.ODeploymentException: ERROR: Can't deploy component with sda D:\usr\sap\J2E\JC01\SDM\root\origin\com.adobe\XMLFormService\Adobe Systems\700.20051206050005.238137\adobe-XMLForm.sdacom.sap.engine.frame.core.configuration.ConfigurationException: Error occurred during DB access: ,
     at com.sap.engine.core.configuration.impl.persistence.rdbms.UpdateProcessor.flush(UpdateProcessor.java:342)
     at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.commitConfigurationHandler(ConfigurationCache.java:1184)
     at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.commit(ConfigurationHandlerImpl.java:914)
     at com.sap.engine.tools.offlinedeploy.rdb.OfflineComponentDeployImpl.deployComponent0(OfflineComponentDeployImpl.java:408)
     at com.sap.engine.tools.offlinedeploy.rdb.OfflineComponentDeployImpl.deployComponent(OfflineComponentDeployImpl.java:264)
     at com.sap.sdm.serverext.servertype.inqmy.extern.EngineOfflineDeployerImpl.performDeployment(EngineOfflineDeployerImpl.java:209)
     at com.sap.sdm.serverext.servertype.inqmy.extern.EngineDeployerImpl.deploy(EngineDeployerImpl.java:96)
     at com.sap.sdm.serverext.servertype.inqmy.EngineProcessor.executeAction(EngineProcessor.java:224)
     at com.sap.sdm.app.proc.deployment.impl.PhysicalDeploymentActionExecutor.execute(PhysicalDeploymentActionExecutor.java:60)
     at com.sap.sdm.app.proc.deployment.impl.DeploymentActionImpl.execute(DeploymentActionImpl.java:186)
     at com.sap.sdm.app.proc.deployment.controllers.internal.impl.DeploymentExecutorImpl.execute(DeploymentExecutorImpl.java:48)
     at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.executeAction(ExecuteDeploymentHandler.java:83)
     at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.handleEvent(ExecuteDeploymentHandler.java:60)
     at com.sap.sdm.app.proc.deployment.states.StateBeforeNextDeployment.processEvent(StateBeforeNextDeployment.java:127)
     at com.sap.sdm.app.proc.deployment.states.InstContext.processEventServerSide(InstContext.java:73)
     at com.sap.sdm.app.proc.deployment.states.InstContext.processEvent(InstContext.java:59)
     at com.sap.sdm.app.view.controllers.DeployEventProcessor.processEvent(DeployEventProcessor.java:11)
     at com.sap.sdm.client_server.deployserver.DeployCmdProcessor.processEvent(DeployCmdProcessor.java:268)
     at com.sap.sdm.client_server.deployserver.DeployCmdProcessor.process(DeployCmdProcessor.java:112)
     at com.sap.sdm.gui.server.GuiAdminRoleCmdProcessor.process(GuiAdminRoleCmdProcessor.java:72)
     at com.sap.sdm.is.cs.session.server.SessionCmdProcessor.process(SessionCmdProcessor.java:67)
     at com.sap.sdm.is.cs.cmd.server.CmdServer.execCommand(CmdServer.java:76)
     at com.sap.sdm.client_server.launch.ServerLauncher$ConnectionHandlerImpl.handle(ServerLauncher.java:286)
     at com.sap.sdm.is.cs.ncserver.NetCommServer.serve(NetCommServer.java:43)
     at com.sap.sdm.is.cs.ncwrapper.impl.ServiceWrapper.serve(ServiceWrapper.java:39)
     at com.sap.bc.cts.tp.net.Worker.run(Worker.java:50)
     at java.lang.Thread.run(Thread.java:534)
Caused by: com.sap.nwmss.jdbc.base.BaseBatchUpdateException: [NWMss][SQLServer JDBC Driver]The DBMS returned an unspecified error. The command code was 0.
     at com.sap.nwmss.jdbc.sqlserver.SQLServerImplStatement.getBatchRowsAffectedCount(Unknown Source)
     at com.sap.nwmss.jdbc.base.BasePreparedStatement.executeBatch(Unknown Source)
     at com.sap.sql.jdbc.basic.BasicPreparedStatement.executeBatch(BasicPreparedStatement.java:263)
     at com.sap.sql.jdbc.mss.MssInetPreparedStatement.executeBatch(MssInetPreparedStatement.java:188)
     at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeBatch(DirectPreparedStatement.java:1102)
     at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeBatch(DirectPreparedStatement.java:1066)
     at com.sap.engine.core.configuration.impl.persistence.rdbms.DBAccessDefault.execInsertFileBatch(DBAccessDefault.java:1213)
     at com.sap.engine.core.configuration.impl.persistence.rdbms.UpdateProcessor.flush(UpdateProcessor.java:318)
     ... 26 more
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineOfflineDeployerImpl.performAction(DeploymentActionTypes).ODEXC)
Deployment of XMLFormService finished with Error (Duration 45812 ms)
Starting Deployment of ADS_SAPOFF
Aborted: software component 'ADS_SAPOFF'/'sap.com'/'SAP AG'/'1000.1.00.16.0.20060203041228':
No further description found.
Deployment of ADS_SAPOFF finished with Error (Duration 2094 ms)[/code]

Rebooted the machine and started deployment again. And the deployment worked.

Adobe Document Services (ADS) Configuration

Hello,
I need to configure ADS for Form Processing (ABAP). However, I got the following landscape:
AS JAVA instance: Netweaver 7.01 (EP/BI-Java)
AS ABAP instance: Netweaver 7.4 SR1
Is there any restriction or consideration regarding this scenario? I mean, having an ABAP stack higher than the JAVA. Is it possible?
Regards,
JAM

Hi JAM,
Please find pre-requisite information in SAP help as below
Configuring Adobe Document Services for Form Processing (ABAP) - Adobe Document Services for Form Processing - SAP Libra…
Prerequisites
The AS Java where the ADS are running should have at least the same release as the AS ABAP.
Caution
The following functions for PDF forms require at least the ADS version on AS Java 7.20:
Parallelization of large print jobs
Stitching of PDF forms
Hope this helps.
Regards,
Deepak Kori

Adobe Document Services URL problem

Hi,
I am trying to connect to the adobe document services to test the configuration, but getting the following kind of error:
"Adobe document service can not be started".
can somebody tell me how to resolve this?
Thanks,
Sunita.

hi sunita,
please do as follows;
1. IIOP start up mode for global node
     Go to configtool
     -> cluster-data -> Global dispatcher configuration -> services
          -> iiop
        check if startup mode is 'always'.
     Also for
     -> cluster-data -> Global server configuration -> services -> iiop
2. IIOP start up mode for instance node
     Go to Visual Administrator
     -> server -> services -> Configuration Adapter
         Configurations -> cluster_data -> dispatcher -> cfg -> services -> Property Sheet IIOP-runtime
     If they have the value like as:
         startup mode=manual and custom field is checked
     Solution1:
         Change startup mode to 'always' for instance node
     Solution2:
         Restore original configuration for instance node using config
         tool.
     Repeat same operation for
     -> Configurations -> cluster_data -> server -> IDxxxx
                    -> services -> propertysheedt.iiop-runtime
3. Restart J2EE engine
thanks,
raj

Questions Regarding Adobe Document Services

Greetings,
We are looking at implementing Adobe Document Services and I have some general questions about running it; any input you can give will be helpful. I am particularly eager for good reference documents that have answers to these questions.
Question 1:
We have multiple ABAP stacks which could use ADS (which runs on the J2EE stack). Can we use just one J2EE instance running the latest version of ADS and hook it up to all our ABAP stacks? Or do we need a separate J2EE instance for each ABAP stack?
Question 2:
Are there direct version dependencies between ADS and the ABAP stack version / J2EE stack version? In other words, if we upgrade the ABAP stack version does the ADS version need to increase to the same stack level?
Question 3:
Does Adobe Lifecycle Designer require a separate client install for it to work in the SAPGUI?
Question 4:
What is meant by "high volume" print scenarios -- and why would this supposedly need a dual-stack system?
Thanks in advance SDNers!
- Kris

actuall the statement to have ABAP+JAVA for performnce reasons is obsolete as of NW 7.0 SP12
please see the Master guide at https://service.sap.com/instguides
For SAP NetWeaver 7.0 SP Stack 06 and higher, run both usage types AS ABAP and AS Java in
one system to improve performance for printing scenarios in this system. This precludes the
possibility of using one central ADS for several systems.
As of SAP NetWeaver 7.0 SP Stack 12, this restriction no longer applies. Therefore you can also
improve performance by using one central ADS for several systems.
this is a good starting point https://www.sdn.sap.com/irj/sdn/adobe
There are in particular for ADS installations on HP-UX performance constraints
please checkout #1133230:
Because the ADS binary files execute using the AIRES emulator, erformance of the ADS will be slightly different from what is indicated in the ADS sizing guidelines.
Performance for small print forms will be approximately 2.0 times slower than indicated in the sizing guideline.
Performance for medium and large print forms and non-cached interactive forms will be approximately 1.5 times slower than indicated in the sizing guideline
Performance for cached interactive forms will be approximately 25% faster than indicated in the sizing guideline
Nesimi

SOAP Runtime exception using Adobe Document Services

Hi all,
we have an intermittent problem with the following scenario:
ECC6 ABAP system which runs our Payroll.
Separate JAVA instance running our SAP portal and Adobe Document Services.
SM59 connection from the ABAP system to the portal server where ADS runs. Connection via port 5554.
We have written our own transaction ZPAYSLIP which allows users to view and print their payslips using ADS. This transaction uses a program generated in transaction HRFORMS.
Periodically, this transaction will fail with the following error at the bottom of the user's screen:
ADS: SOAP Runtime Exception: CSoapExceptionTransport: (100101SOAP Framework error: SOAP Runtime Exception)
A lot of the problem is that this issue is sporadic and difficult to reproduce. Whenever it has been reported to me and I try to reproduce the error I am unable to. A test of the SM59 connection shows everything is OK and if I ask the user to retry it, it will work.
I have asked our network team to check the connection between the 2 servers at the time when the error happens, but they cannot find any problems with connectivity between them, and yet it looks to me like the problem is a temporary loss of connectivity or that ADS somehow becomes temporarily unavailable.
I have done the checks as referred to in sapnote 944221 (many times!) but that all checks out OK.
We have logged a call with SAP, but they haven't really come up with a solution apart from restarting the JAVA engine which is not what we want to have to do.
We also experience the same error from time to time with some of our portal functionality which also uses ADS.
Has anyone experienced a similar error or have any suggestions as to how we might fix this?
Regards....John

Hi,
We have encountered a very similar issue after patching our dual stack ECC to NW23/ERP603 sp8. After first correcting it by routing the ADS calls directly to the server (and not through the web dipspatcher), we then updated our SAP Web Dispatcher to a newer version and this seems to have resolved it while maintaining the necessary load-balancing functionality of the web dispatcher.
Hope this helps.
Ruben

Error in installing creditionals for Adobe Document Services

Hi All,
I have installed SAPNW2004sJavaSP9_Trial on my local machine and when I try to register the Register the password for credential by following the steps below I face a problem in step 4. The error is a pop up as enclosed.
An error occured while indexing the credential files:
com.adobe.service.sap.ConfigurationException:An error occured while indexing the credential files
1.Log on to the Visual Administrator (C:\usr\sap\J2E\JC00\j2ee\admin\go.bat)
2. On the Cluster tab, choose Server 0 -> Services -> Document Services Configuration
3. On the Runtime tab, select Credentials
4. Choose Browse to search for the name of the credential and then Select
5. In the Alias field, enter the alias of the credential you installed, for example ReaderRights. (Entries for the name of the credential are case-sensitive)
6. In Password field, enter the password you received together with the credential you installed (filename.txt in <zip_extract_folder>\SAPNetWeaver04SneakPreviewJavaSP11\ADSCredentialFiles). Confirm the password again and then click Add
&#56256;&#56451; Restart the following services for the changes to take effect: PDF Manipulation Module, Document Services Trust Manager
7. Restart also the application com.adobe/AdobeDocumentServices
I followed the steps given the following posts
Latest NW Sneakpreview SP16 and Adobe Interactive Forms
TrustServices Credentials problem
Adobe Document Services: How to upgrade from ADS SP 9 to ADS SP 15
But, it still does not resolve my problem. I also upgraded the version to SP16 and yet it does not resolve the problem. Can someone tell me what could be wrong?
Thanks for all your help in advance.
Regards,
Divya

Hi,
All the form-related services have to be started first: the IIOP on dispatcher and server, all the Document Services *, PDF manupulation and XML form module.
Then you should be able to register your credential.
Francois

Sharing Adobe Document Services Instance

Similar Messages

Maybe you are looking for