hozawa Posted March 5, 2014 Share Posted March 5, 2014 There's a buildomatic targets to drop sugarcrm-db and foodmart-db from the database.If there any way to delete resources created by executing "js-ant import-sample-data-pro"? Link to comment Share on other sites More sharing options...
Solution fcerbell Posted March 5, 2014 Solution Share Posted March 5, 2014 Hi,I dont think that there is such a command. Furthermore, you will also have to remove the JNDI connections in the META-INF/context.xml file and in the copy of this file made by Tomcat in his configuration folder. RegardsFrançois Link to comment Share on other sites More sharing options...
hozawa Posted March 5, 2014 Author Share Posted March 5, 2014 Thanks. I thought so. That means if somebody installs the demo, the easiest way to remove it is to re-install JasperReports Server again. There should be a message warning not to install the demo in the production server. Link to comment Share on other sites More sharing options...
fcerbell Posted March 6, 2014 Share Posted March 6, 2014 Well, you dont have a lot of folder to remove from the repository, you have two schemas to remove from the database and about 15 lines to remove from one file. It seems to be feasible. But, reinstalling would be a good option as you missed some important informations from the install guide. You would have the opportunity to better understand and it would improve you knowledge on JRS. There is a note in the install guide against installing the packaged bundle in production. So, you have to execute the manual WAR installation which describes in detail all the steps. You should not install a product in *production* before reading the whole install guide. You are talking about production, not dev, not test, ... Link to comment Share on other sites More sharing options...
hozawa Posted March 16, 2014 Author Share Posted March 16, 2014 I didn't install it nor doing installation. Just been give a "situation". The installation guide is too much pages to read and confusing to many people because it mixes bundled installation (for demo and test) with war installation (for production). I've just rewritten the Installation Manual for Development and Production Use so people won't keep making this mistake. I want to eliminate using the bundled installation altogether because when people see something that "seems" to be working, they tend it continue using it. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now