Now you have familiarized yourself with the Portal Operations interface, it is time to get to work and get the newly deployed engines operational and ready to run in the Hopp Runtime.
This means using the Portal Operations to restart the Runtime, so the newly deployed engines are loaded and then run the setup so the Runtime learns about the new stuff in the engines.
A quick note before you start: From now on, we assume that the preceding exercises in Studio were completed correctly. If at any point you realize that you need to go back to a previous exercise to correct something in Studio, please remember the complete path any correction in Studio needs to go through in order to be operational in the Portal Operations.
- Validate without any validation errors
- Publish to Generator
- Visual Studio
- Generate Engine
- Deploy Engine, verify that deployment succeeds
- Portal Operations
- Restart Track
- Run Setup of relevant Engine
- Check that Setup job completes successfully
You must go through these steps every time you have modified in Studio in order to test your changes in the Portal Operation!
Start (or restart) the track
The first step is to restart the Track that has loaded the Hopp Runtime and the previous versions of the engine.
You do this by navigating to the Execution/Track menu item in the Portal Operations menu.
If the track is stopped (red dot) you need to start it and if it is already running (green dot), you need to restart it in order to load your new engines.
Click the Action Context Menu
and select Restart
The track is now started, has loaded your new engines (provided of course that you have deployed the engines in the previous step) and is idling, ready to execute your wishes!
The next step is to run 2 setup jobs to setup the Source-and Target engines in order to synchronize the engines and the runtime
- In the menu, select Administration/Manage
- Check these radio buttons
- Source Engine: Setup only
- Target Engine: Setup
- Leave all other on Skip
Click the Action Context Menu and select Submit
The Portal Operations will now show a dialog previewing the changes in the runtime. In this case the changes are
for the Source engine
for the DataServices
Valueset TranslateCardTypes from the Source engine
Valuesets CardTypes and CardStatus from the Target Engine
Initially, the tabs in the dialog are marked with a red dot. This is to warn you of potential data loss
You need to click the Accept button on both the Source preview tab and the DataServices preview tab in order to enable the Ok button
Click Confirm and the Portal Operations will submit two jobs, one for each engine
TIP: These last 2 steps of restarting the Track and running setup of the newly deployed engines can be launched directly when deploying the engine from Visual Studio. Just check the Start/Restart Track checkbox and the Run setup checkbox in the Deploy dialog.
In the Portal Operations job list you can follow the execution of the 2 jobs and check that they were completed successfully
- In the Portal Operations menu, select Execution/Jobs
- The 2 newest jobs are at the top of the list
- In the 2 panels to the right of the job list, you can see
- The parameters for the job
- The results of the job execution
- Right click on the row of the new job to see the Instances option, this will show the job log. If a job fails, this is the place to look for an explanation
- Please note that this panel refreshes automatically, so there is no Refresh Button
What happened here?
By restarting the track, you cause the track to load the new engines and by running the 2 setup jobs you have synchronized the engines and the runtime so the latter now knows about the new items you have added in Studio.
If you look at the Business Objects to Export (select Source/Objects in the Portal Operations menu and click the Refresh button, you will see that the new Card Business Object is now present, but that nothing has been exported yet.
Card is marked red because it depends on data from the Source System for Src.DebitCard and also the view CardStatus, both of which have not been loaded yet.
So it would not make any sense to export the Cards before loading these.
Luckily that's exactly what you are going to do in the next exercise.