If you are unable to create a new account, please email support@bspsoftware.com

 

XML file as a Datasource connection troubleshoot

Started by Ravisha, 28 Apr 2021 11:59:11 PM

Previous topic - Next topic

Ravisha

I'm on CA 11.1.6. I've created a XML datasource connection to a local XML file (with the connection string -> D:\sample.xml;VALIDATE=ON). However, the connection fails upon testing the datasource connection with a warning (shown in the attached image file or the URL below). Any suggestion as to how to resolve the issue or any workaround would be much appreciated. Please advise.

https://ibb.co/b1c30B7

PS: Not sure why I'm unable to attach files with this post.

MFGF

Quote from: Ravisha on 28 Apr 2021 11:59:11 PM
I'm on CA 11.1.6. I've created a XML datasource connection to a local XML file (with the connection string -> D:\sample.xml;VALIDATE=ON). However, the connection fails upon testing the datasource connection with a warning (shown in the attached image file or the URL below). Any suggestion as to how to resolve the issue or any workaround would be much appreciated. Please advise.

https://ibb.co/b1c30B7

PS: Not sure why I'm unable to attach files with this post.

Hi,

The error indicates that the Cognos server can't find M:\sample.xml. Have you tried using a UNC path in your file name? Does the service account for Cognos have access to the location your XML file is located in?

With regards to including the image in the post, you already uploaded it to ImgBB, so just grab the IMG tags from there and include them in the post to embed the image.

Cheers!

MF.
Meep!

Ravisha

#2
@MFGF, I'd like to thank you for your response.

I have CA installed on my local machine and the service runs on local system account (LogOn). Per your advice, I've changed it to UNC path \\LOCALHOST\M$\FX.xml;VALIDATE=ON and it fails to connect (with and without VALIDATE=ON option). As shown in the image below, not sure why it is looking for DSN (ODBC) / DSN name. I guess it is looking for a XML driver to be able to connect to the XML file  :o . My goal is to connect to a file source (it can be a text or csv or xml) and create a datasource query subject in FM model. I thought of using ODBC datasource connection. However, later I realized that DQM based FM models doesn't accept odbc datasource connections. Please advise.


MFGF

Quote from: Ravisha on 30 Apr 2021 07:50:24 PM
@MFGF, I'd like to thank you for your response.

I have CA installed on my local machine and the service runs on local system account (LogOn). Per your advice, I've changed it to UNC path \\LOCALHOST\M$\FX.xml;VALIDATE=ON and it fails to connect (with and without VALIDATE=ON option). As shown in the image below, not sure why it is looking for DSN (ODBC) / DSN name. I guess it is looking for a XML driver to be able to connect to the XML file  :o . My goal is to connect to a file source (it can be a text or csv or xml) and create a datasource query subject in FM model. I thought of using ODBC datasource connection. However, later I realized that DQM based FM models doesn't accept odbc datasource connections. Please advise.



Hi,

Is there a particular reason you have to do things this way? Cognos Analytics supports you uploading files and then using these in Data Modules - you can join them with other files/database tables/FM package etc in the Data Module. It sounds like this might be an easier solution for you?

Cheers!

MF.
Meep!

Ravisha

#4
Quote from: MFGF on 03 May 2021 07:05:25 AM
Hi,

Is there a particular reason you have to do things this way? Cognos Analytics supports you uploading files and then using these in Data Modules - you can join them with other files/database tables/FM package etc in the Data Module. It sounds like this might be an easier solution for you?

Cheers!

MF.

My reasoning for taking this automated approach foresees that we will receive a file of any format/extension of our interest (on weekly basis) in which some key-value pairs will be contained which will be used as a datasource query subject in the existing FM model. This datasource query subject will then be used in a parameter map to pass the value into a function (in conjunction with a session parameter) in some of the query items in both business layer as well as any sql based report that uses this function.

I hope that answers your questions  :)