Decide on Organizational Identity Pooling
As of COmanage Registry v1.0.0, whether or not Organizational Identities are pooled must be decided at setup time, and once set cannot be changed. For more information on which setting you should select, see Organizational Identity Pooling.
If you are worried that you may select the wrong setting, you should probably be setting up a development instance first so that you can mock up your data to see how you would like it to operate. That way, if you made the wrong choice you can just "throw away" the development instance and try again.
Run Registry Setup
Run the Registry configuration script. Be sure to enter the username that will be returned by your web server's authentication engine. For example, under Apache this corresponds to $REMOTE_USER.
Be careful with file ownerships here. You will need to run this command as the web server user or as root, depending on whether or not the web server user can write files to the application directory (which is normally a bad idea). If running as root, make sure the cache directory (wherever app/tmp points to) and all of its subdirectories and files are writeable by the web server. chown -R and chgrp -R may be in order.
$ cd app $ ./Console/cake setup Enter administrator's given name > Pat Enter administrator's family name > Lee Enter administrator's login username > plee@university.edu
setup is intended to be run once. After you run it, you should be able to login via the web interface and make whatever changes you need that way. If you need to run it again, the easiest approach is to drop the database and start over.
When running this step under v0.9.4, you may notice deprecation messages like
Deprecated (16384): Validation::notEmpty() is deprecated.
These messages may be safely ignored, and will be addressed in a future release (CO-1119).