 Sophia, the owner of a small but rapidly scaling logistics and delivery company, needs to automate several business processes such as managing package routing, optimizing driver schedules, and the customer support flow. Sophia wants to use a single instance of UnO to manage the different processes without disruptive interactions between them while keeping data separated between business areas. While Sophia might require more UnO instances for her purposes, she would like to keep the IT maintenance team small to reduce the overall costs.  The Solution: UnO with Multitenancy Multitenancy is an architectural model that enables a single product instance to securely serve multiple distinct tenants. This architecture is built on resource sharing: all hardware and software resources are shared among tenants, while each business process has its own data, which is kept separated from the others. This means each tenant gets its own isolated environment: separated scheduling items and user permissions, while sharing the same underlying UnO engine. The core of this type of deployment is running multiple independent automation environments without the overhead of maintaining different installations.  Sophia can now create and manage multiple tenants from the UnO Tenant Manager UI.  The tenant manager admins can assign different admin users to their respective tenants, both during the tenant creation and even later when editing them. Chosen admins receive an email within seconds when a tenant is created, including all the entry points to the new environment. Email templates, justification parameters and more multitenant-related properties can be set during the deployment phase by assigning proper values to variables inside the values.yaml file: refer to the official documentation on how to customize your UnO environment properly. The respective admins can define user roles and access control lists that are specific to a tenant and not usable/visible elsewhere. Sophia is enthusiastic about the business solution and decides to recommend this to her colleague, Peter. Peter really wants to try the solution, but he has no internal team to manage it and is afraid that he cannot set up the necessary infrastructure. Sophia suggests he adopt the HCL UnO SaaS solution, a multitenant environment managed by HCLSoftware. Peter can now fulfill the company’s needs easily and rapidly.  Francesco Carpineti Francesco is a Software Engineer with several years of Java experience across development, L3 support, and test automation. Currently working on the test automation for UnO UI, he combines a rigorous technical approach with the versatility gained from his extensive background as a theatrical actor.  Matteo Forti Born as a physicist with a passion for computer science and coding. Joined HCL in January 2022 and currently works as test leader for the UnO Team. Math enthusiast and science geek with a side passion for graphic arts and new technologies.  Federico Pizzari Federico Pizzari joined HCL in March 2023 as a Software Engineer and works in the UI team on the Dynamic Workload Console and the UnO UI. He has a bachelor’s degree in Computer Science and is working on his master’s degree. Strong enthusiast of everything tech, he also loves hiking, skiing and more generally being in contact with nature.  Giorgio Proietti
He joined HCL in January 2023, works on the UnO’s and Workload Automation’s UI as a Software Engineer. He has a passion for anything computer related, games and music.
0 Comments
Your comment will be posted after it is approved.
Leave a Reply. |
Categories
All
|
RSS Feed