Summary: This document provides basic information about the extension providing NoSQL database support for the JEE Analyzer.
Extension ID
com.castsoftware.nosqljava
What's new?
Please see NoSQL for Java - 1.6 - Release Notes for more information.
Supported NoSQL databases
The NoSQL for Java extension provides support for the following NoSQL databases:
Database | Details about how the support is provided |
---|---|
Amazon DocumentDB | Amazon DocumentDB support for Java source code |
Azure Cosmos DB | |
Azure Cosmos DB support for Spring Data source data | |
Couchbase | Couchbase support for Spring Data source code |
Couchbase support for Java source code | |
CouchDB | CouchDB support for Java source code |
DynamoDB | |
DynamoDB support for Spring Data source code | |
Elasticsearch | Elasticsearch support for Java source code |
Elasticsearch support for Spring Data source code | |
MarkLogic | |
Memcached | Memcached support for Java source code |
MongoDB | |
MongoDB support for Spring Data source code | |
Redis | |
Redis support for Spring Data source code |
Function Point, Quality and Sizing support
- Function Points (transactions): a green tick indicates that Function Point counting and Transaction Risk Index are supported
- Quality and Sizing: a green tick indicates that CAST can measure size and that a minimum set of Quality Rules exist
Function Points (transactions) | |
---|---|
Quality and Sizing |
AIP Core compatibility
CAST AIP release | Supported |
---|---|
8.3.x |
Supported DBMS servers
This extension is compatible with the following DBMS servers:
DBMS | Supported |
---|---|
CSS / PostgreSQL |
Prerequisites
Required? | Extensions |
---|---|
com.castsoftware.jee.1.2.14 and above | |
com.castsoftware.internal.platform 0.9.0-beta2 and above | |
com.castsfotware.wbslinker 1.6.11 and above |
Download and installation instructions
The extension will not be automatically downloaded and installed in CAST Console. If you need to use it, should manually install the extension using the Application - Extensions interface:
Handling of NoSQL Java Collection objects for transaction purposes
All NoSQL "Collection" type objects are not classed as having code - i.e. they are codeless and are created via "getcollection" statements. As such, these objects either exist or do not and therefore NoSQL for Java extension does not compute a checksum on them. See https://mongodb.github.io/mongo-java-driver/3.4/driver/tutorials/databases-collections/ for more information. This means that in reality, if a transaction is really changed to add or remove a collection, then the java code itself is changed and so the transaction will be marked as modified. This in turn means that in an environment where the same release of a the NoSQL for Java extension is used for successive analyses, changes in java objects are enough to change the transaction values.