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

Post a Comment

Popular posts from this blog

Difference between Route, Service Callout, Publish

When you are first starting with OSB it can be a little tricky to determine when to use a Route, Service Callout or a Publish node.  All three can be used to call either a Business service or a local Proxy service.  You can use the following lists to determine which will best fit your needs. Route Last node in request processing.  It can be thought of as a bridge between request pipeline processing and the response pipeline processing. You can only execute one route in your Proxy Service. Can only be created in a route node. OSB will wait for the Route call to finish before continuing to process. If you are calling a Business service  and  you specify  Best Effort  for QoS (Quality of Service), then OSB will release the thread it is holding while the business service executes. If you are calling a Business service  and  you specify  Exactly Once  or  At Least Once  for QoS, then OSB will hold onto the thread while the business service executes. If you are calling a l
Read more

OSB actions in proxy service

Image
In this post we will see about different types of actions to message flows using the Oracle Service Bus Administration Console, such as route, publish, service callout, transport headers, conditional actions, error actions, and message transformation actions. Actions are the elements of pipeline stages, error handler stages, route nodes, and branch nodes that define how messages are to be defined as they flow through a pipeline            Action                           Description                     Dynamic Publish Publish a message to a service identified by an XQuery expression                          Publish Publish a message to a statically specified service.                        Publish Table Publish a message to zero or more statically specified services. Switch-style condition logic is used to determine at run time which services will be used for the publis
Read more

XQuery functions that supported by OSB

NAMESPACES ------------------------------------------------------------------------ xml=http://www.w3.org/XML/1998/namespace fn=http://www.w3.org/2004/07/xpath-functions op=http://www.w3.org/2004/07/xpath-operators err=http://www.w3.org/2004/07/xqt-errors fn-bea=http://www.bea.com/xquery/xquery-functions op-bea=http://www.bea.com/xquery/xquery-operators dt-bea=http://www.bea.com/xquery/xquery-datatypes var-bea=http://www.bea.com/xquery/xquery-variables xf-aug02=http://www.w3.org/2002/08/xquery-function op-aug02=http://www.w3.org/2002/08/xquery-operators xs=http://www.w3.org/2001/XMLSchema xsd=http://www.w3.org/2001/XMLSchema xdt=http://www.w3.org/2004/07/xpath-datatypes local=http://www.w3.org/2004/07/xquery-local-functions declare default function namespace "http://www.w3.org/2004/07/xpath-functions XQUERY FUNCTIONS ------------------------------------------------------------------------ fn:node-name($arg as node()?) as xs:QName? fn:
Read more