Wildfly Final (SpagoBI 5.2.0) Davide Zerbetto 2016/11/08 16:55

Transcription

1 Wildfly Final (SpagoBI 5.2.0) Davide Zerbetto 2016/11/08 16:55

2 Table of Contents Introduction... 3 JDBC drivers configuration... 3 Thread pool component configuration... 3 Environment variables... 4 Metadata database creation and configuration... 4 Data sources... 5 Other changes in standalone.xml... 6 Page 2 - last modified by Davide Zerbetto on 2016/11/08 16:55

3 Introduction JDBC drivers configuration Thread pool component configuration Environment variables Metadata database creation and configuration Data sources Other changes in standalone.xml Introduction SpagoBI is compatible with Wildfly final. You should download SpagoBI source code from github ( ) and compile it with Maven, activating profile "wildfly". In this way, you'll get deployable war files for Wildlfy final. Here below we provide some details about installation: many steps described in this document can be also performed using the Wildlfy admin web console, but we explain all those steps dealing with all involved configuration files. JDBC drivers configuration You have to add the JDBC driver module for each JDBC driver you need. As an example, for MySQL, you need to add the MySQL JDBC java driver library into wildfly final/modules/system/layers/base/com/mysql/main plus a modules.xml file containing: <module xmlns= "urn:jboss:module:1.3" name= "com.mysql.driver" > <resources> <resource-root path= "... the MySQL JDBC driver jar file (e.g.: mysql-connector-java jar)..." /> </resources> <dependencies> <module name= "javax.api" /> <module name= "javax.transaction.api" /> </dependencies> </module> Then you have to configure those JDBC drivers in within the drivers tag: <driver name= "mysql" module= "com.mysql" > <driver-class>com.mysql.jdbc.driver </driver-class> </driver> Thread pool component configuration You find here attached a module ( thread-pool-module.zip ) that implements a thread pool, required by some SpagoBI functionalities, based on commonj ( library: create the following folder and unzip the module inside it: wildfly final/modules/system/layers/base/de/myfoo/commonj/main Then configure the thread pool in within bindings tag: <object-factory name= "java:global/spagoworkmanager" module= "de.myfoo.commonj" class= "de.myfoo.commonj.work.myfooworkmanagerfactory" > <environment> <property name= "maxthreads" value= "5" /> <property name= "minthreads" value= "1" /> <property name= "queuelenght" value= "10" /> <property name= "maxdaemons" value= "10" /> </environment> </object-factory> Page 3 - last modified by Davide Zerbetto on 2016/11/08 16:55

4 Environment variables SpagoBI needs some environment variables to work properly: those variables must be defined in within bindings tag: name= "java:/urls/spagobi_resource_path" value= "${jboss.server.data.dir}" name= "java:/urls/spagobi_sso_class" value= "it.eng.spagobi.services.common.fakessoservice" name= "java:/urls/spagobi_service_url" value= " name= "java:/urls/spagobi_host_url" value= " Here below we explain the meaning of those variables and how to configure it: 1. spagobi_resource_path contains a reference to a path in the file system, this will be used in order to store static resources such images, i18n files, etc: we set ${jboss.server.data.dir} as default but you have to check widlfly permissions on that folder (writing permission is needed); 2. spagobi_sso_class is a Java class that is specific for a SSO system; default value is it.eng.spagobi.services.common.fakessoservice but you can change it when using an SSO solution (see SSO documentation for details); 3. spagobi_service_url is an URL used by the external engines to communicate with SpagoBI core; since SpagoBI core and external engines are installed on the same application server, you can leave it as "localhost"; 4. spagobi_host_url is the URL that is used by the client browsers to communicate with SpagoBI; after having installed SpagoBI, you must change it to the actual SpagoBI URL. Metadata database creation and configuration You have to set up a database to contain SpagoBI metadata. Please refer to the "JDBC drivers configuration" chapter to see how to install the JDBC driver (pay attention to the fact that it must suit the RDBMS you are using). You have to create an empty schema, the suggested name of this schema is "spagobi"; SpagoBI will create required tables by itself at first startup. Once the schema is created, you have to change the datasource in within datasources tag: <datasource jndi-name= "java:/jdbc/spagobi" pool-name= "spagobi" enabled= "true" > <connection-url>... JDBC connection URL... </connection-url> <driver>... name on the JDBC driver... </driver> <pool> <min-pool-size>5 </min-pool-size> <max-pool-size>10 </max-pool-size> </pool> <security> <user-name>... JDBC user... </user-name> <password>... JDBC password... </password> </security> </datasource> Recommended JNDI name is "java:/jdbc/spagobi". At last, you have to set the proper database dialect in files: Page 4 - last modified by Davide Zerbetto on 2016/11/08 16:55

5 1. wildfly final/standalone/deployments/spagobi/web-inf/classes/ hibernate.cfg.xml (set hibernate.dialect property according to your database); 2. wildfly final/standalone/deployments/spagobi/web-inf/classes/ jbpm.hibernate.cfg.xml (set hibernate.dialect property according to your database); 3. wildfly final/standalone/deployments/spagobi/web-inf/classes/ quartz.properties (set org.quartz.jobstore.driverdelegateclass property according to your database); 4. wildfly final/standalone/deployments/spagobicockpitengine/web-inf/ classes/hibernate.cfg.xml (set hibernate.dialect property according to your database). Data sources Data sources containing data to be analyzed by SpagoBI must be configured in within datasources tag: as an example: <datasource jndi-name= "java:/jdbc/foodmart" pool-name= "foodmart" enabled= "true" > <connection-url>jdbc:hsqldb:file:${jboss.server.data.dir}/database/foodmart </connection-url> <driver>hsqldb </driver> <pool> <min-pool-size>5 </min-pool-size> <max-pool-size>10 </max-pool-size> </pool> <security> <user-name>sa </user-name> </security> </datasource> (pay attention to the fact that this is just an example: the HSQLDB "foodmart" database is not included in Wildfly). Please refer to the "JDBC drivers configuration" chapter to see how to install the JDBC driver (pay attention to the fact that it must suit the RDBMS you are using). You have to define your data sources, you are free to specify the jndi-name but, when defining the data source using the SpagoBI administration web GUI (Resources > Data sources), remember to use the same JNDI name, for example: Page 5 - last modified by Davide Zerbetto on 2016/11/08 16:55

6 Other changes in standalone.xml Apart from JDBC drivers, datasources, thread pool configuration, you should slightly modify default within the servlet-container tag as follow: <servlet-container name= "default" allow-non-standard-wrappers= "true" > This was required to permit some REST services to handle HTTP requests and response correctly. Page 6 - last modified by Davide Zerbetto on 2016/11/08 16:55