Deploying Management Agent Using agentDeploy Script
In case, your target systems have no support for SSH, you can use agentDeploy script to deploy Management Agents. To be able to use this method, you need to create a user for management agent and create required directories and give permission to the Management agent user.
Let’s say we’ll create a group named “oinstall” and a user named “oracle” belongs to this group, and install the agent software to “/u01/agent”. Login as root user and issue the following commands:
|
1 2 3 4 5 |
[root@targetsystem ~]# groupadd oinstall [root@targetsystem ~]# useradd -g oinstall oracle [root@targetsystem ~]# passwd oracle [root@targetsystem ~]# mkdir -p /u01/agent [root@targetsystem ~]# chown -R oracle:oinstall /u01/agent |
Of course, I assume that you don’t have oracle user and oinstall group, and there’s no directory named “/u01/agent”. Instead of creating new user, group and directory, you can use an existing user, group and directory (if the directory is empty). Do not forget to check if OMS and target system can resolve each other’s host name!
Login to the OMS host as oracle user (again I assume you used oracle to install OMS), and log in to OEM using emcli:
|
1 |
[oracle@cloudcontrol12 ~]$ /u01/app/Middleware/oms/bin/emcli login -username=sysman |
