System in Cloud Service contains several different elements. The most important piece for the user is our Modeler. The Modeler is a set of plugins made for eclipse that allow you to model your solution with data-flow diagrams. Through the Modeler you can also perform tests for your solution either on your machine or directly in the cloud machine of your choice.
We provide you a web application to manage your account and the cloud resources that you need, it is the Management Console. Many operations (like creating new machines) can be run both in the Modeler and in the Management Console. However, with the Console you will have more details about your account and it will let you manage the access rules to the service for the Modeler projects.
You are also able to integrate your System in Cloud with other applications via SDKs provided for some programming languages.
To fully understand the concept of our service we introduce some of the terms that we will be using.
System is the solution that you develop for your problem. It is defined by its model. However, you can updated the model any time.
Model is a set of data-flow diagrams and other artifacts (like scripts) that graphically describe the solution to your problem. It is contained on a jar file and it can be deployed in our platform and attached to your system.
Machine is a counterpart of virtual machine of Iaas cloud providers (like "instance" for Amazon Web Services). We built up for you an abstraction of what is defined by laas providers. You will only need to care for the RAM and CPU capacities.
Instance is the unit of the System that is really doing your solutions. You can have many Instances for one System working in parallel. Instances are allocated on Machines, consuming their resources. You can allocate as many instances as possible to one Machine to fully exploit its capacity.
If you are familiar with Eclipse IDE you can skip this point and use already our update site:
Otherwise, there is a more detailed explanation on how to install our below.
In the presentation below we show how to create a new project.
Our project management and structure is based on maven system (http://maven.apache.org/) system. Even if you are not familiar with this tool, eclipse should be enough to normally work with the Modeler.
The principal elements of the Modeler that you will be using are introduced in the following presentation.
Data-flow diagrams describe the solution of the problem. Embeded tasks help you manage the complexity by nesting one diagram inside another. In the following presentation you will learn how to create and use the Data-flow diagrams.
This part of the Modeler completes the idea of Unit Testing. You can test each diagram of your solution individually. Just like a black box with its inputs and outputs. Test Diagram is a functionality where you insert the diagram to test into an Embedded Task. You can use almost the same set of elements to create your tests as the ones you use to create your system diagrams. Besides, for test diagrams we provide many block that can help you testing your data, such as File Reader, Webcam and many more. In the following presentation, you will learn how to create and use test diagrams.
Messages that contain specific data (as integers) are exchanged between ports. In the presentation below we describe shortly common types of data.