on 10-15-2009 10:35 PM
We have a single installation of ADS installed with 3 separate EP 6 installations that use it remotely for document services. Two of three EP installations can access the ADS and are successfully using Adobe Interactive Forms. The third is not. I compared the EP that is not working with one that was and here is what I discovered.
1) Comparing the components listed in the System Information reveals that there are no "com.adobe" vender components in the non-working EP.
2) Calling the SAP Adobe Services Congfig URL http://<server>:<port>/AdobeDocumentServices/Config returns configuration information on the first two "good" Portals, but returns a 404 error message on the 3rd
3) In the Visual Administrator, if you go to the Cluster tab, choose Server -> Services -> Security Provider, There is no com.adobe/AdobeDocumentServices*AdobeDocumentServicesAssembly.jar that you need to configure the Policy to assign the ADSUser.
I take all of this to mean that the 3rd Enterprise Portal needs an additional installation of an Adobe Document Services component and then some configuration in order to use the remote ADS system. Can somebody please point us in the right direction? I am a content developer and not an SAP Admin, so please, if you can, provide specific information.
Thank you!!!
SAP-JEE Portal 6.40 SP20 64 bit
Adobe Services EP Portal 6.40 32 bit
Hello,
the component you found is the ADS itself. You do not need them in case you do not need use the local ADS.
For remote ADS the WebService client proxy has to be configured correclty.
In the Visual Admin: / If you are not using SSL /
Web Services Security Service >> Web Service Clients >> sap.com >> tcwdpdfobject >> com.sap.tc.webdynpro.adsproxy.AdsProxy*ConfigPort_Document
Please ensure that this is configured correctly for the 3rd portal as well.
Best regards,
Dezso
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Dezso,
So we tried configuring the Web Service Proxy for ADS from our remote EP implementation using basic authentication. Now we are getting a different error.
When a manager logs into the portal and selects a PCR and then tries to open it, at which point the EP tries to retrieve a form from the ADS, an exception is thrown that reads:
-
com.sap.engine.services.webservices.jaxrpc.wsdl2java.ClientProtocolException: An error occured while reading data from the destination sap.com/tcwdpdfobject/com.sap.tc.webdynpro.adsproxy.AdsProxy/SecConfigPort_Document. The error was: java.security.cert.CertificateException No such view:
...
-
One of the only differences between Production EP and the other EPs is that client browsers are forced to use SSL/HTTPS to connect to it. I wouldn't image that the EP is then in turn trying to use SSL to connect to the ADS would it?
Thanks!
Also, I did not configure the Security configuration (under Web Services Security Service >> Web Service Clients >> sap.com >> tcwdpdfobject >> com.sap.tc.webdynpro.adsproxy.AdsProxySecConfigPort_Document*) but it looks like the Logon Data section -> authentication had been set to X.509 Client Certificate. Nothing else on the page has been filled in other than some default values for Destination. I'm changing the Logon Data, Authentication to None. Should this help???
I want to test this but I'm not a manager. I don't want to have to keep bothering my boss to test this for me!
Thank you.
- Redding
We had to enlist the help of SAP and eventually made a setting within the EP production portal Visual Admin that forced Web Dynpro components to make SOAP calls to the remote ADS server. This somehow magically fixed our problem (it doesn't make since to me since SOAP is still nested within HTTP).
Hi John,
I can't remember off the top of my head, but fortunately I document most everything in Wiki here at work. Here's what we did: (I believe #3 is where we instruted WebDynpro to use SOAP)
1. Checked that the following settings were made:
Web Services Security Service >> Web Service Clients >> sap.com >> tcwdpdfobject >> com.sap.tc.webdynpro.adsproxy.AdsProxyConfigPort_Document
Please also check the FP_ICF_DATA_ destination as per ntoe 915399.
2. Determined that the WebDynpro of the EP Portal was trying to use SSL to call the ADS server. Made the following changes:
Visual Administrator -> Server -> Services -> Configuration Adapter here: Webdynpro -> sap.com -> tcwddispwda -> Propertysheet default -> sap.protocolSchemeForADSCall >> custom value: HTTP
3. After making the previous change and restarting we got a different exception (see SAP message. Next, apply SAP note 867502 to your portal server. After change this WebDynpro property, it will send template/runtime data as different way (not use HTTP/HTTPS protocol). Please use Visual Administrator to maintain propertysheet default: go to Server -> Services -> Configuration Adapter -> webdynpro -> sap.com -> tcwddispwda Please edit the entry "sap.ADSCallingMode", change that value from "http" to "soap", save the changes and restart the cluster.
I hope this solves your problem.
- Redding
User | Count |
---|---|
83 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.