Requirements:

• Docker environment
• Docker Compose
• A valid progress.cfg file
• Container Image for PASOE (See wiki page https://community.progress.com/s/question/0D54Q00007pHAYgSAO/docker-container-for-pasoe-faq)

Use the Container Image

1. Update the value for `serviceURI` in `webui/grid.js` to point to your Docker host.

2. Create a copy of the sports2000 database and start the database server (broker):

`prodb sports sports2000`

`proserve sports -S 20000`

3. 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.

4. 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.

5. Build the custom container image for the sample application:

`docker-compose build`

See [suggestions in the wiki](https://community.progress.com/s/question/0D54Q00007pHAYg/docker-container-for-pasoe-faq) if you are having issues.

6. Increase virtual memory settings to run Elasticsearch:

* sudo sysctl -w vm.max_map_count=262144

* See the following link for additional info:

* https://www.elastic.co/guide/en/elasticsearch/reference/current/vm-max-map-count.html

7. Start the services:

`docker-compose up -d`

8. Check that the PAS for OpenEdge instance starts:

`docker-compose exec sports tail -f /oelogs/catalina.out`

9. Check that Elasticsearch starts:

`docker-compose logs -f elasticsearch`

10. Access the PAS for OpenEdge instance via a web browser:

`https://<docker-host-machine>:8811/`

`https://<docker-host-machine>:8811/Sports/`

`https://<docker-host-machine>:8811/Sports/static/SportsService.json`

`https://<docker-host-machine>:8811/Sports/rest/SportsService/Customer`

**Note**: By default, the PAS for OpenEdge instance will use HTTPS with a test certificate. You will need to accept access with this certificate.

11. Access the web ui service via a web browser:

`http://<docker-host-machine>:8080`

12. Access Elasticsearch to check on available logs:

`http://<docker-host-machine>:9200/_cat/indices`

13. 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