Get Started

Access to AWS Blu Insights is limited to AWS Blu Age practitioners who are working on modernization opportunities, AWS Blu Age customers, and certified individuals with the AWS Refactor Accreditation Program. This latter is based on three complementary levels of certifications. Each level grants access to different services.

Introduction to AWS Blu Insights

With AWS Blu Insights, you break up your work into separate projects. Each project contains everything related to the work at hand; all the people involved, every document, file, task, important dates, etc. Everything! Unlike email where everything starts disorganized and you have to constantly manage the chaos, AWS Blu Insights projects keep everything organized by default. Things are always where you expect, and it’s obvious where to put stuff.

Every project includes the tools all teams need to work together; Assets, To-Dos, Schedule, Documents, Management, and Catch-up. You can turn off the ones you don’t need to tailor things to the project at hand. Spreading work across a bunch of apps is inefficient, expensive and onboarding your team is a pain. AWS Blu Insights eliminates all of those issues by combining everything you need in one place. It’s “easy mode” for work.

Start by creating a demo project or your own project in order to discover all the features of AWS Blu Insights. 

To create a demo project, you can choose from our four different technologies in the Codebase section:

To create your own Codebase project, just click on the +New button:

You can also create a To-Dos project by going to the To-Dos section.

The To-Dos type allows you to collaborate, manage projects, and organize tasks. It’s packed with all the features to help your team succeed. From boards and documents to events and timelines, AWS Blu Insights features give your team the power to quickly set up workflows and meet deadlines. 

In addition to the power of the todo project, the Codebase project type provides a complete code management package, from uploading source code resources to exploring insights, planning the project, and testing.

On the home page, you will also find the list of all the projects you have visited recently. The first project in this list is the last one you have visited. You can clean this list at any time by clicking the trash can icon.

The activities of your team are available in the activities feed. They correspond to the activities of the project you have currently selected. The activities can be filtered.

Access AWS Blu Insights

AWS Blu Insights access is possible directly from the AWS Console. Users will get direct access to AWS Blu Insights from the console using their AWS accounts. To do so, they have to follow these steps:

1. Connect to the AWS Console.
2. Navigate to the AWS Mainframe Modernization service.
3. Go to the ‘Tools’ section.
4. Launch AWS Blu Insights.
5. Enter your name and your email.
6. Request access and check your email inbox.

AWS Blu Insights will associate your email to the AWS account.

For more details, check the FAQ.

People and Permissions

Adding members to projects

To invite members (customers, partners, colleagues…) into your projects, head to the people page of a project. You’ll see the option to invite a client to the project:

Enter the complete email of the client and click on “Add another person”. Registered members will be visible on the table and non-registered ones will be listed on the invitation tab. Once registered they will automatically be listed on the first tab. All invited members will receive an email to register and/or connect to AWS Blu Insights so they will be able to see the project.

Setting permissions

Different permissions can be granted to invited members depending on their roles. These permissions are grouped into Profiles and are managed at 4 levels:

• Visible / Hidden Modules
• View / Edit permissions
• Visible / Hidden columns
• Authorized / Unauthorized Download

If Codebase projects are created from a Secured Space, download authorizations can be deactivated by the owner of the Secured Space.

By default, a AWS Blu Insights project is built within 3 profiles

• Owner: it has no restrictions on the project. It is assigned to the project creator and can be assigned to more members. It is a non-editable profile.
• Team: it gives almost all the permissions except delete actions, edit others’ dashboards and access to the catch-up module.
• Guest: it gives View access to all modules except Settings and Catch-up.

Modules are managed at the project level and the profiles are automatically updated accordingly (See Settings)

Deny members access to the project

Denying a member access is more useful than deleting him from the project to keep the history of their contributions (comments, documents, etc..).

To deny access to members, select them and click on Deny Access.

To grant them access again to the project, select them and click on Grant Access.

Download Rights

Download Authorizations

Owners of the project controls downloads authorizations among all team members.

• Secured Spaces:
  • The owner of the Secured Space determines if users can download its content or not through the “Download” authorization.
• Codebase:
  • The owner of the project can manage, through user profiles on the People page, the following authorizations:
    • Download source code
    • Export reports
  • For Codebase projects created from Secured Spaces, if the “Download” permission is disabled on the Secured Space, it will override the profiles’ permissions.
• Versions Manager:
  • The invited users keep the “Download source code” and “Export reports” permissions they have on the reference Codebase project.
• Transformation Center:
  • The invited users keep the “Download source code” and “Export reports” permissions they have on the reference Codebase project.
  • A new “Download outputs” permission can be given to invited users.

Document Download

You can only download documents which are directly shared with your profile (or contained in a shared folder). Profiles are managed on the People page of your project.

Page 404

When you see 404 page, it means something has gone wrong. Among the reasons, it can be that:

• You have typed the wrong address
• You are trying to open a page that no longer exists
• You are not authorized to access the project
• You have been invited to a specific type of project that you are not authorized to access (see The accreditation program)

Artefacts

Codebase upload

As a modernization project point of contact and user of AWS Blu Insights, you can follow this process to get the codebase from your customer:

1. Customer requests access to AWS Blu Insights.
2. Once access requested, the customer should notify you (and provide their email address used to register), so that you can request the activation of their account.
3. Invite the customer to prepare their legacy source code. Information regarding the legacy artefacts format is available below.
4. Ask your customer to create you an AWS account (it will be billed for the usage of the Transformation Center – See Pricing)
5. You request access to AWS Blu Insights using the customer AWS account
6. Customer uploads source code to AWS Blu Insights:   
   i)   Creates a secured Secured Space   
   ii)  Uploads the application source code (compressed into a .zip or .7z archive)   
   iii) Invites you to the Secured Space

Source Code

We list in this page a few guidelines and expectations regarding the assessment baseline.

Artefacts of the codebase

• The code baseline is made of elements called artefacts
• An artefact is a single file corresponding to a single piece of the application, i.e.:
  • A single program
  • A single control card
  • A single copybook
  • A single database schema
  • Etc.

Versions wise

• Artefacts versions are the ones used to build the application version in production

Content wise

• All artefacts contributing to the build or the run of the application in production
• Scheduler configuration (e.g. OPC, SCL, etc.)
• Scripts (e.g. JCL, REXX, etc.)
• Batch scripts (e.g. CMD, BAT)
• Screens (e.g BMS maps, PROCS).
• Programs (e.g. COBOL, PL/1, Assembler, Easytrieve, SAS) and copybooks and any of their dependencies
• Schema and metadata (e.g. LISTCAT) of the persistence (e.g. DB2 DDLs, IMS (MFS, PSB, DBD), VSAM and GDG formats)
• Parameter and configuration files (such as control cards – CTL or the CICS system definition – CSD file) used to determine execution flow and resolve dynamic calls
• All existing documentation: naming convention, architecture document, interfaces description, etc.

Format wise

• All code and database description artefacts must be in a textual format (or in a special format for 2 cases below).

Special Formats

AWS Blu Insights can extract a suitable codebase from special formats, such as:

• SAVF format for iSeries applications.
• PBL format for PowerBuilder applications.

Test Data

Depending on the project (customer requirements, legacy technologies, etc.), different types of test cases can be required.

Screen Test Cases

• Video recording of all the screens positive and negative cases
  • 1 video with a positive case and 1 video with negative cases, per each test case
  • Video duration should be limited to ~10 minutes per screen
• Database extractions related to the Screen
  • At start of the recording
  • At the immediate end of the recording

See Test Capture & Replay for TN3270 and TN5250 to see how AWS Blu Insights can automate the definition of these test cases.

Batch Test Cases

• Inputs for the job execution (configuration, parameters, files…)
• Outputs generated by the job (files, reports…)
• Execution log of a single batch job or step (including its duration)
• Database extractions related to the batch before and after execution

Backend Test Cases

• Execution log of a back-end service (including response time)
• Database extractions related to the backend service before and immediately after execution
• Recording of backend input and output messages {(Input Message 1, Output Message 1) … (Input Message n, Output Message n)}

Database Test Cases

Database extractions for the Tables in related to the POC migration

• One with a large volume of data
• One with a smaller volume (fewer records per table) of data per table than a production set data

For Project migration, all the used Tables will be extracted.

Test Data Format

• All artefacts are in native format and native encoding (no charset or encoding is changed): no listing or printing format
• Export/dump of artefact is done using legacy native tools from the legacy platform
• No charset or encoding transformation (e.g. EBCDIC encoding is kept)
• Transfer/offload is binary (not ASCII)

Start a new modernization project

Please read carefully and check the pre-requisites. Access approvals need up to 24 hours to be processed.

The success of an AWS Blu Age modernization project starts with a tight collaboration between experienced L3 Certified individuals (L2 Certified could be involved in the assessment phase) and the final customer. To use AWS Blu Insights, as explained during the training program, you need to follow the workflow described below. 

1. Invite the customer to prepare their legacy source code (see expected legacy artefacts here).
2. Ask your customer to create you an AWS account. It will be billed for the usage of the code generation – See Pricing.
3. Request access to AWS Blu Insights using the customer AWS account.
4. Ask your customer to requests access to AWS Blu Insights and wait for the activation by the AWS Blu Age team.
5. Customer uploads source code to AWS Blu Insights:   
   i) Creates a Secured Space   
   ii) Uploads the source code   
   iii) Invites you to the Secured Space
6. Create the Codebase and Transformation Center projects to start the assessment.

Only the creator of the Codebase project can create the related Transformation Center project. This allows the customer to control the usage of a billable service. Read more here and here.

Filters

To filter your data in an easy and powerful way, we designed our own query language: AWS Blu Insights Query Language (BQL).

How to use it?

Just type your BQL query in the filter field displayed on top of almost every page.

Constructing BQL queries

This section describes information about fields that are used for searching. A field in BQL is a word that represents a AWS Blu Insights artifact. In a statement, a field is followed by an operator, which in turn is followed by one value or a regular expression (regex). The operator compares the value of the field with the value on the right, such that only true results are retrieved by the statement. 

Types

=, !=, like, not like

name = 'file.ext'
                                        name like 'file.*'
                                        assigned to = "N'GOLO"
                                        name like '^disc' 

in, in all, not in

workpackage in ['Workpackage1', 'Workpackage2']

workpackage in all ['Workpackage1', 'Workpackage2']

=, !=, <, >, <=, >=, between ... and ...

effective lines > 5
                                        effective lines between 10 and 15

=, !=, <, >, <=, >=, between ... and ...

start date > 2021/02/10

An additional operator is Empty is available for every types. This operator works without value type, e.g. name is empty.

Fields

Assets

To-Dos

Management

Pipeline

Note

The “=” operator can be used with ‘uncategorized‘ like workpackage = ‘uncategorized’. This operation is similar to workpackage is empty. The fields available are Workpackage, Status and Label.

Logical operators

To build even more complex filters, you can use logical operators “and” and “or”. You can also use parentheses to group your conditions. Thus, you can build powerful filters such as:

(name like '\\.CBL' and workpackage in ['WP1', 'WP2']) or start date between 2021/04/10 and 2021/04/25

Running a saved search

Saved searches are shown on the left side of the advanced search input. Click on the “filter” button on the left side of the search input to display it.

To run a filter, e.g. Epics, simply click it. The BQL for the search will be set, and the search results will be displayed.