System Profile
System Full Name | Ship Safety Bulletins - Bulletins de la sécurité des navires |
---|---|
Business Contact | Manny Bou-Mitry, Natalia Bass |
Business Owner | Manny Bou-Mitry |
Source Code Location | https://dev.azure.com/transport-canada/DSD-MARINE%20Support/_git/SSB |
Technology Assessment
Database Platform and Version | Oracle 12c |
---|---|
Development Language and Framework | ASP .NET Framework 4.7.2 VB .NET Framework 4.7.2 |
Operating System and Version | Windows Server 2016 |
Environment Access Information
ENV | UN | PW | UNC | URL | DB |
---|---|---|---|---|---|
DEV | n/a | n/a | \\wwwappsmssdev\wwwappsroot\saf-sec-sur\4\ssb-bsn | http://tcwwwtest/eng/marinesafety/bulletins-menu.htm | SSB_EXTA@TTSXD |
ACC | n/a | n/a | \\tctestmaster\wwwappsroot\Saf-Sec-Sur\4\bulletins | http://tcwwwtest/eng/marinesafety/bulletins-menu.htm | SSB_USER@TTSXA (Note from Tibo - this should be using SSB_EXTA. Pls investigate before next release) |
PROD | n/a | n/a | \\tcwwwmaster\wwwapps\Saf-Sec-Sur\4\bulletins | http://www.tc.gc.ca/eng/marinesafety/bulletins-menu.htm | SSB_USER@TTSXPP (Note from Tibo - this should be using SSB_EXTA. Pls investigate before next release) |
System Overview
Web site allowing visitors to search for Marine Security Safety Bulletins.
- Bulletins are stored in subfolders in the main web site directory (\\tcwwwmaster\wwwapps\Saf-Sec-Sur\4\bulletins). Subfolders are organized by year.
- There is no admin interface for the SSB application. Client admins have direct access to the SSB production data in order to add, edit or otherwise modify the SSB web application's data, lookup values, etc.
Good To Know
- Connection string is located in web.config file
- SSB was modified as part of the 2019-01-19 Oracle DB Migration. The previous connection string was SSB_USER@DMZ11P
- NOTE: After the migration, the app did not work. In order to get it to work, Marcin Wieczorek (Unlicensed), from the Web Technical Support Group, copied the bulletins.dll and bulletins.pdb files from ACC to Prod. The files in ACC were dated 2017-06-05 while the ones in PROD were dated 2014-02-13. This indicates that it's possible the app was not working even prior to the DB migration.
How-To and Fixes
How To Perform a Basic Test
- Perform a Search
- Click on a bulletin # (eg. "11/2018") and ensure the bulletin comes up
- Click on View Archive Results
Request timeout when attempting a bulletin search
Problem:
Attempting to perform a search on the SSB production web site results in a timeout error message. This functionality was working back in February 2019.
Solution:
DOS 458
Unable to update replacement bulletin code
Problem:
I’m trying to modify a record in the SSB database and I’m getting the below error, I can’t even save nor delete any record.
Solution:
DOS 411
Unable to Access SSB Application (Oracle Account Locked)
Problem:
Would you know why we can’t access SSB database, getting the following error message: "ORA-28000: the account is locked"? Does it reside now on a different server, we’re connecting to the one indicated in the attached RDIMS document?
Solution:
TFS 14057
Request to insert bulletins into the SSB database
Problem:
The user has request that new bulletin information be added to the SSB database.
Solution:
Bug 34317, has details using the following SQL script:
--Transaction Log: 18 June 2020 @ 0725 --insert into ssb.bm001_bulletin Rows affected: 1 --SQL: DECLARE str_v_bulletin_cd VARCHAR2(10) := '16/2020'; str_v_bulletin_title_enm VARCHAR2(255) := 'Hazards and Risks of Girding During Towing Operations'; -- update this value str_v_bulletin_title_fnm VARCHAR2(255) := 'Dangers et risques liés à l`engagement pendant les opérations de remorquage'; -- update this value str_v_replacement_bulletin_cd VARCHAR2(10) := null; -- update this value dte_v_date DATE := TO_DATE('2020-06-05', 'yyyy-mm-dd'); -- update this value num_v_archived_ind NUMBER(1) := 0; -- update this value BEGIN insert into ssb.bm001_bulletin (bulletin_cd, bulletin_title_enm, bulletin_title_fnm, replacement_bulletin_cd, date_created_dte, date_last_update_dte, date_current_dte, archived_ind) values (str_v_bulletin_cd, str_v_bulletin_title_enm, str_v_bulletin_title_fnm, str_v_replacement_bulletin_cd, dte_v_date, dte_v_date, dte_v_date, num_v_archived_ind); DBMS_OUTPUT.PUT_LINE('insert into ssb.bm001_bulletin Rows affected: ' || sql%rowcount); -- 1 row --COMMIT; END;