This content has been marked as final. Show 4 replies
Go thru below links so that you will have basic idea about local-agent and Java EE Agent.
Agent Installation in ODI11g
and the details regarding Java EE vs. Standalone Agents
After this if you get any doubts, then plz do share.
Standalone and Java EE Agents:
The Oracle Data Integrator agents exists in two flavors: standalone agent and Java EE agent.
A standalone agent runs in a separate Java Virtual Machine (JVM) process. It connects to the work repository and to the source and target data servers via JDBC. Standalone agents can be installed on any server with a Java Machine installed. This type of agent is more appropriate when you need to use a resource that is local to one of your data servers (for example, the file system or a loader utility installed with the database instance), and you do not want to install a Java EE application server on this machine.
A Java EE agent is deployed as a web application in a Java EE application server (for example Oracle WebLogic Server). The Java EE agent can benefit from all the features of the application server (for example, JDBC data sources or clustering for Oracle WebLogic Server). This type of agent is more appropriate when there is a need for centralizing the deployment and management of all applications in an enterprise application server, or when you have requirements for high availability.
It is possible to mix in a single environment standalone and Java EE agents in a distributed environment.
For more details please go thru below link
Hi Bhabani and Phanikanth,
The info you both provided was really helpfull and thanks a lot for the quick reply.
But still I am struck up with some basic question like I know when we need to schedule we require agent other than scheduling Can u please let me in which scenarios we use this standalone agents......