How can I install the Oracle OMA component?
The OMA – Oracle management Agent connects the OMS to managed targets. We should install the OMA on every managed target host. There are three ways to install the OMA.
1- Using the Oracle Product CDs (Interactively). It is the same is regular Oracle installation. $ /stage/Disk1/runInstaller.
2- Using the batch process (Silent Installation). It is the same as above but in silence no interaction.
$ /stage/Disk1/runInstaller –responseFile ./agent.rsp –silent doDiscovery=True startAgent=TRUE (you can find the sample response file in the $ORALCE_HOME/install directory.
3- Using the OMS process (On Demand). You don’t need the Oracle product CDs. Go to each server and use its browser and type: http://oms-servername:4889/agent_download and then select the OMA. Make sure that the wget utilize is in /usr/local/bin/wget. If not, then make a link for it. For example: $ ln –s /usr/bin/wget /usr/local/bin/wget. You should make a new directory for the OMA before doing anything. Then run root.sh
What are the Key Configuration files for the OMA?
The key configuration files for the OMA are:
1. ./sysman/emd/targets.xml
2. ./sysman/config/emd.properties
3. ./sysman/config/emagentlogging.properties
What is Blackouts?
We use blackouts to suspend target monitoring, schedule maintenance periods for these targets. This will prevents unnecessary alerts from being sent while a target is down for maintenance.
What are the differences between Application Server Control and Grid Control? -
Grid control needs to be installed separately but Application Server control will be installed the same time that you install OracleAS. - Grid has the OMS and the Oracle Application Server control has no OMS. - Grid has may target type but the Oracle Server Control only has OracleAS. - With the Oracle Application Server Control, you can do server configuration but you can not do this with the Grid Control. - Both can do application configuration. - The application server control is Farm/cluster aware but not Grid. - With Grid control you can do Group, Historical Monitoring and Alerts, Application Service Level management, Job system, Configuration management, Mobil access via EM2GO. But you can not do any of the above function by Application Server Control.
How do we access to Grid control and Application Server control?
- to access to Grid control: http://oms-server:7777/em - to access to Application Server control: http://application-server:1810/
What are J2EE and OC4J?
Think of J2EE as an application and OC4J as an instance. You deploy the J2EE applications to the OC4J instance.
What are the Oracle configurations Infrastructure Services? - Identity Management: It provides Internet Directory (OID) and Single Sign-On capabilities. - Central Management: It centrally manages an application server instance with a separately installed Oracle management Agent (OMA). - Oracle Application Server Clusters: It manages multiple instances using one database repository. You can configure a J2EE and Web Cache instance to use a metadata repository.
How can I access to the Oracle Application Server Topology?
http://application-server:1810/emd/console/ias/topology/topologyjsp - or - http://application-server:1810/emd/console/ias/topology/topologyapplet
How can I deploy an OC4J Application?
1- Create an OC4J instance: On the Application Server Control Home page, click create OC4J instance. Then enter instance name, and click Create.
2- Add a data source: Select the create instance. Click the Administration tab; and under Application Defaults, select Data Sources and click Create. Enter the application data source information, and then click Create.
3- Deploy a J2EE application: Click Application, from the created instance. Click Deploy EAR file. Click browse and select the .ear file of the application you want to deploy. Enter an application name and then click Continue.
4- Now, we can monitor the OC4J application from the Application Server control.
What is ASLM – Application Service Level Management?
With ASLM, you manage application availability, monitor application performance, and diagnose application response-time issues.
What are beacons?
Beacons are a function of the Management Agent. It has responsibility of replaying transactions at specified time and measure the performance and response times of the transaction. To create it, click Management system, agents, and select the agent you want to configure as a beacon. Select it from the drop-down and then click Go. Once you give it a name and proxy information, click OK.
How to configure Web Applications for monitoring an application?
Do the following steps to configure Web application for monitoring.
1- Create the Web application.
2- Create transactions.
3- Create and assign beacons to Web applications.
4- Define availability.
5- Configure end-user response-time monitoring.
6- Configure middle-tier performance monitoring.
Basic commands an Oracle Database Administrator must know (using default port). Use the http://:7777 URL with your Web browser to connect to HTTP Server. Use the ias_admin username to connect to the OMS. Use the iSQL*Plus tool if was installed by using the http://:5560/isqlpus URL to connect iSQL*Plus. Make sure that you have started the iSQL*Plus on the database server (# isqlplusctl start). Reference: http://www.iselfschooling.com/FREE_Oracle_Training/04_Advanced/02_Grid/lesson01.html
February 21, 2009
Part-3
Labels: Grid control
Subscribe to:
Post Comments (Atom)
0 comments:
Post a Comment