Skip to main content

Convert App based Integration to Scheduled Integration without wrapper in OICS

we all know that converting a scheduler integration to REST is quite easy , where as the reverse is not possible and the only way to achieve it is through creating a wrapper scheduler integration and invoking the trigger one as child from there.

But there is another way through which we can achieve the direct conversion.

For that please refer to below example.

Note : Every step mentioned has to be done very carefully

Create Scheduler Integration.

I’ve created a base one in which it invokes a SOAP service.



 I’ve created a small trigger integration which I’m going to change to scheduler without any wrapper.


Please follow the below steps to convert rest based to scheduler:

    1)  Export the integration.

    2) Rename the iar file to zip.

    3) Now unzip the file.

    4)  Compare the properties files of both scheduler and rest based integration and make the changes to rest based as per the scheduler integration



After changes


Now open the resources folder:

Move the scheduler resource file “Processor_8” to the App driven / rest based trigger integration

Scheduler file


Now open the PROJECT_INF folder and compare the analysis files between the two integrations and remove the rest_trigger components form the analysis file of app driven integration and replace them with the scheduler components.


Post changes



Similarly for project.xml file as well


That’s all now once you are done with the changes.

Now zip the "icspackage" folder and rename it with the integration name


After importing back the lates one to the OIC , now the rest based integration is converted to scheduled




Hope you have liked the article and learnt something new for the day.

-Preetham Konjeti








Labels:

Comments

  1. AnonymousMay 28, 2024 at 5:49 AM

    For the following step - "Move the scheduler resource file “Processor_8” to the App driven / rest based trigger integration" - Can you please publish the exact Source and Target path.

    ReplyDelete
  2. AnonymousMay 28, 2024 at 6:09 AM

    Also please publish a screenshot Post Project XML changes.

    ReplyDelete

Post a Comment

Popular posts from this blog

ChatGpt X Oracle Digital Assistant Integration

  Introduction In this article I will be explaining about integrating the ChatGpt with Oracle Digital Assistant. NOTE : This is not a suggestion to have ChatGPT in your ODA, this article is just to showcase the flexibility of the ODA to easily integrate with anything. Main article ChatGPT ChatGPT is an AI language model developed by OpenAI, capable of processing natural language input from users and generating coherent and relevant responses. It has been trained on an enormous corpus of text data using unsupervised learning, allowing it to generate responses that are not just grammatically correct, but also contextually appropriate and engaging. ChatGPT is particularly useful in scenarios where there is a need for rapid and accurate responses to user queries, such as in customer service or personal assistants. However, it may struggle to generate appropriate responses in certain situations and may not be suitable for scenarios requiring a high degree of personalization or...
2 comments
Read more

Wait for Synchronous Integration in OICS

   Introduction: Wait is the most common thing we use to slow down the process at any given point of time, but this wait action is by default disabled for synchronous integrations. Main Article: Create a JavaScript ( syncWait  let  ) with the below Code: function syncWait(waitTimeinmillisec) {   const begin = Date.now();   while ((Date.now() - begin) < waitTimeinmillisec){   }   return waitTimeinmillisec; } now call this JavaScript in your synchronous Integration with the seconds you want to halt your integration * 1000. Call this JavaScript in places you need in your synchronous Integration. That's it you had overcome the synchronous Integration Limitation. Example: -Preetham Konjeti.
Post a Comment
Read more