Deploy to No-Code Container

OpenLegacy provides the ability to implement business logic using JSON metadata instead of writing code. This is done using a no-code methodology that allows the creation of integration solutions with legacy programs for non-programmers and makes the application development process faster and more user-friendly.

A container image is a lightweight, standalone, executable package of software that includes everything needed to run an application. Container images become containers at runtime. 

You can use a single connector project when working with a no-code container.


How to Deploy an OL-Hub Project to No-Code Container

  1. Create and Test your (single connector) Project in the OL-Hub

  2. When you are ready to deploy to the No-Code container,
    Pull an OpenLegacy No Code image from Docker Hub.
    The images are connectors based:


  3. Define the container environment file

    1. OPZ example
      OL_SOURCE_PROVIDER=OL_PROJECT_ZIP
      OL_PROJECT_ZIP_PATH=/usr/opz/ol-project.opz
      OL_LICENSE_KEY=<license>
    2. Hub Provider example
      OL_SOURCE_PROVIDER=HUB
      OL_HUB_PROJECT_NAME=ol-project
      OL_HUB_API_KEY=Ew3ztSQQA
      OL_HUB_URL=https://api.ol-hub.com
      OL_ACTIVE_PROFILES=prod-server,print-debug-logs
      OL_LICENSE_KEY=<license>
      See properties in OpenLegacy LowCode API - Supported Environment Variables
  4. Run the NoCode app docker image using the following commands:

    1. OPZ Provider example:
      docker run --interactive --tty--name ol-project --publish 8080:8080 --env-file /home/username/nocode/olzip.env --volume /home/username/nocode/ol-project.opz:/usr/opz/ol.opz openlegacy/<nocode image type>:tag
    2. Hub Provider example:
      docker run --name ol-project --publish 8080:8080 --env-file /home/username/nocode/hub.env openlegacy/<nocode image type>:tag
  5. If the NoCode app requires proprietary library dependencies (e.g. SAP container),
    you need to give access to these files to the Docker container by mounting a directory with them to the /usr/app/lib path:

    1. Mounting the directory
      --volume /home/user/nocode/sapfiles:/usr/app/lib
    2. The command with the dependencies library (for example, for SAP container)
      docker run --name sap --publish 8080:8080 --env-file /home/username/nocode/hub.env --volume /home/user/nocode/sapfiles:/usr/app/lib openlegacy/sap-nc-rest:tag