[CASE-OPENED] Reporting Server(7.6.5) - HTTPS not communicating

July 01, 2009, 11:30 AM

Here is my scenerio:
I am trying to run a procedure from my WF Reporting server(7.6.5) by making a
call to a Weblogic Application server where 3 xml files reside. My procedure
contains 3 lines that idetify the location of the XML files.
XMLDEF TRANSACTION HTTP
https://wswzp3332.wellsfargo.c...essionid=a78f25e53c-
132a1b14edc776b11223231f1f5107fdb?jsessionid=a78f25e53c132a1b14edc776b11223231f-
1f5107fdb
XMLDEF TRANSACTION2 HTTP
https://wswzp3332.wellsfargo.c...essionid=a78f25e53c-
132a1b14edc776b11223231f1f5107fda?jsessionid=a78f25e53c132a1b14edc776b11223231f-
1f5107fda
XMLDEF VERIFIED_DATE HTTP
https://wswzp3332.wellsfargo.c...essionid=a78f25e53c-
132a1b14edc776b11223231f1f5107fd9?jsessionid=a78f25e53c132a1b14edc776b11223231f-
1f5107fd9

When I run the procedure I get this message:
(FOC42251) XML FILE
'https://wswzp3332.wellsfargo.com:8034/tpr_proxy_web/proxy;jsessionid=a78f25e53
Exiting due to Exit on Error...
...RETRIEVAL KILLED
(FOC026) THE REPORT IS NO LONGER AVAILABLE

If I take this line and paste it into my browser on the Reporting Server I can
read the xml file from the weblogic server:
https://wswzp3332.wellsfargo.c...essionid=a78f25e53c-
132a1b14edc776b11223231f1f5107fdb?jsessionid=a78f25e53c132a1b14edc776b11223231f-
1f5107fdb

If I change the 3 lines in my XMLDEF statement to HTTP the report runs just
fine.

I have made sure I have the XML adapter. For some reason HTTPS is giving me a
headache.

This message has been edited. Last edited by: Kerry,