Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 41 Next »

Must be done on Tuesday & Thursday every week.

The following are required in order to be able to process the reports:

  1. access to the folders in ncrws548 for FOAEA.

    1. To gain provided access to this folder (normally part of Pre-Onboarding ) you can log an Orion request “Request Access to a Shared Network Folder”.

      1. request modify access to \\TC4S0A\GROUPS\AARA\AARAD\ and all subfolders.

  2. access to the TC-FOAEA@tc.gc.ca mailbox.

    1. to gain access log an Orion ticket for Shared (generic mailbox)

      1. Name of Shared (generic) mailbox or its email address is DSD FOAEA / LAEOEF DGSN TC-FOAEA@tc.gc.ca

    2. To add the FOAEA shared mailbox to your outlook, refer to Shared Mailbox Mapping Procedure from Step 6. “Add an Account”.

      1. the account being added is TC-FOAEA@tc.gc.ca

      2. important re the instructions for the account to connect with (per step 8, it uses your email address and your password, not FOAEA credentials)

  3. Additional permissions are required on the account in order to be able to open the emails, see Decryption permissions - BSD - Civil Aviation - Confluence (atlassian.net)

  4. Access to RDIMS document #8026700 - if you don’t have access, ask a team lead.

    If there 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 .

    The correct inbox name to select is shown below.

Document

RDIMS #

FOAEA System Information

8018693

FOAEA Data Transfer Log

8026700

Instructional Video of Processing method

Video is available at :
\\Tc4s0a\groups\AARA\AARAD\FOAEA
20210603_110633.mp4

Note: this MP4 is about 2.4GB - it works much better if you copy to C:\ before attempting playback
A smaller (low res) version is available here as well :
20210603_FOAEA_SMALL.mp4

Part 1 - Process outgoing files to be sent to Justice Canada (steps 2-6)
Part 2 - Process incoming files sent from Justice (steps 7-14)

PART 1 - Process Outgoing

  1. Create a FOAEA folder on your desktop, with 2 subfolders: Incoming and Outgoing.

  2. Go to \\ncrws548\scripts\CivAv\FOAEA\FOAEA\OutputMail.

  3. Move the files into your Outgoing desktop folder.

  4. Select all the files and encrypt them (right-click → Encrypt Entrust Files).

    1. Ensure that the box is checked off. Click Next.

    2. Click Add.

    3. Search for FOAEAEXC and click through the next few steps.

  5. Copy Outgoing encrypted files into \\ncrws548\scripts\CivAv\FOAEA\FOAEA\ArchiveOut and delete the unencrypted files.

  6. Delete the files in \\ncrws548\scripts\CivAv\FOAEA\FOAEA\OutputMail after archiving files in step 5

  7. Send each outgoing encrypted file in a separate email to both FOAEAEXC@justice.gc.ca and Flas-it-SO@justice.gc.ca. Mark it as Protected B. For ex, if there are two encrypted files, there must be two separated emails

    • Subject: Name of file

    • Include your signature

    • PART 2 - Process Incoming

  8. Open the DSD FOAEA / LAEOEF DGSN (TC-FOAEA@tc.gc.ca) inbox, save the files from the new emails into your Incoming desktop folder & mark the emails with the “Processed” category tag.

  9. Select all the files and decrypt them (Right-click → Decrypt & Verify).

  10. Go to \\ncrws548\scripts\CivAv\FOAEA\FOAEA\InputMail.

  11. Delete the existing files in here (only delete the files that have the same number as those you just sent by email).

  12. Move decrypted files into the InputMail folder.

  13. Move encrypted files from Incoming desktop folder to \\ncrws548\scripts\CivAv\FOAEA\FOAEA\ArchiveIn.

  14. Update the log file (RDIMS #8026700), for example entering this information

  15. Update your task “Justice Canada-Family Order..” with the above information from the RDIMS

  16. Permanently delete the files from your local folders. (or else you can make a backup for later trouble shoot if there is any error)

The process ends here. The later steps 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\InputMailcan 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:

  1. \\ncrws548\scripts\CivAv\FOAEA\FOAEA\FoaeaLog

    • Verify that the files added have “Database download successful” message.

  2. \\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.

  • No labels