Configuring the Destination URL for the Adobe Document Services

[Former Member]

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

<b>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.</b>

In our scenario

<i>We are running NW04s SP11 on 2 machines

1) <u>32-bit machine with ADS and credentials properly configured on Web AS for Java installation</u>

<b>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)

</b>

2) <u>64-bit machine with portal installation on Web AS for Java, with ESS and MSS</u>

<b>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) </b>

</i>

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 .

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

[krishanu_biswas]

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

[Former Member]

hi Krishanu,

Thanks for your input, we have followed the same guide that you mentioned.

As I said the machine which is hosting ADS has interactive web dynpro applications running without any problem. But the same application deployed on portal server which is acting as client to this web service is not able to render interactive form [browser has emply content area in place of interactive form], all the elements outside the interactive form on the browser are displayed properly. The not so good thing is I am not able to catch any exceptions or errors.

I checked into web dynpro logs of portal and Adobe logs of ADS, there are no errors, ADS is infact receiving the request from portal and also generating a response [I am able to see pdf file binary data in ADS logs], but after that I am not sure whether that response is reaching portal or not.

Any suggestions?

Also is it possible to run ADS on 64-bit windows machine and be supported by SAP. PAM mentions it wil only support 32-but windows machine.

thanks,

Sanketh