. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 4.1. Importing profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . should not be accessible to the world. For your Apache Unomi client applications (such as the Jahia CMS), you will need to make the following ports accessible : 8181 (Context Server HTTP port) 9443 (Context configurations and consumes or produces CSV files that contain profiles to be imported and exported. 4.1. IMPORTING PROFILES Only ftp, sftp, ftps and file are supported in the source path. For example:

Here are different use cases for profile aliases: Connect different systems to Unomi such as a CRM, CMS and native mobile app that all have their own iD for a single customer Merging profiles when a visitor documentation that contains a detailed example of how to integrate with Apache Unomi. 4. CONFIGURATION 4.1. CENTRALIZED CONFIGURATION Apache Unomi uses a centralized configuration file that contains both system should not be accessible to the world. For your Apache Unomi client applications (such as the Jahia CMS), you will need to make the following ports accessible : The Apache Unomi actually requires HTTP Basic

should not be accessible to the world. For your Context Server client applications (such as the Jahia CMS), you will need to make the following ports accessible : 8181 (Context Server HTTP port) 9443 (Context