This topic summarizes the history of significant changes in TIBCO® Artifact Management Server release 1.4.0, including features, enhancements, and corrections.
TIBCO AMS 1.4.0 adds the following updates and new features:
AMS now supports substitution variables and substitution files in AMS configuration. See Creating Substitutions for details.
AMS now offers more powerful and consistent methods to create encrypted password values within configuration files. See Encrypting AMS Configuration Data for details.
Clients can now download only the metadata attached to AMS artifacts, without having to download the entire artifact.
AMS now supports adding resource directories to the Java classpath so files in these directories can be found as resource files. See OPTIONS for details.
New commands were added to enhance AMS. See AMS Command Reference for details.
AMS can be containerized under CentOS 7, for Docker deployments to the cloud. See Creating Docker Images for details.
The AMS REST API documentation has changed to more accurately represent the request and response models of many endpoints. These changes had no effect on the request or response payloads, so backwards compatibility in maintained except where specified in Migration and Compatibility.
Functional changes were also made to support:
Artifact length in artifact response models (may affect backwards compatibility).
Included/excluded/convert query parameters in requests that contain artifact content in its request or response.
Content-compressed property in request payloads that add or update an artifact's content.
New health check endpoint.
AMS 1.4.0 includes the following functionality changes.
A progress bar was added to the Import Artifact dialog, showing the progress for loading the content. When the content exceeds 25 MB, the content is compressed for the import process and the shown content size shown is its compressed size.
When an artifact's content exceeds 25 MB, the Content screen shows the following message fragment: The artifact size of ...MB is too large to displayed safely in the browser. The user can open the editor, but at a risk of running out of memory.
When an artifact has invalid contents based on its artifact type (for example, a StreamBase Decision Table that has invalid or unparseable XML), the Content screen shows the following message fragment: An error occurred while opening the editor. The user can open the artifact content in a text editor.
The following features are deprecated in this release.
The ams-server --cipher command is now deprecated and removed from AMS. It is still supported for backward compatibility. For details, see below.
Refer to the following migration and compatibility notes when upgrading to AMS 1.4.0.
AMS continues to honor enciphered text using the now-deprecated and removed ams-server --cipher command. However, TIBCO recommends regenerating enciphered values using the new ams-server --secret encrypt command.
Response models containing artifact data has one new property artifactLength that may affect backward compatibility for REST API clients that perform strict parsing of the response payload. See AMS API for details.
This section describes known limitations in the current release of the TIBCO Artifact Management Server. Each item includes a description, and whenever possible, one or more workarounds.
AMS 1.4.0 does not contain any known limitations.
This section describes resolved limitations in the current release. Each item includes a tracking number and a description.
| Fixed in 1.4.0 | |
|---|---|
| Number | Resolution |
| SB‑43704 | Deleting a new project that did not contain artifacts would fail in some circumstances. This was fixed. |
| SB‑43082 | This release fixes an issue that prevented hiding projects. |