7 Reconfiguring the Management Agent and Management Service

7.1.1 Configuring the Management Agent to Use a New Management Service

When you install the Management Agent on a managed host, you associate the Agent with a particular Management Service. The Management Agent uses the Management Service URL address and port to identify and communicate with the Management Service.

After you install the Management Agent, you can later reconfigure the Management Agent so it is associated with a different Management Service. Reconfiguring the Agent requires no changes to the Management Service. The reconfigured Agent will begin communicating with the new Management Service after the Agent is restarted.

To associate the Management Agent with a new Management Service after you have installed the Agent:

1. Stop the Management Agent.

   
   

   See Also: "Starting, Stopping, and Checking the Status of the Management Agent on UNIX"

   
   

2. Locate the emd.properties file in the Agent home directory:

   AGENT_HOME/sysman/config/emd.properties
   
   

3. Use a text editor to open the file and locate the REPOSITORY_URL property.

4. Modify the value for the REPOSITORY_URL property so it references the new Management Service.

   For example:

   REPOSITORY_URL=http://mgmthost2.acme.com:4889/em/upload
   

5. Modify the value for the emdWalletSrcUrl and emdWalletDest properties so they reference the new Management Service and the new Oracle home path, respectively:

   For example, if the new Management Service is on a host called mgmthost2.acme.com and the new Oracle home is /private/oracle/em10g, modify the properties as follows:

   emdWalletSrcUrl=http://mgmthost2.acme.com:4889/em/wallets/emd
   emdWalletDest=/private/oracle/em10g/sysman/config/server
   
   

6. Save your changes and close the emd.properties file.

7. Delete all the files in the following directories:

   AGENT_HOME/sysman/emd/upload/
   AGENT_HOME/sysman/emd/state/
   
   

8. Restart the Management Agent.

7.1.2 Changing the Management Agent Port

The Oracle Management Agent uses a predefined port number to receive requests from the Management Service. This port number is defined by default when you install the Agent on a managed host. If you later need to modify this port, you can use the following procedure. You might need to modify this port number if you have existing software that uses the default Agent port.

To change the Management Agent port:

1. Stop the Management Agent.

   
   

   See Also: "Starting, Stopping, and Checking the Status of the Management Agent on UNIX"

   
   

2. Locate the emd.properties file in the Agent home directory:

   AGENT_HOME/sysman/config/emd.properties
   
   

3. Use a text editor to open the file and locate the EMD_URL property.

   For example:

   EMD_URL=http://managed_host1.acme.com:1813/emd/main
   
   

4. Modify the port number in the EMD_URL property so the Agent uses a new unused port on the managed host.

   For example:

   EMD_URL=http://managed_host1.acme.com:1913/emd/main
   
   

5. Start the Management Agent.

7.1.3 Controlling the Amount of Disk Space Used by the Management Agent

Oracle designed the Management Agent to work within a set of disk space limits. These limits prevent the Management Agent from using too much disk space and causing performance or resource issues on your enterprise systems. However, if disk space becomes an issue, you can adjust the default settings that are used to control the amount of disk space used by the Management Agent.

As the Management Agent on a particular host gathers management data about the targets on the host, it saves the collected data on the local disk until the data is uploaded to the Management Repository. The agent saves this collected data and metadata in the following directory:

AGENT_HOME/sysman/emd/upload

By default, the Management Agent will save up to 50MB of collected data in the upload directory. If the amount of collected data exceeds 50MB, data collection is stopped temporarily until the data is uploaded to the repository and more disk space becomes available.

In addition, the Management Agent checks to be sure that the percentage of disk space currently in use on the local disk does not exceed 98 percent. If the this value is exceeded, the Management Agent stops collected data and stops saving information to the Management Agent log and trace files.

You can modify these default settings as follows:

1. Stop the Management Agent.

   
   

   See Also: "Starting, Stopping, and Checking the Status of the Management Agent on UNIX"

   
   

2. Locate the emd.properties file in the Agent home directory:

   AGENT_HOME/sysman/config/emd.properties
   
   

3. Use a text editor to open the file and modify the entries shown in Table 7-1.

4. Save your changes and exit the file.

5. Restart the Management Agent.

7.1.4 About the Management Agent Watchdog Process

The Oracle Management Agent is the Enterprise Manager component that gathers the data you need to manage your enterprise efficiently. As a result, Enterprise Manager includes software that keeps track of the Management Agent processes and makes sure the Management Agent stays running.

For example, if the Management Agent quits unexpectedly, this self-monitoring process—referred to as the watchdog process—will restart the Management Agent automatically.

In most situations, the watchdog process works in the background and requires no configuration or maintenance. The watchdog process is controlled by the emwd script located in the following directory of the Management Agent home directory:

AGENT_HOME/bin/emwd

You can identify the watchdog process by using the following command UNIX systems:

$PROMPT> ps -ef | grep emwd

7.1.5 Setting the Management Agent Time Zone

In today's global economy, it is not uncommon for the systems you manage to reside in multiple locations throughout the world. For example, if your company headquarters are in New Hampshire, USA, you may need to manage systems that reside in California, Canada, and in Europe.

As Enterprise Manager collects monitoring data from Management Agents running on these remote systems, it is important that the data is correlated accurately. A software failure on a machine in Ontario, Canada might be the cause of a performance problem on a machine in Hoboken, New Jersey.

To correlate this data, it is important that Enterprise Manager obtains the correct time zone for each Management Agent that you install. The following sections describe how the Management Agent obtains the time zone and how to correct the problem if the time zone for a Management Agent is incorrect:

• Understanding How the Management Agent Obtains Time Zone Information

• Troubleshooting Management Agent Time Zone Problems

• Troubleshooting Oracle Management Service Time Zone Problems

AGENT_HOME/sysman/config/emd.properties

AGENT_HOME/sysman/admin/suportedtzs.lst

Could not determine agent time zone. Please refer to to the file:
ORACLE_HOME/sysman/admin/supportedtzs.lst and pick a timezone region with a
standard offset of +5:0 from GMT and update the property 'agentTZRegion' in the
file: ORACLE_HOME/sysman/config/emd.properties

OMS does not understand the timezone region of the agent.
Either start the OMS using the extended list of time zones supported by 
the database or pick a value of time zone from
ORACLE_HOME/emdw/sysman/admin/nsupportedtzs.lst, update the property 'agentTZRegion' in the file
ORACLE_HOME/sysman/config/emd.properties and restart the agent.
A value which is around an offset of  -05:00 from GMT should be picked.

7.2.1 Configuring the Management Service to Use a New Repository

When you install and deploy the Management Service, you associate the Management Service with a Management Repository. The Management Service uses the database host, database system identifier (SID), database port, management user, and management password to identify and communicate with the Repository.

This repository information is stored in the emoms.properties file, which can be found in the following directory of the Oracle Application Server Home where the Oracle Management Service is installed and deployed:

IAS_HOME/sysman/config/

The following sections describe how to modify the repository information in the emoms.properties file and provide details about how Enterprise Manager keeps the Management Repository password secure.

oracle.sysman.eml.mntr.emdRepUser=SYSMAN
oracle.sysman.eml.mntr.emdRepPwd=sysman
oracle.sysman.eml.mntr.emdRepPwdEncrypted=false
oracle.sysman.eml.mntr.emdRepSID=oemrep1
oracle.sysman.eml.mntr.emdRepServer=system12.mycompany.com
oracle.sysman.eml.mntr.emdRepPort=1521

7.2.2 Configuring the Management Service to Use a New Port

When you install the Management Service, the port number for the Management Service is automatically set to 4889. The following procedure describes how to manually change the port number after the Enterprise Manager installation. For example, you will have to modify the port number if you attempt to install two Oracle Management Services on the same host computer.

To change the default Management Service port:

1. Stop the Management Service.

   
   

   See Also: "Controlling the Oracle Management Service"

   
   

2. Locate the following httpd_em.conf file located in the following directory in the Oracle Application Server home directory where you installed and deployed the Management Service:

   AS_HOME/sysman/config/
   
   

3. Open the http_em.conf file with a text editor and change all occurrences of 4889 to the new port number you want to use.

4. Save and close the http_em.conf file.

5. Locate the emoms.properties file in the same sysman/config directory.

6. Open the emoms.properties file with a text editor and change the following entry so it references the new port number of the Management Service:

   oracle.sysman.emSDK.svlt.ConsoleServerPort=4889
   
   

7. Restart the Management Service.

8. Reconfigure each Agent on your managed hosts to use the new management port.

   
   

   See Also: "Configuring the Management Agent to Use a New Management Service"