1. Eric Westfall – Indiana University James Bennett – Indiana University ADMINISTERING A PRODUCTION KUALI RICE INFRASTRUCTURE

2. KUALI RICE @ INDIANA UNIVERSITY Integrated with 26 enterprise applications Hosting 50 eDocLite applications Over 400 different KEW Document Types 24 x 7 x 365 availability Approximately 99.8% uptime in the last year (including maintenance)

3. EXPANDING IMPLEMENTATION

4. USAGE

5. ARCHITECTURE AND INFRASTRUCTURE Red Hat Enterprise Linux on VMware Load balancer with four clustered Kuali Rice standalone server instances Java 6 Tomcat servlet container Shared file system mount for attachments Oracle 11g database

6. IU KUALI RICE ARCHITECTURE

7. MAINTAINED BY A team of 3 FTE, who do… Production Support System Maintenance Upgrades Integration Projects Application and eDocLite Development

8. CONFIGURING CLIENT APPLICATIONS

9. LOAD TESTING Using Apache JMeter Perform standalone and coordinated load tests Load testing transactions include  Document search  Action list  Taking mass actions  Viewing route logs  Creation and routing of documents

10. LOAD TESTING EXAMPLE OUTPUT

11. KEYSTORE ADMINISTRATION Keystore needed for KSB security Keytool commands  genkey  selfcert  export  import  list

12. KEYSTORE ADMINISTRATION Items to consider in a production setting: Keep certificate expiration dates in mind Testing and prod keystores should not be the same New applications must:  Create a certificate  Include a copy of the KR certificate in their keystore  Give their certificate to be included in the KR keystore

13. UPGRADING RICE Process: 1.Bring in new Kuali Rice foundation jars 2.Make changes to the IU version of Rice which includes: Updating customizations Merging "patched" code Produce IU Rice client jars 3.Perform DB updates to test environment 4.Bring up standalone testing environments 5.Work with clients to bring in IU Rice client jars and update code

14. EDOCLITE MANAGEMENT Reasons for changes to existing eDocLites  Annual changes due to nature of form  Addition of a new field  Change to drop down contents  Change to field validation

15. EDOCLITE DEVELOPMENT Process: 1.Request comes in for a new eDocLite 2.Meet to review requirements 3.Develop initial eDocLite 4.Test and make changes until ready for prod 5.Ingest eDocLite into production

16. IU EDOCLITE EXAMPLE S