Leading up to this point, you have been expanding the mapping in Studio and the generated manual code in Visual Studio to include the Business Object Card and related items, such as Valuesets, Constants rules and Bags. You now have two brand new engines built, ready and rearing to go.
The next step is to get them deployed to the runtime environment. That is what is going to happen in this exercise. In later exercises, you will be running the setup in the Runtime so it learns about the modifications done in the newly deployed engines.
In most real-life production setups, the runtime environment includes a master server and one or more migration servers. The master server serves as a repository for common files as well as common master databases of the runtime environment.
A migration server is a (normally quite powerful) server used to execute the actual migration. In addition, the Studio and Visual Studio will be running on the individual Workstation of each team member.
This training setup is of course simpler - everything runs on the same machine.
Right now, the Source- and Target Engines in their new versions exist inside your Visual Studio. In order to do any good, they must be compiled and deployed to the Hopp Runtime. In the configuration of the Hopp Runtime, the shared deployment location for each engine has already been defined for each engine as part of the setup of your training environment.
Deploy to build the engine and deploy it to the shared deployment location.
- Right-click the class library project in Visual Studio and select Hopp: Deploy in the context menu (for the Source engine right-click the SourceEngineCustom project)
At this point, the Visual Studio extension will contact the Portal in order to authenticate your and assure that you have the necessary authorization to deploy engines. Don't worry, in your training environment you have all the authorization you need.
But - depending on how long your trainee slot has been idle - the Portal may ask you to sign in:
If you see this, please sign in with
User: TraineeXX (where XX is your Trainee number - for instance Trainee01)
Password: password (literally the word 'password', all lower case)
The Visual Studio extension will then show a dialog listing all the tracks where this engine is deployed and lets you optionally restart the track and run the setup after deployment.
In this training setup, the engine is only deployed to one track there is only one.
At this point, you can actually restart the track to load the new engine and also to run the subsequent setup job. However, for this exercise, you will do that a bit later on, so for now just leave the Start/Restart Track checkbox unchecked and click the Deploy button
Don't worry if there is a red dot next to the Track. That just means the Track is not currently running.
That's it, you have now deployed your two new engines to the Runtime environment. Now is the time to leave Visual Studio behind and jump to the Portal Operations to start using the engines.
What happened here?
You have built and deployed the Source- and Target engines to the Hopp Runtime environment.
Next up is to do a restart of the Runtime causing it to load the new engines and finally 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.
Before you do so, we need to introduce you to the next part of the Hopp solution> The Portal / onwards to the next exercises!