. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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

看到的结果居然是，CMS 垃圾收集器的线程。。。
这，这，这不科学。

垃圾回收

看垃圾回收日志，发现一直在进行 Full GC，但是几乎没啥效果，GC 完了，老年代依然是几乎 满的状态。
即使是 CMS，也不能避免传说中的 stop the world，所以响应时间变长了。

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

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 4.1. Wicket distribution and modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . when working with this framework. We’ll learn more about custom components in the next chapters. 4.1. Wicket distribution and modules Wicket is available as a binary package on the main site http://wicket python • (4) brew install cairo • (5) brew install py2cairo • (6) pip install Django==1.5 • (7) pip install "django-tagging<0.4" • (8) sudo pip install carbon • (9) pip install whisper • (10) sudo

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 4.1. Wicket distribution and modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . when working with this framework. We’ll learn more about custom components in the next chapters. 4.1. Wicket distribution and modules Wicket is available as a binary package on the main site http://wicket python • (4) brew install cairo • (5) brew install py2cairo • (6) pip install Django==1.5 • (7) pip install "django-tagging<0.4" • (8) sudo pip install carbon • (9) pip install whisper • (10) sudo

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 4.1. Wicket distribution and modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . when working with this framework. We’ll learn more about custom components in the next chapters. 4.1. Wicket distribution and modules Wicket is available as a binary package on the main site http://wicket python • (4) brew install cairo • (5) brew install py2cairo • (6) pip install Django==1.5 • (7) pip install "django-tagging<0.4" • (8) sudo pip install carbon • (9) pip install whisper • (10) sudo

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 4.1. Wicket distribution and modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . when working with this framework. We’ll learn more about custom components in the next chapters. 4.1. Wicket distribution and modules Wicket is available as a binary package on the main site http://wicket python • (4) brew install cairo • (5) brew install py2cairo • (6) pip install Django==1.5 • (7) pip install "django-tagging<0.4" • (8) sudo pip install carbon • (9) pip install whisper • (10) sudo

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 4.1. Standalone Broker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . over the wire using the core protocol. The broker always just deals with core API interactions. 4.1. Standalone Broker The normal stand-alone messaging broker configuration comprises a core messaging allocation rates, and the number of times the GC pauses (or concurrent phase time in the case of CMS). Underlying data gathered from Java’s MemoryPoolMXBeans. Disabled by default. JVM thread Gauges

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 4.1. Standalone Broker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . over the wire using the core protocol. The broker always just deals with core API interactions. 4.1. Standalone Broker The normal stand-alone messaging broker configuration comprises a core messaging allocation rates, and the number of times the GC pauses (or concurrent phase time in the case of CMS). Underlying data gathered from Java’s MemoryPoolMXBeans. Disabled by default. JVM thread Gauges