The Portal is a web application presenting the results of the migration to all stakeholders. For instance
- The Migration Team
- Users from the business involved in the migration
In addition to the static presentation of the migration results the Portal also allows for users to edit certain aspects
- Status, Responsible User and Comments on Events to support the Event resolution workflow
- Data content for Translation Valuesets
The Portal presents the results that were stored when the latest migration iteration executed the Export and the Import. In order to improve Portal responsiveness, you will in this exercise submit a Publish job in the Director to store aggregated results and statistics in optimization tables in the Migration database.
This job will also synchronize the Project database with new Events to participate in the workflow.
Publish to Portal
The first thing to do is to submit a job in Director to publish the results of your latest migration iteration to the Portal.
The Publish job does not provide new information, it will just sum and aggregate the Business Object instances and Events in the migration result to help the Portal to be as responsive as possible.
- In Director, select Administration/Manage in the menu
- Check the Portal radio button Publish
- Click the Submit button to open the selection dialog
- Select the Portal tab, move all Business Objects to the Selected box
- Click the Ok button to submit the Publish job
- Follow the job progress in the Job list
A bit further on you will see that the Portal shows delta indicators to signal whether counts (of Events or Instances) increase, remain level or decrease. These delta indicators compare the current counts to a baseline.
You may have noticed the Baselines button next to the Portal Publish radio button in Administration/Manage. You can click this button to manage baselines, including create a new baseline, set a baseline as the current baseline and delete a baseline.
migFx is able to migrate multiple separate businesses in the same project. In fact, the Workshop project you are working on is migrating two separate banks from one multi-tenant system to another. In migFx, we say the migration is separated into Partitions.
migFx has user authorization in place here. For instance, in the Portal you can view the results for all partitions only because you are authorized as a migration team member.
migFx can also selectively authorize users to see results for only one Partition and not any other Partitions. So in the case of the Workshop project, users in one bank can only see the results for this bank, not results for other banks included in the migration.
When you were in the Target Map right at the beginning of these exercises you created the Interface Fields for the Card root Business Object, one of Interfaces Field acts as partition field. It is the actual value of this Interface Field for each Business Object that determines which Partition the Business Object belongs to.
The Portal is a web application and is viewed through a web browser of your choice. In the training setup you are using Chrome, but the Portal works in other browsers, for instance Firefox and Edge - but not Internet Explorer.
The Portal is just that - a Portal. As such, the Portal can host different modules each of which handles different aspects of the migration. Some mandatory modules are delivered out-of-the-box with migFx, other modules are optional.
In your training setup, the (mandatory) Migration module is the one that handles all the Events, Translation Valuesets and so on, and will be the focus in these exercises.
The training environment also includes these optional modules:
- Scope & Test: Manages which Business Areas are in scope for the migration and assists and tracks User Acceptance Test results
- Issue Management: Creates and manages issues, with attachments, states, history, discussion etc.
The optional modules are integrated into the Portal in the training environment, but will not be covered further in these training exercises.
As an aside, the Portal architecture is open and extensible. This allows you to implement your own modules - outside the purview of hopp tech - that nevertheless integrate seamlessly into the Portal. In many cases, it is useful to implement a reconciliation module to display proprietary reconciliation information in the Portal.
We have set up Chrome with the Portal as your homepage, so it should show up automatically, when you launch Chrome. If not, you can navigate to this url: https://localhost:430XX, where XX is your Trainee number - 2 digits (for instance https://localhost:43001 for trainee 01).
The Portal may ask you to sign in (unless Remember me was checked not long ago)
- User: TraineeXX (for instance Trainee01)
- Password: password
- You are welcome to let Chrome save your password (if this has not already been done)
There are many elements in the Portal. For the sake of these exercises, the focus is really on working with the Workshop project. You get to the Workshop project by clicking the arrow to list the active Projects and then click the Workshop card:
Once you have clicked the Workshop card, the Portal will take you to the area where you will work on the actual migration of the Workshop project:
|1||Authorization: Authorize user to the project and partitions|
Business Objects: Configure which Business Objects are in scope for this migration project
Translation: Configure which Translation Valuesets are in scope for this migration project
|2||Statistic: Displays statistics for the migrated Business Objects|
Parameters: Shows a list of the actual values of the parameters in place for this migration iteration (The values of the Constants from the Source and Target Maps that were marked as Run Parameters)
Test: Part of the Scope & Test module and not active for the Workshop project
Events: An aggregated list of the Events that occurred during the migration
Translation: Edit and manage the Translation Valuesets
Items: List and search in specific instances of Business Objects
Issues: Part of the Issue management module - lists issues in the migration project
Partitions and Tracks
Once a menu item is selected, you will in many cases need to select a Partition and potentially a Track:
|Partitions||The Partition box contains the actual partition values that exist in the migration project. You can only see the All level because you are authorized to do so|
|Tracks||The Director executes the migration in what is called a Track and a project can have as many active Tracks as you want. This enables you separate different aspects of the migration.|
For instance, in a banking migration it is quite normal to separate the migration of historic transactions (huge volume, little complexity) in a separate track and keep the golden track for the complicated stuff unpolluted in another track.
In your training setup, the Workshop project only has 1 track: Training