Originally Posted by
Norm
(...snip...)It's been a weak point in my experience. Will be interested in how it's done.
Norm
Usually, distribution of the jar is the first approach. The tool I am using is rich with features the advanced worker can utilize for time-effectiveness and blunder reduction. Eranga answered the first part of my question.
Niveditha: Which is the Server in which you want to deploy?
Originally, test on Tomcat - locally - using NetBeans idea of how that should go. Try to do everything using the fancy tools and reading as much as I can. Test moderately, then deploy to a Tier-1 commercial server I have hired. These guys know what they are doing. I have Tomcat already up, but do not know how to restart - I was told yesterday how to do it, but did not gain any footing on actually being able to do it. In lieu of doing what I was instructed, I put up a xml file in WEB-INF.
What I am trying to do here is grasp how NetBeans wants to do it. I am able to compile a class file, I will look in dist this morning. I can put the jar file in libs on the commercial server. What my goal here seeks to achieve is grasp all the xml and so on that should wrap the application. I have several apps I want to have run individually, as well as a default that wil come up if nothing else is found.
edit: What I ended up doing is putting the ( I found the .war file !... horray ) in webapps.
I also put up a .jsp in public_html to call the servlets I had compiled today. Not much traffic so I can test in the intended directory for a few days.