Documentation
Quick Start

There are different ways to install Symbolic. In downloads page you can find RPM, WAR and source files.

Symbolic requires func certmaster property configured. Use the official howto to configure it.
Before start to install symbolic you should have these packages installed:

  • Java SDK: On Fedora just install java-1.7.0-icedtea-devel (on fedora 8) or java-1.6.0-openjdk-devel (on fedora 9), or, in alternative (on RHEL and previous fedora versions), the official java sun from the official website.
  • Grails (RPM)
  • JBoss Application Server (only if you are interested in WAR version)

RPM

After downloading RPM file you just need to call (from root user):

rpm -ivh symbolic-0.1.rpm

Now you have to check if JAVA_HOME (default for fedora8 is /etc/alternatives/java_sdk and on RHEL5 is /usr/java/latest) and GRAILS_HOME (by default in both releases set to /usr/share/grails) in init V script is property set (we will export these settings to an external files next minor release).
By default with Fedora 8 package

To launch symbolic just type (from root)

service symbolicd start

Symbolic start in a while, if you want to have a brief information about execution, there is a log file in

/var/log/symbolic.log
WAR

WAR file is shipped with two others files: data source file (symbolic-ds.xml) and config file (SymbolicConf.properties).
WAR and datasource should be putted into deploy application server directory (for example $jboss_dir/server/$instance/deploy) and edited as your own.
Configuration files is optional: if you want to use (by copy or create it into /etc/symbolic/ ), you may have ability to configure LDAP settings and certmaster certificate directory. Without config file, symbolic start with default settings.

Source

You can get source from git repository or snapshots. Symbolic is growing fast so we raccomend to use git.
To launch application, just unzip snapshot or clone/pull from GIT repository and enter into program directory:

grails run-app

or type

symbolic

If you got problems or bugs, please refer to our trac in "Support & Development" section.