Invantive Composition for Word
Provider CompanyInfo: Company.info business web services. |
Company.info business web services.
Code for use in settings.xml: CompanyInfo
Alias: cio
Status: Production
Available in Editions: Paid
Technical Documentation: https://ws1.webservices.nl/soapnoheaders
Documentation
WARNING!COMPANY.INFO OFFERS NO BUDGET CONTROL. WITH A FEW TEST QUERIES YOUR FULL COMPANY.INFO BUDGET AMOUNT CAN BE FULLY EXHAUSTED. INVANTIVE IS NOT LIABLE FOR ANY MONETARY OR OTHER LOSSES BY THE USE OF COMPANY.INFO. INVANTIVE ALSO REJECTS ALL CLAIMS DUE TO POSSIBLE BUGS OR OTHER CAUSES LEADING TO BUDGET LOSS AT COMPANY.INFO.
AS A HINT, PLEASE MAKE SURE TO APPLY THE FOLLOWING MEASURES:
* Some results are returned in multiple pages such as on dutchBusinessSearchParametersV2. Each page will cost money. Retrieve only the number of pages you need; often the first page will be sufficient to achieve your goals. The 'page' table function parameter when explicitly supplied as null will retrieve all pages.
* To get an impression of how Invantive UniversalSQL translates into individual API calls, please query the data dictionary view 'sessionios', such as with 'select * from sessionios@datadictionary'.
Provider Attributes
The following provider attributes are available for CompanyInfo:
Code |
Description |
Default Value |
Set from Connection String |
Set from Set SQL-Statement |
Set from Providers File |
|---|---|---|---|---|---|
force-case-sensitive-identifiers |
Consider identifiers as case-sensitive independent of the platform capabilities. |
False |
✓ |
✓ |
✓ |
forced-casing-identifiers |
Forced casing of identifiers. Choose from Unset, Lower, Upper and Mixed. |
|
✓ |
✓ |
✓ |
http-disk-cache-compression-level |
Compression level for the HTTP disk cache, ranging from 1 (little) to 9 (intense). Default is 5. |
5 |
✓ |
✓ |
✓ |
http-disk-cache-directory |
Directory where HTTP cache is stored. |
C:\Users\gle3\Invantive\Cache |
✓ |
✓ |
✓ |
http-disk-cache-max-age-sec |
Maximum acceptable age in seconds for use of data in the HTTP disk cache. |
2147483647 |
✓ |
✓ |
✓ |
http-get-timeout-ms |
HTTP GET timeout (ms) |
300000 |
✓ |
✓ |
✓ |
http-memory-cache-compression-level |
Compression level for the HTTP memory cache, ranging from 1 (little) to 9 (intense). Default is 5. |
5 |
✓ |
✓ |
✓ |
http-memory-cache-max-age-sec |
Maximum acceptableage in seconds for use of data in the HTTP memory cache. |
2147483647 |
✓ |
✓ |
✓ |
http-post-timeout-ms |
HTTP POST timeout (ms) |
300000 |
✓ |
✓ |
✓ |
invantive-sql-forward-filters-to-data-containers |
Whether to forward filters to data containers. |
True |
✓ |
✓ |
✓ |
invantive-sql-shuffle-fetch-results-data-containers |
Whether to shuffle results fetched from data containers. |
False |
✓ |
✓ |
✓ |
invantive-use-cache |
Whether to cache the results of a query. |
True |
✓ |
✓ |
✓ |
maximum-length-identifiers |
Non-default maximum length in characters of identifier names. |
|
✓ |
✓ |
✓ |
pre-request-delay-ms |
Pre-request delay in milliseconds per request. |
0 |
✓ |
✓ |
✓ |
requests-parallel-max |
Maximum number of parallel data requests from individual partitions on the data container. |
32 |
✓ |
✓ |
✓ |
result-set-cache |
Action: provide 'empty' to empty. |
|
|
✓ |
|
slot-based-rate-limit-length-ms |
Length in ms of a slot-based rate limit. |
60000 |
✓ |
|
✓ |
slot-based-rate-limit-slots |
Number of slots of a slot-based rate limit. Null means no slot-based rate limit |
|
✓ |
|
✓ |
standardize-identifiers |
Rewrite all identifiers to the preferred standards as configured by standardize-identifiers-casing and maximum-length-identifiers. |
True |
✓ |
✓ |
✓ |
standardize-identifiers-casing |
Rewrite all identifiers to the recommended standard platform-specific casing when changing a data model on a case-dependent platform. |
True |
✓ |
✓ |
✓ |
trace-native-calls |
Trace native calls to data container backend. |
False |
✓ |
✓ |
✓ |
use-fallback-environment |
Use fallback environment. |
|
✓ |
|
✓ |
use-http-disk-cache-read |
Whether to use HTTP responses from previous queries stored on disk to answer the current query. |
True |
✓ |
✓ |
✓ |
use-http-disk-cache-write |
Whether to memorize HTTP responses on disk. |
True |
✓ |
✓ |
✓ |
use-http-memory-cache-read |
Whether to use HTTP responses from previous queries stored in memory to answer the current query |
True |
✓ |
✓ |
✓ |
use-http-memory-cache-write |
Whether to memorize HTTP responses in memory |
True |
✓ |
✓ |
✓ |
use-metadata-cache |
Whether to use the metadata calculated previously Has only practical use during development on a XML provider. |
True |
✓ |
✓ |
✓ |
use-result-cache |
Whether to use result sets from previous queries that can answer the current query |
True |
✓ |
✓ |
✓ |
Generated 11-01-2019 20:24 on version 17.30.0-PROD+1821.
