Apache Unomi 1.x - Documentation
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 2.2.5. How to create a new rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 8.13. Rule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 11.6.6. Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .0 码力 | 158 页 | 3.65 MB | 1 年前3Apache Unomi 2.x - Documentation
accessing : http://localhost:8181/cxs/context.js?sessionId=1234 11) If something goes wrong, you should check the logs in ./data/log/karaf.log . If you get errors on ElasticSearch, make sure you are using the ElasticSearch version specified in the documentation whenever possible. If in doubt, don’t hesitate to check with the Apache Unomi community to get the latest information about ElasticSearch version compatibility webapp/index.html . However you will still need to use the REST API calls to create the scope and rule to make it all work. 2.4.1. INSTALLING THE WEB TRACKER IN A WEB PAGE Using the built-in tracker0 码力 | 117 页 | 4.78 MB | 1 年前3Apache ActiveMQ Artemis 2.32.0 User Manual
same logic applies when mapping a JMS message or a Core message to STOMP. A STOMP 1.0 client can check the presence of the content-length header to determine the type of the message body (String or bytes) tor> The type of this attribute is integer. When this attributed is configured, the broker will check the size of the body of each STOMP frame arrived from connections established with this acceptor when they have not received any packets from the server within the time given by client-failure- check-period as explained in section Detecting Dead Connections. 11.1. Reconnect to the same server Set0 码力 | 528 页 | 10.88 MB | 1 年前3Apache Unomi 1.1.x - Documentation
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 using the JSON format and a typical mergers PropertyType properties then profiles or sessions subdirectory thendirectory Rule rules Scoring scorings Segment segments Tag tags ValueType values Blueprint is used to declare that can be used as consequences of Rules 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 0 码力 | 32 页 | 477.20 KB | 1 年前3Apache ActiveMQ Artemis 2.37.0 User Manual
same logic applies when mapping a JMS message or a Core message to STOMP. A STOMP 1.0 client can check the presence of the content-length header to determine the type of the message body (String or bytes) tor> The type of this attribute is integer. When this attributed is configured, the broker will check the size of the body of each STOMP frame arrived from connections established with this acceptor when they have not received any packets from the server within the time given by client-failure- check-period as explained in section Detecting Dead Connections. 11.1. Reconnect to the same server Set0 码力 | 539 页 | 11.16 MB | 1 年前3Apache ActiveMQ Artemis 2.36.0 User Manual
same logic applies when mapping a JMS message or a Core message to STOMP. A STOMP 1.0 client can check the presence of the content-length header to determine the type of the message body (String or bytes) tor> The type of this attribute is integer. When this attributed is configured, the broker will check the size of the body of each STOMP frame arrived from connections established with this acceptor when they have not received any packets from the server within the time given by client-failure- check-period as explained in section Detecting Dead Connections. 11.1. Reconnect to the same server Set0 码力 | 539 页 | 11.14 MB | 1 年前3Apache ActiveMQ Artemis 2.35.0 User Manual
same logic applies when mapping a JMS message or a Core message to STOMP. A STOMP 1.0 client can check the presence of the content-length header to determine the type of the message body (String or bytes) tor> The type of this attribute is integer. When this attributed is configured, the broker will check the size of the body of each STOMP frame arrived from connections established with this acceptor when they have not received any packets from the server within the time given by client-failure- check-period as explained in section Detecting Dead Connections. 11.1. Reconnect to the same server Set0 码力 | 537 页 | 11.11 MB | 1 年前3Apache ActiveMQ Artemis 2.34.0 User Manual
same logic applies when mapping a JMS message or a Core message to STOMP. A STOMP 1.0 client can check the presence of the content-length header to determine the type of the message body (String or bytes) tor> The type of this attribute is integer. When this attributed is configured, the broker will check the size of the body of each STOMP frame arrived from connections established with this acceptor when they have not received any packets from the server within the time given by client-failure- check-period as explained in section Detecting Dead Connections. 11.1. Reconnect to the same server Set0 码力 | 537 页 | 11.11 MB | 1 年前3Apache ActiveMQ Artemis 2.30.0 User Manual
methods for an address' duplicate ID cache to check the cache's size and clear it Support for min/max expiry-delay Per-acceptor security domains Command-line check tool for checking the health of a broker AMQP. Bug fixes. 1.5.0 Full release notes. Highlights: AMQP performance improvements. JUnit rule implementation so messaging resources like brokers can be easily configured in tests. Basic CDI A comma separated string to be passed on to the broker config as network-check-list. The broker will shutdown when all these addresses are unreachable. Using0 码力 | 500 页 | 6.37 MB | 1 年前3Apache ActiveMQ Artemis 2.29.0 User Manual
methods for an address' duplicate ID cache to check the cache's size and clear it Support for min/max expiry-delay Per-acceptor security domains Command-line check tool for checking the health of a broker AMQP. Bug fixes. 1.5.0 Full release notes. Highlights: AMQP performance improvements. JUnit rule implementation so messaging resources like brokers can be easily configured in tests. Basic CDI A comma separated string to be passed on to the broker config as network-check-list. The broker will shutdown when all these addresses are unreachable. Using0 码力 | 499 页 | 6.37 MB | 1 年前3
共 372 条
- 1
- 2
- 3
- 4
- 5
- 6
- 38