Which two are valid considerations when leveraging the OIC connectivity agent for high availability on-premise environments? (Choose two.)
Click on the arrows to vote for the correct answer
A. B. C. D. E.AE.
Sure, I can provide a detailed explanation for each of the considerations related to leveraging the Oracle Integration Cloud (OIC) connectivity agent for high availability in on-premise environments.
A. You cannot have more than two agent instances per agent group. Attempting to include a third agent instance in the same group during installation results in an error.
This statement is true. When using the OIC connectivity agent, you can have a maximum of two agent instances per agent group. This is because each agent group has a master agent and a standby agent, which are responsible for processing requests. The standby agent is ready to take over in case the master agent fails or goes offline. Therefore, if you attempt to include a third agent instance in the same group during installation, an error will occur.
B. Each host on which the agent is installed must be configured on separate subnets assigned to the same OIC agent group.
This statement is not entirely accurate. While it is recommended to configure each host on which the agent is installed on separate subnets, it is not a requirement. Instead, each agent instance should have a unique IP address and hostname, which should be registered in the DNS server. Also, all agent instances within the same agent group should be able to communicate with each other over the network, regardless of the subnet they are on. This can be achieved by configuring the necessary network settings, such as firewalls, routing, and DNS.
C. You should install the connectivity agents on the same host as the target application, then specify different agent group identifiers for each agent during its installation.
This statement is not correct. It is recommended to install the OIC connectivity agents on a separate host from the target application. This ensures that the agents do not compete for resources with the target application, such as memory, CPU, and network bandwidth. Also, it enables better fault isolation and improves the scalability and performance of the integration solution. Furthermore, each agent instance should be configured with a unique agent group identifier during installation, which identifies the agent as part of a specific agent group within OIC.
D. You will need to have OIC ServiceDeployer role permissions in order to download and install the OIC on-premise connectivity agent.
This statement is partially true. To download and install the OIC on-premise connectivity agent, you need to have the necessary permissions and privileges in OIC, which include the ServiceDeployer role. This role allows you to manage the lifecycle of OIC integrations, including deploying, configuring, and monitoring the connectivity agents. However, you also need to have access to the installation files and documentation, which are available from the Oracle Cloud Infrastructure (OCI) console or the Oracle Technology Network (OTN) website.
E. The File Adapter is not supported in high availability environments. When using the File Adapter and if some groups have multiple instances, use a dedicated agent group (with one agent only).
This statement is true. The File Adapter in OIC is not designed for use in high availability environments. Therefore, if you need to use the File Adapter in a deployment that has multiple agent groups with multiple agent instances, you should use a dedicated agent group with only one agent instance. This ensures that the File Adapter does not encounter issues related to file locking, concurrency, or consistency. Additionally, you should configure the File Adapter to use a shared storage location, such as a network file system (NFS) or a cloud object storage (COS) service, to store the files that are being processed by the integration.