Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Insert excerpt | ||||||||
---|---|---|---|---|---|---|---|---|
|
This page is for data modellers who want to connect to data sources via HTTP.
Overview
An HTTP datasource is a modelling object whose properties provide the information needed to connect to an external source of data via HTTP. This may be a web site, a web service or some other target that allows XML, HTTP or text data to transferred over HTTP.
You must have one HTTP datasource for each HTTP location to which you need to connect. Each HTTP datasource must have at least one HTTP datasource instance. You can add several instances if you want to configure different settings.
In an analysis model, you can add:
a HTTP Collector to load data from a site or service.
a HTTP Exporter to update the site or service with processed data from the model.
The HTPP datasources you create appear in the Basic Settings → HTTP Datasource list in HTTP collector and HTTP exporter properties. In the properties for collectors and exporters, you can optionally specify the HTTP datasource instance using the Advanced → Datasource Instance Expression.
To add a new HTTP datasource to an analysis model:
Go to the model's toolbar → Create group.
Click
to expand the menu.Insert excerpt _http _http nopanel true Drag a
onto the analysis model.Insert excerpt _http_datasource _http_datasource nopanel true
To add an existing HTTP datasource to an analysis model, in the model diagram toolbar:
Go to the model toolbar → List group.
Click
to expand the menu.Insert excerpt _http _http nopanel true Click
to open the list of available HTTP datasources.Insert excerpt _http_datasource _http_datasource nopanel true Drag a HTTP datasource into the analysis model.
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|
HTTP Datasource
Insert excerpt | ||||||||
---|---|---|---|---|---|---|---|---|
|
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|
Basic Settings
Field | Description | |||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Name | Enter the name of the HTTP Datasource. | |||||||||||||||||||||||||||||
Enabled |
| |||||||||||||||||||||||||||||
Protect During Import |
| |||||||||||||||||||||||||||||
Connection Type | Select:
| |||||||||||||||||||||||||||||
The following properties are available when Connection Type is https | ||||||||||||||||||||||||||||||
Check Certificate |
This will check that the web site's certificate matches the web site address, is signed by a valid certification authority, and has not expired. | |||||||||||||||||||||||||||||
SSL Protocol |
The SSL Protocol selects a list of actual protocols that are supported, and enables a sub-set of that list. If this field is blank, PhixFlow will select a default value which will work in almost all cases. Valid settings depend on the version of Java that PhixFlow is running under. These are the allowed values for Oracle's Java 8: TLS, TLSv1, TLSv1.1, TLSv1.2 | |||||||||||||||||||||||||||||
SSL Protocols Enabled |
This field specifies the SSL Protocols that should be enabled (as a comma-separated list). E.g. SSLv3,TLSv1,TLSv1.1,TLSv1.2 If this field is blank, the SSL Protocol (above) determines the Protocols that are enabled. |
Datasource Instance Details
This section has a toolbar with standard buttons.
The grid contains a list of HTTP datasource instances that belong to this HTTP datasource. Each datasource defines the connection details to an HTTP target. A number of instances can be defined to allow for several connections under a single HTTP datasource. You must define at least one HTTP datasource Instance for each HTTP datasource.
Double-click on a row to open the HTTP datasource instance properties.
To add a HTTP datasource to the list, click
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|
To remove a datasource instance from the grid, use the toolbar button
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|
Secret Key Details
This section has a toolbar with standard buttons.
The grid contains a list of the secret keys available to this datasource. A secret key is a way to securely store datasource authentication values; see Secret Key and Local Secret. To use the secure values in HTTP collector or exporter expressions, refer to the secret key using:
_datasource.key
where key is the secret key name listed in this grid.
Advanced
Field | Description |
---|---|
Internal ID | Read-only. PhixFlow displays the identifier for this datasource. The PhixFlow support team may ask for this identifier during troubleshooting. |
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|
HTTP Datasource Instance
Insert excerpt | ||||||||
---|---|---|---|---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|
Basic Settings
In addition to the standard icons, the properties toolbar includes
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|
Field | Description | ||||||||
---|---|---|---|---|---|---|---|---|---|
Name | Enter the name of the HTTP datasource instance. This must be unique, although one instance may be named "Default". Typically, if a datasource has only one instance then it usually named "Default". | ||||||||
Enabled |
| ||||||||
Username | Enter a username for an account that can access the HTTP datasource instance. | ||||||||
Password | Enter the password for an account that can access the HTTP datasource instance. | ||||||||
URL | URL of the HTTP target for this instance, without the leading http:// prefix. E.g. rss.slashdot.org/Slashdot/slashdot This field is made available as the _url internal variable in the Collector or Exporter Url Expression. |
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|
Live Search | ||||||||
---|---|---|---|---|---|---|---|---|
|
Panel | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
|
Learn More
For links to all pages in this topic, see Analysis Models for Batch Processing Data.
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|