Create ODBC Data source within IIS - iis

Please can someone direct me where i go within IIS in order to create an ODBC DSN.
Tried numerous sites. My old it manager set it up a while ago and i need to change some settings.

Related

Have excel file with ODBC link hosted in sharepoint

we have a case management system stored with the vendor, and use an excel file on a server locally to access some data, so have an ODBC link setup with security etc.
We are looking to dump the server, and i want to know if there is a way to have the excel file which will be put onto a sharepoint folder have the ODBC link embedded or linked so that a specific machine is not needed to be setup for its use.
I hope that makes sense...

Cognos Hyperion Essbase connection

We have cognos analytics which we want to connect to Hyperion cube but domain network in which they both are present are different because Hyperion is an application which over parent company owns and Cognos is owned by the my company which is a sister company to corporate.
Is their any other way we can access the Hyperion cube directly in cognos.
You should be able to use the Oracle Essbase data source available within the IBM Cognos Administration\Configuration.
If you are using the compatible query mode(CQM) you'll need to install the Essbase client, set the environment variables and possibly adjust the cqe_config.xml depending on your version.
If you are using the dynamic query mode(DQM) you'll need to copy the Jar files into the drivers folder within the Report Server install.
All the above is covered in more detail via the following link:
https://www.ibm.com/support/knowledgecenter/en/SSEP7J_10.2.2/com.ibm.swg.ba.cognos.dyn_query.10.2.2.doc/t_dqm_olap_install_drivers.html

Publish an Excel 2013 OData data connection file (odc) using GPO WITHOUT sharepoint

This is quite a specific request for help.
We have trying to give all our excel users a single workbook connection to an OData which is centrally managed (so we can update it in future, and to stop users adapting it).
Ideally we could publish this out using GPO and have it show up in the "Connection on your network" section of the connections within Excel. We can publish the .odc file to all computers but that would require all users to update the connection manually, which we are trying to avoid.
We have recently decommissioned our sharepoint server so that's not an option.
We attempted a registry change as listed here https://martinmason.wordpress.com/2012/06/17/excel-2010-connection-files-on-the-network-sharepoint-data-connection-libraries-and-the-enterprise/
but couldn't get it to accept a network location.
And we can't possibly know all the workbooks connected so can't do a VBA/Powershell update on the connection string as mentioned here Mass update Excel file connection string
It seems to be the exact same question asked here https://social.technet.microsoft.com/Forums/office/en-US/932aa489-6b6f-4de3-9935-f4d8748eea84/excel-2010-data-connection-files-odc-on-a-network-folder?forum=excel but the response still involved sharepoint...
Any help would be greatly appreciated

first time using SSRS web server, setting up website

its my first time using this and as a newbie I have many questions. Any help are appreciated.
My ultimate goal is to have reports created from database that will be able to be accessed by other end users on website so they can view/filter the report data online in a shared way with some user control settings.
So I have already made my reports in the visual studio linking to databases.
And I have also set up the Reporting Service Configuration Manager so that I can access SSRS home page and the site setting at http://'127.0.0.1'/Reports/Pages/Folder.aspx
Now my question is, how will the other end users be able to get onto the website and get access to the reports I created with SSRS? Do I upload the reports in .rdl on my report site manually or do I deploy it from VS? How do I turn my '127.0.0.1/Reports' into a public site for other user's access? Or do I have to create it using a sharepoint?
Thanks so much, I need a guidance to head toward the right direction! :)
Now my question is, how will the other end users be able to get onto the website and get access to the reports I created with SSRS?
Users will need 2 things from you to access the site: the server name/address, and a means of authenticating to it. By default, authentication is handle via Windows domain auth (which you can change, with varying degrees of effort...).
Do I upload the reports in .rdl on my report site manually or do I deploy it from VS?
It actually makes no difference in the end; do whichever you find easier. (There are also plenty of other ways to deploy reports, such as through powershell!)
How do I turn my '127.0.0.1/Reports' into a public site for other user's access?
Well you're halfway there - At this point, you could probably open up your firewall (port 80, maybe 443 depending on your config), and have people connect to your computer via IP or hostname - for example, if your computer's IP was 12.34.56.78, they could visit 12.34.56.78/Reports/ and access the site. If you have a means of creating a URL and pointing it to your SSRS server, you might need to open the configuration manager again and bind that URL to SSRS.

How do I know which database is configured SharePoint?

I'm in a machine that has already SharePoint installed, so when I started the SharePoint Central Administration to config, this message appear to me: "Can not connect to the database configuration."
How do I know which database is configured SharePoint?
Normally the Admin database is created using the naming convention SharePoint_AdminContent_{GUID}. However if there's more than one, you'll need to use SQL Management studo or other tool to look inside the DBs, look for a table called "DatabaseInformation" which will contain two items, look in the AlternateAccessMappingXML entry and look for the XML tage IncomingUrl, that should help you narrow it down.
Or just use the SQL profiler and watch for connections.
By default SharePoint will install the Database on the same machine as the web server, but you can ask whoever installed SharePoint on the machine.
Anyhow, most likely it's not relevant and something else is the problem, follow the resolution methods described here and you'll probably have it fixed.

Resources