Transcript Running Kuali: A Technical Perspective

Running Kuali:
A Technical Perspective
Ailish Byrne - Indiana University
Jay Sissom - Indiana University Foundation
Overview
•
•
•
•
Requirements
Setup/Installation
Build Configuration
Basic Data Setup
•
•
•
•
Service Configuration
Workflow Rules
System Parameters
HTML Customization
Required Technical Knowledge
•
•
•
•
•
Java
XML
Spring
Struts
OJB
•
•
•
•
•
Web (http, jsp, tags)
Log4J
JUnit
Tomcat
Oracle
Requirements - Database
•
•
•
•
•
1GB RAM min - 4GB recommended
2 CPU min - more would be good
11GB data disk space
Oracle 10g Enterprise Edition
Tested on Redhat Enterprise Linux, AIX, Windows
XP/2003
https://test.kuali.org/confluence/display/KULCFG/Test+Server+Setup
Requirements - Web
•
•
•
•
•
2GB RAM minimum
2 CPU AMD
1GB disk space for application
Consider Load Balancing
Tested on Redhat Enterprise Linux, Mac OS/X,
Windows XP/2003
https://test.kuali.org/confluence/display/KULCFG/Test+Server+Setup
Requirements - Batch
•
•
•
•
2GB RAM minimum
CPU - depends on parallel vs. sequential batch schedule
36MB disk space for application
Tested on Redhat Enterprise Linux, Mac OS/X,
Windows XP/2003
https://test.kuali.org/confluence/display/KULCFG/Test+Server+Setup
Kuali Distribution
•
•
•
•
•
•
•
Download Kuali Binary & Source
Extract zip file
Optionally import into Eclipse
Obtain and setup JDK 1.5.0_08 & ANT 1.6.3
Setup database
Execute the ant help target of build-packaged.xml
Follow instructions on screen
http://kuali.org/resources/download.shtml
https://test.kuali.org/confluence/display/KULCFG/Test+Server+Setup#TestServerSetup-setupdatabase
Other J2EE Software
Apache 2.0.55
Eclipse 3.1.2
Recommended for implementation
Optional for development
Zeus ZXTM-lb
Optional for load balancing
Anthill Pro
2.50.18998
Optional for unit testing
https://test.kuali.org/confluence/display/KULCFG/Test+Server+Setup
Build Configuration
• build-packaged.properties
– Machine and user specific configuration
– e.g. encryption key, mail server, directory locations
• dev = source / tst = binary
• build-packaged-dev.properties
– Environment specific configuration
– e.g. server URL, datasource info
Basic Data Setup
• Some tables must be reviewed
• Some tables must be populated
• Some unneeded codes should be inactivated
https://test.kuali.org/confluence/display/KULCFG/Application+Data+Setup
Service Config & Overrides
• Update build-packaged.properties with your
institution code
• Create your institution spring beans file
• Modify appropriate build properties with your
values to customize external config files
• Add your service override bean definitions to your
institution spring beans file
https://test.kuali.org/confluence/x/wVM
Service Config & Overrides
• Kuali logging levels can be increased or decreased
• Log4j config files in externalConfigDirectory
– log4j.properties for web app and batch
– workflow-log4j.properties for workflow
• By default
– Batch logs go to standard out
– Web/Workflow logs go to log files
Workflow Rules
• Add rules for pre-configured rule templates via
the workflow rule document
• Add custom rules
– Upload xml rule attribute definition(s)
– Upload xml rule template definition
– Upload new document type definition
https://test.kuali.org/confluence/display/KULDOC/Case+Studies+and+Examples
System Parameters/Rules
• Review/update existing
• Create and populate workgroup that should have
maintenance permission
• Create corresponding security group
• Add parameter (value to control runtime system
behavior) or rule (definition of legal/illegal values)
https://test.kuali.org/confluence/x/-kw
HTML View Customization
•
•
•
•
Your institution can customize the look and feel of the Web UI
Images and CSS files can be easily changed
distribution/work/web-root/css/portal.css
JSP tags can be modified to remove from or add to screens
Conclusion
• Kuali is very configurable for your institution
• Support: [email protected]
• Questions?