1 Reply Latest reply on Oct 22, 2004 11:54 PM by 279007

    InterConnect and High Availability

      We use Oracle InterConnect Server (9.0.4) to integrate the e-Business Suite with our legacy applications. We are currently planning the deployment to production of these integrations. The documentation how to use RAC (real application cluster) is rather limited. Does anyone have experience with InterConnect in conjunction with RAC?
      We need to have high availability but we don't want to run multiple instances of an adapter simultaneously (to ensure serialisation of the processing of the messages coming from the legacy applications). How is the persistence, caching etc.. done in such a setup?

      thank you,

      Claude Boussemaere
        • 1. Re: InterConnect and High Availability

          If it is just HA that you want in IC (which means running the adapters against a RAC database for hub and the spoke connections), all you need to do is configure the adapter.ini and hub.ini parameters with connection information of the alternate nodes.

          In terms of persisting runtime data in the local file system, you can turn pipelining option off.
          adapter.ini parameters:
          //Set this to false if you want to turn off the pipelining from the Bridge towards the hub.
          //Set this to false if you want to turn off the pipelining from the hub towards the bridge.
          The adapters will then not persist the messages in a local file persistence. Any message at any given time will either be sitting in the hub db or in the EBS instance.

          The adapters cache only the metadata locally and hence you wont have to worry about metadata cache.

          If the hub/spoke db fails, the adapter's JDBC connections will fail over to the alternate instance(s) in a round robin fashion.