ARIS Risk & Compliance Manager enables you to subscribe to events from a messaging provider (default: Universal-Messaging by Digital Event Services) and use them as a basis for generating defined objects in ARIS Risk & Compliance Manager, for example, test cases. Control using events is configured during the setup or subsequently using ARIS Cloud Controller.
Examples - Commands for ARIS Cloud Controller
reconfigure arcm_m arcm.config.eventProviderActive="true"
reconfigure arcm_m arcm.config.eventProviderUrl="nsp://localhost:9000"
reconfigure arcm_m arcm.config.eventSagInstallationLocation="C:/SoftwareAG"
reconfigure arcm_m arcm.config.eventRoutingConfigurationLocation="C:/EventsRoutingConfiguration
reconfigure arcm_m arcm.config.eventProviderServiceAlias="UniversalMessaging"
reconfigure arcm_m arcm.config.useDurableEventSubscriptions="true"
Meaning of parameters
Central specification to activate event enabling. If the value false is specified, the service is not started. If true, the other parameters must contain valid values.
The parameter must contain the valid URL of a Universal Messaging server instance, for example, nsp://eventserver:9000.
The identifier of the service or more precisely of the message settings to use. Default is UniversalMessaging.
Specifies the absolute path to the root directory of a local SAG installation or to the root directory of the extracted non-osgi client archive. Example: C:\SoftwareAG
Specifies the absolute path to an arbitrary directory where the routing configuration is stored. During the first start-up of the application, the DigitalEventServices subdirectory is automatically created to save the out-of-the-box configuration. Example: C:\EventsRoutingConfiguration
By default, event enabling is based on permanent message subscriptions. This functionality can be disabled by setting the value of this optional parameter to false.
Support digital event types
Predefined digital event types are provided in order to generate defined objects from the events received in ARIS Risk & Compliance Manager. During the first start-up of the application, the specific digital event types, bundled under the des.aris.arcm namespace, are automatically created in the event types default location of the SAG installation. Example: C:/SoftwareAG/common/DigitalEventServices/TypeRepository/eventtypes/des/aris/arcm
They need to be copied into the TypeRepository of the event-generating system. The sending of events with the digital event types provided in ARIS Risk & Compliance Manager is part of Complex Event Processing. Further information on this can be found in the Complex Event Processing documentation.
Operation of a self-contained installation of ARIS Risk & Compliance Manager
If ARIS Risk & Compliance Manager and the Universal Messaging server are not located on the same host, the required configurations and resources cannot be directly referenced and used. In this case, the resources can be extracted from SAG installation with the tool NonOsgiClientArchiveCreator, provided in the Add-ons/UniversalMessaging/ARCM folder of the ARIS Risk & Compliance Manager installation medium. NonOsgiClientArchiveCreator.zip must be unpacked to the host system of the SAG installation, then createClientArchive (batch script or shell script) can be executed. Both scripts require an existing java runtime installation on the host system. On a Linux system, it can be necessary to change the privileges for the root folder of the unpacked tool, for example, sudo chmod –R 777 ./ . The creatClientArchive script prompts the path of the local SAG installation and then extracts all required resources, including the license information, to the archive ./build/UniversalMessagingNonOsgiClient.zip. Then the UniversalMessagingNonOsgiClient.zip archive must be unpacked to the host system of the ARIS Risk & Compliance Manager installation and referenced as already described for configuration parameter arcm.config.eventSagInstallationLocation.
*For further information about operation of Universal Messaging, particularly configuration using Software AG Platform Manager, refer to the product-specific documentation.
Warning
To guarantee fault-free operation and compatibility, make sure that the version of the copied resources for the ARIS Risk & Compliance Manager installation is always synchronized with the version of the Universal Messaging server used.