Skip to main content

Generating and Deploying Engines

Generate, Deploy and Debug​

A right-click on a TargetEngine project or a SourceEngineCustom project will show the project context menu with the Hopp submenu:

Hopp Menu options

Generate​

The Generate... context menu item open the generation dialog:

Generate dialog

The dialog allows you to specify the Published xml file to use as input for the code generation. This is the file containing the published Source/Target Map from Hopp Studio. By default, this is the Published XML file in the engine project, but you can override it before generation if you temporarily want to generate from another file.

The dialog gives you a label with the last modified time of this file as a sanity check. If the file is more than 10 minutes old, the label is red.

Click Ok to start the code generation. Visual Studio will show the output from the code generator in the Output tool window:

Generation Output

Deploy​

The Deploy... menu item will first build the engine in question. If the build succeeds, the Visual Studio extension will invoke the Portal. The Portal will in turn query the Runtime configuration and show a dialog with a list of all the tracks using the engine about to be deployed:

Deploy dialog

For each track, you can choose what should happen after the engine is deployed:

  • Starting or Restarting the Track will cause the newly deployed engine to be loaded
  • After starting the Track, you can choose to run the Set Up of the deployed engine

These actions are exactly the same as the ones normally done in the Portal Operation so you can also opt out of them here and deploy the engine without checking any options. You will then have to go to the individual tracks in Portal Operations and do the start/restart and setup from there.

Debug​

If you have authorization to connect to the Hopp master and track databases, you can launch the migration of selected Business Objects from within Visual Studio.

This allows you to:

  • Set breakpoints in Visual Studio in order to debug and single step through Bag/Rules implementations
  • Test and verify the generated engine locally before deploying it to the Director Runtime.

The Debug... menu item will first build the engine. If the build succeeds, the Visual Studio extension will invoke the Portal.

The Portal will in turn query the Runtime configuration and show a dialog to select what to debug:

Debug dialog

After selecting which Track to debug, you can run debug on a limited set of Business Objects selected

  • By Business Object
    • Any arbitrary
    • On a Key
    • That fired a given Event
  • By Item Set

Click Start to launch a debug job in the Runtime. The Runtime will start the job process locally on your machine, and the Visual Studio extension will attach the debugger to the job. The debugger will stop on any breakpoints it hits during execution.