-
Users Handbook
-
-
-
- Intro & Basics
- All Objects have Descriptions
- Check for unused procedures
- Compiled Procedures up to date
- Invalid Source Layers
- Required Columns
- Check for abnormally ended Jobs
- Check for blocked Jobs
- Check for disabled Tasks
- Check for duplicate tasks in different Jobs
- Check for duplicate tasks in same Job
-
-
-
Administrators Handbook
-
- Register URL
- Configure SSL/HTTPS
- Configure Proxy-Server
- How to edit the appsettings.json file
- System Settings
- Global Parameters
- Allow Service Account to Logon as a Service
- LDAP & SSO Authentication
- Migrating Testcases and Configuration
- Licenses Management
- Manual Configuration
- Exposing the BiG EVAL REST API to other Network Segments
-
- Articles coming soon
-
Developers Handbook
-
Known Problems
-
Demo Virtual Machine
-
Release Notes
-
General
The BiG EVAL API is organized around REST. Our API has predictable resource-oriented URLs, accepts and returns JSON-encoded request and response bodies and uses standard HTTP response codes, authentication and verbs.
Because your BiG EVAL license allows you to install multiple BiG EVAL instances, you can install a development-instance to test the REST API without affecting your productive BiG EVAL instance.
The API may change with every release of BiG EVAL. But we strive to make everything backward compatible. But please read the release-notes to get informed about changes.
Table of Contents