Enabling the Connections app registry service for customization
To leverage custom config extensions, enable the app registry service. You need Component Pack installed to do so. If Component Pack is not available, you can inject customizations using window-scoped JavaScript objects. For more information, refer to Customizing through window-scoped JavaScript objects.
By default, Connections applications do not attempt to make requests to the app registry service if the app registry service has not been deployed as part of a Component Pack installation.
Note
When adding new entries to the App Registry, it is important to ensure that no other entries with the same namespace are enabled or active within the system. This is to prevent conflicts, maintain system integrity, and ensure seamless functionality across all applications.
Procedure
To enable the app registry service:
-
Locate the file
WAS_HOME\profiles\WAS_Profile\config\cells\Host_name\LotusConnections-config\LotusConnections-config.xml
. -
In the file, locate the
sloc:serviceReference
section. whereserviceName="extensionRegistry"
. -
Check that both the
enabled
andssl_enabled
properties are set totrue
. -
If they are not set to
true
, update the configuration file so the section looks as follows. Replaceadmin\_replace
with the appropriate server domain:<sloc:serviceReference bootstrapHost="admin\_replace" bootstrapPort="admin\_replace" clusterName="" enabled="true" serviceName="extensionRegistry" ssl_enabled="true"> <sloc:href> <sloc:hrefPathPrefix>/appregistry</sloc:hrefPathPrefix> <sloc:static href="admin\_replace" ssl_href="admin\_replace"/> <sloc:interService href="admin\_replace"/> </sloc:href> </sloc:serviceReference>
-
Sync your changes and restart the server.
Sample customization using the Connections app registry
In this example, you can use custom style extensions to update the Connections colorway to green. Refer to the following procedure, which involves creating a custom config extension:
-
Log in to your HCL Connections environment as an administrative user and navigate to the URL
https://__CONNECTIONS_DOMAIN__/appreg/apps
. -
Click on the New App + button and select Code Editor in the side menu.
-
Copy the following template of an app registry configuration and paste it into the App Editor:
{ "name": "Connections Custom Config Extension", "title": "Connections Custom Config Extension", "description": "Connections Custom Config Extension - Description", "services": [ "Connections" ], "state": "enabled", "extensions": [ { "name": "connections-custom-config-extension", "type": "com.hcl.connections.custom.style", "payload": { "style-customization": { "generic": { "--color-header": "#2c4433", "--color-navigation": "#366032", "--color-navigation-selected": "#609c5a" } }, "cacheExpiration": 20000 }, "path": "global", "state": "enabled" } ] }
-
Click Save to apply your changes.
-
Refresh your Connections UI to view the changes.
Defining object properties in the app registry configuration
The most important properties in the app registry configuration are the type
and payload
properties within the extensions
array:
-
type
specifies to which component the extension relates. Currently, the following types are available:Extension Type Description com.hcl.connections.nav Customization of the menu entries on the side navigation bar com.hcl.connections.custom.style Customization of header elements and general theming via custom styles com.hcl.connections.banner Configuration of the administrative banner and its content com.hcl.search.customization Customization of the search box and the connected search application com.hcl.share.extension Extension of the Connections share actions and targets com.ibm.itm.entry.person.default Customization of the Important To Me bar com.hcl.appreg.ext.templatedLink Extension of communication options for the business card com.hcl.connections.tours Extension of the Connections welcome tour -
payload
is specific to the individual component and the mandatory and optional properties that the component supports. For more information around the expected values forpayload
, refer to the customization topic for each component.
In addition to type
and payload
, extensions also expect name
and title
properties that provide context within the app registry overview page or are used to render labels on the UI, respectively.
Parent topic: Creating custom configuration extensions