...
There is a “hard” deadline for this work to be completed: September 20, 2022. |
---|
Payments using the TCCOPS DLL
...
already disabled in the GALRO development and acceptance environments,
...
prior to any deployments to those environments with the TCCOPS API changes. This was confirmed by Elad.
I attempted to test the existing payment process on GALRO development on Friday, August 19th, 2022
See task 196794 Baseline test of behaviour of GALRO - TCOPS in Development environment.The updated code was not yet deployed to Acceptance as of August 25, 2022 and it was not possible to pay for a Mark. The result is the same as per task 196794 Baseline test of behaviour of GALRO - TCOPS in Development environment.
...
Please refer to the instructions regarding getting GALRO running locally on the main GALRO external page under "Debug project".
As a general note, the only step that appears to be required at this time is to ensure that the template is present. Refer to the section mentioned above: "Debug project".
It was also necessary to update the SourceSystemKey token entry in web.config because the existing one contained a “+” sign.
I have made this change in the web.config that is used on localhost and this has been merged into the GALRO repos.
...
When an error occurs in TCCOPS you will see an error such as “Moose”, “Eagle”, etc.
These codes are
only documented within the TCCOPS
repos.
TCCOPS is not a CIVIL aviation applications. For assistance resolving TCCOPS error codes, please reach out to Elad Shalom)/TCCOPS team.
For
contact information about the
Developer testing:
The relevant database info is found in CCARCS (a key table seems to be is authorization)
CARS/CCARCSD.World.
see task 196806 Developer testing of GALRO where I have outlined some recommendations for the testing.
...
Publishing / Deploying
Please see the publish project section on the External GALRO page and the following tasks:
Development: 196808 Deploy to Develpment
Acceptance: 196185 198185 Deploy to acceptance...
The web config
It was necessary to update SourceSystem Key value on localhost, dev and acceptance. I expect it will also have to be done on Acceptance. Please refer to the following tasks:
Localhost: 198139: webconfig - update the SourceSystemKey entry on local host
Development: 198142: webconfig - verify / update the SourceSystemKey entry on development - and update DateAppLastModified date
Acceptance: 198144 webconfig - verify / update the SourceSystemKey entry on acceptance - and update DateAppLastModified date
Production: 196345 198145 webconfig - verify / update the SourceSystemKey entry on prod - and update DateAppLastModified date
...