Configuring a proxy
Put the iGrafx platform behind an HTTP proxy: set up an Apache reverse proxy, make Tomcat proxy-aware in server.xml, and allowlist the license-activation URL for outbound traffic.
Put the iGrafx platform behind an HTTP proxy: set up an Apache reverse proxy, make Tomcat proxy-aware in server.xml, and allowlist the license-activation URL for outbound traffic.
Problem
Finish a new installation in the browser: set the administrator account and site URL, then enter the database connection details and install the platform.
Prepare the database before installing the platform: install Microsoft SQL Server, create the administrative and repository databases, and create the database user the platform connects with.
Deploy the iGrafx platform from the WAR file: set the base directory, JVM memory, and logging, add the required mail libraries, and deploy into the root context.
Problem
Problem
The two directories the platform uses — the installation directory (application code) and the base directory (configuration and data that survives upgrades) — and the key files in each.
Install, configure, and maintain the iGrafx platform on your own servers: database setup, application server deployment, post-deployment configuration, and repository management.
Install the iGrafx platform on Windows from the pre-deployed Apache Tomcat package: extract it, install the service, open the firewall, and verify it runs.
You want to push the URL of your iGrafx platform to your iGrafx Desktop Client users (i.e. Flowcharter), so they can pick it from the list of known URLs?
Upgrade an on-premises iGrafx platform: plan the stepping-stone version path, back up, replace the application server (pre-deployed Tomcat or WAR), and apply post-upgrade administration and database changes.