This topic summarizes the history of significant changes in TIBCO® Artifact Management Server release 1.2.0, including features, enhancements, and corrections.
TIBCO AMS 1.2.0 added the following updates and new features:
AMS now supports additional file types that can be created, edited, or stored in the repository and deployed to StreamBase Studio. For a complete list of supported file types, see Supported Artifact Types.
Multiple artifacts can be checked out in a single operation.
Users can sign into the AMS through an OpenID Connect provider such as Google. A new OpenIDConnectAuthenticationRealm in AMS.com determines the single sign-on behavior. See Configuring Single Sign-On for configuration information.
Users, roles, and permissions are now dynamically configurable through the web client. Also, users can be disabled by administrators. See Permission Management.
Errors in decision tables appear in the new Problems view. Clicking on an error message displays a details about the error.
AMS supports replacing artifacts stored in the repository with newer or older versions, or externally sourced versions.
AMS now includes a command prompt with its environment pre-set for running AMS command-line utilities. See AMS Command Prompt for more information.
Major enhancements were made to navigation of projects and artifacts, including groups and filters. There are now several ways to view projects and artifacts: as a flat list, with a tree view, and using bread crumbs.
A user can lock an artifact, preventing other users from changing the same artifact. An administrator can release a lock held by another user.
AMS supports JSON-encoded metadata for artifacts. JSON allows for the addition of fields without requiring the AMS to know how to interpret the metadata. See Editing Model File Artifacts Using the Text Editor for more information.
Functionality was changed as described in the new enhancements described in the previous section. This guide was updated to address these enhancements.
Prior to AMS 1.2.0, the default web client port was 8080. The port number was changed to 2443 (secure) or 2185 (non-secure) to prevent possible conflict with other TIBCO products' port numbers.
Prior to AMS 1.2.0, the local authentication realm provided zero or more AMS users and their roles. In 1.2.0, the local authentication realm is used to seed users and roles in AMS persistence realm.
No features are deprecated in this release.
There are no known migration issues when upgrading from AMS 1.x to AMS 1.2.0.
AMS 1.2.0 is compatible with StreamBase 7.6.6 and above for decision table artifact deployments, and StreamBase 7.7.1 and above for model file artifact deployments.
This section describes known limitations in the current release of the TIBCO Artifact Management Server. Each item includes a tracking number, description, and whenever possible, one or more workarounds.
Currently there are no known limitations.
This section describes resolved limitations in the current release of the TIBCO Artifact Management Server. Each item includes a tracking number and a description.
| Fixed in 1.2.0 | |
|---|---|
| Number | Resolution |
| SB‑41199 | The AMS server will fail on startup if the configuration file and database reside in the same directory. This was fixed. |
| SB‑30955 | In prior releases, AMS could not be launched with StreamBase 7.7.0 Command Prompt. AMS 1.2 resolved this issue by introducing the Artifact Management Server Command Prompt, for Windows. |