Error while creating logical port for Reporting

Question

Hi,
In one of the training materials for Duet Enterprise, i saw the steps for creating logical port for the consumer proxy /IWTNG/CO_PXY_RECORDS_REPOSITO.
When i am trying to create the logical port, i am getting an error saying,
" SRT Framework exception: Error in WSDL access: Exception occurred in communication framework:Error in HTTP Framework:500 Native SSL error
https://<server:port>/_vti_bin/OBAFileReceiver.asmx?wsdl "
I would like to know is it really necessary to create this logical port for "Reporting Scenario" and is it not created automaticallly using the Installation Wizard??
And in case it has to be created, how to resolve this SRT framework exception?
~ Ramanath.

Answer 1

Hi,
the consumer proxy  /IWTNG/CO_PXY_RECORDS_REPOSITO was used in Duet Enterprise SP01. Now with SP02 the consume proxy /IWTNG/CO_OBAFILE_RECEIVER_SOA is created.
However, the SSL error that you are getting looks a little strange (it does not mean that there is an error, but it is worth checking):
So can you go to SOAMANAGER -> Service Administration -> Single Service Configuration. In here select "Consumer Proxy" from the "Search by", Search Pattern "/IWTNG/CO_OBAFILE_RECEIVER_SOA" and Field: Both.
You should find one entry. Select it and click "Apply Selection".
Now go to the Configurations tab. Here you should see one Logical Port with name "LOGICALPORTFORREPORTING" with Creation Type "Manually Created". In fact this logical port was created by the Wizard.
Click on Display and scroll down again. Now in the "Additional Information" tab there is a string after HTTP Destination, e.g. 0050568E3F5A1ED096F22339C44BAF83.
Copy this value and go to your SAP GUI -> Transaction SM59.
Here click on Find/Search and search for this HTTP Destination. You should find one Type G RFC Destination that has the target host of your SharePoint server and the path prefix /_vti_bin/OBAFileReceiver.asmx.
Now you can test the service. Just click on Connection Test. The result should be a HTTP Response: 200.
If not, then something went wrong with the automatic configuration and we should take another look at it (for example maybe the SSL certificate from SharePoint that was imported by the Wizard is not valid)
Regards,
Holger.
PS. Don't use the "Ping Web Service" test from SOAMANGER -- unfortunately this is not working consistently.