Skip to content Skip to sidebar Skip to footer

With version 10, Trimble eCognition has simplified the deployment of eCognition Server that allows production-oriented customers to easily move their operational environments to the cloud.

The eCognition Server engine is now available in docker image formats that support both Windows and Linux operating systems. The docker images are available directly within DockerHub and all eCognition customers with a valid version 10 license can utilize these in their own cloud environments.

By moving your eCognition Server processing to the cloud your organization can benefit from:

  • Cost effective cloud machines that can be used when needed and designed to best fit specific project needs, i.e. [need example of powerful system setup ideal for big CNN processing]
  • Cost effective hardware use based on usage time
  • Security (i.e. cloud makes it easier to meet government compliance requirements)
  • Scalability of cloud machines that meet specific project needs
  • Increased mobility, i.e. monitor processing via a smartphone
  • Disaster recovery available via backups
  • Simplified CI/CD (Continuous Integration/Continuous Delivery)
  • Flexibility to build on top of eCognition docker images to build your own integrations

In this blog post we will demonstrate how to set up the eCognition License Server in a cloud environment.

Setup eCognition License Server (Linux) on AWS

The eCognition Command-line engine or eCognition Server GRID docker setup requires an active eCognition Server license to be available within the eCognition License Server. Here, we provide an example for how to set up the eCognition Licenses Server for Linux on an AWS EC2 instance.

EC2 Instance Setup

For testing purposes the “Amazon Linux 2 AMI (HVM), SSD Volume Type”, 64-bit (x86), t2.micro instance is chosen. This is a cost-effective instance, but it is enough to serve up to 10 Server licenses (1 Server license is required per core).

In the instance creation wizard, a security group needs to be installed. In this exemplary set up a new security group is created with minimal requirements for the License Server to run:

  • TCP Port 22 (SSH) – needed for basic access to the instance via Putty or other shell
  • TCP Port range 27000 – 27009 – ports needed for License Server communication
  • TCP Custom Port 41000 – this is a random number for the License Server vendor daemon port (the same number needs to be selected in the administration console after the License Server is installed, see instructions below)
  • TCP Custom Port 8090 – License Server Web Console Access

By completing these steps you are ready to launch the instance.

Once the instance is up and running, set up a Putty connection to the instance with a private SSH key (default AWS user is ‘ec2-user’ for login). Now, you can download the eCognition License Server installation (Linux) from

Please upload the downloaded installation rpm using the PSCP utility that comes with the Putty installation using a command like the following:

  > pscp -P 22 -i c:\temp\my_private_ssh_key.ppk

Prerequisites Installation

Install Linux Standard Base. The original package is redhat-lsb, although Amazon has its own distribution for it. As it is not installed with newer distributions of Linux by default this has to be done using the following commands:

  > sudo yum install lsb

Install FUSE:

  > sudo yum install fuse fuse-devel fuse-libs fuse
  > modprobe fuse

Install License Server:

  > sudo rpm -i eCognition-License-Server-10.0-4286.x86_64.rpm

License Activation

Activate the license:

  > cd /opt/eCognition\ License\ Server\ 10.0/
  > export LD_LIBRARY_PATH=.
  > ./serveractutil -served -comm soap -commServer
-activationID <enter_activationID> -hybrid <Number of licenses>

Below this section you can find the Activation ID of the “eCognition Server” license – <enter_activationID> together with the quantity of licenses to activate <Number of licenses>. Note that the defined quantity of licenses to activate cannot exceed the number of licenses you have acquired.

Exemplary output of this command:

Generating transfer request using:
        Activation ID = ghef-99zx-ertv2-demo-id
        Expiration = 31-dec-2020
        Activatable Count = 0
        Activatable Overdraft Count = 0
        Concurrent Count = 0
        Concurrent Overdraft Count = 0
        Hybrid Count = 1
        Hybrid Overdraft Count = 0
        Repair Count = 0
Status: 4, Creating request
Status: 5, Request created
Status: 6, Context created
Status: 7, Connected to remote server
Status: 8, Request Sent
Status: 9, Polling for response
Status: 10, Waiting for response
Status: 9, Polling for response
Status: 11, Done
Status: 6, Context created
Status: 7, Connected to remote server
Status: 8, Request Sent
Status: 9, Polling for response
Status: 10, Waiting for response
Status: 9, Polling for response
Status: 11, Done

Use the following command to restart the License Server:

  > sudo systemctl stop eCognitionLicenseServer.service
  > sudo systemctl start eCognitionLicenseServer.service

If the installation was successful, navigate to LicenseServerIP:8090, otherwise check the LicenseServer.log for more details in the logs/ folder of the installation.

In the screenshot above, click on the “Administration” tab and enter the default username/pwd “admin”/“admin” (You are then asked to change the default password which is highly recommended). In this administration console, choose the “Vendor Daemon Configuration” tab:

Now select “Administer” and enter the explicit port that was defined in the EC2 Security Group (e.g. “41000”) earlier and click “Save”:

Now you need to restart the License Server again for the changes to take effect: 

  > sudo systemctl stop eCognitionLicenseServer.service
  > sudo systemctl start eCognitionLicenseServer.service

Done! The eCognition License Server is now ready to serve the licenses to eCognition engines running in AWS.


Follow Us on Social Media

For more news on eCognition