Note: LSEG Messenger is also known by its previous named of Reuters Messenger and Eikon Messenger.
For LSEG administrators, MCO eComms administrators, and implementation teams.
Before you begin
Confirm whether your organization will use direct connection with LSEG or client-managed Secure File Transfer Protocol (SFTP) transfer.
Confirm your organization has the required LSEG or Reuters account access.
Confirm LSEG Messenger logs can be exported in the supported Reuters format.
Confirm the users whose LSEG Messenger communications should be captured.
Confirm the email addresses or identities used to identify each user in LSEG Messenger.
Confirm you have administrator access to MCO eComms.
Choose an acquisition method
MCO eComms supports two LSEG Messenger log acquisition methods.
Method | Description |
Direct connect with LSEG | MCO acquires logs directly from LSEG and manages the import process with limited client IT involvement. |
Client-managed SFTP transfer | Your organization acquires logs from LSEG in the supported Reuters format and places them in an MCO-managed SFTP location. |
Configure direct connect with LSEG
Use direct connect when MCO will acquire logs directly from LSEG.
Confirm your organization has the required Reuters account access for granting access.
Contact your MCO implementation or support contact to start direct connect setup.
Provide the access details required for MCO to connect to your LSEG or Reuters account.
Receive the MCO connection details required by LSEG.
MCO provides the required IP address, Pretty Good Privacy (PGP) key, and passphrase.
Confirm with LSEG that logs are exported in the supported Reuters format.
Confirm with MCO that the import process is active.
Configure client-managed SFTP transfer
Use client-managed SFTP transfer when your organization will acquire logs from LSEG and transfer them to MCO.
Confirm your organization has an internal process for exporting LSEG Messenger logs.
Confirm the logs are exported in the supported Reuters format.
Contact your MCO implementation or support contact to confirm the MCO-managed SFTP location.
Transfer the exported logs to the MCO-managed SFTP location.
Confirm with MCO that the files are received and processed.
Map users to LSEG Messenger identities
Mapping users to their LSEG Messenger identities allows MCO eComms to associate captured communications with the correct user profiles.
Users can be mapped by the primary email address in their profile or through additional LSEG Messenger source mappings.
Sign in to MCO eComms as an administrator.
Go to Settings > Users. The Users page opens.
Locate the user you need to map.
Click Edit. The user profile opens.
Locate the Sources section.
Click Edit in the Sources section. The section enters edit mode.
Click Add Source. A new source mapping row appears.
In Source name, select LSEG Messenger.
In Unique Identifier, enter the email address or identity used to identify the user in LSEG Messenger.
Click the check icon. The source mapping row is saved in the profile editor.
Add any additional LSEG Messenger identities required for the user.
Click Save. MCO eComms saves the user profile.
Result
Newly arriving LSEG Messenger messages that match the mapped identities are associated with the correct user profiles. Once messages are mapped, the users’ retention and detection policies apply to future LSEG Messenger communications.
Important! New source mappings will update existing messages and alerts in the account for search and display reference purposes. However, they will not retroactively apply retention and detection policies to messages already in the application.