Initial configuration steps - v. 1.x on Documentation - V2

Install additional tools and patches - optional - v. 1.x

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

Info

Summary: this page describes how to perform various actions that may be necessary and not automatically managed by the GUI/CLI installation process.

Introduction

Due to some constraints with regard to the GUI/CLI installation process for the Console/Node packages, it may be necessary to perform some additional manual actions depending on the Console / AIP Core releases you are using. Each is described below.

Install default discoverers

Note

Note that the patching of the default discoverers is not required if you are using Console ≥ 1.8.x.

Configure AIP Node storage folder locations - optional - v. 1.x

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

Info

Summary: this page describes how to configure the Node storage folder locations. This is an optional but recommended step in the installation configuration process.

Introduction

Each Node that is managed by Console requires a set of storage folders that are used to store items related to each Application onboarded and analyzed with the specific Node via the Console. Currently the following storage folders are required on each Node and they will be set to a default location as listed below.

Ensure AIP Console and AIP Nodes are running - v. 1.x

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

Info

Summary: describes how to ensure that the Console and all Nodes are running.

Step 1: Start Node back-end package(s)

Ensure the Node back-end packages you have installed on dedicated Nodes are running, otherwise the Console package will complain that it cannot access them. This should be done regardless of whether you are using a single machine or a **multi-node deployment scenario.**To launch the Node back-end package, you can do any of the following. You will need to do this on EACH Node where you have installed the Node package.

Complete start-up wizard - v. 1.x

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

Info

Summary: describes how to complete the start-up wizard that is displayed the first time you connect to Console.

Introduction

The start-up wizard is displayed the first time you connect to the Console as described in Ensure AIP Console and AIP Nodes are running - v. 1.x. The wizard provides a user-friendly method to configure various mandatory settings and options, such as:

Verify the installation
Assigning the Administrator role to a user
Entering a license key
Configuring access to CAST Extend / use of a proxy caching server
Configuring a Measurement schema

Each step in the wizard is explained in detail below.

Declare AIP Nodes in AIP Console - v. 1.x

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

Info

Summary: This step explains how to declare all your Nodes in Console.

Introduction

In a multi-node deployment scenario where Console is installed on a dedicated server, Console does not yet know about the remote analysis node(s) (i.e. Node package(s)) that you have installed. Therefore any Nodes that you want to manage in Console must be declared manually as described below.

Process

Browse to the following URL to access the Nodes panel in the Administration Center - modify the URL for your own environment:

Determine Extension Strategy - v. 1.x

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

Info

Summary: before commencing Application analyses, CAST highly recommends determining your Extension Strategy.

Introduction

CAST publishes a variety of extensions to provide additional analysis and measurement capabilities (see What are extensions for more information) and in turn, Console provides an integrated GUI to manage the use of these extensions in each Application analysis. Out-of-the-box, Console contains few restrictions or settings with regard to extensions. While this provides flexibility for Application Owners or Analysis Managers, it can sometimes be problematic if specific extensions need to be avoided for whatever reason. To counter this, Console provides a set of Extension Strategy settings that can be used to control the extensions that can be installed both automatically and manually in the integrated GUI. For example, admins can choose to do any of the following: