I need to migrate my Glassfish 4.1 from Windows Server 2008 to Windows Server 2016.
I've copied the Glassfish folder and pasted it in the new Windows Server 2016, but it is working only locally (http://localhost:80/myWebApp); if I try to access myWebApp via browser through another computer (http://172.29.13.228:80/myWebApp), it doesn't work.
After adding the Web Server feature (using the Server Manager), then I can access normally a IIS page via browser, which means the web server is working; but it still doesn't work when I try to access the Glassfish.
Does anyone knows what feature to add or what to configure in the Windows Server to get access to the Glassfish ?
I've researched and find out that I just needed to create a rule on the firewall on Windows Server and give permission on desired ports, there's no need to add any Windows web server feature.
Related
I try to install an ASP.NET application to IIS on Windows Server 2019.
The application is built against NET 4.7.1, and it works just fine on IIS in Windows Server 2012 and 2016.
However, when I try to install it on new server running Windows Server 2019, the problems starts from the configuration phase.
Specifically:
I copy the app with all the files in a folder on new server (2019)
I create the appPool, using ApplicationIdentity, enable 32 bit access
I create the web application, set to path the folder, set the appPool
to my newly created apppool
I set the permissions to read / write access for IIS AppPool\DefaultAppPool
But I cannot even do any further configuration in IIS Management.
When I try to edit any config option (default page, etc, etc) IIS manag gaves me error that it cannot access the web.config file
I even set temporarily access rights to web app's folder to full access for everyone (!!!) - no success.
Any idea what can be?
It's possible that was an error with creating the VPS image.
I recreated it and after that everything went ok
Its been ten years since I worked with IIS. Windows Server 2008 is new to me. Now, I need to install a private-bower service on Windows Server 2008, and I'm not sure if I need IIS 7 and iisnode or if there is a better way.
Running private-bower, starts a server at http://localhost:5678/
What is the best way to expose that as a service for an internal network on Windows Server 2008?
Or in noob terms: how would I convert http:localhost:5678 to run in Win Server 2008 and IIS7?
I can install node/npm. So using node is an option, within IIS using iisnode and IIS7 (link below) but would I need to? Is there an easier way in IIS?
I'm not sure where to start to configure the :5678 port to be an external service, and how to keep it running, in a remote desktop login.
The links I've been using are:
private-bower: https://www.npmjs.com/package/private-bower
Node on IIS:
http://admin-ahead.com/blog/node-js-installation-windows-2008-r2-server/
iisnode:https://github.com/tjanczuk/iisnode
But I need some help with Window Server 2008 and IIS 7, possibly a link describing ideal service configuration. Thanks.
Found an example that is for Windows Server 2012:
The recommended way to install private-bower as a Windows Service:
https://github.com/Hacklone/private-bower/wiki/Install%20as%20a%20Windows%20service
I want to deploy a Website which i have created using Microsoft Visual Studio 2008 Express Edition onto a remote server having Microsoft Windows Server 2008.
I don't know anything about deployment. I want to know what are the things required on the Server in order to make the website work for all the client machines.
i had used ajax toolkit, VisualStudio2008 Express Edition and mysql on my developer machine.
One method which i tried is using copy website,it dint work,may be because i don't know the proper way to do it.
Please help me to deploy my ASP.net website.
The first step to setup your website on Windows Server 2008. Is to setup IIS. Installing IIS7 on Windows Server 2008.
Once that's completed, setup your SQL server on either that machine or a different one.
Depending on your setup. Copy your website files to your web site directory. By default it's [Drive]:\inetpub\wwwroot. You can change the target by virtual directories.
One note, you will need to install AJAX on your server for it to run correctly.
I have a webApp in my IIS 7.5 on windows server 2008 now I need to move this particular web app (not all of them) to another IIS 7.5 on the new windows server 2008 R2.
Can anyone please suggest?
thanks
Web Deploy is probably the best, it can do it server to server (ie live sync/migration) as well as allow you to generate a package that can then be installed in the other server:
http://www.iis.net/download/WebDeploy
It includes GUI (extends IIS Manager) as well as command line options, can do it over HTTPS or directly using the IIS configuration APIs. It supports moving configuration, content, GAC, DLLs, Database, Certificates, SSL settings and more.
My asp.net web app is hosted on this URL on my local machine:
http://localhost:45433/
I want to access the same application from a different computer on the network. I tried replacing the localhost with my IP but it did not work.
any ideas!
UPDATE 1:
Now, I am getting this error:
Login failed for user ''. The user is not associated with a trusted SQL Server connection.
If your application is hosted using Visual Studio's built in web development server then this server does not allow remote connections. It is for testing purposes only and accepts connections only from localhost. In order to access your application from remote clients you might need to deploy it to IIS.
First, add the application as a virtual in IIS, and as long as you can access the machine on the network, you can do:
http://<machine name>/<virtual>
I do that at work, where I can access my co-worker's web site.
HTH.
That looks a lot like a url used by the development web server in visual studio. That web server only responds to requests from the localhost. It won't work for other requests from other machines on your network.
You need to install IIS on your machine (must be a Pro version of Windows) and deploy to that IIS install to share your app on the network.
I don't think the built-in version of Cassini (VS debug server) allows remote connections.
However, the UltiDev version, built off of the same code base with a few enhancements, does, and is a much lighter-weight install than IIS (especially if you can't find your OS install DVD). It also integrates nicely with Visual Studio for debugging purposes.