Production
1. General Requirements
SN# | Server | Load balancer | Config | Details |
1 | Hybr front-end server 1 (Load balanced) |
|
| Front end server 1
|
2 | Hybr front-end server 2 (Load balanced) |
|
| Front end server 2
|
3 | Hybr RP server 1 (Load balanced) |
|
| Backend server 1
|
4 | Hybr RP server 2 (Load balanced) |
|
| Backend server 2
|
5 | SQL Server 1x SQL Server 1x |
Private IPs
|
| SQL Server that holds all 4 product’s databases |
2. VCONNECT SERVICE SPECIFIC REQUIREMENTS
This is required only if you have opted for VConnect feature capability that helps you manage On-premise and Cloud data centers. This must be on application server where VConnect will be installed.
VMware vSphere PowerCLI (Supported Versions: 5.5 to 6.3 R1)
VMM 2012/2016 Console (Supported Versions: UR10)
AWS CLI (Supported Versions: 1.11.10 to 1.11.13)
Azure PowerShell (Supported Versions: 1.5 - 7)
2.1 PowerShell configurations
Run the following commands in Command prompt on the Application Server and use appropriate thresholds for your environment
winrm set winrm/config/winrs '@{MaxShellsPerUser="500"}'
winrm set winrm/config/client '@{AllowUnencrypted="true"}'
Run the following commands in the Windows Power Shell ISE on the Application server and use appropriate thresholds for your environment
Set-Item -Path WSMan:\localhost\Plugin\microsoft.powershell\Quotas\MaxShells -Value 500
Set-Item -Path WSMan:\localhost\Plugin\microsoft.powershell\Quotas\MaxShellsPerUser -Value 500
Set-Item -Path WSMan:\localhost\Plugin\microsoft.powershell32\Quotas\MaxShells -Value 500
Set-Item -Path WSMan:\localhost\Plugin\microsoft.powershell32\Quotas\MaxShellsPerUser -Value 500
Restart-Service winrm
2.2 vSphere specific configuration
This is required for only for vCenter integration.
Clusters that will be configured with VConnect must have DRS turned on in vCenter
Ensure that VM Templates in the vCenter environment used for VM provisioning through VConnect, are created with only 1 core per socket and 1 CPU
3. WORKFLOW SERVICE SPECIFIC REQUIREMENTS
Need not share the below details, but be ready with this for workflow configuration
Smtp and Imap settings:
Host name
Port number
User name
Password
4. IDENTITY PROVIDERS
Supports Microsoft Entra ID or ADFS 2016
Microsoft Entra ID Pre-requisites
Use this only if cloud admin organization user accounts are maintained in Microsoft Entra ID
Refer Microsoft Entra ID prerequisites for steps to retrieve below information.
Directory ID
Application ID
Application Client Secret
Microsoft Entra ID user account for Admin (this should belong to the same directory mentioned above)
‘User’ directory role is enough for admin user
ADFS Pre-requisites
Use this only if cloud admin organization user accounts are maintained in ADFS
Application ID
Application Client Secret
Obtain Authority and Metadata address of ADFS 2016
User account for admin
‘User’ directory role for admin user is suffice
5. OTHERS
Azure storage account.
Standard storage account is needed for using Queues and Table. Refer section 3 of Microsoft Entra ID Prerequisites (link below).
Last updated