Install and configure

This page provides the instructions for the AMM skill's installation to the v.10.2.5+ instance.

Requirements

Hardware

The AMM skill runs on the standard Intelligent Automation Cloud hardware configuration, as documented in System Requirements.

Server	Recommended OS	CPU (cores)	RAM (GB)	HDD (GB)
Master	RHEL 8.5	8	32	750
Agent	RHEL 8.5	4	16	150
Analytics	Windows Server 2016	16	32	150
MSSQL	Windows Server 2016	2/4	8/16	500

• RPA bots are not required for Adverse Media Monitoring.
• High-availability environments require the PROXY server.

Software

Before installing AMM, make sure that your environment meets the requirements:

• You have installed IA Cloud Enterprise v.10.2.5+ and have Control Tower and Analytics components enabled. For IA Cloud 10.1.6+, ODF 2 is installed automatically along with the system.
• You have the bundle with AMM Business Process and ML models.
• You have received the credentials for the required watchlists or licenses for the external screening software to be integrated with AMM.
• You have the Advanced Package Import and Import/Export permissions in Control Tower.

To check that ODF is installed:

1. Log in to Control Tower, and click Advanced > Data Storesin the menu.

2. In the list, find the Data Stores with the_odf_transactions and _odf_transactions_status names. The ODF is already installed on your instance if they are on the list.

   

If the Data Stores are missing, download ODF and save odf-install-package-10.1.0.7.zip to your local workstation.

Performance

Adverse Media Monitoring leverages BEP servers, which can be horizontally scaled for higher volumes.

Below is a sample of the volumes that can be expected when using the provided version and configuration. The system shows stable performance and resource consumption during the whole test, without unexpected spikes and errors, or any critical errors and warnings in logs.

The Search provider used is Google API, note that throughputs may vary slightly based on provider.

Configuration:

Skill version	Environment topology	Tested IA Cloud version	Number of RPA Bots	Number of OCR Workers	AutoML Worker configuration	Control Tower Worker configuration
3.1.0	3 / 6 / 20 Agents	10.2.7	5	7	1 CPU / 4 GB memory	0.4 CPU / 2 GB memory

Results:

Number of Agents	Number of Entities	Duration	Number of AMM Workers	Hits/hour
3	840	1 hr 30 min	8	11,200
6	840	55 min	18	16,800
20	840	24 min	60	42,000
20	840	34 min	60	59,000

Here, 1 Entity = 20 articles.

Install AMM

There are two ways of installing the skill:

• If you are setting the AI Digital Worker up for the first time, use the Solution Catalog.
• If you have worked with the AI Digital Worker in earlier IA Cloud versions, use the package.

To install the AMM skill:

From Solution Catalog

1. In the Control Tower main menu, go to Digital Workers and, on the right, click the Solution Catalog button.

   

2. On the Digital Workers tab, find the Adverse Media Monitoring group and click Details in it.

   

3. In the Digital Worker window, click Install.

   

For more information about the installation, see Install AI Agents.

From bundle

You can request the bundle with the required release version from your account manager or the Support team. Once you acquire it, perform the following steps:

1. In Control Tower, go to Digital Workers > View all.

   

2. On the right, click the plus (+) button > Upload new.

3. In the AI Digital Worker upload dialog, click Add and select the received bundle with the Business Process.

   The installation starts automatically.

   

After the successful installation, AMM appears in the corresponding group.

Configure AMM

Once Adverse Media Monitoring is installed, configure the skill before running it for the first time.

Starting in 10.2.5.X +, you can configure multiple variations, or sets of parameters, for AMM. For example, a different media provider or a set of keywords per variation. For more information, see the 10.2.5 release notes.

Set up credentials

Before setting the news providers, ensure you have obtained the corresponding license with credentials.

The following search providers are supported:

• Google API v1-rev86-1.25.0
• Dow Jones Factiva Rest API 2.0
• LexisNexis L&P News v1
• World-Check One

If you are using Google API, provide the credentials first. To do that on a GCP-hosted environment, see the instruction under the expand:

To use other providers besides Google API, you must first set up the above credentials in the Secrets Vault. For the step-by-step instructions, see this guide.

Select provider

To select a news provider, do the following:

1. In the Control Tower menu, in the Digital Workers section, find your newly installed AMM skill, and click the Prepare button.

   The Prepare your digital worker window containing a configuration form appears.

2. In the window, on the Provider tab, select a news provider for searching for news about the entity or individual. "Google API" is set by default.

   The required configurations may differ based on the selected news provider.

   

Configure provider

The Adverse Media Monitoring skill supports news retrieval from the following news providers:

• Google API v1-rev86-1.25.0
• Dow Jones Factiva Rest API 2.0
• LexisNexis L&P News v1
• World-Check One

You also have to customize and train the skill to use other providers.

The Factiva options can be used with the provided API keys for development, testing, and demonstration purposes. For production usage, you must acquire corresponding production keys from Dow Jones.

To configure a provider, specify the providers' parameters. For a detailed description of each setting, see the following sections.

Google API

• Google API Credentials Location. Specify the corresponding Secret Vault alias for the Google API system.

• Article Language. Select the language of articles to search in. 'Any' language is used by default.

• Number of articles to extract. Specify the maximum number of reports to fetch from 1 to 20. By default, up to 20 articles are retrieved.

• Search Time period. Select an option to find information published during a specific time frame. To specify the starting and the ending date for the articles' search, select Custom Range.

• File types to exclude from results. Select the file types that you want to exclude from Google results:

  • Html is included by default.
  • Non-HTML file types do not have the same metadata and tagging. Excluding them reduces the number of articles to review and false hits by 50% without increasing the risk of missing a true hit.

Factiva

• Factiva API URL. Select the address of the Factiva API. Available options:

  • https://api.beta.dowjones.com
  • https://djrc.api.dowjones.com

• Factiva Credentials Location. Specify the corresponding Secret Vault alias for the Factiva system.

• Article Language. Select the language of articles to search in. The 'English' language is used by default.

• Number of articles to extract. Specify the maximum number of reports to fetch from 1 to 100. By default, up to 20 articles are retrieved.

• Search Time period. Select an option to find information published during a specific time frame.

LexisNexis

• LexisNexis API URL. Select the address of the LexisNexis API. By default, https://services-api.lexisnexis.com.
• LexisNexis Authentication URL. Specify the Authentication URL for the LexisNexis News. By default, https://auth-api.lexisnexis.com.
• LexisNexis Credentials Location. Specify the corresponding Secret Vault alias for the LexisNexis News system.
• Article Language. Select the language of articles to search in. The 'English' language is used by default.
• Number of articles to extract. Specify the maximum number of reports to fetch from 1 to 100. By default, up to 20 articles are retrieved.
• Search Time period. Select an option to find information published during a specific time frame.

World-Check One

• World-Check One API URL. Select the address of the World-Check One API. The default one is https://api-worldcheck.refinitiv.com.
• World-Check One Group. Specify the Group Id for the World-Check One system.
• World-Check One Credentials Location. Specify the corresponding Secret Vault alias for the World-Check One system.
• Article Language. Select the language of articles to search in. The 'English' language is used by default.
• Number of articles to extract. Specify the maximum number of reports to fetch from 1 to 100. By default, up to 20 articles are retrieved.
• Search Time period. Select an option to find information published during a specific time frame.

Configure keywords

In the Prepare your digital worker box, specify keywords for search on the Keywords tab. You can add a maximum of 28 words.

The following keywords are added by default:

• English:

  ACCUSE, ARREST, BRIBE, CONVICT, CORRUPT, COUNTERFEIT, CRIME, EMBEZZLEMENT, FRAUD, GUILT, ILLEGAL, INDICTMENT, INVESTIGATION, KICKBACK, MONEY LAUNDERING, NARCOTIC, PENALTY, SANCTION, SENTENCED, EVASION, TERRORIST, THEFT, TRAFFICKING, VIOLATION

• Spanish:

  ACUSAR, ARRESTAR, SOBORNO, CORRUPTO, FALSIFICACIÓN, CRIMEN, MALVERSACIÓN, FRAUDE, CULPA, ILEGAL, ACUSACIÓN, INVESTIGACIÓN, CONTRAGOLPE, LAVADO DE DINERO, NARCÓTICO, MULTA, SANCIÓN, SENTENCIADO, EVASIÓN, TERRORISTA, ROBO, TRÁFICO, VIOLACIÓN

info

For the World-Check One provider, the keywords highlight important sections within each article returned by the search, but not for the API call. You must configure keywords to be used in a search at the World-Check One's website.

Configure high-risk countries

Select countries from the dropdown or enter their names in the search field. The high-risk countries configured here are highlighted in articles returned from each investigation.

Configure output

In the Prepare your digital worker box, on the Output tab, specify the following parameters of the report for a screening request:

• Enable Manual Review. Select Yes to enable Manual Review Step.
• Require users to disposition all articles. Enable the setting if users are required to disposition all articles before closing an investigation in Workspace.
• Format. Select the report file format for a screening request to be generated: HTML or PDF.
• Delivery. Select the delivery method in which the report is sent after generation. By default, Object storage.
• Object Storage. Specify the secured storage location for saving the report after generating it. By default, S3 location.

Review settings

Once you complete the required fields, review the configuration. If everything looks correct, click Finish. You are now ready to use the Adverse Media Monitoring skill.

Advanced settings

Configure Data Purge

The Data Purge Business Process is an additional part of Adverse Media Monitoring AI Digital Worker that allows for cleaning up old data on the environment.

Configure Data Purge settings

To configure Data Purge settings, do the following:

1. Log in to the Control Tower.

2. Click the Advanced tab and select Data Stores.

3. Select uc_amm_configuration_v1 and set the following parameters:

   Name	Value	Example	Description
   dataPurge.storagePeriodInDays	Integer	30	How many days should pass after the completion of the transaction to delete the data
   dataPurge.deleteReports	true/false	false	Set to "true" to delete generated reports
   dataPurge.deleteAnalyticsData	true/false	false	Set to "true" to delete analytics data

Configure Data Purge scheduling

You can run the Data Purge BP manually or on a schedule.

To configure the schedule, do the following:

1. Log in to Control Tower.

2. Go to the Advanced tab and select Schedules.

3. Click Create.

4. On the Create Schedule window, select the following parameters:

   • In Task or Process Definition, select "Adverse Media Monitoring Data Purge vX.X.X | AMM | X.X.X".
   • In Input Data, select “Empty”.
   • Specify Schedule Period to run Data Purge only for some period. Otherwise, leave it empty.
   • In Schedule Name, set the operation's name, for example, "Adverse Media Monitoring Data Purge".
   • In Schedule Frequency, specify days and times when Data Purge must be started. It is recommended to set the time when the environment is least loaded, for example, nightly hours on weekends.

   

5. Click Save.

After that, the purge operation runs automatically on a specified day and time.

To learn more about data clearing, see the following sections on Purge in the Enterprise Edition documentation:

• Overview
• Configure and run
• API

Configure REST API Endpoints

To configure REST Endpoints for Adverse Media Monitoring, perform the following steps:

1. In Control Tower, open the main BP definition (Adverse Media Monitoring vX.X.X), and on the Data tab, select Streaming Records from External Sources. Here, you can also specify a custom signal id:

   

2. On the Run tab, click Run This Process.

3. After the BP starts, return to the Run tab and click Show API to find all available generated endpoints:

   

Verify settings

To check that the Business Process is imported correctly, try running an investigation.