Pilota controls all jobs and settings in the integration providing a rich developer and end-user interface.
Pilota is our end user interface.
Along with controlling jobs, users with the appropriate experience can create, modify, or remove any integration module. These of course are the queries which that extension uses to obtain its source data.
Pilota includes one of the most requested abilities: the ability to execute a job on demand. This allows for those times that data needs to be updated before it can be used for reporting or dashboard display.
Pilota interacts only with Ronzinante.
It has no access to any database. When Pilota is opened, the first dialog box asks for the server and port of the Ronzinante that it is to connect with. Once connection is established, available objects, such as jobs, entities, and connections are shown in the Object Explorer interface. Within the Object Explorer, jobs can be run on demand or integration changes can occur.
Pilota has been designed using a docking window system found in many popular integrated development environments, also known as IDEs. This type of environment allows the user to maximize the working area.
With Pilota, jobs can be configured quickly and easily.
A key aspect of controlling the integration is determining what modules need to be included during a run. Pilota’s jobs function allows for multiple extensions to be used. You can configure as one integration for all modules and the time could be set to execute nightly at a time of your choice. All in less time than ever before.
Pilota allows you to:
- Control Jobs, Integration, scheduling
- Start jobs on-demand
- Utilize entities
- Manage integration definitions, queries, file structures and more
- Define Crosswalks