Name | Description |
---|---|
DataSpider Studio | Studio is an IDE designed to maximize developer productivity and to simplify service deployment and administrative tasks. |
DataSpiderServer | Service execution environment |
ScriptRunner | Application interface for the external invocation of service |
CLI Console | command line and web accessible server management console |
Name | Description |
---|---|
DataSpider Studio for Web | Studio for Web is an IDE for the design, operation, and management of services on web browser. |
WebConsole | WebConsole is a tool for the operation and management of services on web browser. |
Browser Help | Browser Help is a help that can be referenced by web browser . |
Name | Description |
---|---|
Designer | is a GUI tool which enables creation of executable, called Script.
In Designer, each process is represented by its corresponding icon. By selecting and dragging the cursor to the next icon in the process flow, icons can be connected and the connected icons represents operations. A script, when its creation is finished, can be registered with DataSpiderServer as a service and can be directly invoked by trigger functions and indirectly by external applications. |
My Projects | Manages all projects created.
Each created project is assigned to a registered user. A list of projects owned by a user is displayed in the My Projects. Creating new projects or editing existing projects are controlled within from My Projects. |
My Triggers | Manages trigger functions.
A list of triggers available to a user is displayed in My Triggers, a convenient accessory to view the results of trigger executed scripts, which includes the script execution status and script execution time. |
My Logs | Enables registration of the filter criteria for the search result, in addition to viewing the result.
Filter criterion are managed by users. It displays the all of the search result that matched the criteria registered by the user. Filter criteria can be useful to aggregate the result of an interest on regular basis. If you are going to check all of the abnormal termination of operations that occurred yesterday in the next morning, you could register it as "Abnormal termination occurred yesterday" and use this filter every morning to gather only the relevant results. |
Explorer | A file manager which allows accessing resources in the DataSpider filesystem
Within the Explorer, files and directories can be created and deleted.It also allows editing of text files. |
Control Panel | Allows users to view and manipulate system settings and controls.
It includes, environmental variables settings, user account settings, resource monitoring tool. |
Directory path | Description | |
---|---|---|
$DATASPIDER_HOME/server | bin(*) | Directory where executable files and configuration files for server applications is stores. |
conf(*) | Directory where configuration files for server applications is stores. | |
data(*) | Directory for users | |
doc | Directory for help files | |
etc | Directory where static configuration files are found. | |
ftp(*) | Directory dedicated to FTP server | |
home | Used for storing project files, containing saved files.User's home directory. | |
lib(*) | Directory for the library that need to be placed outside. | |
lic(*) | Directory for license files. | |
logs(*) | Directory for log output. | |
plugin | Directory for adapter and trigger modules. | |
samples | Directory where sample projects can be located. | |
schema(*) | Directory where schema is stored. | |
share | Directory for all shared project files | |
system | Directory for system modules. | |
thirdparty_license(*) | The license agreement for third party software that DataSpider Servista uses is stored. | |
tmp(*) | Directory where temporary files are created. | |
$DATASPIDER_HOME/client | bin(*) | Directory where executable files and configuration files for client applications is stores. |
conf(*) | Directory where configuration files for client applications is stores. | |
doc | Directory for help files | |
logs(*) | Directory for log output. | |
plugin | Directory for adapter and trigger modules. | |
report | Directory of generated specification files. | |
system | Directory for system modules. | |
tmp(*) | Directory where temporary files are created. |