Application Scaling in PAM360 using PostgreSQL Server10 minutes to read
Considering the continually growing user base, an organization should have continuous and uninterrupted access to the database to provide sustainable service. In general, application scaling is the process of improving an application's ability to handle huge loads and operations without disrupting its performance and user experience. In PAM360, implementing Application Scaling via the external PostgreSQL database cluster aims at providing uninterrupted access to the resources and accounts, thereby enhancing the application scalability and overall performance. The model operates with one main node and several subnodes connected by a single PostgreSQL database cluster. At the end of this document, you will have learned the following topics related to Application Scaling:
1. PrerequisitesThe PAM360 main node and all its sub-nodes should point to the same PostgreSQL database cluster, although they do not need to be connected individually. However, the main node, i.e., the machine that will perform the operations, is required to satisfy any of any of the following conditions:
The Architecture Diagram Depicting Application Scalability in PAM360Notes: 2. Configuring the Application Nodes (Main-Node and Subnode)To configure the main-node pointing to the database cluster, do the steps that follow:
Notes: To configure a subnode pointing to the same database cluster, do the steps that follow:
Note: Repeat the procedure for all the required subnodes. Now all the subnodes will start with the relevant SSL certificate and use the same PostgreSQL cluster as the backend database. Once the main-node and subnodes are configured, navigate to Admin >> Configuration >> Application Scaling to view and manage them from the PAM360 GUI. 3. Changing a Subnode into a Main-NodeFollow the below steps to change any of the configured subnode in the PostgreSQL database cluster into a main-node. This change can be done at any point in time from any of the available PAM360 application servers.
For Windows: For Linux: 4. Node-Based Operations Performed from PAM360 Web InterfaceNote: Only the administrators and users with custom roles having the 'Application Scaling' permission can enable, disable, rename, delete, and restore the subnode(s), from the server that act as a main-node. a. Enable/Disable a Subnode
b. Rename a Node
c. Delete and Restore a SubnodeNavigate to 'Admin >> Configuration >> Application Scaling'. To Delete a Subnode:
Note: Deleting the subnode will only hide the node from the Application Scaling dashboard and will not remove the entry from the database cluster. Delete the physical server and any server-specific configurations to remove the server from PAM360 entirely. To Restore a Subnode:
Note: The subnode(s) cannot be restored if the node(s) is(are) removed from the database cluster and the application server(s). 5. Node-Based Audit TrailsBy default, PAM360 comprises Resource, User, and Task-based audit categories. Once configured and Application Scaling is enabled, the product additionally shows node-based audits in each category with the main-node and available subnode(s) in separate columns. This assists you with the complete audit trails under Resource Audit and User Audit. To know more about Audits, click here. | |
[Webinar] Weave privileged access security into your org-wide ITSM workflows. Register now