Integration

Get Involved. Join the Conversation.

Topic

    Subrahmanyam Vempati
    Connectivity Agent ICS Vs OICAnswered
    Topic posted September 28, 2018 by Subrahmanyam VempatiBronze Trophy: 5,000+ Points, tagged Agent, Cloud, Integration, Tip 
    438 Views, 6 Comments
    Title:
    Connectivity Agent ICS Vs OIC
    Summary:
    Difference between the connectivity agent execution
    Content:

    Hi Team,

    I wonder how the connectivity agent of OIC is much lighter than the ICS agent .

    ICS agent is almost 1.7 GB and OIC is just 140MB. What makes this difference?

    Can anyone explain the internal architecture?

    Is still the weblogic running behind the scenes for OIC?

    Thanks,

    Vempati

    Best Comment

    Ravi Sankaran

    Hi Raghavendra,

    This is what you need to be aware of

    Connectivity Agent in OIC has the same functional capabilities as what you have seen with the one in ICS. 

    In fact, it has already got more in the form of automatic patching and High Availability (which is under controlled availability). 

    Here are the salient features of the Connectivity Agent that are vividly described in the documentation.

    • No ports are opened on the on-premises system for communication.

    • All communication is secured using SSL.

    • The on-premises connectivity agent registers with Oracle Autonomous Integration Cloud over SSL using the provided Oracle Autonomous Integration Cloud credentials.

    • The on-premises connectivity agent checks for work by making outbound requests through the firewall.

    • The on-premises connectivity agent can use a proxy to access the internet (the same proxy as other internal applications and browsers use). Authentication support for outbound proxy access is provided.

    • The on-premises connectivity agent connections are configured by the agent retrieving the configuration details from Oracle Autonomous Integration Cloud.

    • The on-premises connectivity agent processes requests by pulling messages from Oracle Autonomous Integration Cloud across SSL.

    • The on-premises connectivity agent posts responses by pushing messages to Oracle Autonomous Integration Cloud across SSL.

    • All communication is initiated by the on-premises connectivity agent.

    • No private SOAP-based web services are exposed.

    • No existing J2EE container is required to deploy the on-premises connectivity agent.

    • No data is persisted in the on-premises agent.

    HA support for Connectivity Agent is currently  under controlled availability. The 2 agents that are associated to a single agent group form a virtual cluster. As you are aware, Agent Group is specified during agent installation. All of the work requests emanating from integration flows having connections bound to this agent group will be available for either of the agent to process. It is the 'Competing Consumer Pattern' that is in the play.

    Hope this helps

    Ravi

    Comment

     

    • Hemanth Lakkaraju

      There is no weblogic for OIC connectivity agent. It's a simle java utility that uses dynamic classloading and communicate with on-prem systems and OIC.

      • Raghavendra Manchigiah

        Could you please let us know which Java feature is used for the communication? Does it look at all data flow as messages between OIC and the onprem system?

        • Ravi Sankaran

          Hi Raghavendra,

          This is what you need to be aware of

          Connectivity Agent in OIC has the same functional capabilities as what you have seen with the one in ICS. 

          In fact, it has already got more in the form of automatic patching and High Availability (which is under controlled availability). 

          Here are the salient features of the Connectivity Agent that are vividly described in the documentation.

          • No ports are opened on the on-premises system for communication.

          • All communication is secured using SSL.

          • The on-premises connectivity agent registers with Oracle Autonomous Integration Cloud over SSL using the provided Oracle Autonomous Integration Cloud credentials.

          • The on-premises connectivity agent checks for work by making outbound requests through the firewall.

          • The on-premises connectivity agent can use a proxy to access the internet (the same proxy as other internal applications and browsers use). Authentication support for outbound proxy access is provided.

          • The on-premises connectivity agent connections are configured by the agent retrieving the configuration details from Oracle Autonomous Integration Cloud.

          • The on-premises connectivity agent processes requests by pulling messages from Oracle Autonomous Integration Cloud across SSL.

          • The on-premises connectivity agent posts responses by pushing messages to Oracle Autonomous Integration Cloud across SSL.

          • All communication is initiated by the on-premises connectivity agent.

          • No private SOAP-based web services are exposed.

          • No existing J2EE container is required to deploy the on-premises connectivity agent.

          • No data is persisted in the on-premises agent.

          HA support for Connectivity Agent is currently  under controlled availability. The 2 agents that are associated to a single agent group form a virtual cluster. As you are aware, Agent Group is specified during agent installation. All of the work requests emanating from integration flows having connections bound to this agent group will be available for either of the agent to process. It is the 'Competing Consumer Pattern' that is in the play.

          Hope this helps

          Ravi

          • Subrahmanyam Vempati
            Hi Ravi, Thanks for the detailed information. As per the below statements , does it uses any messaging queues ? The on-premises connectivity agent processes requests by pulling messages from Oracle Autonomous Integration Cloud across SSL. The on-premises connectivity agent posts responses by pushing messages to Oracle Autonomous Integration Cloud across SSL. Thanks, Vempati
    • Ankur Jain

      Hi,

      There is no weblogic as well as no derby database in OIC agent. Multiple OIC can run on single host machine.

      OIC agent supports high availability too.

       

      Regards,

      Ankur

      • Subrahmanyam Vempati
        Thanks for the response Ankur. Agent High availability is still not in general availability it seems. But customers can request to enable that falg to avail that feature.