Create Physical agent in
topology with following parameters:
B. Generate the server template.
Go to that location where jar file is located e.g: /oradata/ODI_SETUP/
Name= Agent name
Host=on which Application
server is installed.
Port=on which application
server runs.’
Web application context:
default (oraclediagent)
Create Application Server Credentials
store:
a.
Go to the
<ODI_HOME>\common\bin and run the wlst.sh file.
b.
Wls:/offline>connect(‘weblogic’,’weblogic123’,’t3://localhost:7001’)
c. Wls:/odi_11g/serverConfig>createCred(map="oracle.odi.credmap",key="SUPERVISOR",user="SUPERVISOR",password="odisuper",desc="key
for supervisor")
d. Wls:/odi_11g/serverConfig>disconnect()
Now Credential store is created for the application
store and defined the SUPERVISOR KEY, which will be used while generating WLS
template.
Generate the server template for JAVAEEAgent.
Before generating server template, define the data sources for the agent.
a. Drag the work repository the data server into this data source and define the JNDI names.
a. Drag the work repository the data server into this data source and define the JNDI names.
B. Generate the server template.
Go to that location where jar file is located e.g: /oradata/ODI_SETUP/
Run the jar -xvf WLST_AGENT.jar file.
Got to the /oradata/odi_home/agentapp
location and see that oracledi.ear file is created. And Deploy this same file
on that application server (e.g:odi_server1).
Now see the deployments of odi_server1: check weather that agent application state is active.
Test the Java EE agent connection from Topology;
Now see the deployments of odi_server1: check weather that agent application state is active.
Test the Java EE agent connection from Topology;
Yehhhh !!!!!! We have
successfully configured ODI JAVA EE agent……Njjoy…..! J
Thank you very much. This rare and detailed article was a great help for getting our ODI Agent v12.2 up and running in the DMZ!
ReplyDelete