Page tree
Skip to end of metadata
Go to start of metadata

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:

Function Point, Quality and Sizing support

This extension provides the following 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)
(tick)
Quality and Sizing(tick)

AIP Core compatibility

This extension is compatible with:

CAST AIP releaseSupported
8.3.x(tick)

Supported DBMS servers

This extension is compatible with the following DBMS servers:

DBMSSupported
CSS / PostgreSQL(tick)

Prerequisites

Required?Extensions
(tick)com.castsoftware.jee.1.2.14 and above
(tick)com.castsoftware.internal.platform 0.9.0-beta2 and above
(tick)com.castsfotware.wbslinker 1.6.11 and above

Download and installation instructions

You will need to manually install the extension using the Application - Extensions interface. When installed, follow the instructions below to run a new analysis/snapshot to generate new results:

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.

Structural rules

  • No labels