OpenSSO & OpenDS Sitting in a Tree, K-I-S-S...
By docteger on Jan 15, 2008
In case you hadn't noticed, OpenSSO build 2 (the soon-to-be christened Federated Access Manager) now stores its configuration data in a data store rather than a flat file. OpenDS is the new embedded configuration store, replacing the previous flat file implementation where configuration files were stored...um...all over the place (okay, there was
sms). Now, OpenDS is installed with OpenSSO and the configuration data is stored. The installed version of OpenDS is not complete (for example, the
binscripts have been removed to make the
opensso.waras small as possible). But you can always download
opends.zip, explode it and point the script parameters to the configuration directory (config_dir_specified_in_configurator/opends). This will most probably change as the OpenDS builds stabilize. Some things based on this move have already changed. For example,
famadmis a utility that lets you manage your OpenSSO installation from the command line. When
famadmwas developed you needed to point to
AMConfig.propertiesduring setup. But from OpenSSO build 2,
AMConfig.propertiesis now stored in an instance of OpenDS. So during setup you need to point
famadmto a bootstrap file named, appropriately enough,
bootstrapis located under the directory defined during configuration as the Configuration Directory. The concept is that the CLI will read the bootstrap file, contact OpenDS, fetch the appropriate properties, and bootstrap itself. So to bring it full-circle, and to tout what I will be doing on my long holiday weekend (which starts as soon as I publish this entry), here's KISS.