[et_pb_section fb_built=”1″ _builder_version=”4.16″ custom_padding=”0px|0px|0px|0px” global_colors_info=”{}”][et_pb_row _builder_version=”4.16″ custom_padding=”0px|||||” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.16″ custom_padding=”|||” global_colors_info=”{}” custom_padding__hover=”|||”][et_pb_text _builder_version=”4.27.0″ custom_padding=”||5%||false|false” inline_fonts=”Roboto” global_colors_info=”{}”]<\/p>\n
Oracle Integration Cloud<\/strong> is a complete integration platform that combines robustness and agility to meet the complex challenges faced by organizations. However, even within this high-performance solution, errors can occur and compromise its potential. In this article, discover the common pitfalls to avoid and follow our advice on how to make the most of this technology.<\/span><\/p>\n [\/et_pb_text][et_pb_text _builder_version=”4.27.0″ custom_padding=”||5%||false|false” inline_fonts=”Roboto” global_colors_info=”{}”]<\/p>\n Oracle Integration Cloud<\/strong> <\/span>(OIC<\/strong>) is emerging as a complete integration platform, combining robustness and agility to meet the complex requirements of modern businesses. Despite its privileged position, it’s crucial to recognize that, even within the most powerful solutions, challenges can arise during implementation. Despite its robustness, <\/span>OIC<\/strong> <\/span>is not immune to common errors and pitfalls that can compromise its full potential during interface development. In the sections to come, we’ll take a closer look at typical mistakes to avoid when usingOracle Integration Cloud<\/strong>, while providing you with tips and best practices for overcoming these obstacles. [\/et_pb_text][et_pb_text _builder_version=”4.27.0″ custom_padding=”||||false|false” inline_fonts=”Roboto” global_colors_info=”{}”]<\/p>\n [\/et_pb_text][et_pb_text _builder_version=”4.27.0″ custom_padding=”||5%||false|false” inline_fonts=”Roboto” global_colors_info=”{}”]<\/p>\n And yes, even <\/span>integrations<\/strong> <\/span>can be talkative, and in a world where the loquacious are not always welcome, this can have serious consequences. Insofar as possible, THIS IS NOT A GOOD PRACTICE and should be avoided at all costs. Successive calls to a system can overload it, impacting its behavior and leading tointegration<\/strong> errors. To solve this problem, it’s often a good idea to maximize the data sent per call. [\/et_pb_text][et_pb_text _builder_version=”4.27.0″ custom_padding=”||||false|false” inline_fonts=”Roboto” global_colors_info=”{}”]<\/p>\n [\/et_pb_text][et_pb_text _builder_version=”4.27.0″ custom_padding=”||5%||false|false” inline_fonts=”Roboto” global_colors_info=”{}”]<\/p>\n In large ecosystems, where the volume of data to be processed<\/strong> is frequently high, and where several files need to be read, developers sometimes opt to use a loop in theintegration<\/strong> to process all the data<\/strong> per instance. However, this approach has significant repercussions. These integrations<\/strong> can run for several hours without reaching their conclusion, with implications for other integrations<\/strong> that cannot start if the queue is saturated.<\/span><\/p>\n In addition, the process may stop after a few hours due to the limitations of the ICO framework<\/strong>, notably the maximum duration of six hours for scheduled processes. To avoid this scenario, we recommend limiting the number of processes per instance,using ICO parameters<\/strong> to save the last files processed for future executions, or opting for recursiveintegration<\/strong> calls.<\/span><\/p>\n [\/et_pb_text][et_pb_text _builder_version=”4.27.0″ custom_padding=”||||false|false” inline_fonts=”Roboto” global_colors_info=”{}”]<\/p>\n [\/et_pb_text][et_pb_text _builder_version=”4.27.0″ inline_fonts=”Roboto” global_colors_info=”{}”]<\/p>\n The <\/span>synchronous integrations<\/strong> <\/span>are designed to provide an immediate response when invoked. The key to overcoming this constraint lies in a precise understanding of needs and a <\/span>integration modeling<\/strong>. [\/et_pb_text][et_pb_image src=”https:\/\/www.sqorus.com\/wp-content\/uploads\/2024\/08\/OIC-integration-app-driven-chargee-1.png” title_text=”OIC-integration-app-driven-chargee-1″ _builder_version=”4.27.0″ _module_preset=”default” custom_padding=”||||false|false” global_colors_info=”{}”][\/et_pb_image][et_pb_text _builder_version=”4.27.0″ custom_padding=”||5%||false|false” inline_fonts=”Roboto” global_colors_info=”{}”]<\/p>\n Example of an app-driven integration that’s a little too busy.<\/em><\/p>\n [\/et_pb_text][et_pb_text _builder_version=”4.27.0″ custom_padding=”||||false|false” inline_fonts=”Roboto” global_colors_info=”{}”]<\/p>\n [\/et_pb_text][et_pb_text _builder_version=”4.27.0″ inline_fonts=”Roboto” global_colors_info=”{}”]<\/p>\n In projects involving several team members, the risk of creating several connectors pointing to the same system with the same identifiers is high. To remedy this situation, it’s simply necessary to set up clear nomenclature rules, shared between the different teams, and to establish a verification process prior to the creation of a new connector. This ensures more efficient connector management.<\/span><\/p>\n [\/et_pb_text][et_pb_image src=”https:\/\/www.sqorus.com\/wp-content\/uploads\/2024\/08\/OIC-regles-de-nomenclature-claires-1.png” title_text=”ICO-nomenclature-rule-clauses-1″ _builder_version=”4.27.0″ _module_preset=”default” custom_padding=”||5%||false|false” global_colors_info=”{}”][\/et_pb_image][et_pb_text _builder_version=”4.27.0″ custom_padding=”||||false|false” inline_fonts=”Roboto” global_colors_info=”{}”]<\/p>\n [\/et_pb_text][et_pb_text _builder_version=”4.27.0″ inline_fonts=”Roboto” global_colors_info=”{}”]<\/p>\n In Oracle Integration Cloud<\/strong>, there are two distinct approaches to reading a file: full reading or reading in chunks (chunks). The method commonly adopted by developers is sequential reading, which, although practical, can prove inefficient for large files, saturating memory by loading the entire file locally before reading it line by line. This approach enables more efficient competitive processing of files, offering greater capacity to manage large volumes of data<\/strong>.<\/span><\/p>\n<\/div>\n<\/div>\n [\/et_pb_text][et_pb_image src=”https:\/\/www.sqorus.com\/wp-content\/uploads\/2024\/08\/OIC-lire-les-fichiers-de-manieres-sequentielle.png” title_text=”OIC-read-sequential-manner-files” _builder_version=”4.27.0″ _module_preset=”default” custom_padding=”||5%||false|false” global_colors_info=”{}”][\/et_pb_image][et_pb_text _builder_version=”4.27.0″ custom_padding=”||||false|false” inline_fonts=”Roboto” global_colors_info=”{}”]<\/p>\n [\/et_pb_text][et_pb_text _builder_version=”4.27.0″ custom_padding=”||5%||false|false” inline_fonts=”Roboto” global_colors_info=”{}”]<\/p>\n In conclusion, navigating theOracle Integration Cloud<\/strong> ecosystem <\/span>requires a thorough understanding of anti-patterns and best practices in order to fully exploit the power of this <\/span>integration platform<\/strong>.<\/p>\n The key lies in a thoughtful approach to design, careful modeling of integrations, optimization of processes, and respect for good naming practices. Avoiding the pitfalls of anti-patterns guarantees robust, high-performance, scalable integration.<\/p>\n By adopting these Council guidelines, developers can confidently navigate the complex world ofICO<\/strong>, maximizing the efficiency of their integrations while avoiding common pitfalls.<\/p>\n It is essential to keep abreast of evolving best practices and to continue refining <\/span>integration strategies<\/strong> <\/span>to guarantee long-term success in the <\/span>deployment and management of Oracle Integration Cloud<\/strong>. [\/et_pb_text][\/et_pb_column][\/et_pb_row][et_pb_row custom_padding_last_edited=”on|desktop” _builder_version=”4.27.0″ background_color=”#2029a0″ background_image=”https:\/\/www.sqorus.com\/wp-content\/uploads\/2023\/12\/Bandeau-LB-Gouvernance-IT.png” background_size=”contain” background_position=”center_right” width=”100%” width_tablet=”90%” width_phone=”90%” width_last_edited=”on|phone” custom_margin=”||3%||false|true” custom_padding=”50px|400px|50px|55px|true|false” custom_padding_tablet=”50px|55px|50px|55px|true|true” custom_padding_phone=”40px|55px|40px|55px|true|true” background_last_edited=”on|phone” background_enable_image_tablet=”off” border_radii=”on|23px|23px|23px|23px” global_module=”25053″ global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.16″ custom_padding=”|||” global_colors_info=”{}” custom_padding__hover=”|||”][et_pb_text module_class=”Titre_40 Titre_blanc” _builder_version=”4.25.1″ _module_preset=”default” header_2_font_size=”30px” global_colors_info=”{}”]<\/p>\n [\/et_pb_text][et_pb_text module_class=”FondBleu” _builder_version=”4.24.3″ _module_preset=”default” text_font=”||||||||” text_text_color=”#d6d8f4″ text_line_height=”30px” global_colors_info=”{}”]<\/p>\n Discover the roles and responsibilities of key profiles, as well as best practices in governance and technological development, to ensure the success of your digital transformation projects.<\/p>\n [\/et_pb_text][et_pb_button button_url=”https:\/\/www.sqorus.com\/en\/ebook-all-about-it-project-governance\/” button_text=”Download” button_alignment=”left” button_alignment_tablet=”center” button_alignment_phone=”center” button_alignment_last_edited=”on|tablet” admin_label=”Bouton de t\u00e9l\u00e9chargement” module_class=”Bouton Fond_blanc” _builder_version=”4.27.0″ _module_preset=”default” custom_button=”on” button_text_size=”15px” button_text_color=”#f36145″ button_bg_color=”#FFFFFF” button_border_width=”1px” button_border_color=”#f36145″ button_border_radius=”50px” button_font=”||||||||” button_use_icon=”off” custom_margin=”20px||||false|false” custom_padding=”13px|25px|13px|25px|false|false” custom_css_free_form=”selector:hover{|| background-color: #FFF6F5 !important;||}” global_colors_info=”{}”][\/et_pb_button][\/et_pb_column][\/et_pb_row][\/et_pb_section][et_pb_section fb_built=”1″ _builder_version=”4.27.0″ _module_preset=”default” global_module=”38598″ global_colors_info=”{}”][et_pb_row _builder_version=”4.27.0″ _module_preset=”default” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.27.0″ _module_preset=”default” global_colors_info=”{}”][et_pb_text _builder_version=”4.27.0″ _module_preset=”default” global_colors_info=”{}”]<\/p>\n <\/p>\n [\/et_pb_text][\/et_pb_column][\/et_pb_row][\/et_pb_section][et_pb_section fb_built=”1″ admin_label=”Section – Blog – Cta Actu” module_class=”Fond_bleu Fond_icone” _builder_version=”4.27.0″ custom_margin=”5rem||5rem||true|true” custom_margin_tablet=”4rem|40px|4rem|40px|true|true” custom_margin_phone=”|20px||20px|false|true” custom_margin_last_edited=”on|phone” custom_padding=”3rem||3rem||true|false” global_colors_info=”{}”][et_pb_row make_equal=”on” admin_label=”Text block” module_class=”LargeurBox” _builder_version=”4.27.0″ _module_preset=”default” animation_style=”fade” locked=”off” collapsed=”off” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.25.0″ _module_preset=”default” custom_padding=”|9rem||9rem|false|true” custom_padding_tablet=”|0rem||0rem|false|true” custom_padding_phone=”|0rem||0rem|false|true” custom_padding_last_edited=”on|desktop” global_colors_info=”{}”][et_pb_text admin_label=”Sous-titre” module_class=”SousTitre” _builder_version=”4.25.0″ _module_preset=”default” text_font=”||||||||” text_orientation=”center” custom_margin=”||10px||false|false” text_orientation_tablet=”” text_orientation_phone=”center” text_orientation_last_edited=”on|tablet” global_colors_info=”{}”]Contact[\/et_pb_text][et_pb_text admin_label=”Titre – H2″ module_class=”Titre_40″ _builder_version=”4.26.1″ _module_preset=”default” text_orientation=”center” global_colors_info=”{}”]<\/p>\n [\/et_pb_text][et_pb_text admin_label=”Texte” _builder_version=”4.27.0″ _module_preset=”default” text_text_color=”#d2d4ec” text_orientation=”center” global_colors_info=”{}”]Contact us today and find out how we can work together to make your company’s digital future a reality.[\/et_pb_text][et_pb_button button_url=”https:\/\/www.sqorus.com\/en\/contact\/” button_text=”Contact SQORUS” button_alignment=”center” module_class=”Bouton fond_orange” _builder_version=”4.27.0″ _module_preset=”default” custom_margin=”30px||||false|false” global_colors_info=”{}”][\/et_pb_button][\/et_pb_column][\/et_pb_row][\/et_pb_section]<\/p>\n","protected":false},"excerpt":{"rendered":" Oracle Integration Cloud: discover best practices to avoid these classic mistakes and maximize your efficiency.<\/p>\n","protected":false},"author":52,"featured_media":41411,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_et_pb_use_builder":"on","_et_pb_old_content":"","_et_gb_content_width":"","content-type":"","_ayudawp_aiss_exclude":false,"footnotes":""},"categories":[505],"tags":[],"metiers":[225],"sujet":[220],"class_list":["post-41392","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-oracle-integration-cloud-soa-en","metiers-it-en","sujet-solution-en"],"acf":[],"yoast_head":"\n
\nIt is precisely on this note that we begin our exploration ofICO’<\/strong>s anti-patterns. <\/p>\n
\nGet ready to deepen your <\/span>understanding ICO<\/strong> <\/span>and discover how to maximize its efficiency while avoiding the most common pitfalls.
\nIt’s worth noting that most of these Councils can also be applied to any type ofdata integration architecture<\/strong>. <\/span>with technologies other thanOIC<\/strong>.<\/p>\n#1 OIC error: chatty integrations<\/h2>\n
\nTo put it more concretely, a <\/span>chatty integration<\/strong> <\/span>is characterized by the fact that it interrogates a system in a unified way for several records.
\nTake, for example, the case of a <\/span>integration<\/strong> <\/span>to read employee data from a <\/span>database<\/strong> <\/span>and update this information in a third-party system via an API.
\nLet’s imagine that the developer has opted for a user loop approach, calling the API individually for each user to update their data. <\/p>\n
\nIn addition, the cost ofICO<\/strong> <\/span>is impacted, as this approach increases message consumption, which can quickly lead to credit overruns.<\/p>\n
\nMany systems offer this possibility; Salesforce, for example, allows up to 200 records to be sent per call.
\nOpt forOIC adapters<\/strong> too <\/span>can also handle a large number of recordings per call.<\/p>\n<\/ul>\n
#2 OIC error: endless processing using a loop<\/h2>\n
<\/span><\/p>\n#3 OIC error: complex synchronous integrations<\/h2>\n
\nAdopting this design model for integrations intended to interact with several systems, and involving numerous conditions, uncontrolled loops or significant iterations, is irrelevant.
\nIndeed, the <\/span>creation of synchronous integration<\/strong> <\/span>is based on the need for rapid response.
\nIt’s important to note that this type ofintegration<\/strong>, also known as app-driven integration, is subject to a 5-minute time limit.
\nAfter this time, theintegration<\/strong> <\/span>returns an error.<\/p>\n
\nIndeed, if the estimate indicates thatsynchronous integration<\/strong> <\/span>is likely to exceed 2 minutes, it makes sense to opt for an asynchronous approach.<\/p>\n#4 OIC error: duplicate connectors in OIC<\/h2>\n
\nThis practice is not recommended, as it has a significant impact on maintainability, making subsequent management complex and prone to potential problems.
<\/span><\/p>\n#5 OIC error: read files sequentially<\/h2>\n
<\/span><\/p>\n
\nTooptimize the scalability of your interfaces<\/strong>, we recommend segmented reading. <\/span><\/p>\nMistakes to avoid with Oracle Integration Cloud<\/h2>\n
\nIf you needOIC expertise support<\/strong> <\/span>or in <\/span>data integration architecture<\/strong>, contact us today to discuss your specific requirements and get started.<\/strong> <\/span>optimize your eco-system<\/strong>.<\/p>\n<\/div>\n<\/div>\nAll about IT project governance<\/h2>\n
Also in our “IT project governance” issue <\/span><\/h3>\n
\n
A project? A request?A question?<\/h2>\n