• Docker environment
  • Docker Compose
  • A valid progress.cfg file
  • Container Image for PASOE with EFK Stack Logging (available from Docker Hub)


Use the Container Image

  1. Download the (the zip file attached to this document).
  2. Change to the sample application folder:
    • cd /pasoe-basic/
  3. Update the value for `serviceURI` in `webui/grid.js` to point to your Docker host.
  4. Create a copy of the sports2000 database and start the database server (broker):
    • prodb sports sports2000
    • proserve sports -S 20000
  5. Copy your valid `progress.cfg` file into the conf directory and rename it to progress.cfg.pasoe. This will overwrite the placeholder progress.cfg.pasoe file in that directory.
  6. Update the DBSERVER environment variable in the docker-compose.yaml file to point to the machine running the database server.
    • Notes:
      • You can also configure the following variables in the docker-compose.yaml file:
        • EFK_LOGGING: This enviroment variable determines whether the container uses the EFK Stack for log management. You can use a volume to externalize the logs if desired.
        • INSTANCE_NAME: The name of the pasoe instance for the container. This variable is defined in the docker-compose.yaml for runtime needs and in the Dockerfile for build time when the PASOE instance is created.
        • APP_NAME: The logical name of the application. Changes to this value will be seen in the Elasticsearch indices.
  7. Build the custom container image for the sample application:
    • docker login
      • This allows access to the PASOE container image in Docker Hub:
        • store/progresssoftware/pasoe:11.7.5

    • docker-compose build
      • See [suggestions in the wiki]( if you are having issues.
  8. Increase virtual memory settings to run Elasticsearch:
  9. Start the services
    • docker-compose up -d
  10. Check that the PAS for OpenEdge instance starts:
    • docker-compose exec sports tail -f /oelogs/catalina.out
  11. Check that Elasticsearch starts:
    • docker-compose logs -f elasticsearch
  12. Access the PAS for OpenEdge instance via a web browser:
  13. Access the web ui service via a web browser:
  14. Access Elasticsearch to check on available logs:
  15. Access Kibana to show the logs:
    • http://<docker-host-machine>:5601
    • Notes:
      • Select Management/Index Management to see the indices in Elasticsearch
      • Select Management/Index Pattern to create an index for Kibana:
        • Create index for pasoe_agent_log
        • Specify @timestamp to filter data by time
      • Select Discover to see entries for the pasoe_agent_log index