diff options
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 15 |
1 files changed, 2 insertions, 13 deletions
@@ -35,23 +35,13 @@ The MSO APIs are configured to accept requests having a **basic auth. header** s All API endpoints are exposed on port **8443**. -##### Example API endpoints in the first open source release +##### Example API endpoints in the first open source release http://aai.api.simpledemo.openecomp.org:8443/aai/v10/query The easy way to trigger these endpoints is to use a RESTful client or automation framework. HTTP GET/PUT/DELETE are supported for most resource endpoints. More information on the REST interface can be found in the AAI Service REST API specification. ## Configuring AAI -The Docker containers use a Chef based configuration file (JSON) in order to provision AAI basic configuration for the demo app use case set up. - -## Logging -EELF framework is used for **specific logs** (audit, metric and error logs). They are tracking inter component logs (request and response) and allow to follow a complete flow through the AAI subsystem - -EELF logs are located at the following location on the AAI Service container: - -- `/opt/app/aai-traversal/logs` (each module has its own folder) - -AJSC Jetty logs can be found under /opt/app/aai-traversal/logs/ajsc-jetty. -The REST interface logs can be found under /opt/app/aai-traversal/logs/rest. +The Docker containers use a Chef based configuration file (JSON) in order to provision AAI basic configuration for the demo app use case set up. ## Testing AAI Functionalities Any RESTful client such as SoapUI may be configured and setup to use for testing AAI requests. @@ -61,4 +51,3 @@ Integration tests are located in `it` directory, and disabled by default in the `<skipITs>true</skipITs>` As a naming convention, All integration test classes should end with `IT`, and will be executed by changing the `skipITs` value in pom file, or through the command line `-DskipITs=false` - |