New and Noteworthy in AMS 1.5.0


Table of Contents
New Features
Changes in Functionality
Deprecated Features
Migration and Compatibility
Known Limitations
Closed Issues

This topic summarizes the history of significant changes in TIBCO® Artifact Management Server release 1.5.0, including features, enhancements, and corrections.

New Features

AMS Now Supports PostgreSQL Database

This release supports PostgreSQL as a database option instead of the AMS-supplied embedded H2 database. The following options are available:

  • Configuring AMS with a PostgreSQL instance

  • Creating a new PostgreSQL server and database on Amazon AWS

  • Creating a new AMS database on an existing PostgreSQL Server

See this page for more information.

Artifact Deployment Across Subnets Now Supported

This release supports artifact deployment to StreamBase nodes that are discoverable outside of the AMS subnet. The new method is called Service Address. See this page for configuration details.

Management Options Now Support Descriptors, Service Addresses

This release adds support for adding, updating, and deleting of:

  • Artifact deployment descriptors

  • Deployment service addresses

For details see User Management Settings.

New Artifacts Supported

The following artifact types are now supported and described here:

  • Python script files

  • TensorFlow model definition files

  • TensorFlow graph definition files

  • Avro schema files

Artifact Validation Performance Improved

To improve validation performance when adding, saving, and loading artifacts, a user setting for automatically validating artifacts is available (and disabled by default).

Changes in Functionality

Web Client Management Now Includes Configurable Deployment Properties

Managing artifact deployment descriptors is now supported from the web client's Management page.

New Commands Added to Support New Database Option

New AMS commands were added to assist with database backup and restore operations. See AMS Command Reference for details.

Deprecated Features

None.

Migration and Compatibility

See this page for general AMS migration and compatibility information.

New Database Maintenance Options Now Available

AMS now supports database:

AMS REST API Changed

AMS REST APIs documentation have changed in the Swagger page, to more accurately represent the request and response models of some endpoints. These changes have no affect on the request or response payloads, so backward compatibility in maintained. For more information about viewing the API, see REST API Changes in AMS 1.5.0.

Functional changes were also made to support:

  • Accepts compressed content query parameter in requests that contain artifact content is its request or response.

  • Include/exclude/convert/compress query parameters in the artifacts sync and checkout requests.

  • Include/exclude/convert/compress query parameters in the lifecycle checkouts request.

  • Compressed content in artifact response models (may affect backwards compatibility).

  • Type and service-address list in deployment descriptor and target response models (may affect backwards compatibility).

  • New Service Addresses endpoints.

Known Limitations

None.

Closed Issues

This section describes resolved limitations in the current release. Each item includes a tracking number and a description.

Fixed in 1.5.0
NumberResolution
SB‑47736Previously, the "high water mark" AMS uses to determine which Subversion repository commits were pulled into AMS would get out of sync, resulting in attempts to pull the same Subversion commits into AMS multiple times. This was fixed.