mrcaffeine

Use caseIt is advisable that you do not run multiple JasperReports Server in a single application container. However it might be desired for some test and development scenarios. The following article outlines required actions and refers to the installation guide when required. I cover the installation with the war-bin installer package as this is advisable for customized installation processes and non-standard environments. The guide will cover both CE and Pro version of JasperReports Server and applies to all versions from v4 on. In the sample use case I'll work under assumption that I'm a developer who is embedding JasperReports Server into another application. For that I have 2 branches - my development branch with JasperReports Server modifications and my stable branch into which I merge verified modifications. The reader should be familiar with JasperReports Server war-bin installer as well as with Tomcat or Glassfish application server. As database postgres is used, for other database configurations please see install guide and provided samples for reference. Example: glassfish 3.1.2In order to have 2 JasperReports Server running on one Glassfish Server instance you should create for each instance a separate glassfish domain. This can be done with glassfish command line tools. Install on Glassfish ServerThis part will outline how to create 2 domains for JasperReports Server. cd <glassfish home>/bin Create domain for development instance that should be running on portbase 5800# create a domain from command line ./asadmin create-domain --portbase 5800 --checkports true --user admin --nopassword true jrs-devel # add admin password ./asadmin --user admin --passwordfile <path to password change file> change-admin-password --domain_name jrs-devel # starting domain for additional settings ./asadmin --user admin --passwordfile <path to password file> start-domain jrs-devel # configure glassfish to allow remote access ./asadmin --user admin --passwordfile <path to password file> --port 5848 enable-secure-admin # stop glassfish domain ./asadmin --user admin --passwordfile <path to password file> stop-domain jrs-develCreate domain for stable instance that should be running on portbase 6800#run same commands as above, just change port and domain name ./asadmin create-domain --portbase 6800 --checkports true --user admin --nopassword true jrs-stable ./asadmin --user admin --passwordfile <path to password change file> change-admin-password --domain_name jrs-stable ./asadmin --user admin --passwordfile <path to password file> start-domain jrs-stable ./asadmin --user admin --passwordfile <path to password file> --port 6848 enable-secure-admin ./asadmin --user admin --passwordfile <path to password file> stop-domain jrs-stableConfigure buildomaticDevelopment instancecreate a new file gf_devel_master.properties in <jrs war-bin dir>/buildomatic # app server settings appServerType = glassfish3 appServerDir=<glassfish home folder> glassfishPort=5848 glassfishDomain=jrs-devel glassfishUser=admin AS_ADMIN_PASSWORD=<password> # db settings dbType=postgresql dbHost=localhost dbUsername=postgres dbPassword=postgres js.dbName=jrsdevel #other settings diagnostic.jmx.name=jrsdevelNow you can run installation process ./js-ant gen-config -DconfName=gf_devel ./js-ant create-js-db -DconfName=gf_devel ./js-ant init-js-db-pro -DconfName=gf_devel ./js-ant import-minimal-pro -DconfName=gf_devel ./js-ant import-sample-data-pro -DconfName=gf_devel ./js-ant deploy-webapp-pro -DconfName=gf_develhttp://localhost:5880/jasperserver-pro should be available after deployment. Stable instancecreate a new file gf_stable_master.properties in <jrs war-bin dir>/buildomatic # app server settings appServerType = glassfish3 appServerDir=<glassfish home folder> glassfishPort=6848 glassfishDomain=jrs-stable glassfishUser=admin AS_ADMIN_PASSWORD=<password> # db settings dbType=postgresql dbHost=localhost dbUsername=postgres dbPassword=postgres js.dbName=jrsstable #other settings diagnostic.jmx.name=jrsstableNow installation process again ./js-ant gen-config -DconfName=gf_stable ./js-ant create-js-db -DconfName=gf_stable ./js-ant init-js-db-pro -DconfName=gf_stable ./js-ant import-minimal-pro -DconfName=gf_stable ./js-ant import-sample-data-pro -DconfName=gf_stable ./js-ant deploy-webapp-pro -DconfName=gf_stablehttp://localhost:6880/jasperserver-pro should be available after deployment. ConclusionsYou have independent JasperReports Server instances installed on one glassfish server, both domains can be operated independently. For CE edition of JasperReports Server it is same process, please refer to documentation for specific manual installation commands. TomcatTomcat as application container has not availability of fine granular control about separate web applications. In order to have multiple parallel instances on tomcat there are 2 choices: install 2 tomcat and configure them to run on different ports.deploy JasperReports Server into one tomcat and manually configure tomcat as required.Multiple tomcat instancesDownload and unzip tomcat package. Configure ports for http, ajp and shutdown as outlined in tomcat configuration. Apply other configurations as desired and required. Development instancecreate a new file tc_devel_master.properties in <jrs war-bin dir>/buildomatic # app server settings appServerType=tomcat7 appServerDir=<path to devel instance tomcat> # db settings dbType=postgresql dbHost=localhost dbUsername=postgres dbPassword=postgres js.dbName=jrsdevel #other settings diagnostic.jmx.name=jrsdevelNow you can run installation process ./js-ant gen-config -DconfName=tc_devel ./js-ant create-js-db -DconfName=tc_devel ./js-ant init-js-db-pro -DconfName=tc_devel ./js-ant import-minimal-pro -DconfName=tc_devel ./js-ant import-sample-data-pro -DconfName=tc_devel ./js-ant deploy-webapp-pro -DconfName=tc_devel http://localhost:<devel port>/jasperserver-pro should be available after deployment. Stable instancecreate a new file tc_stable_master.properties in <jrs war-bin dir>/buildomatic # app server settings appServerType=tomcat7 appServerDir=<path to stable instance tomcat> # db settings dbType=postgresql dbHost=localhost dbUsername=postgres dbPassword=postgres js.dbName=jrsstable #other settings diagnostic.jmx.name=jrsstableNow installation process again as outline above with -DconfName=tc_stable instead of -DconfName=tc_devel. http://localhost:<stable port>/jasperserver-pro should be available after deployment. Single tomcat instanceDevelopment instancecreate a new file tc_devel_master.properties in <jrs war-bin dir>/buildomatic # app server settings appServerType=tomcat7 appServerDir=<path to tomcat> # db settings dbType=postgresql dbHost=localhost dbUsername=postgres dbPassword=postgres js.dbName=jrsdevel #other settings diagnostic.jmx.name=jrsdevel webAppNamePro=jrs-develNow you can run installation process as outlined before, http://localhost:8080/jrs-devel should be available after deployment. Stable instancecreate copy of file tc_devel_master.properties with name tc_stable_master.properties in <jrs war-bin dir>/buildomatic Change properties js.dbNamediagnostic.jmx.namewebAppNameProand add values for stable instance there. Then run installation process again as outlined before. http://localhost:8080/<webAppNamePro> should be available after deployment. Conclusionsin order to not overwrite the web applications you need to set individual names. Also - after deployment you need to verify tomcat memory settings to see if they fit the needs of your scenario. Other Application ServersFor Jboss and other web application server follow example as given for glassfish. Once individual instances / domains / profiles etc have been created, configure JasperReports Server accordingly and start manual installation steps.