Sponsored Content
Operating Systems Solaris NetIQ AppManager and Solaris 10 Post 302771312 by NetIQ on Wednesday 20th of February 2013 09:00:11 AM
Old 02-20-2013
To deploy and configure the AppManager Unix Agent you should use the AppManager Unix Agent Manager (UAM) – a Java Application. This console can establish a bi-directional communication with the agent.

For alerting and data collection the Agent needs to talk to an AppManager Management Server (MS) - a Windows Service. This is a unidirectional connection established by the Agent to the MS. The Agent needs to know what MS to talk to by configuring it with the UAM. The MS needs to have the Unix communication (port 9001) enabled.

If you have further question, please do not hesitate to ask or post to the NetIQ AppManager Forum.
 

3 More Discussions You Might Find Interesting

1. Solaris

Unable to login using ssh,telnet onto my solaris machine with solaris 10 installed

Hi, I am unable to login into my terminal hosting Solaris 10 and get the below error message "Server refused to allocate pty ld.so.1: sh: fatal: libc.so.1: open failed: No such file or directory " Is there anyways i can get into my machine and what kind of changes are required to be... (7 Replies)
Discussion started by: sankasu
7 Replies

2. Solaris

Solaris ssh client hangs when connecting to another Solaris machine

Got a strange problem. I have 4 Solaris servers all configured the same, Solaris 10 x86 update 10. When I try to ssh from one Solaris 10 server to another server ssh hangs. I have an identical server and when I try this everything works fine. The weird thing is if I am root on the server... (1 Reply)
Discussion started by: ccj4467
1 Replies

3. Solaris

How to add Solaris text console to Solaris grub2 menu?

Hi, I am new to sloaris and just instlled the solaris 11.2, i know little more about linux, i open the /boot/grub/grub.cfg in solaris and there is many other entries forl solaris 11.2 one of them is for 'Oracle Solaris 11.2 text console' but at boot grub2 only show the first default entry that... (1 Reply)
Discussion started by: shamsat
1 Replies
Agent::Driver::Default(3pm)				User Contributed Perl Documentation			       Agent::Driver::Default(3pm)

NAME
Log::Agent::Driver::Default - default logging driver for Log::Agent SYNOPSIS
# Implicit use use Log::Agent; logconfig(-prefix => "prefix"); # optional # Explicit use use Log::Agent; require Log::Agent::Driver::Default; my $driver = Log::Agent::Driver::Default->make("prefix"); logconfig(-driver => $driver); DESCRIPTION
The default logging driver remaps the logxxx() operations to their default Perl counterpart. For instance, logerr() will issue a warn() and logwarn() will call warn() with a clear "WARNING: " emphasis (to distinguish between the two calls). The only routine of interest here is the creation routine: make($prefix) Create a Log::Agent::Driver::Default driver whose prefix string will be $prefix. When no prefix is configured, the first letter of each logged string will be uppercased. CHANNELS
The "error", "output" and "debug" channels all go to STDERR. BUGS
If logdie() is used within an eval(), the string you will get in $@ will be prefixed. It's not really a bug, simply that wrapping a code into eval() and parsing $@ is poor's man exception handling which shows its limit here: since the programmer using logdie() cannot foresee which driver will be used, the returned string cannot be determined precisely. Morality: use die() if you mean it, and document the string as an exception. AUTHOR
Raphael Manfredi <Raphael_Manfredi@pobox.com> SEE ALSO
Log::Agent::Driver(3), Log::Agent(3). perl v5.10.0 2009-07-23 Agent::Driver::Default(3pm)
All times are GMT -4. The time now is 10:14 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy