The latest version of Tackle has the Developers view and the new Architects view to support the three main roles of users:
Administrators: Has access to some application-wide configuration parameters that other users can consume but not change or browse.
Example actions: Define Git credentials, Maven settings, .xml files.
Architects: Often the technical leads for the migration project that can create and modify applications and information related to it. The Architects do not need to have access to sensitive information, but can consume it.
Example actions: Associate an existing credential to access the repository of a given application.
Migrators: Developers that can run assessments and analysis, but cannot create or modify applications in the portfolio. Maybe an example action?
The developer view is intended to be used by migrators and stakeholders and has three pages with different functionalities.
The Application inventory page manages the applications being migrated and is where the assessment and analysis processes are performed. The application list provides a holistic view of the application portfolio using an extensible tagging model to classify application types. The applications can be expanded to show more detailed information which can be edited and managed.
This page has two tabs with different information and functionality: Assessment and Analysis.
Use the Assessment tab to facilitate a conversation before migrating an application with stakeholders such as technical subject matter experts and application owners or users. Tackle does not prescribe solutions but instead provides a script of discussion points to identify potential migration risks.
Assessment categories include:
Reviewing the results will help stakeholders develop suitable migration strategies for applications or application types. Only one assessment can be done at once, but assessment results can be applied to other applications.
Additional functionality includes:
Use the Analysis tab to perform an automated examination of the application that views binaries, source code, and dependencies to find possible issues that might prevent the application from running on the new platform. The process starts by retrieving and then analyzing one of the following repositories:
There is an option to upload a locally stored binary. This only works if a single application is selected.
Additional functionality includes:
The Reports page provides an overview of the assessments and reviews for the entire application inventory. The Reports page contains the following sections:
By default, all applications are selected. You can clear some of the application check boxes to filter the report.
The Controls page is where the application parameters are managed by the architect or developers as the instance is configured and edited as the project progresses.
The parameters include:
The administrator view is intended to be used by administrators to set up the Tackle instance environment.
This management module enables administrators to create and manage credentials for access to private repositories. It also allows for the architects to assign the credentials to applications without knowing their contents.
The credentials page displays the available credentials with an Edit and Delete buttons and the following fields:
Note: Type specific credential information such as keys and passphrases will be hidden or shown as [Encrypted].
This management module configures the repositories used by Tackle with the following options.
This management module configures HTTP & HTTPS proxy settings and credentials. To configure the proxies click the radio button and enter the following information.