Apache Unomi 1.x - DocumentationdestinationURL The full URL for the page view. This doesn’t have to be a real existing URL it could be an internal SPA route. Default value : page URL referringURL The referringURL also known as the previous URL public.address:-http://localhost:8181} contextserver.internalAddress=${org.apache.unomi.cluster.internal.address:-https://localhost:9443} Default values are stored in a file called $MY_KARAF_HOME/etc/custom same file : org.apache.unomi.cluster.public.address=http://localhost:8181 org.apache.unomi.cluster.internal.address=https://localhost:9443 If you need to specify an ElasticSearch cluster name, or a host0 码力 | 158 页 | 3.65 MB | 1 年前3
Apache Unomi 2.x - Documentationpublic.address:-http://localhost:8181} contextserver.internalAddress=${org.apache.unomi.cluster.internal.address:-https://localhost:9443} If you change these ports, also make sure you adjust the following port=8181 org.apache.unomi.cluster.public.address=http://localhost:8181 org.apache.unomi.cluster.internal.address=https://localhost:9443 org.apache.unomi.elasticsearch.cluster.name=contextElasticSearch used. By default, Apache Unomi comes with some built-in allowed expressions that cover all the internal uses cases. Default allowed MVEL expressions (from https://github.com/apache/unomi/blob/unomi-0 码力 | 117 页 | 4.78 MB | 1 年前3
Apache Unomi 1.1.x - Documentationsource and target can represent just about anything. Events can also be triggered as part of Unomi’s internal processes for example when a rule is triggered. Events are sent to Unomi from client applications being triggered. When a rule triggers, it creates new actions based on the event data and the rule internal processes, providing values for parameters defined in the associated `ActionType. Example actions0 码力 | 32 页 | 477.20 KB | 1 年前3
共 3 条
- 1













