Table of contents Plan your Deployment Strategy for Aternity on-premise 11.0.3 To plan your Aternity on-premise deployment, you must choose the size, shape and contingencies to put into place for your deployment. Plan your deployment of Aternity on-premise ProcedureStep 1 Size your deployment to determine the number of servers and their hardware requirements. Some Aternity components can share the same computer, depending on the size of your deployment. Size of deployment Description Trial deployment (up to 1000 devices) Learn more Trial POC deployment for Aternity on-premise In the trial deployment, the Aternity Management Server hosts Oracle Database Server, Data Warehouse Server, and Aggregation Server. For details about the hardware specifications, learn more. Small deployment (up to 30,000 devices) Learn more Small Aternity deployment In the small deployment, the Aternity Management Server hosts Data Warehouse Server. For details about the hardware specifications, learn more. Medium deployments (up to 60,000 devices) Learn more Medium sized Aternity deployment Aternity requires one Aggregation Server per 40,000 monitored devices and one Vertica Database Server node per 25,000 monitored devices. So, calculate the number of servers you need following the amount of monitored devices in your organization. Data Warehouse Server should be deployed on a dedicated machine separately from other Aternity servers in deployments with more than 40,000 monitored devices. For details about the hardware specifications, learn more. Large deployments (up to 110,000 devices Learn more Large Aternity deployment Aternity requires one Aggregation Server per 40,000 monitored devices and one Vertica Database Server node per 25,000 monitored devices. So, calculate the number of servers you need following the amount of monitored devices in your organization. Data Warehouse Server should be deployed on a dedicated machine separately from other Aternity servers in deployments with more than 40,000 monitored devices. For details about the hardware specifications, learn more. X-large deployments (up to 160,000 devices) Learn more X-large Aternity deployment Aternity requires one Aggregation Server per 40,000 monitored devices and one Vertica Database Server node per 25,000 monitored devices. So, calculate the number of servers you need following the amount of monitored devices in your organization. Data Warehouse Server should be deployed on a dedicated machine separately from other Aternity servers in deployments with more than 40,000 monitored devices. For details about the hardware specifications, learn more. XX-large deployments (up to 220,000 devices) Learn more XX-large Aternity deployment Aternity requires one Aggregation Server per 40,000 monitored devices and one Vertica Database Server node per 25,000 monitored devices. So, calculate the number of servers you need following the amount of monitored devices in your organization. Data Warehouse Server should be deployed on a dedicated machine separately from other Aternity servers in deployments with more than 40,000 monitored devices. For details about the hardware specifications, learn more. Step 2 Secure your deployment to determine whether to implement secure HTTPS for external access to Aternity. Secure your connections to monitored devices and to users of the system Step 3 Choose the network topology of your deployment, which determines the placement of firewalls and any ports to open between them. Centralized deployment of Aternity on-premise Step 4 Choose a policy of backups for your deployment. Implement redundancy via failover in Aternity Step 5 Prepare the operating systems and other software requirements for each server. Important Synchronize all Aternity components to have the same date, time AND time zone. Step 6 Perform your setup or upgrade of Aternity on-premise on the computers you prepared. Step 7 Plan and deploy Agent for End User Devices on devices, so they report their performance to Aternity Important Aternity on-premise 11.x requires that devices ONLY run Agent for End User Devices 9.0, 9.1.7, 9.2.x, or Agent 11.0. Product Supported Agent for End User Devices Aternity 11.x Agent 9.0, 9.1.7, 9.2.x, or Agent 11.0 Aternity 10.x Agent 9.0.x, 9.1.7 or 9.2.5 ONLY. Aternity 9.x Agent 9.0.x ONLY. Workflow for deploying Agent for End User Devices in your organization Choose Aternity Sizing and Hardware System RequirementsChoose the Network Topology Layout for AternityChoose your Backup Strategy for Aternity 11.0.3Parent topic Start Deploying Aternity on-premise 11.0.3 ServersRelated tasksInstall Aternity on-premise 11.0.3Related referenceSecure Your Aternity on-premise Deployment (Getting Started) SavePDF Selected topic Selected topic and subtopics All content Related Links
Plan your Deployment Strategy for Aternity on-premise 11.0.3 To plan your Aternity on-premise deployment, you must choose the size, shape and contingencies to put into place for your deployment. Plan your deployment of Aternity on-premise ProcedureStep 1 Size your deployment to determine the number of servers and their hardware requirements. Some Aternity components can share the same computer, depending on the size of your deployment. Size of deployment Description Trial deployment (up to 1000 devices) Learn more Trial POC deployment for Aternity on-premise In the trial deployment, the Aternity Management Server hosts Oracle Database Server, Data Warehouse Server, and Aggregation Server. For details about the hardware specifications, learn more. Small deployment (up to 30,000 devices) Learn more Small Aternity deployment In the small deployment, the Aternity Management Server hosts Data Warehouse Server. For details about the hardware specifications, learn more. Medium deployments (up to 60,000 devices) Learn more Medium sized Aternity deployment Aternity requires one Aggregation Server per 40,000 monitored devices and one Vertica Database Server node per 25,000 monitored devices. So, calculate the number of servers you need following the amount of monitored devices in your organization. Data Warehouse Server should be deployed on a dedicated machine separately from other Aternity servers in deployments with more than 40,000 monitored devices. For details about the hardware specifications, learn more. Large deployments (up to 110,000 devices Learn more Large Aternity deployment Aternity requires one Aggregation Server per 40,000 monitored devices and one Vertica Database Server node per 25,000 monitored devices. So, calculate the number of servers you need following the amount of monitored devices in your organization. Data Warehouse Server should be deployed on a dedicated machine separately from other Aternity servers in deployments with more than 40,000 monitored devices. For details about the hardware specifications, learn more. X-large deployments (up to 160,000 devices) Learn more X-large Aternity deployment Aternity requires one Aggregation Server per 40,000 monitored devices and one Vertica Database Server node per 25,000 monitored devices. So, calculate the number of servers you need following the amount of monitored devices in your organization. Data Warehouse Server should be deployed on a dedicated machine separately from other Aternity servers in deployments with more than 40,000 monitored devices. For details about the hardware specifications, learn more. XX-large deployments (up to 220,000 devices) Learn more XX-large Aternity deployment Aternity requires one Aggregation Server per 40,000 monitored devices and one Vertica Database Server node per 25,000 monitored devices. So, calculate the number of servers you need following the amount of monitored devices in your organization. Data Warehouse Server should be deployed on a dedicated machine separately from other Aternity servers in deployments with more than 40,000 monitored devices. For details about the hardware specifications, learn more. Step 2 Secure your deployment to determine whether to implement secure HTTPS for external access to Aternity. Secure your connections to monitored devices and to users of the system Step 3 Choose the network topology of your deployment, which determines the placement of firewalls and any ports to open between them. Centralized deployment of Aternity on-premise Step 4 Choose a policy of backups for your deployment. Implement redundancy via failover in Aternity Step 5 Prepare the operating systems and other software requirements for each server. Important Synchronize all Aternity components to have the same date, time AND time zone. Step 6 Perform your setup or upgrade of Aternity on-premise on the computers you prepared. Step 7 Plan and deploy Agent for End User Devices on devices, so they report their performance to Aternity Important Aternity on-premise 11.x requires that devices ONLY run Agent for End User Devices 9.0, 9.1.7, 9.2.x, or Agent 11.0. Product Supported Agent for End User Devices Aternity 11.x Agent 9.0, 9.1.7, 9.2.x, or Agent 11.0 Aternity 10.x Agent 9.0.x, 9.1.7 or 9.2.5 ONLY. Aternity 9.x Agent 9.0.x ONLY. Workflow for deploying Agent for End User Devices in your organization Choose Aternity Sizing and Hardware System RequirementsChoose the Network Topology Layout for AternityChoose your Backup Strategy for Aternity 11.0.3Parent topic Start Deploying Aternity on-premise 11.0.3 ServersRelated tasksInstall Aternity on-premise 11.0.3Related referenceSecure Your Aternity on-premise Deployment (Getting Started)
Plan your Deployment Strategy for Aternity on-premise 11.0.3 To plan your Aternity on-premise deployment, you must choose the size, shape and contingencies to put into place for your deployment. Plan your deployment of Aternity on-premise ProcedureStep 1 Size your deployment to determine the number of servers and their hardware requirements. Some Aternity components can share the same computer, depending on the size of your deployment. Size of deployment Description Trial deployment (up to 1000 devices) Learn more Trial POC deployment for Aternity on-premise In the trial deployment, the Aternity Management Server hosts Oracle Database Server, Data Warehouse Server, and Aggregation Server. For details about the hardware specifications, learn more. Small deployment (up to 30,000 devices) Learn more Small Aternity deployment In the small deployment, the Aternity Management Server hosts Data Warehouse Server. For details about the hardware specifications, learn more. Medium deployments (up to 60,000 devices) Learn more Medium sized Aternity deployment Aternity requires one Aggregation Server per 40,000 monitored devices and one Vertica Database Server node per 25,000 monitored devices. So, calculate the number of servers you need following the amount of monitored devices in your organization. Data Warehouse Server should be deployed on a dedicated machine separately from other Aternity servers in deployments with more than 40,000 monitored devices. For details about the hardware specifications, learn more. Large deployments (up to 110,000 devices Learn more Large Aternity deployment Aternity requires one Aggregation Server per 40,000 monitored devices and one Vertica Database Server node per 25,000 monitored devices. So, calculate the number of servers you need following the amount of monitored devices in your organization. Data Warehouse Server should be deployed on a dedicated machine separately from other Aternity servers in deployments with more than 40,000 monitored devices. For details about the hardware specifications, learn more. X-large deployments (up to 160,000 devices) Learn more X-large Aternity deployment Aternity requires one Aggregation Server per 40,000 monitored devices and one Vertica Database Server node per 25,000 monitored devices. So, calculate the number of servers you need following the amount of monitored devices in your organization. Data Warehouse Server should be deployed on a dedicated machine separately from other Aternity servers in deployments with more than 40,000 monitored devices. For details about the hardware specifications, learn more. XX-large deployments (up to 220,000 devices) Learn more XX-large Aternity deployment Aternity requires one Aggregation Server per 40,000 monitored devices and one Vertica Database Server node per 25,000 monitored devices. So, calculate the number of servers you need following the amount of monitored devices in your organization. Data Warehouse Server should be deployed on a dedicated machine separately from other Aternity servers in deployments with more than 40,000 monitored devices. For details about the hardware specifications, learn more. Step 2 Secure your deployment to determine whether to implement secure HTTPS for external access to Aternity. Secure your connections to monitored devices and to users of the system Step 3 Choose the network topology of your deployment, which determines the placement of firewalls and any ports to open between them. Centralized deployment of Aternity on-premise Step 4 Choose a policy of backups for your deployment. Implement redundancy via failover in Aternity Step 5 Prepare the operating systems and other software requirements for each server. Important Synchronize all Aternity components to have the same date, time AND time zone. Step 6 Perform your setup or upgrade of Aternity on-premise on the computers you prepared. Step 7 Plan and deploy Agent for End User Devices on devices, so they report their performance to Aternity Important Aternity on-premise 11.x requires that devices ONLY run Agent for End User Devices 9.0, 9.1.7, 9.2.x, or Agent 11.0. Product Supported Agent for End User Devices Aternity 11.x Agent 9.0, 9.1.7, 9.2.x, or Agent 11.0 Aternity 10.x Agent 9.0.x, 9.1.7 or 9.2.5 ONLY. Aternity 9.x Agent 9.0.x ONLY. Workflow for deploying Agent for End User Devices in your organization Choose Aternity Sizing and Hardware System RequirementsChoose the Network Topology Layout for AternityChoose your Backup Strategy for Aternity 11.0.3Parent topic Start Deploying Aternity on-premise 11.0.3 ServersRelated tasksInstall Aternity on-premise 11.0.3Related referenceSecure Your Aternity on-premise Deployment (Getting Started)