Using VS Code for ECL Development on HPCC Systems

Подробнее о видео

This Latest installment of the Developers Video Series will discuss using VS code, the Visual Studio Code for HPCC Systems ECL development. This video will look at setting up VS Code, the Visual Studio code application as your integrated development environment for developing ECL Code.
To get Visual Studio code you can download from the Visual Studio website go to code.visualstudio.com to get the Visual Studio.
Once you install Visual Studio code you once you've installed visual studio code go to the extensions page and do a search for the ECL you should find the ECL Language Extension in the Visual Studio Extensions.
Once you have Visual Studio – VS Code – and installed the ECL Language Extension you are now ready to work with ECL on an HPCC Systems cluster.
Now let’s configure your system to work with an HPCC Systems Cluster.
With your ECL Extension installed - Create a new folder then create a new file in that folder.
You can name that file anything you want as long as it has an ECL extension. The ECL extension tells the Visual Studio code that it is an ECL file.
At this point, we may get a message that there is no Launch configured for ECL. We're going to create one.
Press the Create ECL Launch button. Which will bring up a selection box. Select ECL.
This then brings up the default ECL Launch configuration.
This is indeed a valid launch configuration if you were going to work on a local HPCC systems deployment, as indicated in the configuration by the name “localhost”.
This configuration only connects to a locally running HPCC Systems instance.
In order to connect and configure a connection to the HPCC Systems cluster that we want to use to run this job on, we are going to have to input that systems information into our launch configuration.
The specific HPCC Systems instance that we want to use, in this case it's going to be play.hpcsystems.com
We're going to modify this launch configuration to develop on that system.
Enter the name of your cluster which for this field is just a nickname that you're going to call the cluster in VS Code. It doesn't really matter what you call it - call it anything you want - we'll call it “play” in our demonstration.
You can leave the type as ECL and then for the protocol if it's a secure cluster, which this one is, we're going to use HTTPS as the protocol.
If it is a secure system using protocol HTTPS it's going to be running on port 18010 so we can change that Port number to 18010
That's if it's a secure protocol running on HTTPS, will use port 18010.
Now we're going to enter the server address which in this case is the host name or IP address for the desired HPCC systems server. In this example it's going to be play.HPCCsystems.com
Here we have to put in the name of our target cluster which we may be targeting a Thor but this needs to reflect the actual name of that Thor. If your target cluster were to be named Thor-100 then this field needs to say Thor-100.
Fortunately our target Thor on the play.hpccssytems.com cluster is just named Thor. Change the value there to Thor. Note that this should be the actual name of the cluster to target.
You can generally just use the defaults for the rest of launch configuration. You should still enter a username, even if it is not required. If you're working on a secure system you need to enter your username, and also enter your password here.
Be sure to save your configuration.
If you need to add a another configuration, for another server or another target cluster, just press the add configuration button and add another configuration as needed.
For this demonstration we are only interested interacting with that Thor target on the Play cluster.
Now we can see from the status that we are connected to our Play cluster.
We can Check the Syntax
Then Submit the code.
If everything is configured correctly we can see our job being processed and the result right here in the VS Code window.
And we can now go over to ECL Watch and we can see the job and workunit that we just created.
© 2023 LexisNexis Risk Solutions