Quick Start: Install Alchemize Today!

Learn how to install Alchemize with ease! This guide walks you through the step-by-step process, ensuring a smooth setup for leveraging Alchemize’s powerful data transformation and integration capabilities. Get started quickly and unlock seamless data operations.

Watch the step-by-step video or download the detailed guide to get started effortlessly!

Alchemize's Installation Guide

Frequently Asked Questions

Can’t find what you are looking for?
Contact our gurus at QA@MaxisTechnology.com

Why is Alchemize not starting and giving a 500 error?

  • A 500 error usually indicates a server issue. Check the following:
  • Ensure the Tomcat service is running on the Front End and Worker nodes.
  • Confirm that all required services, like PostgreSQL, are active and accessible from each node.
  • Verify that the configuration details (database username, password, IP addresses, etc.) were correctly entered during installation.
  • Review the Tomcat logs for any specific error messages that could point to missing configurations or dependency issues.

How can I verify that all Alchemize services are running correctly?

  • Log into each node and check the status of critical services:
  • For Tomcat, use # sudo systemctl status tomcat.
  • For PostgreSQL, use # sudo systemctl status postgresql or the command specific to your database.
  • You can also check the Alchemize logs located on the Front End node for any warnings or errors.

What should I do if the installation fails partway through?

  • If the installation process fails:
  • Review the console output for error messages. The specific step or error will provide clues.
  • Verify that all prerequisites (dependencies, correct operating system version, etc.) are installed.
  • Ensure the user executing the installation has the necessary permissions.
  • Check the installer logs, if available, for more details on where the process may have stopped.

How do I change the JVM RAM allowance after installation?

  • To adjust the RAM allocation:
  • Locate the configuration file for Tomcat (often in /etc/systemd/system/tomcat.service or a similar directory).
  • Edit the JVM options, typically in # JAVA_OPTS, to set the desired RAM limit.
  • Restart the Tomcat service to apply changes: #sudo systemctl restart tomcat.

How do I add or remove Worker Nodes after installation?

  • To add or remove Worker Nodes:
  • Ensure the new Worker Node meets all software requirements and is accessible by SSH.
  • Update any Alchemize configuration files to reflect the IP addresses of added or removed nodes.
  • Restart the Alchemize services on all nodes to ensure the cluster recognizes the changes.

How can I check if the license was installed correctly?

  • To verify the license:
  • Log in to Alchemize and go to the License section (gear icon in the upper right).
  • Confirm that the license status shows as valid and check the expiration date.
  • If the license is not valid, ensure you used the correct file and try re-importing it.

What should I do if I encounter “permission denied” errors during installation?

  • These errors often indicate missing permissions for the user running the installation:
  • Ensure the user has sufficient permissions to execute files and write to necessary directories.
  • Run chmod on the installer files to set appropriate permissions (chmod ug+x *.sh as an example).

Why can’t I connect to the database during installation?

  • If there’s an issue with database connectivity:
  • Check that PostgreSQL is running on the Storage Node and is accessible from other nodes.
  • Verify the IP address and port number for PostgreSQL are correct.
  • Ensure that the firewall settings allow traffic on the database port (default: 5432).

How can I troubleshoot Tomcat startup issues after installation?

  • If Tomcat doesn’t start or has errors:
  • Check the Tomcat logs (typically in /opt/tomcat/logs).
  • Ensure there are no port conflicts on the Front End Node.
  • Verify that sufficient memory is allocated to the JVM.
  • Restart Tomcat with # sudo systemctl restart tomcat.