Installing the MaxMind GeoIPLite2 IP lookup database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 2.5.6. Installing Geonames database . . . . . . . . . . . . . . . . . . . . . . . code such as client-side code. Since there is no difference between this endpoint and any other administration-focused endpoints, attackers could easily re-use stolen credentials to wreak havock on the whole INSTALLING THE MAXMIND GEOIPLITE2 IP LOOKUP DATABASE Apache Unomi requires an IP database in order to resolve IP addresses to user location. The GeoLite2 database can be downloaded from MaxMind here : http://dev

code such as client-side code. Since there is no difference between this endpoint and any other administration-focused endpoints, attackers could easily re-use stolen credentials to wreak havock on the whole INSTALLING THE MAXMIND GEOIPLITE2 IP LOOKUP DATABASE Apache Unomi requires an IP database in order to resolve IP addresses to user location. The GeoLite2 database can be downloaded from MaxMind here : http://dev mmdb file into the "etc" directory. 4.6. INSTALLING GEONAMES DATABASE Apache Unomi includes a geocoding service based on the geonames database ( http://www.geonames.org/ (http://www.geonames.org/) ). It

Installing the MaxMind GeoIPLite2 IP lookup database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 2.6.3. Installing Geonames database . . . . . . . . . . . . . . . . . . . . . . . INSTALLING THE MAXMIND GEOIPLITE2 IP LOOKUP DATABASE The Context Server requires an IP database in order to resolve IP addresses to user location. The GeoLite2 database can be downloaded from MaxMind into the "etc" directory. 2.6.3. INSTALLING GEONAMES DATABASE Context server includes a geocoding service based on the geonames database ( http://www.geonames.org/ ). It can be used to create

fulfills the order, sends order information to the warehouse system and then updates the order database with the order details. Once it’s done that it acknowledges the message to tell the server that has been processed and can be forgotten about. Often the send to the warehouse system, update in database and acknowledgement will be completed in a single transaction to ensure ACID properties. 3.2.2 allows outrageous persistence message performance, something not achievable when using a relational database for persistence (although JDBC is still an option if necessary). Apache ActiveMQ Artemis clients

fulfills the order, sends order information to the warehouse system and then updates the order database with the order details. Once it’s done that it acknowledges the message to tell the server that has been processed and can be forgotten about. Often the send to the warehouse system, update in database and acknowledgement will be completed in a single transaction to ensure ACID properties. 3.2.2 allows outrageous persistence message performance, something not achievable when using a relational database for persistence (although JDBC is still an option if necessary). Apache ActiveMQ Artemis clients

fulfills the order, sends order information to the warehouse system and then updates the order database with the order details. Once it’s done that it acknowledges the message to tell the server that has been processed and can be forgotten about. Often the send to the warehouse system, update in database and acknowledgement will be completed in a single transaction to ensure ACID properties. 3.2.2 allows outrageous persistence message performance, something not achievable when using a relational database for persistence (although JDBC is still an option if necessary). Apache ActiveMQ Artemis clients

fulfills the order, sends order information to the warehouse system and then updates the order database with the order details. Once it’s done that it acknowledges the message to tell the server that has been processed and can be forgotten about. Often the send to the warehouse system, update in database and acknowledgement will be completed in a single transaction to ensure ACID properties. 3.2.2 allows outrageous persistence message performance, something not achievable when using a relational database for persistence (although JDBC is still an option if necessary). Apache ActiveMQ Artemis clients

fulfills the order, sends order information to the warehouse system and then updates the order database with the order details. Once it’s done that it acknowledges the message to tell the server that has been processed and can be forgotten about. Often the send to the warehouse system, update in database and acknowledgement will be completed in a single transaction to ensure ACID properties. 3.2.2 allows outrageous persistence message performance, something not achievable when using a relational database for persistence (although JDBC is still an option if necessary). Apache ActiveMQ Artemis clients

341 Embedded Database Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341 Connection to a Production Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358 Embedded Database Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366 Connecting to a MongoDB Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

341 Embedded Database Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341 Connection to a Production Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358 Embedded Database Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366 Connecting to a MongoDB Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .