Difference between revisions of "Finished"
Jump to navigation
Jump to search
| (7 intermediate revisions by 2 users not shown) | |||
| Line 11: | Line 11: | ||
|- | |- | ||
| Message Queue | | Message Queue | ||
| − | | <code> | + | | style="text-align:center;" | <code>finished</code> |
|} | |} | ||
| Line 17: | Line 17: | ||
It performs the following tasks: | It performs the following tasks: | ||
| − | * Updating <code>[File]</code> table records to populate <code>[NumberOfChildren]</code> and <code>[FullPathID]</code> columns | + | * Updating <code><nowiki>[</nowiki>[[File Table|File]]<nowiki>]</nowiki></code> table records to populate <code>[NumberOfChildren]</code> and <code>[FullPathID]</code> columns |
| − | * Record final load data in the <code>[Statistics]</code> table | + | * Record final load data in the <code><nowiki>[</nowiki>[[Statistics Table|Statistics]]<nowiki>]</nowiki></code> table |
* Generate the [[Type_Load_Log|Load Log]] | * Generate the [[Type_Load_Log|Load Log]] | ||
* Update the <code>[MD5Hash]</code> table with a unique list of hashes | * Update the <code>[MD5Hash]</code> table with a unique list of hashes | ||
| + | |||
| + | =Automatic Backup= | ||
| + | You can have a backup made of the freshly loaded media by adding the following to your configuration. | ||
| + | |||
| + | <source lang="xml"> | ||
| + | <autobackup>Yes</autobackup> | ||
| + | <backupfolder>C:\Temp\s7</backupfolder> | ||
| + | </source> | ||
| + | |||
| + | {| class="wikitable" | ||
| + | |- | ||
| + | ! Name | ||
| + | ! Data Type | ||
| + | ! Description | ||
| + | |- | ||
| + | | autobackup | ||
| + | | style="text-align:center;" | boolean | ||
| + | | When true, it generates a media export | ||
| + | |- | ||
| + | | backupfolder | ||
| + | | style="text-align:center;" | string | ||
| + | | The name of the folder to hold the backup | ||
| + | |} | ||
| + | |||
| + | The output filename will have the format of a timestamp followed by the media id. | ||
| + | For example: | ||
| + | <pre> | ||
| + | 2021-01-24-06-05-59-18229588-049F-9E2B-868B-F8841392A4AF.tpmf | ||
| + | </pre> | ||
| + | |||
| + | =Automatic Publishing= | ||
| + | You can have the freshly loaded media pushed to another instance of Truxton by adding the following to your configuration. | ||
| + | |||
| + | <source lang="xml"> | ||
| + | <autopublish>Yes</autopublish> | ||
| + | <apname>EnterpriseTruxton</apname> | ||
| + | <apserver>localhost</apserver> | ||
| + | <apport>5432</apport> | ||
| + | <apuser>postgres</apuser> | ||
| + | <appassword>Truxton4n6</appassword> | ||
| + | </source> | ||
| + | |||
| + | {| class="wikitable" | ||
| + | |- | ||
| + | ! Name | ||
| + | ! Data Type | ||
| + | ! Description | ||
| + | |- | ||
| + | | autopublish | ||
| + | | style="text-align:center;" | boolean | ||
| + | | When true, it will copy the freshly loaded media from the local server to a remote one | ||
| + | |- | ||
| + | | apname | ||
| + | | style="text-align:center;" | string | ||
| + | | The name of the database to receive the freshly loaded media | ||
| + | |- | ||
| + | | apserver | ||
| + | | style="text-align:center;" | string | ||
| + | | The name of the database server machine to receive the freshly loaded media | ||
| + | |- | ||
| + | | apport | ||
| + | | style="text-align:center;" | integer | ||
| + | | The port number the server is listening on | ||
| + | |- | ||
| + | | apuser | ||
| + | | style="text-align:center;" | string | ||
| + | | The name the account to use to log onto the database server | ||
| + | |- | ||
| + | | appassword | ||
| + | | style="text-align:center;" | string | ||
| + | | The password of the account used to log onto the database server | ||
| + | |} | ||
Latest revision as of 12:09, 24 February 2021
| Executable | Finished.exe
|
| Stage | 240 |
| Percent Complete | 94% - 100% |
| Message Queue | finished
|
The Finished ETL is responsible for completing a Truxton load. It performs the following tasks:
- Updating
[File]table records to populate[NumberOfChildren]and[FullPathID]columns - Record final load data in the
[Statistics]table - Generate the Load Log
- Update the
[MD5Hash]table with a unique list of hashes
Automatic Backup
You can have a backup made of the freshly loaded media by adding the following to your configuration.
<autobackup>Yes</autobackup>
<backupfolder>C:\Temp\s7</backupfolder>
| Name | Data Type | Description |
|---|---|---|
| autobackup | boolean | When true, it generates a media export |
| backupfolder | string | The name of the folder to hold the backup |
The output filename will have the format of a timestamp followed by the media id. For example:
2021-01-24-06-05-59-18229588-049F-9E2B-868B-F8841392A4AF.tpmf
Automatic Publishing
You can have the freshly loaded media pushed to another instance of Truxton by adding the following to your configuration.
<autopublish>Yes</autopublish>
<apname>EnterpriseTruxton</apname>
<apserver>localhost</apserver>
<apport>5432</apport>
<apuser>postgres</apuser>
<appassword>Truxton4n6</appassword>
| Name | Data Type | Description |
|---|---|---|
| autopublish | boolean | When true, it will copy the freshly loaded media from the local server to a remote one |
| apname | string | The name of the database to receive the freshly loaded media |
| apserver | string | The name of the database server machine to receive the freshly loaded media |
| apport | integer | The port number the server is listening on |
| apuser | string | The name the account to use to log onto the database server |
| appassword | string | The password of the account used to log onto the database server |
