Managing the Configuration Registry
The configuration registry is a database of key-value pairs. Here you can register custom web pages, custom functions, and details for certain predefined values.
To access the configuration registry:
Log in to the Management Portal as a user with the %HS_Administrator role.
Select your Foundation namespace.
Click Health > Configuration Registry.
To create a new key, click the Add Value button. To modify an existing key, select the key in the table.
Enter the key and its value in the appropriate fields and click Save.
Configuration registry key categories include:
\HomeCommunity — details of the home community’s contact information.
\IHE — details required for IHE communication.
\LegalAuthenticator — details about the person legally responsible for exported content.
\UI — configuration details for custom web pages invoked by the Management Portal.
These are detailed in the sections that follow.
Use the \IHE keys to control various aspects of IHE functionality.
Use this key to identify the OID of your home community. A home community is an entity that has a single XDS document registry. The value of this key may be an OID value or the IdentityCode of an OID identified in the OID registry. For example: you might have an OID called “HomeCommunity”, that is both an AssigningAuthority and a HomeCommunity type OID. In that case, enter HomeCommunity as the value for this key.
An affinity domain is responsible for assigning unique MPI IDs for one or more home communities. Use this key to identify the OID of your IHE affinity domain assigning authority. This may be an OID value or the code of an OID identified in the OID registry. Often, this is the same OID as the \IHE\HomeCommunity OID.
Set this key to zero if the XDS.b repository, called RepositoryName, does not support MTOM attachments.
Legal Authenticator Keys
Use the \LegalAuthenticator keys to hold the contact details and identity of the individual in your organization who bears legal responsibility for exported content:
The \UI keys identify user interface pages that have been customized for a site. Most of the Zen pages in the user interface may be customized, including any page that is invoked by one of the $$$HSUILink macros. Typically, custom user interface pages extend the standard UI page and replace one or more XDATA blocks. To replace a standard UI page with your own page, use a key of the form \UI\[subpackage \]...\class to identify the page you are replacing, and set the value to the complete class name of your custom page, including the .cls extension. For example:
To replace the class HS.UI.Logout.cls, use the key \UI\Logout and a value like Custom.Logout.cls
After adding a custom page you must log out and the log back in in order to see the new page.
The Application Class
The class HS.UI.ApplicationOpens in a new tab specifies styles and banners that are used by all UI pages. To customize styles and banners system-wide, extend HS.UI.Application.cls. You may customize the stylesheet by overriding the Style XDATA block, or customize page headers by overriding the DrawTitle() method.
Register your custom application page using the key \UI\Application.
Individual pages may also override the Style XDATA block or DrawTitle() method on a per-page basis.