Running the Application
Command Line Arguments
| Flag | Description | Required | Default |
|---|---|---|---|
-c,--conf <CONFIGURATION> | Path to the configuration file | Yes | pof-network-extractor.conf |
-d,--date <DATE> | Allows to network model to be written to a specific dates file | No | Today |
--detailed-stats-log | Used to show detailed messages for each warning collected in the summary output | No | false |
-df,--disable-fixes | Used to disable network fixes. This should be used when extracting an imported GEO world | No | false |
-f,--force-data-overwrite | Forces an overwrite if an existing extract database exists | No | false |
-h,--help | Show the help | ||
-i,--instance <instance> | Oracle database instance holding the PoF database | Yes | nms |
-p,--port <port> | The port number of the server running the PoF Oracle database | Yes | 1521 |
-s,--server <SERVER> | Server running the PoF Oracle database | Yes | localhost |
-usn, --use-service-name | Oracle database instance holding the PoF database | Yes | nms |
To run the tool, execute one of the following command at a terminal:
-
using an SID:
java -Xmx<heap size> -Xms<heap size> -jar <path to pof-network-extractor jar> -c <path to config file> -s <PoF Oracle server> -i <PoF Oracle SID> -
using a service name:
java -Xmx<heap size> -Xms<heap size> -jar <path to pof-network-extractor jar> -c <path to config file> -s <PoF Oracle server> --usn -i <PoF Oracle service name>
where:
- heap size is the desired size of the heap. E.g. 16g
Heap Size Estimation
PoF system with 2.5 million components requires around 10GB
The LV Mapping data requires around 2GB
Together with the process overhead, the recommended heap size is 16GB