I am developing my first web application with EJB, JSF and JPA. I use rational developer for developement and test, and our server is an iSeries with websphere 8. I do not have access to the test and production server, i can only manage the one I locally installed for developement purpose.
So now, my web application is working perfectly on my local installation, but I can't make it work on the production or test server. I produce the EAR with Rational Developer, our sysadmin publishes it on the server, the logs show no error (everything seems fine), but when I then try to reach the application via browser, i get the message
404 not found: requested url was not found on this server
In locale, i have the application installed under
http://localhost:9080/<contextroot>/pages/login.jsf
I tried several different urls but I always get that error message:
http://<production_server_url>/<contextroot>/pages/login.jsf
http://<production_server_url>:80/<contextroot>/pages/login.jsf
http://<production_server_url>:9080/<contextroot>/pages/login.jsf
http://<production_server_url>/<contextroot>/
I asked the sysadmin to send me the screenshots of the steps he goes through when installing the app on the server to see if there was some difference in the configuration, but everything is the same. The contextroot is correct.
We have other web applications that run on the servers, but those are simple .war files, this is the first EAR we try to deploy (i.e. as such, websphere incapuslates war files into ear projects in order to run them)
We have no idea what to do, can anyone help?
What bothers me the most is that the deploy itself goes well, the app is installed and running, I just cannot reach it
Thanks
Solution: The application server was running on a different, non-standard port. As suggested by #Jarid i found the correct port under
<profile_config>/cells/<cellname>/nodes/<nodename>/serverindex.xml
at endpoint WC_defaulthost. I can access the application at
http://<production_server_url>:>WC_defaulthost_port>/<contextroot>/pages/login.jsf
Related
I hope its okay to ask here, I could not find a specific existing thread for this.
I have developed a Blazor server application in .NET 5 for a client, and it has been hosted on azure app service (on Linux plan). We have several environments (Dev, test,prod), and the deployed app works as intended in all environments, except when deployed to the production app. It works fine for a while, but at a point something happens and the browser dev tools console says 404 not found for all the css and script files. Because it is .NET 5, application insights are not supported in Azure.
In the Program.cs's CreateHostBuilder I have added the UseStaticWebAssets, and in Configuration in Startup.cs app.UseStaticFiles.
And as mentioned, it works perfect in all other environments, and for a while it works good in production after restarting the App Service.
Any idea what might be causing this?
Thanks!
Morten
I put a basic, no frills node npm-express blog site up on a azure website and the IIS load balancing or just iisnode itself seemed to cause issues running the app.js. Running outside of IIS didn't experience any issues. No websockets, just express using vash templates.
The issues I ran into are:
Using web deploy and some node_modules intermittently not deploying. npm lwip for instance would work at first then wouldn't if deploying again. Sometimes other js and vash files would not update also.
When using the site there was a plain vash templates section (the public facing side) and a login side of the site. The simple one page public facing side would intermittently create a 500 error. One out of every three request would do this. No logs generated and all logging was turned on. The error was from iisnode and not node itself.
Using visual studio 13 with all the latest updates, remote debugging simply didn't work. Basically in the dark. Oddly the logged in portion using npm-passport-local worked but that never changed domains when using. It was only the pages on the public side that this would happen. FYI, the public side had multiple domains and various sub domains pointing to the site. All entered correctly in the azure portal and would work with the intermittent 500 error. The page had links to other blogs with full urls, hence the domain would change. Which should be an issue but I suspect had something to do with it.
I ended up having to create a azure vm and install node on it myself to get the site working without the use of IIS. FYI, running the node site locally on my sand I never encountered any issues either.
Has anyone else experienced issues like this using iisnode and did you find a work around for this?
I suspect it may happen when multiple domains are used for the same instance.
Today I discovered Sails and have been watching a few tutorials. One thing I can't seem to work and find out is how to deploy it to a standard web server, like for example via an FTP client. I've seen the tutorial on how to deploy it to a Heroku account, but this isn't really what I'm after, as we already rent a Windows 2012 server.
I've got a feeling I'm completely missing something here, so can someone please help me out :)
Many thanks
You can transfer all files via FTP to your Webserver (include all node-modules).
But you have to make sure NodeJS is installed on your server. Than login into your Server (e.g. via SSH) and start your Sails-App (node app.js)
I have successfully tested the vline-node example locally, but would like to push it out to a server. I have tried to install the example as an application on an IIS8 website, placing the example code under wwwroot. I have done tried this both within the root and inside a virtual directory, pointing to the views folder. I am able to login to the application from a browser on the server, although, since javascript is turned off on the server browsers for security, so functionality is missing.
However, when I try to access the site from a remote browser I am not able to login. Actually, I can see that there is something wrong with my paths, as the include files are not found.
The more I've thought about this the more confused I've become. I'd like to run this under IIS, but wonder if that makes sense. Can someone offer a clean solution for hosting the vline-node example on a Windows Server, ideally under IIS?
Since you are using the node example, you'll need to make sure that node is actually running on your IIS server. Here's a SO response that may be helpful: How to run Node.JS server for a web application?
Note that in our node example the "main" file is vline-node.js, so use that in place of the app.js that is mentioned.
i have a webapplication which is realized with servlets running on a tomcat server. This web application should also include a realtime videochat, for which i have choosen easyrtc. I have setup the easyrtc server already (via nodejs) and have changed the default port to 9090, to make it different from tomcat. It works just fine when running standalone, but i have problems to integrate it within the tomcat web application (since the easyrtc files are searched under the tomcat's port, which is 8080). I have read the manual but i have not yet found a solution for my requirement. Can someone point me in the right direction, probably providing some best practive? An iframe would be no alternative, since i need to share some javascript variables among the different pages on my web app.
Thanks in advance,
fredddmadison
I have found the solution:
When initializing the easyrtc on the client side, the following call can be used to set the url for webrtc:
easyRTC.setSocketUrl(some_url);
and everything works as expected.