- Related Products
- ADAudit Plus
- ADSelfService Plus
- EventLog Analyzer
- Exchange Reporter Plus
- AD360
- Log360
This use case will list the steps to construct an orchestration policy to automatically update your MS SQL database using custom scripts whenever a user-specific action is performed in ADManager Plus.
User-specific arguments will be used to locate the users in the database and based on the request sent, appropriate action will be carried out in the product.
Prerequisite: Ensure that the MS SQL script is downloaded and moved into the <InstallationDirectory>\ADManager Plus\Scripts folder.
Creating an orchestration template using custom scripts
Action | Arguments | Example |
---|---|---|
Insert | Server Name, Database Name, Port Number, Authentication Type, Table Name, Column Names, Column Values, User Name, Password | Windows Authentication "EmpServer", "Empdata", "1433", "Windows", "Users", "col1|col2", "%employeeID%|%telephoneNumber%" Server Authentication |
Update | Server Name, Database Name, Port Number, Authentication Type, Table Name, Column Names, Column Values, Where Query, User Name, Password | Windows Authentication "EmpServer", "Empdata","1433" "Windows","Users","col1|col2" "%employeeID%|%telephoneNumber%","samAccountName='%sAMAccountName%'" Server Authentication |
Delete | Server Name, Database Name, Port Number, Authentication Type, Table Name, Where Query, User Name, Password | Windows Authentication "EmpServer","Empdata","1433","Windows","Users","samAccountName='%sAMAccountName%'" Server Authentication |
This use case will list the steps to construct an orchestration to automatically update your Oracle database using custom scripts whenever a user-specific action is performed in ADManager Plus.
User-specific arguments will be used to locate the users in the database and based on the request sent, appropriate action will be carried out in the product.
Ensure that the following steps are performed before orchestrating this event:
Action | Arguments | Example |
---|---|---|
Insert | Host ID, Port Number, Service Name, User Name, Password, DBA Privilege, Table Name, Column Names, Column Values | "localhost", "1521", "sys", "Oracle", "orcl.test", "SYSDBA" "Users", "col1|col2", "%employeeID%|%telephoneNumber%" |
Update | Host Id, Port Number, Service Name, User Name, Password, DBA Privilege, Table Name, Column Names, Column Values, Where Query | "localhost", "1521", "sys", "Oracle", "orcl.test", "SYSDBA" "Users", "col1|col2", "%employeeID%|%telephoneNumber%", "samAccountName='%sAMAccountName%'" |
Delete | Host Id, Port Number, Service Name, User Name, Password, DBA Privilege, Table Name, Where Query | "localhost", "1521", "sys", "Oracle", "orcl.test", "SYSDBA" "Users", "samAccountName='%sAMAccountName%'" |
This use case will list the steps to construct an orchestration to automatically update your PostgreSQL database using custom scripts whenever a user-specific action is performed in ADManager Plus.
User-specific arguments will be used to locate the users in the database and, based on the request sent, appropriate action will be carried out in the product.
Ensure that the following steps are performed before orchestrating this event:
Action | Arguments | Example |
---|---|---|
Insert | Driver Name, Server, Port Number, Database, User Name, Password, Table Name, Column Names, Column Values | "PostgreSQL Unicode(x64)", "TestServer1", "45678", "TestDB", "loginUser", "Test@123" "Users", "col1|col2", "%employeeID%|%telephoneNumber%" |
Update | Driver Name, Server, Port Number, Database, User Name, Password, Table Name, Column Names, Column Values, Where Query | "PostgreSQL Unicode(x64)", "TestServer1", "45678", "TestDB", "loginUser", "Test@123" "Users", "col1|col2", "%employeeID%|%telephoneNumber%" "samAccountName='%sAMAccountName%'" |
Delete | Driver Name, Server, Port Number, Database, User Name, Password, Table Name, Where Query | "PostgreSQL Unicode(x64)", "TestServer1", "45678", "TestDB", "loginUser", "Test@123" "Users", "samAccountName='%sAMAccountName%'" |