Changes to Versata Runtime Libraries 

The Advantage application Framework leverages Versata as a foundational component of our application stack. Versata is deployed as binaries files, which are built from compiled source code. On occasion, changes are made to the Versata libraries to facilitate strategic enhancements. 

To provide additional rollback flexibility, previous Versata binaries are delivered in case of an identified unknown issue where the root cause is related to Versata. If necessary, sites can turn on the DeployOriginalVersataBin property/flag, which will revert the binary files to the previously delivered binary files.

The DeployOriginalVersataBin property/flag is defined in <VLS_HOME>/VLS/bin/server_bootstrap.properties. By default, the value for this flag is false. When the flag is set to true and the container is bounced, the container startup scripts will deploy the original Versata binaries and make it available for the application runtime. 

Diagram showing changes to Versata Runtime libraries within the Advantage Container. Process starts when DeployOriginalVersataBin property in server_bootstrap.properties Default = false within the Container startup script. Then, there is a check for whether DeployOriginalVersataBing == true or false. If it is true, then the original Versata jars placed in a backup folder will be copied to runtime location and then go to advantage.ear/lib. If it is false, then the Versata Jars compiled from source will be used in the runtime location and then also go to advantage.ear/lib, where the process ends