Configuring the Management Agent to
Use a New Management Service
Use a New Management Service
In today's demonstration I am showing how to reconfigure
Management Agent when I have migrated/move our OMS to New Server. In this case after movement OMS, agent
repository URL is still trying to access existing OMS server which is down as I
have migrated to new one.
When you install the Management Agent
on a managed host, you associate the Management 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 Management
Agent requires no changes to the Management Service. The reconfigured
Management Agent will begin communicating with the new Management Service after
the Management Agent is restarted.
To associate the
Management Agent with a new Management Service after you have installed the
Management Agent:
- Stop
the Management Agent.
Locate the emd.properties file
in the Management Agent home directory:
AGENT_HOME/sysman/config/emd.properties
Editor AGENT_HOME/sysman/config/emd.properties
and locate the REPOSITORY_URL property.
Modify the value for the REPOSITORY_URL property so it
references the new Management Service.
For example:
REPOSITORY_URL=https://oem250:4889/em/upload
- Also
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 oem250 and
the new is oem251, Oracle home is, modify the properties as follows:
emdWalletSrcUrl=http://oem251:4889/em/wallets/emd
emdWalletDest= /u01/app/oracle/Agent12cR5/agent_inst/sysman/config/server
Save your changes and close the emd.properties file.
- Delete
all the files in the following directories:
AGENT_HOME/sysman/emd/upload/
AGENT_HOME/sysman/emd/state/
- Restart
the Management Agent.
dns100:> emctl
start agent
Oracle
Enterprise Manager Cloud Control 12c Release 5
Copyright
(c) 1996, 2015 Oracle Corporation. All
rights reserved.
Starting
agent ........... started.
dns100:>
dns100:>
dns100:>
dns100:>
emctl status agent
Oracle
Enterprise Manager Cloud Control 12c Release 5
Copyright
(c) 1996, 2015 Oracle Corporation. All
rights reserved.
---------------------------------------------------------------
Agent
Version : 12.1.0.5.0
OMS
Version : 12.1.0.5.0
Protocol
Version : 12.1.0.1.0
Agent
Home :
/u01/app/oracle/Agent12cR5/agent_inst
Agent
Log Directory :
/u01/app/oracle/Agent12cR5/agent_inst/sysman/log
Agent
Binaries :
/u01/app/oracle/Agent12cR5/core/12.1.0.5.0
Agent
Process ID : 6608
Parent
Process ID : 6565
Agent
URL :
https://dns100.ora.com:3872/emd/main/
Local
Agent URL in NAT : https://dns100.ora.com:3872/emd/main/
Repository
URL :
https://oem251.ora.com:4903/empbs/upload
Started
at : 2015-10-03 05:52:05
Started
by user : oracle
Operating
System : Linux version
2.6.39-400.209.1.el5uek (amd64)
Last
Reload : (none)
Last
successful upload :
2015-10-03 05:52:14
Last
attempted upload :
2015-10-03 05:52:14
Total
Megabytes of XML files uploaded so far : 0.01
Number
of XML files pending upload : 0
Size
of XML files pending upload(MB) :
0
Available
disk space on upload filesystem : 87.64%
Collection
Status :
Collections enabled
Heartbeat
Status : Ok
Last
attempted heartbeat to OMS :
2015-10-03 05:52:10
Last
successful heartbeat to OMS :
2015-10-03 05:52:10
Next
scheduled heartbeat to OMS :
2015-10-03 05:53:10
---------------------------------------------------------------
Agent is Running and
Ready
No comments:
Post a Comment