Application Scaling in PAM360 using Microsoft SQL Server10 minutes to read
In general, Scaling is the process of making an application bigger and better, and scalability is the inherent capacity of an application to handle growth without any hindrance. For a privileged access security solution like PAM360, it is essential to make it highly available and scalable so that even with increased complexity, the application can render the maximum overall performance, without having any significant effect on the average service level per node. The Application Scaling model in PAM360, designed using Microsoft SQL server, is aimed at providing enhanced scalability and performance while ensuring uninterrupted access to the privileged resources and passwords stored in PAM360. The model works with one main PAM360 node and several subnodes, all of them connected to a single MS-SQL database cluster.
1. How does it Work?The main node for PAM360 and all its subnodes must point to the same MS-SQL cluster, though they do not have to be connected individually. However, the main node, i.e., the machine that will carry out the scheduled operations, requires to fulfill either of the following conditions:
The Architecture Diagram Depicting Application Scalability in PAM360
2. Steps to Configure the Main Node and SubnodesTo configure subnodes pointing to the same cluster, follow the below steps:
2.1 Steps to View the Configured Nodes in PAM360Once the main node and subnodes are configured, navigate to Admin >> Configuration >> Application Scaling to view them from the PAM360 interface. Here, you can enable or disable Application Scaling using the toggle button. 3. Steps to Change a Subnode into a Main NodeFollow the below steps to change any secondary node into the main node. This change can be done at any point of time from any subnodes.
For Windows: For Linux: Click here for more information on how to set up a Microsoft SQL cluster. 4. Steps to Rename a Node
5. Steps to Enable/Disable a Subnode
6. Steps to Delete and Restore a SubnodeNavigate to Admin >> Configuration >> Application Scaling. To Delete a Subnode,
7. Node Audit TrailsPAM360, by default, provides separate sections for Resource, User, and Task-based audits. Additionally, the product shows node-based audits for the main node and each subnode as separate columns with the complete audit trails under Resource Audit and User Audit when Application Scaling is enabled. To know more about Audits, click here. | |
[Webinar] Weave privileged access security into your org-wide ITSM workflows. Register now