bonita (4) Versions 0.1.0

• • 5.7.1
  • 0.1.2
  • 0.1.1
  • 0.1.0

Follow1

= DESCRIPTION: Download BonitaSoft from a remote location and install it into the tomcat directories according to the directions. The cookbook has been tested with the "Subscription Pack" 5.6.1 version of the Bonita product. First you need to download the "Bonita Open Solution Deployment" package from the downloads page (http://www.bonitasoft.com/products/BPM_downloads/all) and upload it to a local location. We install it in a local Maven repository with coordinates "com.bonitasoft:bonitasoft-server-sp:5.6.1:tomcat:zip". Unfortunately the install can not be completely automated as BonitaSoft requires that you generate a license for the specific host that the product is deployed upon. So after the initial install you need to generate a license key as per the directions given by BonitaSoft (i.e. Run either /usr/local/bonita-5.6/licenses/generateRequestForAnyEnvironment.sh or /usr/local/bonita-5.6/licenses/generateRequestForDevelopmentEnvironment.sh and send of request to bonita and wait for a response). The license needs to be made available over http. We make this license also available in a local Maven repository. The cookbook has only been tested when deploying to MS SQL server but it is expected that modifying the configuration settings will make the cookbook work with other database vendors. = REQUIREMENTS: * Ubuntu (?) = ATTRIBUTES: * `node["bonita"]["package_url"]` - The url to package containing the bonita software. * `node["bonita"]["package_checksum"]` - The package checksum. * `node["bonita"]["license_url"]` - The url to the license file for the bonita software. * `node["bonita"]["license_checksum"]` - The license file checksum. * `node["bonita"]["database"]["hibernate"]["dialect"]` - = "org.hibernate.dialect.SQLServerDialect". * `node["bonita"]["database"]["exo_jcr"]["dialect"]` - The xCMIS jcr dialect. Defaults to "mssql". * `node["bonita"]["database"]["hibernate"]["interceptor"]` - The Bonita hibernate interceptor. Defaults to "org.ow2.bonita.env.interceptor.MSSQLServerDescNullsFirstInterceptor". * `node["bonita"]["database"]["jdbc"]["driver"]` - The class name of the database driver. Defaults to "net.sourceforge.jtds.jdbc.Driver". * `node["bonita"]["database"]["jdbc"]["bonita_url"]` - The database jdbc url for bonita. Defaults to nil. * `node["bonita"]["database"]["jdbc"]["xcmis_url"]` - The database jdbc url for xcmis. Defaults to nil. * `node["bonita"]["database"]["jdbc"]["username"]` - The database username. Defaults to "bonita". * `node["bonita"]["database"]["jdbc"]["password"]` - The database username. Defaults to "bonita". * `node["bonita"]["database"]["driver_package_url"]` - The url to package containing database driver. * `node["bonita"]["database"]["driver_package_checksum"]` - The checksum of the package containing database driver. * `node["bonita"]["xcmis"]["username"]` - The xCMIS username. Defaults to "xcmis". * `node["bonita"]["xcmis"]["password"]` - The xCMIS password. Defaults to "xcmis". = USAGE: Here is some example properties defined on a role that includes bonita. :bonita => { :package_url => "http://repo.example.com/com/bonitasoft/bonitasoft-server-sp/5.6/bonitasoft-server-sp-5.6-tomcat.zip", :package_checksum => "15462a164fffe0533782fba3d2e9f0a6fbec308c", :license_url => "http://repo.example.com/com/bonitasoft/bonitasoft-server-sp/license/5.6/license-5.6-MyUser-bonita.example.com-20111128-20120226.lic", :license_checksum => "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx", :database => { :driver_package_url => "http://repo.example.com/net/sourceforge/jtds/jtds/1.2.4/jtds-1.2.4.jar", :driver_package_checksum => "6761d4a036e661a8719a54b507a0fb8e", :jdbc => { :bonita_url => 'jdbc:jtds:sqlserver://db.example.com/BONITA', :xcmis_url => 'jdbc:jtds:sqlserver://db.example.com/xCMIS', :username => 'username', :password => 'password', } }, :xcmis => { :username => 'xcmis_username', :password => 'xcmis_password' } } = TODO: Currently when running Bonita on a SQL Server instance you need to execute the following SQL; ALTER DATABASE BONITA SET ALLOW_SNAPSHOT_ISOLATION ON ALTER DATABASE BONITA SET READ_COMMITTED_SNAPSHOT ON This should be automated somehow...