KRMS Administration Guide

(work in progress - content tdb. The below preface is patterned after the KEW TRG - what will admins need to administer for KRMS? I've put in some placeholder content-topics for a TOC skeleton.)

This guide provides information on administering a Kuali Rules Management System (KRMS) installation. Out of the box, KRMS comes with a default setup that works well in development and test environments. However, when moving to a production environment, this setup requires adjustments. This document discusses basic administration as well as instructions for working with some of KRMS’ administration tools.

Initial Set up tasks

What do I have to install so that people can use KRMS?

What do I have to create or customize so that people can work with business contexts, agendas, and rules?

Do I have to define permissions or approval processes so that people can create and maintain KRMS agendas and rules?

(Other? Anything we have to do to setup integration/interaction with KEW? KIM? KEN? KOM? PeopleFlow? with other service bus?)

Ongoing Maintenance tasks

Troubleshooting and diagnostics

Optimizing performance

Content TBD. For example, would logging alternatives affect performance? Are there selectable levels of KRMS execution logging? Etc., etc..

Other?