Application Scaling with Microsoft SQL Server in PAM360
Application scaling with Microsoft (MS) SQL server in PAM360 is aimed at providing enhanced scalability and performance, and also to ensure uninterrupted access to the privileged resources and passwords stored in PAM360. The application scaling model works with a main PAM360 node and several sub nodes, all of them connecting to a common MS-SQL database cluster.
1. How Does it Work?
The main node for PAM360 and its corresponding sub nodes must point to the same MS-SQL cluster but they do not need to be connected to each other. However, the main node (or the machine that will carry out the schedule operations) needs to fulfill either of the following conditions:
- The main node and the target end-points for which agentless password management capabilities are enabled from PAM360 should reside in the same subnet.
- If the main node and the target end-points reside in different networks, they should be able to communicate to each other, i.e., they should not be blocked by a firewall or reside outside the range of connectivity such as demilitarized zones.
2. Steps to Configure Sub Nodes
To configure sub nodes pointing to the same cluster, follow the below steps:
- Install the PAM360 in the machine which will act as the main node.
- In the PAM360 installation directory, copy the database_params file from this path:
< PAM360_installation_directory >\conf\database_params.conf.
- Paste the database_params.conf file to the path < PAM360_installation_directory >\conf\> in all the nodes which you want to assign as the sub nodes for PAM360.
- Install PAM360 in all the secondary nodes.
2.1 Steps to View the Configured Nodes in PAM360
Once the main node and sub nodes are configured, follow the below steps to view them from the PAM360 interface.
- Navigate to Admin >> Configuration >> Application Scaling.
- Here, you can enable or disable the sub nodes using the toggle button. However, you need to restart the main node and decommission the sub nodes for the changes to take effect.
3. Steps to Change a Sub Node into a Main Node
Follow the below steps to change any secondary node into the main node. This change can be done at any point of time from any sub nodes.
- Keep the MS-SQL database running.
- Stop all application servers including the main node.
- Open a command prompt and execute the following commands:
- Current main node and the list of available servers will be displayed. Choose any server from the drop-down and click Save.
- Restart all application servers that were stopped earlier.
- The selected server will be assigned as the main node now.
Click here for more information on how to set up a Microsoft SQL cluster.