Step 1: Before applying the patch in the LIVE environment, it’s important to discuss it with the Payroll team, Finance, and Supervisor. Based on the patch's criticality, we need to decide the most suitable date for the upgrade.
For critical patches(if a patch fixes the major bug, or more enhancement features or before this patch update is made in the backend, like .Net version upgrades, repository key changes, or IP address replacements), it’s generally recommended to schedule the upgrade on a Friday after hours or over the weekend. This ensures that if any system issues arise after the patch, CIVICA can address them during the weekend, minimising any impact on staff productivity.
Step 2: Obtain the patch release notes from the path: \\cobauthapp\client
Step 3: Request the Records team to create a folder in CM10 under Content Manager. Save the specific patch files in this folder for everyone to access, like below.
Step 4: Afterward, we need to send a notification to all staff at least 48 hours in advance, informing them of the patch update, including the date, time, and details. On the day of the patch, we must notify staff to log out before the upgrade begins. After the patch is completed, staff should restart their systems to ensure they connect to the new system. Please find the email attached for reference
AUTHORITY OUTAGE NOTIFICATION | |
Patch Upgrading: |
Authority LIVE Environment |
Current Version: |
7.1.42.1 |
New Version: |
7.1.43 |
|
Authority Outage Date: Timing: |
4 April 2025 |
Action Required | |
Pre-Patch Upgrade: |
The Authority system will be unavailable from 8:00 PM to 1:00 AM on 4 April 2025. Please ensure you log out before the outage begins. |
Post-Patch Upgrade: |
After the patch upgrade, please restart your computer to ensure a new network connection. |
Required Support | |
|
If you need assistance, have any questions regarding this patching process, or encounter any issues during this period:
Thank you for your cooperation. | |
Step 5: After business hours, before starting the patch upgrade, take snapshots of all three servers as outlined below. This will help in case a server needs to be restored. Depending on the situation, additional database backups may also be required before the new patch upgrade in the LIVE environment.
COBAUTHAPP
COBAUTHAPI
COBUAUTHSQL
Step 6: You will need to manually disable the antivirus on the APP, API, and SQL servers. This will help to reduce the patch upgrade process time.
From the right-hand side of the task bar of each server, APP, API and SQL, click the "S" like below
Below screen will appear and then from setting option
Disabled everything like below:
----------------------------------------------------------------------------------------------------------------------------------------------
Live patch upgrade Procedure:
-> LIVE Environment We have login COBAUTHAPP and COBAUTHAPI servers using Username: Authtech and Password: In the Keypass tool.
(LIVE and Non-Productive(TEST, TRAIN and DEMO) Environments Repository and modules all are different. We need to be careful when running the command in LIVE.
- First Login COBAUTHAPP, Open the command prompt from the desktop
: Run the command “artman -version”
It will show what version is installed in the LIVE Environment and the latest CIVICA version.
2. Run the command “update_auth_repo”, It will update/download the latest version from the CIVICA cloud into the Moira Local repository.
3. Once completed, we have to stop the server using the command “wasservice -stop live”. It will stop the COBAUTHAPP server.
4. COBAUTHAPI: To Stop services in the LIVE environment before we upgrade the new patch.
5. Once logged in to the COBAUTHAPI, Open the “IIS Manager” from the task bar, Stop the “CIVICA Authority Task Service (Instance Live)”. The below example is Stopped the LIVE environment service.
6. Open the Service (Local) from the taskbar -> Application pools-> Select the LIVE environment upgrading example “LIVE”-> Stope services for all LIVE in Application pools.
Once you stop services like below, It will show particular services Stopped.
Finally, we stopped the LIVE environment “Service unavailable” until we started the servers again.
7. Now upgrading process, Run the command “upgrade_authority” and “yes” It will upgrade the latest version in a LIVE environment. (It will take 3- 4 hours for upgrading process, sometime its take longer depends on patches).
7. Initial stage CIVICA will do all prechecks for each module and directory. If everything is successful, it will ask “commence the upgrade type “y”, if we type “y” and enter, it will start upgrading. It will take 3-4 hours for upgrading.
8. Before upgrading CIVICA will do all prechecks for each module and directory. If everything is successful, it will ask “commence the upgrade type “y”, if we type “y” and enter, it will start upgrading. It will take 3-4 hours for upgrading.
Note: After Patch P40, we are encountering a new JSON error during the upgrade to the latest patch.
Sometimes JSON updates successfully, but sometimes it comes with an error, so the pre-check is completed with an error.
This time need to run the bash command: "gen_master_Json -u" It will fix the JSON error
After again continue running with "upgrade_authority"
9. We can monitor each Directory for I-service and E-services upgrading below:
Then it will upgrade each module of LIVE environment
10. We have to monitor every few minutes. If any server log error occurs, from directory: \\cobauthapp\d$\IBM\WebSphere\AppServer\profiles\live\logs\server1
we need to log a ticket to the CIVICA service desk.
(or)
Copy the server log error from the below D drive on a particular date for patch upgrading, except the file has more memory.
11. Below you can see the Patch upgrade Live successfully:
12. Once the upgrading is completed the server automatically restarts by itself, If it's not we have to restart the server manually by running the command “wasservice -start live”.
Below case the server restarted by itself, we no need to run any command.
12. We have restarted the application pool and Service (Local) from COUBAUTHAPI:
13. Once everything is complete, try to open the LIVE environment from the Intranet portal. Then, refresh the portal or clear the caching error.
14. Once done open the LIVE environment and make sure its current version is upgraded. admin access from authority -> system-> web platform.
Once everything completed successfully, from each APP, API and SQL servers, please enable the Antivirus like below:
Thanks,
Saranya...