profile image
Mark Sheyn
Solution Architect
About
Mark is a Solution Architect working at L2 support for various HCL products: Unica Discover, SoFY is the name of few. He has more than 17 years of comprehensive experience in the information technology, services, and software industry, proving records of resolving problems and achieving the highest level of customer satisfaction.
Posts by Mark Sheyn
article-img
Marketing & Commerce | November 4, 2021
Configuring ELK components in Unica Discover 12.1.2
When we are asked what is Elasticsearch used for ? Some of you may say it is an indexing tool, or an analytics solution, maybe some will answer it is an unstructured database, a Big data software or even some may think it's like Google search with autosuggest on your complex data. It is actually all of the above and more... But... What is Elasticsearch? Throughout the years it has evolved to become a complete solution known as the ELK stack, a simple, fast and scalable ecosystem that had become popular for exploring your complex data. The ELK Stack is a collection of three open-source products — Elasticsearch, Logstash, and Kibana. ELK is one of the few new-age frameworks which is capable of handling Big Data demands and scale. ELK Stack is designed to allow users to take data from any source in any format and search, analyze, and visualize that data in real-time. Logstash works towards parsing and transforming event data which is then passed on to Elasticsearch to be stored, searched and indexed. Kibana then accesses Elasticsearch DB to Explore, Visualize and Share. ELK has been utilized in the latest Unica Discover 12.1.2 to expose Discover logs, windows logs (Widows Event Viewer) and also to use ElasticSearch to search the log files. There is documentation on ELK Configuration that will help you learn more about the ELK stack in Unica Discover. In this blog, I'd like to consolidate the information from our documentation and provide clear steps on how to configure ELK in Unica Discover. Steps for configuring ELK components in Unica Discover  1. After Unica Discover 12.1.2 upgrade/installation, the "System Logs" will appear on the portal under "Discover." 2. Steps to configure ELK components on the portal. NOTE: If you are a new user or an existing...
article-img
Marketing & Commerce | May 12, 2021
Unica Discover – Configuring HBR (Health-based Routing) Transport Service Pipeline Agent
In the world of marketing, the customer is a real asset. And to deliver great customer experiences, the marketing team needs to dive right into the customer insights - what they like, when and where to reach out, what people are interested in, and how best to connect. Unica Discover is the offering of Unica Suite that helps you by providing behavioral insight into the online user journey, allowing you to deliver the kind of optimized experience that improves conversion and makes users want to visit again. In this blog today, we will highlight the Health-based Routing) Transport Service Pipeline Agent of Unica Discover and how you can easily configure it. Transport service is a 32-bit process. Multiple pipeline agents are running under transport service. HBR is one of the pipeline agents. HBR can run the main process (parent pipeline) and also child pipelines. Original HBR agent has a limitation: parent and child pipelines are sharing the same memory allocation. 32 bits process can utilize up to 2 GB. Often, memory utilization exceeds the 2GB limit, and transport service is restarting or just stays down. The goal is to - Optimize and improve the performance of HBR agent. Fully Utilize all hardware (RAM) resources of the machine. SOLUTION MODULE AND KEY FEATURES Health-Based Routing enables the routing of hit data to multiple canisters for processing based on the health and load on each canister. Use HBREx agent instead of the original HBR. The Extended HBR session agent (HBREx) implements multiple child pipelines for an individual pipeline in the canister to better utilize memory. This improves the hits processing performance of the pipeline. The difference between original HBR and Extended HBR (HBREx) is that child pipelines are running separate processes in HBREx and are no longer part of the parent pipeline process....
Close
Filters result by
Sort:
|