e. To start managed server odi_server_1, change
directory to WLS Home
-C:\Oracle\Middleware\user_projects\domains\ODI_DOMAIN\bin, and use the
execute command StartManagedWeblogic odi_server1. For Username, enter
weblogic. For the password, enter welcome1. Verify that your managed
server is started in RUNNING mode.
f. From ODI Designer, test connectivity of your configured ODI Java EE agent. Click OK.
3. Use Enterprise Manager to administer ODI.
a. Start the browser and enter http://localhost:7002/em. Log in to Enterprise Manager. For the user, enter weblogic. For the password, enter welcome1. On the screen that follows, click Continue.
b. With Enterprise Manager, a process and resources can be monitored and managed.You can explore the deployed application by clicking on each link. You can see running processes, workload, log file information, and more. Drill down into ODI objects by expanding ODI in the left panel, as shown in the following screen.
c. Expand odiconsole node. Then click MASTER REPOSITORY to view more details.
Note: Your information may differ from the information provided on these screens.
d. Click the OracleDIAgent to see the Java EE agent information.
e. Click the localagent node to see details for the standalone agent.
f. Expand the Application Deployment node, and then click oraclediagent. View the WebLogic server application deployment information.
then execute the command stopManagedWebLogic odi_server1. For the user name, enter weblogic. For the password, enter welcome1.
b. To stop the WebLogic server, execute the command stopWebLogic.
f. From ODI Designer, test connectivity of your configured ODI Java EE agent. Click OK.
3. Use Enterprise Manager to administer ODI.
a. Start the browser and enter http://localhost:7002/em. Log in to Enterprise Manager. For the user, enter weblogic. For the password, enter welcome1. On the screen that follows, click Continue.
b. With Enterprise Manager, a process and resources can be monitored and managed.You can explore the deployed application by clicking on each link. You can see running processes, workload, log file information, and more. Drill down into ODI objects by expanding ODI in the left panel, as shown in the following screen.
c. Expand odiconsole node. Then click MASTER REPOSITORY to view more details.
Note: Your information may differ from the information provided on these screens.
d. Click the OracleDIAgent to see the Java EE agent information.
e. Click the localagent node to see details for the standalone agent.
f. Expand the Application Deployment node, and then click oraclediagent. View the WebLogic server application deployment information.
then execute the command stopManagedWebLogic odi_server1. For the user name, enter weblogic. For the password, enter welcome1.
b. To stop the WebLogic server, execute the command stopWebLogic.
No comments:
Post a Comment