Justice Canada - Family Orders Data Transfer
Must be done on Tuesday & Thursday every week.
The following are required in order to be able to process the reports:
access to the folders in ncrws548 for FOAEA.
To gain provided access to this folder (normally part of Pre-Onboarding ):
log an Orion request “Request Access to a Shared Network Folder”.
request modify access to \\TC4S0A\GROUPS\AARA\AARAD\ and all subfolders.
access to the TC-FOAEA@tc.gc.ca mailbox.
to gain access log an Orion ticket for Shared (generic mailbox)
Name of Shared (generic) mailbox or its email address is DSD FOAEA / LAEOEF DGSN TC-FOAEA@tc.gc.ca
To add the FOAEA shared mailbox to your outlook, refer to Shared Mailbox Mapping Procedure from Step 6. “Add an Account”.
the account being added is TC-FOAEA@tc.gc.ca
important: in step 8, it use your email address and your password, not FOAEA credentials
Team members need additional permissions in order to be able to open the emails, see Decryption permissions - BSD - Civil Aviation - Confluence (atlassian.net)
To access to RDIMS document #8026700:
Launch the Windows DM Extension from your computer’s desktop.
Click RDIMS in the upper right hand pane of the dialog.
Select Search.
Search for 8026700.
Right click the document name (8026700).
Select Check-out. If you don’t have access, ask a team lead.
Add your changes to the end of the document.
Save and close the document.
Important: once you are finished, Right click the document. Select Check-in. Otherwise, other team members won’t be able add their updates.
If an email accidentally gets moved to an incorrect folder such as Archive, Deleted, etc., to move it back to the inbox select the one with the mailbox name on it and not “inbox”.
Inbox is your own TC outlook inbox Right click on a file you want to move, choose move to 'Other folder” , choose the FOAEA inbox
Document | RDIMS # |
---|---|
FOAEA System Information | |
FOAEA Data Transfer Log | |
Instructional Video of Processing method | Video is available at : Note: this MP4 is about 2.4GB - it works much better if you copy to C:\ before attempting playback |
Part 1 - Process outgoing files to be sent to Justice Canada (steps 2-6) - Outgoing files should have “SIL' inside file names
Part 2 - Process incoming files sent from Justice (steps 7-15) - Incoming files should have “SOL” inside file names
PART 1 - Process Outgoing
Create a FOAEA folder on your desktop, with 2 subfolders: Incoming and Outgoing.
if you already created the Incoming and Outgoing folders, make sure they are empty.
Copy the files from
\\ncrws548\scripts\CivAv\FOAEA\FOAEA\OutputMail
into your Outgoing desktop folder.Select all the files from this ‘Outgoing’ desktop folder and encrypt them (
right-click
→Entrust Encrypt Files
).Ensure that the “Encrypt the files for other …. “ check box is checked. Click
Next
.Click “Add”.
Search for
FOAEAEXC
and click through the next few steps.
The encrypted files have the extension p7m.
To see file extension, enable the checkbox for “File name extensions by going to the Window Menu->View->File name extensions.
Copy the Outgoing encrypted files (extension p7m) from “Outgoing” folder
\\ncrws548\scripts\CivAv\FOAEA\FOAEA\ArchiveOut
.Don’t copy the xml files to the ArchiveOut directory.
Delete the files in
\\ncrws548\scripts\CivAv\FOAEA\FOAEA\OutputMail
after steps 3,4,5.The “OutputMail” folder should be empty.
Delete the unencrypted (extension xml) files from your Outgoing desktop folder.
Send each outgoing encrypted file from Outgoing desktop folder in a separate email to both
FOAEAEXC@justice.gc.ca and Flas-it-SO@justice.gc.ca
.If there are two encrypted files, there must be two separate emails.
Example:
From:
dsd-foaea-laeoef-dgsn@tc.gc.ca
To:
FOAEAEXC@justice.gc.ca; Flas-it-SO@justice.gc.ca
Subject: Name of file being sent.
Don’t forget to mark the email as Protected B.
Include your signature.
PART 2 - Process Incoming
Empty your local ‘Incoming’ desktop folder.
Open the
DSD FOAEA / LAEOEF DGSN (
TC-FOAEA@tc.gc.ca) inbox.Save the files from the new emails into your ‘Incoming’ desktop folder.
When you open the emails to move the files, the files are Decrypted automatically.
Mark the Unprocessed emails with the “Processed” Category tag in the Inbox (Click on the ‘Lock’ symbol).
If multiple emails having the same filename are received, process the first one and mark the duplicate(s) as duplicate with the “Duplicate” category tag.
Go to
\\ncrws548\scripts\CivAv\FOAEA\FOAEA\InputMail
.Delete the existing files. (only delete the files that have the same number as those you just sent by email to Justice Canada).
To prepare for the next file transfer:
copy Decrypted files from Step 9-Incoming local desktop folder into the InputMail (
\\ncrws548\scripts\CivAv\FOAEA\FOAEA\InputMail
) folder.
Copy same Decrypted files from ‘Incoming’ local desktop folder to
\\ncrws548\scripts\CivAv\FOAEA\FOAEA\ArchiveIn
.Retrieve the RDIMS document 8026700, as explained at the beginning of this document.
Add the following updates :
Date.
Sequence number (previous number incremented by 1).
the incoming and outgoing files you processed.
your initials.
Example
Update your task “Justice Canada-Family Order.” with the above information from the RDIMS by copying the whole row from RDIMS, paste into the task’s discussion box:
notify the team leader, and product owner.
mark the task “Done”.
Don’t' forget to check the document back into RDIMS once you have finished editing it.
There should not be a red-check mark next to the name of the document in the Windows Explorer DM Extension and it should not show “checked out”. The status can be verified by right clicking the document and selecting “History”.
The process ends here. The following steps are for verification/debugging errors:
Files in \\ncrws548\scripts\CivAv\FOAEA\FOAEA\OutputMail
get uploaded to ACES and DAPLS at 1 AM.
Only 2 files in \\ncrws548\scripts\CivAv\FOAEA\FOAEA\InputMail
can be processed each night. →
Need to find out what program is processing these files.
\\ncrws548\scripts\CivAv\FOAEA\FOAEA\FOAEA.EXE ?
To check log files:
\\ncrws548\scripts\CivAv\FOAEA\FOAEA\FoaeaLog
Verify that the files added have “Database download successful” message.
\\ncrws548\scripts\CivAv\FOAEA\FOAEADownload\Log
Verify that connection to DAPLS and ACES was successful.
SKIPPED files
Details in PBI #195723 - August 2022
In this instance, 2 output files at (\\ncrws548\scripts\CivAv\FOAEA\FOAEA\OutputMail) produced by the overnight job, were destroyed during the encryption process. (*SIL* files)
TC3SLSIL.007087.XML
TC3SLSIL.007088.XML
However we did still have the input files (*SOL* files) both in the email bucket and on the server at (\\ncrws548\scripts\CivAv\FOAEA\FOAEA\ArchiveIn)
As these files are numbered sequentially and subsequent files had been processed and forwarded to Justice afterward.
This posed an issue in terms of finding a way to get the database to re-process files having a lower cycle number.
The following unsuccessful attempts were made to correct this issue :
Altering the MDB files in the “database” directory (as per the directions in the System Information guide 8018693), to remove references to the skipped files, thus hopefully, rolling the cycle counter backward.
Pasting the XML data from the input files into 2 newer input files with higher cycle numbers. Analysis of the output showed that the data that had been “pasted in” was ignored.
The solution agreed upon was to ask Justice if they could do the following (Eric Gardner was their IT contact - all emails can be found in the PBI)
Have their database ignore cycles 7087 & 7088
Reprocess that data into new files - cycles 7101 & 7102
Have those new files process as part of our normal sequencing
RECOMMENDATION
The procedure should be supplemented to add a new directory called OutputMail-Backup.
All of the decrypted SIL files should be copied to both OutputMail and OutputMail-Backup ( either by the overnight procedure - or - manually the next morning ) before any attempt is made to encrypt the new files for emailing to Justice.
In this way we would ensure that a copy of all SIL files are retained in event of an accident during encryption.