I have just completed a project as part of a college degree.
However I would like to deploy the project and make it live.
I am unsure of how to do this as I have never done it before?
I know I need to buy a domain name and some server space to host the project.
If anyone can point me in the right direction that would be great?
Thanks in advance!
There are a few inexpensive hosting options such as Slicehost or Linode that will let you run Tomcat, Jetty, or whatever servlet container you choose. You may be able to find an even cheaper solution by looking for hosting providers that run Tomcat but you won't have as much control. So, for example, you could get the cheapest Slicehost account which gives you full access to your own server. Install Tomcat, a database if necessary, and deploy your war. At that point you'll be running with an IP address. Register a domain name and point the name servers to the Slicehost name servers and you'll be 'live'. You may want to run Apache in front of Tomcat and you should probably learn about securing your server (Shorewall is one option), but this should get you started.
Related
I'm new to web back-end and about to deploy a website(with both backend and frontend). As far as I know, If you own a server, you can install whatever software you want. But how about when you have a free hosting, is it possible for you to install softwares like Tomcat, Mysql,etc yourself.
Ps: as far as I know, hosting is a folder inside a server, so in my opinion, you'll depend on the server which contains the hosting. Still I get confused.
I highly appreciate you all for spending time read this post.
Hosting is just deploying your applications and then serve them to the internet. If you are using free hosting, I suppose that they must be managed service which mean you cannot do anything except the functions the hosting provider provide. In my opinion, it is better to get your own vps if you want to control your server fully. You can just install software you want in ubuntu or other supported os, and then serve your port to public. If you would like to try, you can use some cheap vps provider first like Contabo VPS.
I have a VPS, Cent OS 6.4 64bit
I want to create a panel (like cPanel) and I want to make it accessible by opening a port (serverip:2082 for example). I have created php files of my own panel but i don't know anything about linux services.
What type of code must I make and where can I put it?
Thank you in advance!
no offense, but if you really don't know about linux service you are 99% away from creating your own panel. You first need to understnad that Cpanel not only modify system files to allow hosting and managing database, but it also do all these without playing with system security.
But to start you need a web server that will host your Cpanel. I prefer it to be different from your webserver that host your website, reason? What if your default apache is inaccessible or crash, your panel will crash with it. Then you need to learn Mysql, or database you want to manage through panel, DNS binding, Name servers, regular expression to manage text files of configuration etc.
I know all these because I already built a Cpanel like application, and know it is not easy job especially with this level of question you asked.
I created my first Java EE application (GWT + Hibernate). I want deploy my application on a Tomcat web server.
Could you give me a step by step tutorial?
You can start with Google App Engine + GWT tutorial if you are trying out deploying into Google Cloud - https://developers.google.com/web-toolkit/doc/latest/tutorial/appengine
This question is massive so I will try to bring it down to some steps that need some research to implement.
1st. You created an application using GWT and Hibernate. That means that you need some kind of a web server that understands java and can re-write the logic from java to javascript (for the clientside), and also connect to the database on the serverside and retrieve the data for the client.
This web server is tomcat so what you need is:
A computer that will work as a server. This could be your own machine or some server you can buy as a hosting solution. Buying something like this requires research and effort on your part and cannot be explained here.
A version of Tomcat or Resin or any other web server that understands java
A domain name. These can be bought from sites like this one, but there are some free ones around the web. They require static ips that is you cannot use them from a home line that changes ips. Even without a domain name you can host your site on the server but you need to access it by writing the machine's ip instead. - optional - A temporary solution would be to use some kind of dynamic dns service on your router.
After having set up tomcat (you might want to give port 80 to tomcat) and the server you can host your application by uploading the war file. You can make a war file from gwt by following the instructions here
To upload the war file you can use the tomcat manager interface, or you can connect to the server and place it manually in the folder used for the web applications.
I know that each step propably needs as much if not more explanation by I hope I cleared the area a little bit here.
For a variety of unfortunate management reasons (budget constraints etc.) I, the developer, have been put in the position to deploy the app in a production environment. The catch is that I don't have any experience in production EJB application server deployment. That said, they are aware that there are no guarantees of success.
The context:
The dev server runs on the latest version of Netbeans with Glassfish v3, on a mac machine
98% / 99% uptime is ok, there are no financial/critical transactions
It is a client/server EJB 3 app, and the web tier, business tier, and resource tiers currently run on the same machine.
I have the liberty to choose the hw/sw infrastructure
Load estimations: 10 simultaneous connexions avg, rare 200 peaks
The outbound public data is text/small pics (it's for iPhone clients), inbound HTTP text only
Basic maintenance will be taken care of (backup, server reboot, etc)
My questions for production deployment:
What are the must haves infrastructure-wise? Minimum system specs etc?
Is it ok to keep Glassfish v3?
Which configuration aspects of the server should I focus on?
Worst case scenario: if I deploy the same software infrastructure (Netbeans/Glassfish v3) as during the development, would the server keep up?
Any piece of advice would be most welcome. Thanks!
For the architecture, you can start small with just a single GlassFish instance with no front web server (GlassFish has one built in that is very capable). If you can wait for the release of GlassFish 3.1 you'll be able to add instances (clustered or standalone) and offer scalability and centralized admin.
Most production instances of GlassFish I've seen run with 1GB-2GB of JVM heap (-Xmx) but your mileage may vary if you load lots of data in memory or if you use some frameworks. If you want better reliability, having them on separate machines is a plus obviously. With two instances on the same machine you can offer continuity of service if one instance fails (but not if the machine fails).
I'd suggest scripting as much as possible the provisioning of the resources (connection pool , JDBC datasource, etc...) and applications using the "asadmin" command-line tool and try to not use NetBeans on the production platform.
Benchmarking with simulated load sounds like a wise thing to try to put together before going live and this survival guide will probably come in handy.
You don't mention the database. Isn't there one?
I suggest the following:
Not a Mac expert but I'll say go with 6GB or more RAM
HDD space is not a problem these days
Do not know much abt Mac Processors (watever eq of dual core etc)
Personally I have not used GF3 in Production but I hope it's stable now so you should be ok.
System Architecture:
Receive all HTTP requests on some web server (Apache or Sun web server) and load balance with your Glassfish server(s).
Now depending on your physical (or virtual) machines create instance of Glassfish Application Server on each machine. If you just have one machine then create atleast 2 instances of Glassfish. This will help to put one node down for maintaince and other to keep going.
As far as deployment is concern make sure you stop debug logs and fine tune JPA logs etc.
Use Ant or other scripts to deploy code and taking backup of existing code.
I hope this will help to kick start and rest you can ask or solve as you go along.
Good luck.
I know this has some crossover to Serverfault.com but the advice on meta.stackoverflow was to ask it here (first) as it requires a .NET dev to answer more than likely.
I am having some problems publishing to my website a Click Once App, I am getting an error message saying (something like) IIS not running, I'm not currently at home to give an exact error message, i'll edit later if it is required to answer this question.
My ISP is lunarpages the plan I am on is this one IIS is definitely running as I have BlogEngine.NET running just fine. Anyone know what is required configuration wise (both server and client) to make this work?
The files that the ClickOnce publish create can be run on just about any web environment (include Apache/Linux.) It simply generates an html page along with the application manifest and your application files. Maybe you can deploy to a local folder and upload the files to the server?