Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Next »

An HTTP Datasource defines a web site, a web service or some other target that allows XML, HTTP or text data to be collected from it, or exported to it, over HTTP. Data is collected from an HTTP Datasource using an HTTP Collector, and exported to an HTTP Datasource using an HTTP Exporter.

For information about the properties toolbar, and about the sections Parent Details, Analysis Models, Description and Audit Summary, see Common Properties.  We recommend you always add a Description that explains the purpose of the item you are creating. 

For a full list of all the PhixFlow property tabs and windows, see Properties, Windows, Menus and Toolbars.

FieldDescription
NameEnter the name of the HTTP Datasource.
Enabled Tick when the configuration is complete and the HTTP datasource is ready to be used.
Protect during import

 Untick to allow this HTTP datasource to be updated or deleted by during import.

 Tick to retain these property settings if this HTTP datasource is imported from another PhixFlow instance.

 More ...

When you have several instances of PhixFlow, for example development and production instances, you may want some item properties to be different for each instance. Usually, when you export from a source instance, then import to a target instance, PhixFlow overwrites item properties with those from the source instance. In the target instance, tick this box to prevent the current setting being overwritten by the source item.

Connection TypeSelect:
  • http: the data will be transferred using standard HTTP (not encrypted).
  • https: the data will be transferred using HTTPS, a secure form of HTTP (encrypted).
The following properties are available when Connection Type is https
Check Certificate

 Tick to validate the web site's security 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

If you are not familiar with SSL Protocol settings, leave this field blank.

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

If you are not familiar with SSL Protocol settings, leave this field blank.

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

HTTP Datasource Instances define the connection details to an HTTP target. A number of instances can be defined to allow for several connections under a single HTTP Datasource. At least one HTTP Datasource Instance must be defined for each HTTP Datasource.

NameEnter 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".
UsernameEnter a username for an account that can access the HTTP datasource instance.
PasswordEnter 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.



  • No labels