Skip to main content

Installing ODIConsole application using weblogic server

Hello everyone!
Here is an interesting tutorial that explains how to install ODI (Oracle Data Integrator) Console application using WebLogic server. The ODI Console is basically a web based console using ADF-faces framework for monitoring and managing the runtime architecture as well as viewing the design time objects.
Using ODI console, developers can view the interfaces whereas administrators can create and import repositories in order to configure theTopology. Through this post, we will learn how to setup the console application from scratch in Oracle Data Integrator!
Pre-requisites: Oracle Data Integrator 11gR1 (build version 11.1.1.5.0), Weblogic server 11gR1 10.3.5, Windows XP SP3 32 bit OS machine
Step 1: Download and install Weblogic server 11gR1 10.3.5
Go to the downloads page for Oracle Weblogic server and install a proper bit version of the same. Once downloaded, run the .exe file. After the installation is completed, you should see a Middleware folder being created in the drive specified. For example, mine exists at D:\Middleware
weblogic_server_download
Step 2: Download and install Oracle Data Integrator
In order to install the console application, you first need to install ODI inside the created Middleware directory, D:\Middleware, with the necessary components checked. Please check this blogpost. During ODI installation make sure you have chosen to install the ODI console component. The installation procedure is almost the same in all the versions till date. Create a master and a work repository before proceeding further.
Step 3: Configuring the domain
Using command prompt navigate upto the bin directory (D:\Middleware\Oracle_ODI1\common\bin) and execute the config.batfile! A configuration wizard should open up.
Now follow the below screenshots!
configure_domain_1
configure_domain_2
Make sure you select the option Oracle Data Integrator – Console
configure_domain_3
configure_domain_4
configure_domain_5
configure_domain_6
configure_domain_7
configure_domain_8
configure_domain_9
configure_domain_10
configure_domain_11
Add the Admin Server by clicking the arrow button.
configure_domain_12
configure_domain_13
configure_domain_14
configure_domain_15
Click on the Create button and the domain creation would begin. Start the Admin Server when completed.
Once the server is up and in running mode, open a new tab in your web browser.
server_running
Enter the address:
http://localhost:7001/console/login/LoginForm.jsp
Change the local host and port to whatever is listed by you in the Admin Server URL above.
Login into weblogic server with the credentials you provided during installation. On the left hand side, click on Environment –> Servers and then select the Admin Server (which should be running)
login_weblogic
odi_console_1
odi_console_2
odi_console_3
odi_console_4
Enter SUPERVISOR credentials for logging into the ODI console!
odi_console_5
odi_console_6
Finally, this completes the installation of ODI console. That’s it for this tutorial. Hope it helps! 

Comments

Popular posts from this blog

ODI KM Adding Order by Option

You can add Order by statement to queries by editing KM.I have edited IKM SQL Control Append to provide Order by.  1) Add an option to KM named USE_ORDER_BY, its type is Checkbox and default value is False. This option determines you want an order by statement at your query. 2)Add second option to KM named ORDER_BY, type is Text. You will get order by values to your query by this option. 3) Editing Insert New Rows detail of KM. Adding below three line code after having clause. That's it! <% if (odiRef.getOption("USE_ORDER_ BY").equals("1")) { %> ORDER BY <%=odiRef.getOption("ORDER_BY" )%> <%} %>  If USE_ORDER_BY option is not used, empty value of ORDER_BY option get error. And executions of KM appears as such below; At this execution, I checked the KM to not get errors if ORDER_BY option value is null. There is no prove of ORDER BY I'm glad.  Second execution to get  Ord

Creating Yellow Interface in ODI

Hello everyone! In Oracle data integrator (ODI), an  interface  is an object which populates one datastore, called the  target , with data coming from one or more other datastores, known as  sources . The fields of the source datastore are linked to those in the target datastore using the concept of  Mapping . Temporary interfaces used in ODI are popularly known as  Yellow Interfaces . It is because ODI generates a yellow icon at the time of creation of a yellow interface as opposed to the blue icon of a regular interface. The advantage of using a yellow interface is to avoid the creation of  Models each time you need to use it in an interface. Since they are temporary, they are not a part of the data model and hence don’t need to be in the Model. So let’s begin and start creating our yellow interface! Pre-requisites : Oracle 10g Express Edition with *SQL Plus, Oracle Data Integrator 11g. Open *SQL Plus and create a new table  Sales  in Oracle. You can use any existing ta

Running Count in Talend Open Studio

Most Talend components keep a count of the records processed using variables like NB_LINE or NB_LINE_OK.  But these are only available after all processing is completed.  Define your own counter variable to keep a running count for use in a tMap. Variables like tFilterRow.NB_LINE or tAccessOutput.NB_LINE_INSERTED can be used to report the number of affected lines after a subjob's processing.  However, it may be of use to get the current line index for use in a tMap.  The index variables used to form NB_LINE aren't available during processing; they're only written out the globalMap at the end of processing. In this example, staging records are loaded from Excel to Access.  The order in which the Excel records are read is preserved in a database column called DISPLAY_SEQ_NB.  Note that there is an auto-increment column used for record ID in the Access table.  This could be used to infer a loading order, but this job uses a separate column to keep the ID as a meaningless surr