NICO - CELN

System Profile

System Full Name

NAPA Issued Certificates Online

System Full Name (French)

Certificats Émis en ligne - NAPA

Business Administrator

Greg Oucharek

Business Owner

John Deruchie

Director

Philippe Ngassam

Subject Matter Expert (Maintenance Team)

Christopher Collins

Division

National Aircraft Certification

NTARS Code

CA34

Source Location

 

Source Code Location

http://tfsprod:8080/tfs/CivAv/NICO-CELN

Migration to DevOps

New Source Code Location (DevOps)

https://dev.azure.com/transport-canada/DSD-CIVAV Support/_git/NICO-CELN

  • NOTE:

    The latest code retrieved by cloning the repos has never been deployed to production.

    At this time, we need to maintain two versions:

  • 1) version that is deployed to prod (v1.5.x):

    • After cloning NICO from the repos, create a new local branch based on the latest remote version 1.5.x version.

      • As of August 2014 version 1.5.2;

        • the next new local branch created should be named v1.5.3.

    • Commit and push your changes to your branch.

      • Don’t do a pull request.

    • Publish to dev and acc using the provided profiles.

web.config:
For the 2014 version, the web.config has to use the template shown below or the left menu won't display the acronyms properly.
On the development server:<add key="CLFVersion" value="gcwu-fegc" />

 

2) the latest version of the code in GIT:

  • Create a separate branch based on development

  • Apply the same changes - don’t overwrite the files with those from 1.5.x.

  • Follow the regular process for review and PR.

The code will run properly with the web.config retrieved from the repos.

  • NOTE:

    The latest code retrieved by cloning the repos has never been deployed to production.

    At this time, we need to maintain two versions:

  • 1) version that is deployed to prod (v1.5.x):

    • After cloning NICO from the repos, create a new local branch based on the latest remote version 1.5.x version.

      • As of August 2014 version 1.5.2;

        • the next new local branch created should be named v1.5.3.

    • Commit and push your changes to your branch.

      • Don’t do a pull request.

    • Publish to dev and acc using the provided profiles.

web.config:
For the 2014 version, the web.config has to use the template shown below or the left menu won't display the acronyms properly.
On the development server:<add key="CLFVersion" value="gcwu-fegc" />

 

2) the latest version of the code in GIT:

  • Create a separate branch based on development

  • Apply the same changes - don’t overwrite the files with those from 1.5.x.

  • Follow the regular process for review and PR.

The code will run properly with the web.config retrieved from the repos.

 

 

Technology Assessment

Platform Type

Web (External)

Database Platform and Version

Oracle 18C

Development Language and Framework

ASP.NET

Operating System and Version

Windows Server 2016

Additional Dependencies

 

Authentication

 

Environment Access Information

ENV

UNC

WWWFILES

URL

DB

ENV

UNC

WWWFILES

URL

DB

DEV

\\ncrws499\cawwwappsx\saf-sec-sur\2\NICO-CELN

 

http://cawwwappsx/saf-sec-sur/2/nico-celn/c_s.aspx

NNDEV

PREACC

 

 

 

NNPROJ

ACC

\\tctestmaster\wwwappsroot\saf-sec-sur\2\nico-celn

 

https://wwwappstest.tc.gc.ca/saf-sec-sur/2/nico-celn/c_s.aspx

NNCLNT

PROD

 

 

https://wwwapps.tc.gc.ca/saf-sec-sur/2/nico-celn/c_s.aspx

NNPROD

TRAINING

 

 

 

NNACEP

System Overview

NAPA Issued Certificates Online (NICO) is an internet application which allows external users to search for NAPA (National Aeronautical Product Approval) system issued certificates, and information on foreign and Canadian product approvals. This application is maintained by the Standards Branch of Transport Canada.

NICO allows the general public to query/view NAPA type certificates and approval information on-line.

Le CELN permet au grand public d'interroger/consulter la liste des certificats NAPA et d'obtenir de l'information relative à l'approbation en ligne.

Good To Know

<--->

How-To and Fixes

<Sub-sections should describe how to address known support request, including any scripts, instructions / steps, etc… >