cancel
Showing results for 
Search instead for 
Did you mean: 

Can not set up Web Service datastore using HTTPS WSDL DS 4.1

prashant_saini
Advisor
Advisor
0 Kudos

I have been trying to configure a Web services data store to connect to an HTTPS Wsdl file

Here is some background.

DS Version: 14.1.1.210

Job Server Windows 2008

if i configure the datastore and leave the field for Keystore path empty, i get the following error:

Error loading [https://stgbbaaviation.taleo.net/enterprise/soap?ServiceName=CorporateRecruitmentSourceService&wsdl]...

org.apache.xmlbeans.XmlException: java.io.IOException: Server returned HTTP response code: 401 for URL: https://stgbbaaviation.taleo.net/enterprise/soap?ServiceName=CorporateRecruitmentSourceService&wsdl

If i put the path C:\Program Files (x86)\SAP BusinessObjects\Data Services\ssl\mds\DSJavaKeyStore.keystore for the keystone path,

I get the following different error:

An error ocurred while importing metadata: WSDLException: faultCode=OTHER_ERROR: Unable to resolve imported document at 'https://stgbbaaviation.taleo.net/enterprise/soap?ServiceName=CandidateService&wsdl':javax.net.ssl.SS... sun.security.validator.ValidatorException: PKIX path building faild: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target (BODI-1111469) (BODI-1112446)

I have recreated the DSJavaKeyStore.keystore and added in additional certificates but nothing seems to work.

As a workaround i saved the wsdl file down to the local machine (I'm currently running designer on the job server machine)

i can then save the web service datastore and import the wsdl function.  but at runtime I get the following error:

There is no response for the web service <getMessageByIdentifier>. Ensure that the network, web server, and service are running

properly. Also ensure that the service client call time out is set properly.

I have edited the

C:\Program Files (x86)\SAP BusinessObjects\Data Services\ext\webservice-c\axis2.xml file as follows for the sections that are listed in the documentation:

    <transportReceiver name="https" class="axis2_http_receiver">

        <parameter name="port" locked="false">6060</parameter>

        <parameter name="exposeHeaders" locked="true">false</parameter>

    </transportReceiver>

<!-- Uncomment the following with appropriate parameters to enable the SSL transport sender.

         Also make sure that the appropriate transport receiver is enabled above.-->

    <transportSender name="https" class="axis2_http_sender">

        <parameter name="PROTOCOL" locked="false">HTTP/1.1</parameter>

        <parameter name="xml-declaration" insert="false"/>

    </transportSender>

    <parameter name="SERVER_CERT">C:\Program Files (x86)\SAP BusinessObjects\Data Services\ssl\server\DS_server_cert.crt</parameter>

    <parameter name="KEY_FILE">C:\Program Files (x86)\SAP BusinessObjects\Data Services\ssl\server\DS_server_privatekey.pem</parameter>

    <parameter name="SSL_PASSPHRASE">C:\Program Files (x86)\SAP BusinessObjects\Data Services\ssl\server\DS_server_privatekey_password.txt</parameter>

I'm not sure what i'm doing wrong.  Not much detail in the documentation on what to enter for the Keystore path in the Datastore config.

also it is unclear if i don't have the correct certifications added to the keystore.

Please help

Accepted Solutions (0)

Answers (2)

Answers (2)

DayaJha
Active Contributor
0 Kudos

Hi Prashant,

Please refer the below KBA related to BODI-1111469 issue in SAP Data Services 4.1 Support Pack 1 Patch 1 (Version 14.1.1.284).

ADAPT01664699

An importing operation from a WSDL that has a recursive import of a schema would fail with the error:  "An error occurred while importing metadata: Unknown JNI error... (BODI-1111469)”. This issue has been fixed in this release.



1804623 - Release Notes for SAP BusinessObjects Data Services 4.1 Support Pack 1 Patch 1 (Version 14.1.1.284)

https://service.sap.com/sap/support/notes/1804623




Thanks,

Daya

Former Member
0 Kudos

Has this been confirmed as working? We just upgraded to 4.1 SP3 patch 1 specifically for this functionality and I haven't been able to get past this JNI error. Could this be caused by multiple reasons? I have confirmed that there are recursive schema imports in these WSDL/XSD files.

prashant_saini
Advisor
Advisor
0 Kudos

.