My organization does not have QlikView WorkBench license. My question is, what are the limitations I will run into as I start using IIS with QlikView instead of QlikView web server.
Is it necessary to have workbench installed with license to be able to develop a web application using Visual studio to display QlikView files?
Currently we have QlikView Web server(non IIS install). If I migrate to IIS install, I just want to know if I may get stuck without a QlikView workbench.
Searched a lot on the net for this info but in vain, so please give some details. I am well versed with Javascript, Ajax, HTML and so on but not yet used them with QlikView .
To answer your questions.
There aren't any limitations, using IIS over Qlikview webserver is more of a personal preference, as most Qlikview experts do not have knowledge in IIS, if you are already familiar with IIS it might just give you an advantage in the future.
You do not need a workbench license to use IIS.
Here is a presentation to get started with Qlikview and IIS, although the presentation is of older versions the basics and fundamentals stay the same:
https://community.qlik.com/docs/DOC-2943
Related
I am trying to find a way to deploy a ASP.Net Core (version 6.0) Website onto a server provided by a domain provider.
The server is Debian and as far as I can understand I cant change things on the server except uploading the files required for the Website.
I have created a simple website in Visual Studio 2022, using MVC Framework. It has no database as it is not required.
So the issue is how would I go about deploying the website onto the server, I understand I have to change my files to be Debian compatible but also I read up on the documents from Microsoft, and they insist I need to install .Net onto the server. Which I cant seem to do.
I tried reading through other solutions but there doesn't seem to be any updated answers.
I am new to this so sorry if this has been asked before. but any help would be welcome.
Is it allowed to build a .NET service for ReverseGeoCoding (LocalLocatorTask) which runs on a server?
We would like to build a service which translates GPS-coordinates to addresses using ArcGIS Runtime SDK for .NET. We are already licensed to use the Standard license needed for LocalLocators.
But now we've heard is not allowed to build server applications, is this true and where can I find this in the terms and conditions?
Thanks,
Frederiek
No it isn't allowed (though I can't find the exact wording) as it basically negates the need for ArcGIS Server or the need for multiple user accounts when the same functionality is deployed as an app.
If you can't use it as an app or use ArcGIS Server / Online directly and really need a windows service then you will need to write your own code to do it. If you can use ArcGIS Server services from the windows service I have a project that manages the REST calls at https://github.com/davetimmins/ArcGIS.PCL
This is currently prohibited by the license agreement, though there is no technical reason why it wouldn't work. It is not tested or certified for services environments by Esri development teams.
I had a engineer design our .net application back in 2009, my guess is that it was coded using visual studio, and all I have is the installer application. We have been using it on our 1 or 2 local client machines very well for the past few years, but now I want to move this front end to the cloud. Instead of installing it as an application on our windows 7 machines.
It is a very simple application used in our small warehouse that keeps track of cargo/shipments etc. It uses Sql Server 2008 Express as a backend which is stored locally.
I know how to get the database in the cloud, their are many options for that, using Amazon or Azure, but how do i get the local client application to the cloud?
I dont have access to the visual studio code, i just have the runtime executable file..
I am sure there is no way to do this, and many of SO users will say i need to re-write the front end.
I have tried to contact the developer and they hav since closed down. Is their anyway i can run this in the cloud?
I welcome all options and solutions!
Thanks.
I believe you have two options for hosting this application:
If you are able to configure the database connection string, you could host the database in the cloud, and distribute the application to your end users. However, you've already stated that you know how to move the database, so I assume this isn't an option.
The only alternative is to run the entire application on a cloud server, and send the user interface to a client using terminal services. This makes it appear as if the application is running locally on the user's computer, while it is actually running on the server.
For an off-the-shelf solution to achieve this, you could consider using Microsoft's RemoteApp Azure service. I'm sure there are other similar offerings available.
I'm quite a newbie, just trying to learn some new things. I've recently started learning c# etc and I'd also like to create a new SQL Server database using SQL Server Management Studio.
The thing is that for some reason I am not able to connect to the server. I might have done something wrong (or haven't done something that I should have done). Been researching the problem a lot on google and I found some tips but I still can't make it work.
I even found some installation tutorial in here: http://www.sqlcoffee.com/SQLServer2014_0005.htm and I only noticed that I used some different options (I used default, didn't change anything) like for example in "Database Engine Config" I chose "Windows authentication mode".
So that's what I get: http://imgur.com/2ftOdSB
Also I think I may have some problem with services, because when I go to the server configuration manager, the list is completely empty.
Thanks for any tips. If I don't solve this, I can always uninstall SQL Server Management Studio and reinstall it - this time following the steps in the tutorial. Hopefully that wont be necessary so help me please:)!
I've had a look at the link you posted about the installation instructions. As I mentioned before SQL server enterprise (database engine) won't install on a non-Server OS, You'll need at least Windows Server 2008. Have a look at msdn.microsoft.com/en-us/library/ms143506(v=sql.120).aspx for the system requirements. During the installation there must have been an option to install the database engine, but it was probably disabled because of your OS.
I suggest you uninstall 2014 Enterprise and download SQL Server 2014 express microsoft.com/en-gb/download/details.aspx?id=42299 and make sure you select database engine as part of the installation.
If you want to get into SQL, I would suggest trying out MySQL first. I've utilized it a little bit and found it to be fairly simple with a decent amount of documentation. This version of SQL will still function with various languages. It doesn't utilize Windows authentication, but rather lets you set a root password specific to the database itself. I don't know if your software is similar to that but there may be an option to not use Windows authentication and instead authenticate within the database software itself.
I am considering switching to a co-located solution running a DNN (DotNetNuke) installation and an email server that mostly just does alias forwarding. I think I can get DNS services outside of this colocation box - but that could be an issue.
I am running this website for a non-profit group and trying to stay inexpensive. Will Windows Server 2008 Web Edition be acceptable for running all of this? My research so far says it will but I am looking for anyone with any experience running web edition and what sort of pitfalls does it have?
I was going to install SQL express as the backend for the DNN site. Indications are that you can't connect to SQL from outside the Web Edition box. Does this include SQL Management studio?
Any assistance or advice on this would be appreciated.
Update:
Still looking for any specifics with Windows Server 2008 Web Edition
We tried running DNN on Windows 2008 64-bit and 32-bit a while back. Not a great experience with intermittant failures and application hangs. We had to revert back to Windows 2003.
This was on a moderately loaded site. If you want to give them any sort of guaranteed uptime/availability I would recommend Windows 2003.