...
The EmpowerID SaaS option alleviates all infrastructure concerns, allowing you to focus on solving business needs with EmpowerID on day one. EmpowerID SaaS runs on a fully redundant Microsoft Azure infrastructure in the region of your choice, with all aspects of management and monitoring handled by our infrastructure team. EmpowerID SaaS deployments are appropriately sized to balance your organization’s demanding SLAs with costs and scaled as and when needed. Additional service options are available for SaaS customers to offload all EmpowerID management tasks, including configuration management, converting their SaaS EmpowerID into a fully managed service. All Customers can phase out all managed service offerings can be phased out as a customer develops as they develop their own internally trained support staff.
Organizations can self-host EmpowerID in their own private Microsoft Azure tenant. Our team can provide any level of support, ranging from consulting to assist your engineers in designing your infrastructure to offering a full-managed service to run and manage your EmpowerID installation. Support for other public cloud platforms such as Amazon Web Services (AWS) is in beta now.
An on-premise installation of EmpowerID allows an organization to manage Cloud and on-premise systems but run EmpowerID from their own data centers. If these organizations run Kubernetes clusters today to host other services, running EmpowerID containers on-premises is easily accomplished. While the traditional installation model is an option for organizations without the know-how to run Kubernetes clusters, EmpowerID is currently testing a lightweight Kubernetes Virtual Appliance technology to offer the benefits of a containerized deployment without all the complexity involved with rolling out a new Kubernetes infrastructure.
...
EmpowerID Worker – Worker containers make up the application tier of the system. They are used for back-end processing of system integration processes such as inventory, synchronization, security management, and internal web service processes. The number and specifications of these depend on the number and types of applications and integration processes being managed. These containers do not service User Interface requests. The EmpowerID Worker container role also performs the same functions as the on-premise Worker Role Service.
It has no inbound connections, so it does not listen on a port or require SSL port bindings.
It requires IIS and is used to process EmpowerID Web Service Garden (used for all of its Worker Process functions).
Responsible for running scheduled jobs and long-running tasks such as…
RBAC Security Compilation
Inventory processing
Resource entitlement processing
Rights enforcement
...
| Info |
|---|
Related Docs Topics: |
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|