-
Notifications
You must be signed in to change notification settings - Fork 0
Plato setup
- Install MySQL 5 Server (tested with version 5.1.54)
- Set UTF8 as a default encoding/collation. Check appropriate MySQL 5.X reference manual for instruction on how to do this. There were some changes so it might not be the same for all versions.
- Configuration
Make the following changes in your MySQL config file (on Linux it is my.cnf and on Windows my.ini)
#in the Server Section [mysqld] max_allowed_packet = 128M max_sp_recursion_depth = 255 thread_stack = 512K
- Restart MySQL server
If you run Planning Suite and IDP on the same domain, you can use a predefined script:
- Switch to the tools directory, there you will find the script setup-database.sh. It creates DB users and databases for IDP and Plato, and prepares a config file for your JBoss AS 7 server.
- Run it via
./setup-database.sh <MySQL root password> <Plato DB password> <IDP DB password> - You will find two new files in this directory: standalone.xml for your production environment, adjust it to your needs, and additionally standalone-test.xml - the configuration for your test server.
- Download and install JBoss AS 7.1.0.Final. You can use JBoss AS 7.1.1.Final, but there are [issues with the included JSF implementation] (https://issues.jboss.org/browse/AS7-4366), so you have to replace the corresponding modules yourself.
- Copy the file standalone.xml you have generated during database setup to [JBOSS_HOME]/standalone/configuration/standalone.xml
- Download [MySQL Connector/J] (http://dev.mysql.com/downloads/connector/j)
- Create a driver module as described in [Installing a JDBC driver as a module] (https://community.jboss.org/wiki/DataSourceConfigurationInAS7#Installing_a_JDBC_driver_as_a_module)
- Go to the modules/org/picketlink/main directory and delete all jar files in it.
- Download Picketlink 2.1.4 jars for JBoss AS 7.1.x here: picketlink-core-2.1.4.Final.jar and picketlink-jbas7-2.1.4.Final.jar
- Copy both Picketlink 2.1.4 jars into modules/org/picketlink/main directory
- In modules/org/picketlink/main do the following changes to the module.xml file :
<module xmlns="urn:jboss:module:1.1" name="org.picketlink"> <resources> <resource-root path="picketlink-core-2.1.4.Final.jar"/> <resource-root path="picketlink-jbas7-2.1.4.Final.jar"/> </resources> <dependencies> <module name="javax.api"/> <module name="javax.security.auth.message.api"/> <module name="javax.security.jacc.api"/> <module name="javax.transaction.api"/> <module name="javax.xml.bind.api"/> <module name="javax.xml.stream.api"/> <module name="javax.servlet.api"/> <module name="org.jboss.common-core"/> <module name="org.jboss.logging"/> <module name="org.jboss.as.web"/> <module name="org.jboss.security.xacml"/> <module name="org.picketbox"/> <module name="javax.xml.ws.api"/> <module name="org.apache.log4j"/> <module name="org.apache.santuario.xmlsec"/> </dependencies> </module>
- Install FITS Tool from http://code.google.com/p/fits .
- Set environment variable FITS_HOME to install directory.
Only necessary if you want to use Minimee services
- Install all tools you want to use on your server.
- Configure tool and services in the files tool-configs.xml and actions-config.xml.
You can find examples in
minimee/src/main/resources/data/services/
Some aspects of Plato can be configured using configuration files. See Plato configuration for further information.
To setup the test server make a copy of the already configured main instance, replace the standalone.xml with the generated standalone-test.xml, and rename it to standalone.xml.
- Install maven version 3 .
- Install git client
- Clone Plato source from the Github:
git clone git@github.com:openplanets/plato.git
- Go into the folder plato and start the build process:
mvn clean install -Dsp.domain=your.planningsuite.domain.org -Didp.domain=your.idp.domain.org -DjbossHomeTest=<JBOSS_HOME_TEST>
Parameters:
- sp.domain: the domain where Planning Suite will be available (defaults to localhost)
- idp.domain: the domain where your identity provider will be available(defaults to localhost)
- jbossHomeTest: the path to your local JBoss server used for testing Note: you can skip this parameter if you also skip all tests via -DskipTests The generated artifacts are in the target sub-folders of planningsuite-ear and idp You have to use the war and ear files. (you cannot deploy the exploded archives, because there is a bug in the maven-war plugin)
- Copy planningsuite-ear/target/planningsuite-ear.ear to your JBoss deployments folder
- Copy idp/target/idp.war to your JBoss deployments folder.
NOTE: If your database is set up for the first time, you have to:
- Edit the file planningsuite-ear/src/main/application/META-INF/persistence.xml and set hibernate.hbm2dll.auto to create
- Generate plannginsuite-ear.ear and deploy it to JBoss (like described above)
- Change hibernate.hbm2dll.auto back to update This is important, otherwise the database gets re-created with each start - and your data gets lost
- Generate and deploy once again plannginsuite-ear.ear