anchor.diff:  │       └── apiman-ds_postgresql.xml
   
   ----
  +
   The modules directory - This directory contains configuration files, including keycloak (URL) configuration files that are added to the WildFly server for apiman. These files are added to the WildFly “standalone” server configuration . The top levels in this directory look like this:
   
   ----
  
positive.code: 
  We’ll keep things simple in this chapter and use the apiman WildFly Overlay distribution. (You can also download apiman packaged as a Docker image.)  If you navigate to the “downloads” page, you’ll see:
  
  ![ExampleImage_2](images/2.png)
  
  Let’s take a look at the contents of the WildFly Overlay. There are three main directories in the WildFly Overlay:
  
  
negative.code: 
  To create the API provider organization, log back into the API Manager UI as the apiprov user and select “Create a new Organization”:
  
  image::images/8a.png[ExampleImage_8a]
  
  Select a name and description for the organization, and press “Create Organization”:
  
  image::images/9.png[ExampleImage_9]
  
  And, here’s our organization:
  
  image::images/10.png[ExampleImage_10]
  
  Note that in a production environment, users would request membership in an organization. The approval process for accepting new members into an organization would follow the organization's workflow, but this would be handled outside of the API Manager API. For the purposes of our demonstration, we'll keep things simple.
  
  