...
- Please indicate the cartridge type (in all cases it will be: cartridge=wfs),
- In data source="" (WFS address in quotes) we need to provide the URL to the chosen WFS service:
* Please remember to never specify the "request" and "typeName" parameters in the URL. Data Pump needs to set them explicitly and it won't be able to do this if they are already provided in URL,
* If there is no VERSION parameter provided in URL, then DataPump will set it automatically to 2.0.0,
* Because the script file is parsed into XML, it is crucial to replace the “&” with “&” otherwise the import operation will fail. - Finally, we need to specify the table name="" parameter:
* In this case, please leave the parameter empty in order to list all tables held by the WFS service.
| Info | ||
|---|---|---|
| ||
Please remember that only the script file is parsed into XML. Therefore when you are using the 3 file scenario (.script, .destination, .source), then the .source file shouldn’t have escaped & inside of it (leave the “&” as they were original). |
Destination
We need to provide a path to the location where the CSV file will be created with a list of all tables held by the WFS service (used only in conjunction with empty table name=""parameter from <source>)
...
- Please indicate the cartridge type (in all cases it will be: cartridge=wfs),
- In data source="" (WFS address in quotes) we need to provide the URL to the chosen WFS service:
* Please remember to never specify the "request" and "typeName" parameters in the URL. Data Pump needs to set them explicitly and it won't be able to do this if they are already provided in URL,
* If there is no VERSION parameter provided in URL, then DataPump will set it automatically to 2.0.0,
* Because the script file is parsed into XML, it is crucial to replace the “&” with “&” otherwise the import operation will fail. - Finally, we need to specify the table name="" parameter:
* In this case, please leave the parameter empty in order to list all tables held by the WFS service.
| Info | title | Important
|---|
Please remember that only the script file is parsed into XML. Therefore when you are using the 3 file scenario (.script, .destination, .source), then the .source file shouldn’t have escaped & inside of it (leave the “&” as they were original). |
Destination
- The connection string to the database syntax is same as for the typical import scripts. In this case, the name under which data will be held in the database needs to be provided in table nameparameter (e.g.: table name=areas_of_onb_inspire), as part of the entire connection string.
...