The Catalog API microService is part of a model-management service which can be used for:
- Implemented for model catalog meta-data storage
- Listing all model meta-data
- Retrieving model meta-data based on modelKey and modelType and projectKey
- Inserting/updating model catalog meta-data via MySQL
- Deleting unwanted catalogs based on modelKey and projectKey
- Maven 3.x.x
- Java 8
- AAF (here)
- Jenkins Job Base
- Email Host
- Kubernetes Namespace
- Install and configure Maven and Java. Many robust installation guides exist for both products and there is not a need for an additional guide here.
- Clone the CatalogAPI repository.
- Install and configure MariaDB. Create the database schema by running Catalogapi_tables_Schema.sql.
- Follow the installation and deployment instructions for AAF (here). CatalogAPI is dependent on AAF. Be sure to create a namespace in AAF.
- Navigate to the project in a terminal and run
mvn installusing the settings.xml file provided with the project.
- Configure CatalogAPI by filling out the configuration files src/main/resources/system.properties, src/main/resources/application.properties, src/main/resources/cadi.properties, and etc/cadi.properties. Fields are preset with default values, localhost addresses, or the dummy text "changeme".
- Generate a new keyfile and use it to replace the dummy file in etc/aafkeystore.
- Create a run configuration with com.att.ajsc.catalogapi.Application as the main class
- Launch with the run configuration.
More details can be found in the wiki for this project