ms_master/steps.md

IFS Deployment Steps Guide

This guide details the steps for installing a new delivery package in IFS, covering environment setup, database preparation, installation, and final cleanup.

---

I. Preparation and Access

1. Log in to VPN:
   • Log in to the IPL - VPN.
2. Log in to Management Server:
   • Log in to the Management Server (e.g., ifsapp).
3. Check Current Delivery Level:
   • Check the current delivery level from the application, specifically using the Delivery Registry.
4. Identify Target Delivery:
   • The delivery you need to install is the next available delivery.
5. Download Delivery Package:
   • Download the delivery from the build place.
6. Copy Delivery Package:
   • Copy the delivery package to the designated delivery installation directory.

---

II. Environment Configuration (Kube & Middle-Tier)

7. Source the Environment with Kube Configuration:
   • Run the following commands to configure kube:

     .\main.ps1 -resource 'GETKUBECONFIG'
     

     copy .\config\kube\config $HOME\.kube\
     

8. Verify Namespace and Pods:
   • The correct namespace is "IPLUPG".
   • Get all namespaces:

     kubectl.exe get ns
     

   • Verify running Pods in the target namespace:

     kubectl.exe get pods -n IPLUPG
     

9. Stop the Middle-Tier:
   • Stop the Middle-Tier. The namespace is "IPLUPG".
   • Command Example:

     <path to delivery installation folder>\mtctl.cmd stop -n IPLUPG
     

---

III. Database Preparation

10. Log in to Oracle Server:
    • Log in to the Oracle Linux server with the username "oracle".
    • Connect to the database:

      sqlplus / as sysdba
      

11. Source the Instance:
    • Set the Oracle environment ID:

      . oraenv
      

      OR

      set oracle_sid=<SID>
      

12. Verify Instance and PDB Status:
    • Check the status of Pluggable Databases (PDBs):

      show PDB
      

13. Check Archive Log Mode:
    • Determine if the DB is running in archive log or no archive log mode:

      archive log list
      

14. Check DB Recovery Destination:
    • Check the recovery file destination and size parameters:

      show parameter db_recovery_file_dest_size
      

      show parameter db_recovery_file_dest
      

15. Create Temporary Directory:
    • Create a directory named "TEST" in the /u02 partition:

      mkdir /u02/TEST
      

16. Configure Recovery Destination (If No Archive Log):
    • If the database is in no archive log mode, configure the destination:

      db_recovery_file_dest_size=100G
      

      db_recovery_file_dest=/u02/TEST
      

17. Set Database to Archive Log Mode:
    • Change DB to Archivelog:

      shutdown immediate
      

      startup mount
      

      alter database archivelog;
      

      alter database open;
      

    • (The "No Archivelog" commands are provided here for later reference.)
      • Change DB to No Archivelog:

      *shutdown immediate*
      *startup mount*
      *alter database noarchivelog;*
      *alter database open;*
      

18. Verify Instance and PDB Status (Post-change):
    • Re-verify the status of PDBs:

      show PDB
      

19. Configure Restore Point:
    • Create a guaranteed restore point before deployment:

      create restore point delivery guarantee flashback database;
      

    • (To drop the restore point later, use: drop restore point delivery;)

---

IV. Delivery Installation and Verification

20. Run the Delivery Database Part:
    • Execute the database installer part of the delivery:

      .\installer.cmd --set action=dbinstaller --values <Path>\ifscloud-values.yaml --values <Path>\solutionset.yaml --set dbInstaller.sysPassword=<DBPassword>
      

21. Verify the Logs:
    • Check for errors and successful completion in the logs located at:

      ifsroot\logs\ifscloudinstaller\
      

22. Run the Delivery Middle-Tier Part:
    • Execute the middle-tier installer part:

      .\installer.cmd --set action=mtinstaller --values <Path>\ifscloud-values.yaml
      

23. Verify the PODs Status:
    • Check the status of the pods to ensure the middle-tier has started successfully:

      kubectl.exe get pods -n IPLUPG
      

24. Login and Verify Delivery Level:
    • Log in to the application and verify that the new delivery level is correctly displayed.

---

V. Post-Installation Cleanup

25. Drop Restore Point (If Successful):
    • If the delivery is successful, remove the restore point:

      drop restore point delivery;
      

26. Stop Application:
    • Stop the application (if necessary).
27. Change Database to No Archivelog:
    • Revert the database to No Archivelog mode:

      shutdown immediate
      startup mount
      alter database noarchivelog;
      alter database open;
      

28. Start Application:
    • Start the application to bring the system online.