This section explains the process for moving Pentaho content and server settings among multiple BA Server instances. Typically this includes either two or three separate servers with identical configurations: One for BA content development, one for testing and QA if desired, and one for production. We recommend that you work with a member of Pentaho professional services to help with the preparation work for deployment to production.
Prepare for Going Live
This section is divided into two parts; the first part serves as a checklist for setting up a BA Server, and the second consists of prerequisites that you must perform before going live with your production server. If you already have your BA production server ready to go, skip ahead to the tasks listed in the Prerequisites for Go Live - Checklist for Production Server table.
The BA Server Set Up Checklist helps you verify that the hardware and software requirements are met, get the software installed, and configure the BA Server and BA Design tools.
|Verify System Requirements|| |
|Obtain Software and Install BA|| |
|Change the BA Server Fully Qualified URL||If you are going to have many machines pointing to one server, make sure you change the fully qualified URL. |
|Configure the BA Server|| |
This checklist guides you through the tasks you need to do to ensure a smooth transition from a development server to a live production server.
|Perform a diff on BA config files|| |
|Verify Data Sources|| |
|Define Security|| |
|Upload Content|| |
Perform a Diff on BA Configuration Files
The most important BA Server configuration settings are stored in the /server/biserver-ee/pentaho-solutions/system/ directory. There are also a few core settings inside of the Pentaho WAR archive deployed to your application server, though they should not change at all after your initial server setup is complete.
Do not change the names of any content files, data sources, solution directories, or other file names during the promotion process. Names should be set during solution development and strictly maintained throughout content promotion. Modifying file names can result in complications with BA content that cannot be immediately detected, which will negatively impact your QA process.
To be absolutely certain that you have all of the BA Server configuration files selected, you should diff the following directories in their entirety:
- /WEB-INF/ inside your deployed pentaho.war
- /META-INF/ inside your deployed pentaho.war
- For JBoss deployments, the PentahoHibernate-ds.xml and quartz-ds.xml files in the /server/default/deploy/ directory
There are binaries inside of the plugin directories for Analyzer, Dashboard Designer, Interactive Reporting, and Community Dashboard Framework. While it may be useful to note any binary differences, which would indicate possible version differences among BA Server or plugin deployments, in general you should be most concerned with XML configuration files and properties files. However, if you have done any plugin customization work, you will need to promote those changes as well.
Move Content to Production Server
This checklist is a compilation of best practices for you to use to promote your BA Server settings, data sources, and content.
Before you dive into going from a development server to your live production server, make sure that you have completed all of the tasks in the Prerequisites checklist.
|Download Content|| |
|Set Up Schedules and Blockout Times|| |