...
- Create a new model called Process Daily Signup Files
- Add a File Collector with Name Read CustSignUp Files
- Double-click on your new File Collector to open the configuration form.
- In the Details tab:
- Tick the Enabled flag
- Leave the Number of Header Lines as 1
- Leave the flag Allow Non-Scheduled Collector ticked
In the field Input Directory Expr. enter the value: "CustomerSignUps/input"
When setting up automated file collection, the directory is relative to the system-wide default input path set for CenterView. To see this:
- Go to
- Admin menu (top right-hand corner of the application) - Select System Configuration
- Go to the System Directories tab
Note the entry Import File Location – the input directory you entered in your file collector gives the input directory for the files relative to this starting location|
In file collectors, when entering Input Directory Expr, File Pattern Expression, Archive Directory Expression or Error Directory Expression - you must surround a fixed text value with quotes. E.g. "file.txt"
When entering Input Directory Expr, Archive Directory Expression or Error Directory Expression you must make directory separators forward slashes
(/), even when you are on a windows platform. E.g. "input/dataFiles"- In the field File Pattern Expression enter the value: ".*"
- Press
- Apply at the top of the File Collector form
- Move to the File Columns tab
- Press
- Create the file attributes automatically from the header row in the file - CenterView will read the file and work out the attributes that make up the file. You will see these attributes appear in the Attributes list
- Press
- In the banner of the File Collector details form, press
- Create a new Stream using the File Collector attributes - Have a look the attributes in the new stream – you can see that these have been derived from the columns in the file collector
- Save all your changes
...
- Go to Admin and open System Configuration
- Set the Effective Date field to 23/03/2009
If you wait for a while you will see the Effective Date appear in the bottom left hand of your application – however, you don't need to wait for this; the change will be applied right away
System Date Override (Effective Date) can be useful on development and testing installations of CenterView – but should never been used on a production system!
- Run ReadCustSignUpFiles
...
- Update the Effective Date to 23/03/2009 and run the Stream; a Stream Set of 6 records will be loaded – for the period 01/01/2000 (the start date of the Stream) – 23/03/2009
- Update the Effective Date to 24/03/2009 and run the Stream again; another Stream Set of 6 records will be loaded – this time for the period 23/03/2009 - 24/03/2009
Update the Effective Date to 25/03/2009 and run the Stream again; a third Stream Set will be loaded – this time for the period 24/03/2009 – 25/03/2009
This is an important configuration – although in this example the results are the same in exercise 2.2, in some cases you cannot guarantee that the key date of your input data will be lined up with your CenterView run (stream set) dates. Since this configuration is based on reading from the latest date of the previous read, the dates used are entirely based on the input data and not on the CenterView run dates.
Note that in practice you generally would not need to add the configuration
<= …{_toDate}…
because you would simply read everything after the previous read date – taking all the data available in the table after that point. So in the example your query would be:
select * from SOURCE_CUST_SIGNUPS
where COLLECTION_DATE > {_inputMultiplier}- Unset the Effective Date