Skip to content

Latest commit

 

History

History
79 lines (53 loc) · 4.42 KB

egeria-dojo-day-1-3-1-2-configuring-the-platform.md

File metadata and controls

79 lines (53 loc) · 4.42 KB
Raw

Blue - Intermediate sessions

Configuring the OMAG Server Platform

In this session, you will learn how to set up the OMAG Server Platform.

Configuring the OMAG Platform Content

Watch this video to get an overview of this session: https://youtu.be/-YScFx0fQk0.

In the previous session you downloaded an application called Postman and loaded collections of pre-defined requests. This tool makes it easy to issue REST API requests to the OMAG Server Platform.

Check that it is working by locating the Get Server Origin request in the Egeria-platform-services collection. When you click on that request in the left-hand list, a new tab opens and you can click on send to issue the request. You should see the same response as when you issues the platform origin request from Swagger earlier. Below is this response in Postman.

Postman server origin

If this does not work, then there is something wrong either in Postman or your platform. Check the URL string that was used in the request (shown in orange in the middle of the screen.)

The screen shot below shows the error message when the egeria environment is not set. This can be fixed by setting it in the top right-hand dropdown. If the Egeria environment is not listed then you need to load the environment (Postman tutorial).

Postman server origin - no environment

If the baseURL variable is set to a different value to the server platform then Postman can not connect. In the screen capture below, you can see the baseURL is set to the default of https://localhost:9443 when it should be https://localhost:9443 because the platform is running in docker.

Postman server origin - wrong base url

Finally, if the OMAG Server Platform is not running the even though everything is set up correctly in Postman, it has nothing to connect to. Restart the platform (Docker tutorial).

Postman server origin - platform down

In last part of this session you will learn how to set up the OMAG Server Platform so that it is secure and determine the services and servers that are associated with the platform.

Review the description of the OMAG Server Platform configuration:

The link below takes you to a task description in the Egeria Administration User Guide. The user guide describes the REST API call(s) needed to complete the task. You can choose to type the request into postman, or use the requests already defined in the Egeria-admin-services-platform-configuration Postman collection.

  • Add the Coco Pharmaceuticals platform security connector to the platform Try running the platform origin command again - it should fail with a security error. Change the user variable in the Egeria environment from me to garygeeke and rerun the request. It will work again because garygeeke is the user id of the Coco Pharmaceuticals IT infrastructure lead and has permission to run the platform commands.

Finally, use the Egeria-admin-services-platform-configuration Postman collection to experiment with the different registered services and and known and active server requests. These are useful to know as we move to configure servers on the platform.

This is the end of the session on the OMAG Server Platform.

License: CC BY 4.0, Copyright Contributors to the ODPi Egeria project.