MRI Operating Information on Documentation - V2

Prerequisites for Infrastructure - Installation - Security - Rights

Mon, 01 Jan 0001 00:00:00 +0000

Version 1.2 - Updated 7-Jul-2021

This information can be downloaded here in a Word format

1. Introduction

This document provides prerequisites regarding Hardware, Software, Network, Security and Rights aspect for a proper CAST installation on site.

The server shall be installed on Client’s site and will be available through a VPN access for CAST users.

2. Service level agreement

Cast will operate the platform and 2 types of operation will be executed.

Technical Survey

Mon, 01 Jan 0001 00:00:00 +0000

2-0 - 11 Nov 2021

The aim of the Technical Survey document is for the application SME to capture technical and non-technical information about an application.

The following different formats are currently used to capture varying degrees of detail as applicable to the engagement. The completed document is used by the CAST Administrator during Qualification and Source Code Delivery phases as detailed at this link Prepare and deliver the source code, and also for the Analysis Configuration phase as detailed at this link eBlue Print - Analysis Configuration and Execution.

Source Code Delivery Instructions

Mon, 01 Jan 0001 00:00:00 +0000

Document version 2-7 — 03 March 2022

The informational material contained in this section is provided as a courtesy for use by CAST’s clients. Licensing details are documented here: https://www.gnu.org/licenses/lgpl-3.0.en.html.

The official CAST AIP technologies documentation is published here.

Introduction

Recommendation

The delivery structure must correspond to your project structure and must be reproducible, to allow for consistency during subsequent analysis. Ask your development team to produce a standard export from the code repository (for example, git clone).

Source Code Delivery for AIP Console

Mon, 01 Jan 0001 00:00:00 +0000

Background and Approach

There are two main approaches to “source code” delivery when onboarding or rescanning an application in AIP Console.

Single Zip file (Preferred) - This requires as input, a single Zip file containing all relevant “Source Code” artefacts. The structure of the folders within the Zip file needs to also remain consistent from release to release. One way to do this is to create separate folders for each technology and also folders by sub technology within technology. This requires that some initial preparation is put into the creation of this Zip file.
Defined folders and files - This requires the configuration of all the files and folders with AIP Console, that contains the same files and folders that would be captured in a single Zip file.

The “source code” delivery needs to contain more than just source code (please see technology specifics below). To perform system-level analysis, AIP Console requires:

Onboarding Validation of Analysis

Mon, 01 Jan 0001 00:00:00 +0000

This page is here to explain steps of application validation done by ServiceEnablement.

Following screenshots have been taken with a console 1.27

Summary

Wrap-up

Operator in charge of implementation does not need ServiceEnablement to request Module design or Exclusion
During implementation, Operator has to comment JIRA.MSREQ with his insight
Outputs must be saved on R:\FR\CUSTOMER\PROJECT\ARCHIVE
Before delivering, operator must ensure list point below

Application Scope

Idea is to ensure Scope Defined, and all necessary code is analyzed.

SQL Database Extractor

Mon, 01 Jan 0001 00:00:00 +0000

Pre-requisite

The CAST Database Extractor can be run in command line (CLI) mode should you wish to automate the extract/initialize process.

When using the command line, the process consists of a set of instructions and commands contained in a batch file (.bat) file. When the batch file is executed, the Java tool (CASTDBGUI.jar) is launched and the process begins. If you are extracting a large amount of data (i.e. multiple schemas/databases or one very large schema/database), you must use a batch file that contains specific Java Heap Space configuration commands (the -Xmx command), otherwise you will likely receive out of memory exceptions. Below is an example batch file for launching the .JAR tool.

Troubleshooting Process

Mon, 01 Jan 0001 00:00:00 +0000

Entry Criteria:

Errors/warning/alerts are encountered in the CAST tools (DMT, CMS, Enlighten, TCC)
Global Application Intelligence Center (GAIC) troubleshooting guide

Process Steps:

When an error or warning is encountered:
1. Refer to the GAIC troubleshooting guide for CAST tools which gives information about:
  1. Which errors/warnings/alerts can be ignored?
2. Remediation, resolution, and workaround details
  1. Refer to Technical Knowledge Base (TKB) for known issues and limitations
  2. Refer to Zendesk for similar issues faced
  3. Raise a Support ticket
  4. Consult Product Management (PMT) or the Research and Development (R&D) team
  5. Consult SME if recommended by Support or PMT

Exit Criteria:

Verify if the above steps have solved the issue

Deliverable Outcomes:

All errors, warnings and alerts are remediated

Best Practices:

Refer to the Zendesk for Solution Delivery best practices