The packaged TIER COmanage release is a Docker container-based implementation of the COmanage Registry. The release consists of Docker containers for COmanage and its database along with a Centos Linux Virtual Machine image that is used to configure and run the containers. Release 17040 of the TIER-COmanage appliance contains the following components:
At the current point in time, TIER Release 180801, we have not written documentation on how to use the containers outside of the VM environment nor have we completed the additional scripting and documentation that will make it easier to configure this COmanage release for use in a production environment. This release is primarily available for use with Oracle VirtualBox, though an Amazon AMI is available. If you are not familiar with VirtualBox, you can read the documentation and download the software from Oracle's web site.
For more information on VirtualBox and starting the VM, see the Shibboleth IdP release notes (navigation pane, left side). The basic procedure is to download the COmanage VM .ova image (1.3 GB) and then select VirtualBox's File/Import-Appliance function.
The initial login/password for the COmanage VM is: comanage/comanage.
passwd |
cd /home/comanage/build/comanage
./bin/build.sh
Configuration Script (setup.sh) Log |
---|
vm>cd /home/comanage/build/comanage/work Welcome to the TIER COmanage Virtual Machine Please supply the Fully Qualified Domain Name (FQDN) of your COmanage Registry. Enter the FQDN or IP address of your server: 137.54.129.66
Enter the COmanage Admin user First Name [Jane]: Enter the COmanage Admin user Last Name [Doe]:
Enter From email address for your messages: jaj@virginia.edu Enter smtp server DNS or IP address [smtp.gmail.com]: Enter email SMTP smtp auth user name: jaj@virginia.edu
working ... Updating shibboleth2.xml to match the FQDN you supplied
Next, cd /home/comanage/build/comanage |
Full testing and evaluation of COmanage is beyond the scope of this document. See the COmanage Web Site for complete information. You can, however, perform some quick initial tests to ensure that you installation is functional.
While the normal idea is that you should never need to look inside a container, it is possible and is sometimes useful for debugging unusual issues. These commands may be helpful.