Table of contents Set Up a New Aternity Data Warehouse Server on a Dedicated PC For large deployments of Aternity on-premise (more than 25,000 monitored devices), you must create a standalone Aternity Data Warehouse Server. The Data Warehouse Server stores the raw data gathered from the Aggregation Servers, and aggregates (summarizes) it for the Database Server. It constantly aggregates and re-summarizes data in the main database in the background, replacing older, more detailed data with summary data as it ages. Therefore older data typically has limited drill-down capabilities. Create a standalone Data Warehouse Server for larger deployments Before you begin Complete deployment of the Aternity Database Server. (Non-DBAs) Use the express database setup for small deployments up to 3000 devices. (DBAs only) Use the custom database setup for larger deployments or to integrate any sized database properly into your enterprise. Complete setting up the Aternity Dashboard Server and the Dashboard Gateway. Complete setting up the Aternity Management Server. Complete setting up the Aternity dashboard layouts. Check your PC conforms to the minimum system requirements: Attribute Requirement Operating system for Management Server and Data Warehouse Server Windows Server 64 bit 2012 R2, 2012, or 2008 R2. Set the date and time formats to Control Panel > Regions > Formats > English (United States). Hardware Hardware specifications depend on the size of your Aternity on-premise deployment. Choose the sizing and hardware specifications for your deployment size. Permissions Ensure you have local administrator privileges on this computer. ProcedureStep 1 Access your standalone Data Warehouse Server PC. Step 2 Log in to the computer as a local administrator. To verify you are a local administrator on this computer, not a domain administrator, open the System control panel, select Advanced system settings > Computer Name, and confirm the Change button is active. Step 3 Download the latest version of Aternity on-premise from our website. The setup package is for all Aternity servers. Download Aternity on-premise from the website Step 4 Right-click the setup and select Run as administrator to begin. Step 5 Select Next and enter the pathname of a local, non-system drive. This reduces the risk of the server application competing with the operating system for disk space. Select the location of the Management Server files Step 6 Confirm that it selects Aternity Data Warehouse Server. Since this is the same tool as that used for the Management Server, select only this option to ensure it is a standalone server. Select the Aternity Data Warehouse Server to create a standalone server Step 7 Select if you want the incoming connection to the Data Warehouse Server (from the Management Server) to be encrypted with HTTPS. Select whether this server receives data encrypted (HTTPS) Field Description HTTP or HTTPS Select HTTPS if you want any connection to this server to be via HTTPS. Tip To see the Aternity's system-wide security settings, view the security overview of all components. Port Enter the port required to receive data from the monitored devices. The default for HTTPS is 443. Custom keystore Enter the pathname of the system's keystore containing your enterprise's certificate. You must add your certificate to the system's Java keystore file (.jks) using Java's keytool utility (see Oracle's keytool documentation). Custom keystore password Enter the password required to access the system's keystore file. Step 8 Configure the memory allocation size of your deployment, and confirm the timezone of the Aternity servers on this computer. Configure the memory allocation and time zone Field Description Java Virtual Machine memory Configure the JVM heap size according to the values listed for the size of your deployment. You can tweak this value later on if required. Customize Timezone Select a time zoneĀ if you want to override the timezone settings of the operating system. Important The time zones of the Database Server, Dashboard Server, Management Server, and Data Warehouse Server must all be identical. JMS Memory Maximum Enter the ActiveMQ JVM heap size according to the value listed for this server for the size of your deployment. You can tweak this value later if required. Step 9 Review the summary, then select Next. Step 10 Define this server's connection to the Management Server. The Data Warehouse Server receives its input and sends its output via the Management Server. Point to the Management Server Field Description Management Server Hostname / IP Address Enter the hostname or IP which is the listening address you defined when creating the Management Server. Management Server Port Enter the port number which it uses for HTTP or HTTPS access, defined when creating the Management Server. Use SSL Transport Select if you defined the Management Server to use secure HTTPS when accessing it. Step 11 Confirm the summary and complete the setup. Step 12 Verify the deployment was successful by confirming that the Windows services shows AternityPlatform as running. Parent topic Install Aternity on-premise v9.0 / 9.0.1Related tasksExpress Setup for the Database Server (for non-DBAs)Set Up a New Aternity Dashboard ServerSet Up a New Aternity Dashboard Gateway ServerSet Up a New Aternity Management ServerAdd Aternity's Dashboard LayoutsSet Up a New Aternity Aggregation Server on a Dedicated PC SavePDF Selected topic Selected topic and subtopics All content Related Links
Set Up a New Aternity Data Warehouse Server on a Dedicated PC For large deployments of Aternity on-premise (more than 25,000 monitored devices), you must create a standalone Aternity Data Warehouse Server. The Data Warehouse Server stores the raw data gathered from the Aggregation Servers, and aggregates (summarizes) it for the Database Server. It constantly aggregates and re-summarizes data in the main database in the background, replacing older, more detailed data with summary data as it ages. Therefore older data typically has limited drill-down capabilities. Create a standalone Data Warehouse Server for larger deployments Before you begin Complete deployment of the Aternity Database Server. (Non-DBAs) Use the express database setup for small deployments up to 3000 devices. (DBAs only) Use the custom database setup for larger deployments or to integrate any sized database properly into your enterprise. Complete setting up the Aternity Dashboard Server and the Dashboard Gateway. Complete setting up the Aternity Management Server. Complete setting up the Aternity dashboard layouts. Check your PC conforms to the minimum system requirements: Attribute Requirement Operating system for Management Server and Data Warehouse Server Windows Server 64 bit 2012 R2, 2012, or 2008 R2. Set the date and time formats to Control Panel > Regions > Formats > English (United States). Hardware Hardware specifications depend on the size of your Aternity on-premise deployment. Choose the sizing and hardware specifications for your deployment size. Permissions Ensure you have local administrator privileges on this computer. ProcedureStep 1 Access your standalone Data Warehouse Server PC. Step 2 Log in to the computer as a local administrator. To verify you are a local administrator on this computer, not a domain administrator, open the System control panel, select Advanced system settings > Computer Name, and confirm the Change button is active. Step 3 Download the latest version of Aternity on-premise from our website. The setup package is for all Aternity servers. Download Aternity on-premise from the website Step 4 Right-click the setup and select Run as administrator to begin. Step 5 Select Next and enter the pathname of a local, non-system drive. This reduces the risk of the server application competing with the operating system for disk space. Select the location of the Management Server files Step 6 Confirm that it selects Aternity Data Warehouse Server. Since this is the same tool as that used for the Management Server, select only this option to ensure it is a standalone server. Select the Aternity Data Warehouse Server to create a standalone server Step 7 Select if you want the incoming connection to the Data Warehouse Server (from the Management Server) to be encrypted with HTTPS. Select whether this server receives data encrypted (HTTPS) Field Description HTTP or HTTPS Select HTTPS if you want any connection to this server to be via HTTPS. Tip To see the Aternity's system-wide security settings, view the security overview of all components. Port Enter the port required to receive data from the monitored devices. The default for HTTPS is 443. Custom keystore Enter the pathname of the system's keystore containing your enterprise's certificate. You must add your certificate to the system's Java keystore file (.jks) using Java's keytool utility (see Oracle's keytool documentation). Custom keystore password Enter the password required to access the system's keystore file. Step 8 Configure the memory allocation size of your deployment, and confirm the timezone of the Aternity servers on this computer. Configure the memory allocation and time zone Field Description Java Virtual Machine memory Configure the JVM heap size according to the values listed for the size of your deployment. You can tweak this value later on if required. Customize Timezone Select a time zoneĀ if you want to override the timezone settings of the operating system. Important The time zones of the Database Server, Dashboard Server, Management Server, and Data Warehouse Server must all be identical. JMS Memory Maximum Enter the ActiveMQ JVM heap size according to the value listed for this server for the size of your deployment. You can tweak this value later if required. Step 9 Review the summary, then select Next. Step 10 Define this server's connection to the Management Server. The Data Warehouse Server receives its input and sends its output via the Management Server. Point to the Management Server Field Description Management Server Hostname / IP Address Enter the hostname or IP which is the listening address you defined when creating the Management Server. Management Server Port Enter the port number which it uses for HTTP or HTTPS access, defined when creating the Management Server. Use SSL Transport Select if you defined the Management Server to use secure HTTPS when accessing it. Step 11 Confirm the summary and complete the setup. Step 12 Verify the deployment was successful by confirming that the Windows services shows AternityPlatform as running. Parent topic Install Aternity on-premise v9.0 / 9.0.1Related tasksExpress Setup for the Database Server (for non-DBAs)Set Up a New Aternity Dashboard ServerSet Up a New Aternity Dashboard Gateway ServerSet Up a New Aternity Management ServerAdd Aternity's Dashboard LayoutsSet Up a New Aternity Aggregation Server on a Dedicated PC
Set Up a New Aternity Data Warehouse Server on a Dedicated PC For large deployments of Aternity on-premise (more than 25,000 monitored devices), you must create a standalone Aternity Data Warehouse Server. The Data Warehouse Server stores the raw data gathered from the Aggregation Servers, and aggregates (summarizes) it for the Database Server. It constantly aggregates and re-summarizes data in the main database in the background, replacing older, more detailed data with summary data as it ages. Therefore older data typically has limited drill-down capabilities. Create a standalone Data Warehouse Server for larger deployments Before you begin Complete deployment of the Aternity Database Server. (Non-DBAs) Use the express database setup for small deployments up to 3000 devices. (DBAs only) Use the custom database setup for larger deployments or to integrate any sized database properly into your enterprise. Complete setting up the Aternity Dashboard Server and the Dashboard Gateway. Complete setting up the Aternity Management Server. Complete setting up the Aternity dashboard layouts. Check your PC conforms to the minimum system requirements: Attribute Requirement Operating system for Management Server and Data Warehouse Server Windows Server 64 bit 2012 R2, 2012, or 2008 R2. Set the date and time formats to Control Panel > Regions > Formats > English (United States). Hardware Hardware specifications depend on the size of your Aternity on-premise deployment. Choose the sizing and hardware specifications for your deployment size. Permissions Ensure you have local administrator privileges on this computer. ProcedureStep 1 Access your standalone Data Warehouse Server PC. Step 2 Log in to the computer as a local administrator. To verify you are a local administrator on this computer, not a domain administrator, open the System control panel, select Advanced system settings > Computer Name, and confirm the Change button is active. Step 3 Download the latest version of Aternity on-premise from our website. The setup package is for all Aternity servers. Download Aternity on-premise from the website Step 4 Right-click the setup and select Run as administrator to begin. Step 5 Select Next and enter the pathname of a local, non-system drive. This reduces the risk of the server application competing with the operating system for disk space. Select the location of the Management Server files Step 6 Confirm that it selects Aternity Data Warehouse Server. Since this is the same tool as that used for the Management Server, select only this option to ensure it is a standalone server. Select the Aternity Data Warehouse Server to create a standalone server Step 7 Select if you want the incoming connection to the Data Warehouse Server (from the Management Server) to be encrypted with HTTPS. Select whether this server receives data encrypted (HTTPS) Field Description HTTP or HTTPS Select HTTPS if you want any connection to this server to be via HTTPS. Tip To see the Aternity's system-wide security settings, view the security overview of all components. Port Enter the port required to receive data from the monitored devices. The default for HTTPS is 443. Custom keystore Enter the pathname of the system's keystore containing your enterprise's certificate. You must add your certificate to the system's Java keystore file (.jks) using Java's keytool utility (see Oracle's keytool documentation). Custom keystore password Enter the password required to access the system's keystore file. Step 8 Configure the memory allocation size of your deployment, and confirm the timezone of the Aternity servers on this computer. Configure the memory allocation and time zone Field Description Java Virtual Machine memory Configure the JVM heap size according to the values listed for the size of your deployment. You can tweak this value later on if required. Customize Timezone Select a time zoneĀ if you want to override the timezone settings of the operating system. Important The time zones of the Database Server, Dashboard Server, Management Server, and Data Warehouse Server must all be identical. JMS Memory Maximum Enter the ActiveMQ JVM heap size according to the value listed for this server for the size of your deployment. You can tweak this value later if required. Step 9 Review the summary, then select Next. Step 10 Define this server's connection to the Management Server. The Data Warehouse Server receives its input and sends its output via the Management Server. Point to the Management Server Field Description Management Server Hostname / IP Address Enter the hostname or IP which is the listening address you defined when creating the Management Server. Management Server Port Enter the port number which it uses for HTTP or HTTPS access, defined when creating the Management Server. Use SSL Transport Select if you defined the Management Server to use secure HTTPS when accessing it. Step 11 Confirm the summary and complete the setup. Step 12 Verify the deployment was successful by confirming that the Windows services shows AternityPlatform as running. Parent topic Install Aternity on-premise v9.0 / 9.0.1Related tasksExpress Setup for the Database Server (for non-DBAs)Set Up a New Aternity Dashboard ServerSet Up a New Aternity Dashboard Gateway ServerSet Up a New Aternity Management ServerAdd Aternity's Dashboard LayoutsSet Up a New Aternity Aggregation Server on a Dedicated PC