I am working on a project to deploy a Java web service using Axis that will ultimately be hosted by an IIS web server. We have generated the stub Java classes using the WSDL2Java Axis utility. Our next step is to deploy the SOAP web service to IIS. Does anyone have any advice on the best way to approach that? It seems that Axis is meant to be used more with Tomcat versus IIS. Can you deploy Axis generated SOAP web services to be hosted by IIS?
Related
As working on converting .NET Core web api to .NET Framework, I had options of couple different ways of achieveing it and I end up reading below links and decide to go with OWIN in IIS.
Difference between OWIN and IIS
ASP.NET Web API 2 hosting differences
Getting started with OWIN in IIS
https://learn.microsoft.com/en-us/aspnet/aspnet/overview/owin-and-katana/getting-started-with-owin-and-katana#host-owin-in-iis
Before I actually put myself into this route, would there be any new updates on .NET Framework (not .NET Core) which beats this solution make it look old?
I'm working on a app that is hosted in Azure.
The app is a web-app based on node.js/express.js.
Is it running on/in a IIS server since it is hosted in Azure?
My app does not use the iisnode package. But i wonder if it is inherently running on IIS since it is hosted in Azure?
Also: As i understand at the moment, IIS-express and express.js is two completely different environments for hosting web-servers.....?
Just according to your description, it seems that you were talking about hosting a node App based on express.js to Azure WebApp for Windows.
Yes for hosting Node.js app in IIS on Azure WebApp for Windows, you need to use iisnode (a native IIS module) to host node.js applications with the web.config file in IIS on Windows. For more details, you can refer to the wiki page iisnode wiki of GitHub repo Azure/iisnode to know what iisnode is, and to know how to host it with a web.config file in IIS via the other wiki page Using a custom web.config for Node apps of GitHub repo projectkudu/kudu.
However, No for Azure WebApp for Windows, because you also can use IIS as a reverse proxy server to handle a Node app via the default port %HTTP_PLATFORM_PORT% specified by Azure WebApp like the blog Running java jar file to serve web requests on Azure App Service Web Apps for Java said. But generally, it's not a recommended way.
Meanwhile, No for hosting Node app on other Azure services, such as Azure WebApp for Liunx, Azure VM, or Azure Container services, these services based on Linux do not require IIS, so the iisnode module also be not absolute required.
I have developed a web application using .net mvc and WebAPI as follows:
SOLUTION
|—— WEB.API Project
|—— Web Application Project
wanting to deploy to my web server. It is possible to deploy both projects on a single web site (in iis)?
Do I need to create two separate sites for the web application and web api (in iis)?
Deploy your mvc web app as an web site & add a virtual directory under that web site & point your web api. This is the way to use 2 application under an web site.
I am creating app which uses Identity 2.1.0 framework in .NET. I started project in Visual Studio 2015 as Empty Web App (template). Now, I use Microsoft.AspNet.WebApi.Owin, and also Microsoft.Owin.Host.SystemWeb NuGet packages in my project. I understand that OWIN is a specification made to avoid monolithic frameworks and to specify how smaller application components interact with servers. However, I have requirement to deploy to Azure App Services.
I have found examples (blogs) where people deploy OWIN Web Api app as self-hosted to the Azure Cloud Services worker role. But I don't want this, as I don't use Cloud Service.
Since I am using Microsoft.Owin.Host.SystemWeb, am I going to be able to deploy this to Azure App service (which I assume manages internal IIS instance) ?
.NET ecosystem newbie here - so please excuse me for any possible redundancies in the question.
Microsoft.Owin.Host.SystemWeb is designed for hosting in IIS and all Azure App Service web apps are hosted in IIS, so this is exactly what you want (In fact, self-hosting likely won't work with Azure App Service).
I am in the process of building a Web based client for a Server application which is running as a Windows Service. The server application currently has a Windows Form based Client Application written in C# and the idea is to obsolete it and provide a new Web based Client Application. The Server application will be exposing REST based APIs and the Client Application would be using the REST APIs to communicate with the Server Application. (Currently the Server App exposes SOAP based endpoints which are consumed by the Windows Form Based App)
The Browser based client application would be written using Angular JS. The Client Application would be used by at max 10 concurrent users. The App is targeted for system administrators and would be used inside the enterprise environment.
Another requirement is to integrate Active Directory Authentication for the Client Application. So given the performance requirement and authentication requirements, I am wondering whether I should use IIS for hosting the Web Application. Or should I just use the existing Server to self host the web pages.
If at all I go with Self Hosting option, would Katana Self host be a good option? Or should i use WCF Rest kit to serve the pages?
What are the performance implications of using a Self Hosted mechanism for hosing the Web Application compared to IIS?
Any suggestion would be greatly appreciated.
WCF REST Starter kit is still in second preview 2 version from 2009 so I'd be pushed to recommend using it.
The question of IIS or self host depends, do you need the features that IIS has out of the box like logging, restart after failure, etc?
My suggestion would be to use ASP.NET Web API (or Nancy, which is an excellent choice too) but keep your hosting layer separate from your application layer so you have the flexibility to decide how you host your service later on.
The second suggestion is performance test early on, pick a hosting mechanism and measure how the service copes under load - you may find out that you're worrying about something that you don't need to.