OIC Gen2 to Gen 3 Upgrade - Key things to be followed

Recently I had worked on OIC Gen2 to Gen 3 Upgrade. Below is the impact analysis by executing OIC Gen2 to OIC3 upgrade for one of the non-prod instance as pilot work.

Below are the few notes from upgrade experience.

  1. Upgrade Issues encountered
    1. Post OIC3 upgrade, the OIC Gen2 activity stream will not be available, unless the activity stream is redirected to OCI object storage.
    1. Instance ID is String (alphanumeric) in OIC3 but data type is Integer in OIC Gen2 - This has huge impact on almost all the integrations as we heavily persisted the instance ID for E2Etracking purpose as part of the orchestration.
    2. OIC3 File Sever IP changed. OIC3 SFTP connections needs to be updated. Also if any of the participating application is doing any IP whitelisting, new OIC3 IP has to be added.
    3. OIC3 doesn’t support the Basic Authentication for any of the OOTB OIC REST API (Connections, Integrations etc). The same API invoked using Basic Authentication in OIC Gen2.
    4. When the OIC service needs to be invoked via Adapter - REST/SOAP, the endpoint should have Runtime Host / URL
    5. In Gen2, default data retention at domain level is 3 days. In OIC3, data retention is at integration level and during the activation need to select the one of the below option
      1. Production : 32 days
      2. Audit : 8 days
      3. Debug : 24 hours 
  1. Upgrade Observations

    1. OCI function - In Gen2, API Gateway needs to be setup in order to expose OCI function as REST API to external world (OIC). In OIC3, OCI function can be directly invoked using OCI function activity.
    2. OIC3 Uses the Oracle Redwood Theme (look & feel)
    3. OIC3 Design time URL and Run time URL are different
    4. Connection can be created from integration development canvas
    5. Menu item 'Integration' changed to 'Design'
    6. Menu item 'Monitoring' changed to 'Observability'
    7. Menu item 'Tracking' changed to 'Instances'
    8. Cut and past the activity added in OIC3
    9. OIC3 doesn't have backward compatibility
    10. Parallel activity added in OIC2. currently in Gen2, parallel activity handled using 'foreach' activity
    11. In OIC2, Read File Segment operation reads only 200 records per read and the value cannot be modified. However in OIC3, Chunk Read size is allowed to modify. The minimum value is 200 and maximum value is 2000 records per read.

Comments

  1. TechieTom: This is such a comprehensive breakdown of the upgrade process. The change in instance ID data type from Integer to String in OIC3 is definitely a significant challenge—thanks for calling that out!
    SEO Company in Delhi
    Invest in Brands

    ReplyDelete
  2. CloudGuru: Great insights! The IP changes and the need to update SFTP connections in OIC3 are crucial to avoid connectivity issues. Definitely something to keep in mind for any future migrations.
    SEO Company in India
    Franchise

    ReplyDelete
  3. DevOpsNinja: The change in how data retention is handled in OIC3 is something we’ll need to account for. The shift to integration-level retention is a big change compared to the domain-level setting in OIC Gen2.
    SEO Services
    Franchise Opportunities

    ReplyDelete
  4. DataEngineerDave: The new Chunk Read size functionality in OIC3 is a game-changer for integrations that deal with large datasets. It’s good to know that the maximum size is increased to 2000 records per read.
    SEO Company
    Franchise Business

    ReplyDelete
  5. IntegrationWizard: I agree with the observation on backward compatibility. The fact that OIC3 doesn't support backward compatibility means any legacy integrations will require significant rework.
    SEO Agency in Delhi
    Business Opportunities

    ReplyDelete
  6. CloudAdminJon: Thanks for highlighting the removal of Basic Authentication for REST APIs in OIC3. This is a critical change for anyone using older API integrations, and we’ll need to implement a more secure authentication method.
    SEO Agency in India
    Distributorship

    ReplyDelete
  7. E2ETracker: The shift from the activity stream in OIC Gen2 to the need for redirecting it to OCI object storage is something that could catch many people off guard. It’s great to see it addressed here.
    kwality walls franchise
    is movierulz safe

    ReplyDelete
  8. SFTPAdmin: The note about the File Server IP change in OIC3 is an important one. If any systems are set up with IP whitelisting, this will definitely cause connectivity issues unless updated promptly.
    yellow chilli franchise
    h&m franchise

    ReplyDelete
  9. APIExpert: Great catch on how OIC3 uses the Oracle Redwood Theme. It’s a subtle change but has a big impact on the user experience and the overall look and feel of the platform.
    caratlane franchise
    apollo franchise

    ReplyDelete
  10. CloudTechie: The fact that OIC3 no longer requires an API Gateway to expose OCI Functions is a huge simplification. It's nice to see that this process is now more streamlined.
    vishal mega mart franchise
    Rajesh Masala Distributorship

    ReplyDelete
  11. JavaDevJill: It’s useful to see the changes in OIC3 around UI and menu names—switching from ‘Integration’ to ‘Design’ and ‘Monitoring’ to ‘Observability’ is definitely something to note for teams getting familiar with the new platform.
    top 10 courier franchise in india
    haldiram distributorship

    ReplyDelete
  12. OracleIntegrationPro: The ability to create connections directly from the integration development canvas in OIC3 is definitely a positive change. It should speed up the integration process significantly.
    cult fit franchise
    Chai Point Franchise

    ReplyDelete
  13. SystemArchitectSam: The need to manually select data retention options during activation in OIC3 is a slight inconvenience, but it’s a necessary customization that will help tailor the platform to specific needs.
    sagar ratna franchise
    first cry franchise

    ReplyDelete
  14. APIConsumerChris: The switch in OIC3 to require Runtime Host/URL for Adapter REST/SOAP endpoints is important for those handling external APIs. A slight change, but it’s worth noting for the migration process.
    franchise dealership
    vivo dealership

    ReplyDelete
  15. LegacyIntegrationDev: The lack of backward compatibility in OIC3 could be a major pain point for legacy systems. Migration needs careful planning to ensure all integrations are transitioned smoothly.
    franchise apply
    tvs dealership






    ReplyDelete
  16. After upgrading to OIC3, the activity stream needs to be redirected to OCI Object Storage. Failing to do so could disrupt tracking and monitoring.
    KFC Franchise
    Pallet rack

    ReplyDelete
  17. The change from an integer to a string for Instance ID in OIC3 impacts integrations heavily, especially those relying on end-to-end tracking.
    Heavy duty racks in Delhi
    Industrial locker in Noida

    ReplyDelete
  18. With OIC3, the file server IP has changed. Be sure to update all SFTP connections to avoid disruptions in data flow.
    Mobile compactor in Delhi
    Cyclone Dust Collector Manufacturer

    ReplyDelete
  19. OIC3 no longer supports basic authentication for OOTB REST APIs, which requires reconfiguration of authentication protocols for integrations.
    Shrink Packaging Machine in Delhi
    Laser engraving machine in Delhi

    ReplyDelete
  20. OIC3 makes it easier to invoke OCI functions directly without needing the API Gateway, simplifying integration with external systems.
    Mio Amore Franchise
    Industrial Storage Rack

    ReplyDelete
  21. OIC3 introduces the Oracle Redwood theme, and some menu items have changed, such as ‘Tracking’ to ‘Instances,’ and ‘Monitoring’ to ‘Observability.’
    Cantilever Racks in Delhi
    Staff Locker in Delhi

    ReplyDelete
  22. In OIC3, parallel activities are no longer handled by the ‘foreach’ activity but are now simplified in the platform, ensuring smoother workflow management.
    File Compactor Storage System
    Centrifugal Blower

    ReplyDelete
  23. OIC3 introduces the ability to adjust the chunk read size from 200 to 2000 records, offering better control over data reading for file operations.
    Shrink Wrap Machine
    Laser Cutting Machine in Delhi

    ReplyDelete

Post a Comment

Popular posts from this blog

OSB actions in proxy service

Difference between Route, Service Callout, Publish

XQuery functions that supported by OSB