One thing that has always been a source of confusion for all beginners is the Weblogic server. I will be coming to that later, before that I will tell you the purpose of this post. Its about the new feature of ODI 11g which can use Weblogic Server for running ODI agent. A comprehensive doc for setting up this is available here
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/odi_11g/setup_jee_agent/setup_jee_agent.htm
I will post my experiences of setting up the ODI agent later since I am still not through it.
So what is Application Server and HTTP server?
For beginners, suppose you want to buy a camera on ebay, you open the website's page on your machine (client), from where does the information that you see - about your desirable camera on your screen - come from ?
How does it calculate the monthly installments for you ? Does it use your machine's calculator app for doing that ? Definitely not.
There is a application server ( usually the big machine residing far away from your home) which accepts your (client) requests and then processes the desired results and sends it over to your machine. To standardize/streamline/secure this communication, there is a middle-man who is called the
http server (HS). So your requests will be given to a http server, http server will forward it to the appropriate application server (AS) and AS after processing the request will respond to the HS with a 'reponse', this response will appear on your (client) machine as the end result, in our case the image of your desired camera and the calculated installment !
Though this is a very simple example I have given, over the period of time, the roles and responsibilities of Application Servers and HTTP servers have increased, but the core functionality remains same. For more details, you can refer to the web :)
Now tell me more about Weblogic ...
Its basically an application which runs usually on big machines which will do the server-side processes. So Weblogic Server is an Application server. What is my application ?? It can be anything that you want to host on this machine. A simple webpage or a complex site like ebay or facebook.
In our case the Application is going to be Oracle Data Integrator's component called 'Agent'.
Weblogic was originally called BEA Weblogic but when Oracle acquired BEA it became Oracle Weblogic.
Weblogic's direct competitors are Apache and Microsoft IIS. Weblogic is lightweight compared to Apache meaning it wont eat much RAM or disk space of the server machine.
Oracle Weblogic server is usually called wls or ows in AS jargon.
And what is Oracle HTTP server ?
Like I said above, it is the middle-man which will direct client requests to the Weblogic AS and respond to clients with response from WLS. It is lovingly called OHS.
Things get real messy when you dig deeper into WLS and OHS, but once you understand the way it works, its quite easy to conceptualize things.
To really get a hang of these two things, you should try installing and configuring Oracle EPM system all by yourself, face the difficulties starting and stopping services, read the log files and Oracle forums. Some things are better learnt the hard way :)
How do I install Agent using Weblogic ?Coming back to the purpose of this post, the 'newest' and the most irritating way of installing an agent is through Weblogic. Its also called the Java EE agent. For installing this agent, you need to install all the features that come with the setup (check Java EE ) and make sure that Weblogic server is installed on the same machine. The path where you will be installing ODI must incorporate Weblogic installation path.
Find out how it is done here
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/odi_11g/setup_jee_agent/setup_jee_agent.htm
and if you are lucky, you might get the agent installed in the first shot. So best of luck !!!