2024-12-14T16:40:53 Status: #blog Tags: #altova #flowforce #mapforce #yaml #xml #xbrl #technology #softwaredevelopment #openapi #raptorxml #docker #containers #containerization Links: [[Altova]] | [[MapForce]] | [[YAML]] | [[XML]] | [[XBRL]] | [[Technology]] | [[Software Development]] | [[OpenAPI]] | [[RaptorXML]] | [[Docker]] | [[Containerization]] | [[Enterprise Solutions]] | [[Altova Server Platform 2025]] # Altova Servers in Docker [[Altova]] has made it easier than ever to deploy and manage its server products with the release of [[Altova Server Platform 2025]]. Whether you're running [[MapForce]] Server, FlowForce Server, [[RaptorXML]] Server, or any of the other Altova server products, you can now use [[Docker]] and Docker Compose to streamline deployment. ![[AltovaServersOnDocker.png]] With the launch of our new open-source project that is immediately available on GitHub, getting started is a breeze. ## Introducing the Altova Server Docker Project We’re thrilled to announce the new [Altova Server Docker project](https://github.com/altova/altova-server-docker) on GitHub. This project provides: - Pre-configured `compose.yaml` file and `Dockerfile` for all Altova Server Platform products. - An automated setup process for creating Docker images and bringing up containers. - Customizable configurations under the Apache 2.0 open-source license. By using this repository, you can set up your environment quickly and adjust it to suit your needs. The modularity of Docker Compose ensures seamless orchestration of multiple Altova server components. ## Getting Started ### 1. Clone the Repository Clone the GitHub repository to your local machine, either from your favorite development environment, such as Visual Code or Cursor, or from the command-line: ```bash git clone https://github.com/altova/altova-server-docker.git cd altova-server-docker ``` ### 2. Customize Configuration The `compose.yaml` and `Dockerfile`s are fully customizable. You can: - Add environment variables to suit your deployment. - Specify volume mappings for persistent storage. - Include pre-existing license files if available (see Altova LicenseServer section below). I would recommend making any changes to those files in your favorite development environment. For example, here is a screenshot of the project in [Cursor](https://www.cursor.com/): [![[DockerComposeUp.png]]](https://xmlaficionado.com/cdn-cgi/image/width=2000,quality=100,fit=scale-down,format=auto/https://publish-01.obsidian.md/access/fce28e11a3060e1ae5f0c9ef0da24dab/XML%20Aficionado/Files/DockerComposeUp.png) ### 3. Build Images and Start Containers Build the Docker images and start your containers with a single command, either by right-clicking on the `compose.yaml` file in your development environment and selecting the `Compose Up` option from the menu (see above screenshot), or from the command-line: ```bash docker compose up -d ``` This fully automated process downloads the server software directly from the [Altova Downloads](https://www.altova.com/download) website, creates the required images, initializes the containers, and ensures everything is up and running in Docker Desktop: ![[DockerDesktop.png]] This is also where you can find the ports under which you can reach the admin interfaces for the various Altova Servers. ## Altova LicenseServer Altova offers flexible licensing options to get you started quickly: - **Evaluation Licenses**: You can request a free 30-day trial license directly from the LicenseServer container’s user interface for each server you'd like to evaluate: ![[RequestEvalLicenses.png]] - Once you have received the licenses via email, upload them to the LicenseServer and then assign them to the respective server software in the Client Management tab. - **Existing Licenses**: Place your purchased server license files into the designated `flowforceserveradv` and `mobiletogetherserveradv` directories (replacing the respective dummy `*.altova_licenses` files that are already in those locations). These will be included during image creation and automatically assigned when the respective containers are started (via `startup.sh` scripts that you can also customize as you see fit). This flexibility ensures that users can either evaluate the software or deploy licensed production environments seamlessly. Please keep in mind that there should always be only one instance running of the Altova LicenseServer container, so if you are planning a cluster-based deployment, such as Kubernetes, please ensure that only one container of LicenseServer is being spun up. ## Why Use Docker for Altova Server Products? Docker offers several advantages for running Altova Server Platform products: - **Simplified Deployment**: Use Docker Compose to bring up containers with minimal effort. - **Portability**: Run the same configurations across different environments. - **Isolation**: Avoid conflicts between applications and dependencies. - **Scalability**: Easily scale up resources as your needs grow. By combining Docker’s strengths with Altova’s server capabilities, you can deploy robust, efficient solutions with ease. ## Is Docker the only deployment platform supported by Altova? No, of course not! You can run Altova Server products on-premises on your own IT infrastructure without a container provider - either on Windows or Linux servers - as well as [[Altova Servers on Azure|on Azure]], Amazon Web Services (AWS), or the Google Cloud, in addition to all other cloud hosting providers. --- # References - [Altova Server Docker GitHub repository](https://github.com/altova/altova-server-docker) - [[Altova Server Platform 2025]] - [FlowForce Server 2025 Advanced Edition](https://www.altova.com/manual/FlowForceServer/FlowForceServerAdvanced/) - [MapForce Server 2025 Advanced Edition](https://www.altova.com/manual/MapForceServer/MapForceServerAdvanced/) - [StyleVision Server 2025](https://www.altova.com/manual/StyleVisionServer/) - [RaptorXML+XBRL Server 2025](https://www.altova.com/manual/RaptorXML/raptorxmlxbrlserver/) - [DiffDog Server 2025](https://www.altova.com/manual/DiffDogServer/) - [MobileTogether Server Advanced Edition](https://www.altova.com/manual/MobileTogether/mobiletogetherserveradvanced/) - [Altova LicenseServer](https://www.altova.com/manual/AltovaLicenseServer/)