Weblogic SNMP Agent with WindowsNT SNMP Agent

Can I setup Weblogic SNMP agent as a sub-agent to Windows NT SNMP agent (Microsoft's version)? According to documentation, sub-agents for Microsft's SNMP agent need to be implemented as 32-bit multithreaded DLLs using the Microsoft SNMP API. Does Weblogic have DLLs that we could use for this purpose?
If that is not possible, is there a roadmap on how to provide the same support as the Microsoft's SNMP agent under Weblogic SNMP agent so that the Weblogic agent would provide the same visibility into the system that the Microsoft's agent does by default? Is this even possible?
Thanks.

"Sanjeev Mishra" <[email protected]> wrote:
>
Does anyone know how to make Microsoft's SNMP Master Agent run on a different port?
I figured this out. It uses the 'snmp' setting from the services file. Just changing that works. Would have been more convenient if there was also a command line flag for that purpose.
Thanks.
"Sanjeev Chopra" <[email protected]> wrote:
Sanjeev Mishra <[email protected]> wrote in message
news:39fde7f2$[email protected]..
Can I setup Weblogic SNMP agent as a sub-agent to Windows NT SNMP agent(Microsoft's version)? According to documentation, sub-agents for Microsft's
SNMP agent need to be implemented as 32-bit multithreaded DLLs using the
Microsoft SNMP API. Does Weblogic have DLLs that we could use for this
purpose?
No.
However, you can have the WLS agent proxy for the NT agent. e.g. you can run
the NT agent on a non-standard port and the WLS agent on 161 and then use
'-otherAgents' option so that the WLS agent will forward any reqs for the NT
agent MIB to that agent. In this setup the SNMP Manager can view that node
as one SNMP entity which supports the WLS MIB + NT MIB
See http://www.weblogic.com/docs51/admindocs/snmpagent.html#use_agent for
details.
If that is not possible, is there a roadmap on how to provide the samesupport as the Microsoft's SNMP agent under Weblogic SNMP agent so that the
Weblogic agent would provide the same visibility into the system that the
Microsoft's agent does by default? Is this even possible?
Thanks.

Similar Messages

UCCE maximum agents with ICM/UCCE agent mix

hello
I saw in the UCCE 9 BOM that ICM can support up to 28800 agents and UCCE 12000 concurrent agents.
Is it possible to support beyond 12000 with a mix of ICM agents (10000) and UCCE agents (4800) concurrent?
Thanks
Mike Kana

Out of the check mark in the queue to skill group node you go to another run external script node, then you loop into that over and over again until the call is answered.
david

SNMP subagent with SMUX SNMP master agent

I'm looking for the smux agent configuration for ucp-snmp to be able to use it as the master agent on a Linux/Solaris server. The subagent would be the LDAP instance snmp sub-agent. According to the documentation, if I have a master agent that I can't get rid of and is smux compliant, I can use it instead of the Netscape SNMP Master agent.
Even by configuring the ucp-snmp master agent as per the Netscape Directory Server documentation, the subagent is not starting. I always get the following error: "Unexpected error" in the console 4.2 window.
I'm using a Netscape Directory Server 4.16
Can anybody help me on what should be the smux configuration and then how to start the LDAP instance subagent?

Hi,
Iplanet does not support for it's products being installed on linux or snmp for linux.

How do I restart the SNMP agents with the original command line options?

I'm creating an application that changes the SNMP trap target configuration files and then restarts the SNMP agent. I'm currently working with the mibiisa agent. I want to make sure that I restart the service with the new trap targets but with the original command line options. How can I restart the mibiisa service with the same command line options that it originally loaded with?

It is not "Network Time" that is the problem, but actually "SystemStarter." SystemStarter is an interim kludge to enable the work or the old StartupItems until they can be converted to LaunchDaemons or LaunchAgents controlled by launchd. Launcd calls SystemStarter to launch all the unconverted StartupItems. ntpd is now under the control of launchd directly.
Launchctl is the command to load and unload the plist files, but I don't think it has a mechanism to restart a daemon.
There are start and stop commands in launchctl, but the man page indicates that they are for debugging purposes.
I also imagine you could just kill the ntp daemon and let it restart with new settings. It is most likely set to "keepAlive" so that it will automatically restart.

SNMP Support with Oracle Agents, does somebody have experience

Hy iam a student in Germany,
I'am working with an Company in air traffic management
and I'am searching for help with SNMP and Oracle 8i
Does anybody have implemented the intelligent Agent in
Oracles 8i to be managed with an HP Open View ore another
NNM System?
In my opinion Oracles Agent doesn't support SNMP Version 3
des encryted neither AgentX requirements.
Is this true?
Is it possible to manage the DB with UCD-SNMP and embeddet SQL?
If you answer to my or write an email I would be very happy.
[email protected]

i read a blog post that you can deploy patches via a Deployment Type for a Application. I configured a Deployment Type as Script Installer for my main Installation (the Main Application is already Deployed) and as the detection method i used "Fileversion".
The Problem now is that i cannot see the Patch in the Software Center of the client PC. Anybody knows why? The Main Installation is located in the ccmcache of the Client PC but not that Patch... (MSP) The Patch is from our own Product.
When i look into the AppDiscoveryLog with CMTrace i can see this:
    Performing detection of app deployment type application patch 123(ScopeId_F005A2B5-3FD9-4873-979E-1B406115BB16/DeploymentType_5f0d99c3-efec-4002-9101-be8ba59140d0, revision 10) for system.    AppDiscovery
14.11.2014 14:41:10    3360 (0x0D20)
+++ Discovered application [AppDT Id: ScopeId_F005A2B5-3FD9-4873-979E-1B406115BB16/DeploymentType_5f0d99c3-efec-4002-9101-be8ba59140d0, Revision: 10]    AppDiscovery    14.11.2014 14:41:10    3360 (0x0D20)
+++ Detected app deployment type application patch 123(ScopeId_F005A2B5-3FD9-4873-979E-1B406115BB16/DeploymentType_5f0d99c3-efec-4002-9101-be8ba59140d0, revision 10) for system.    AppDiscovery    14.11.2014 14:41:10
3360 (0x0D20)

Dialog between the SNMP Master Agent and a SNMP SubAgent

I have developped a SNMP SubAgent. The Master Agent uses the static method to register the SubAgent. In the Registration File of the SubAgent, I have specified the UDP port number (example: port = 1234). When the SubAgent is started (by the MasterAgent), it must open the UDP port specified in the Registration File. The dialog works fine between the SubAgent and the Master Agent.
I would prefer not to specify the UDP port number in the Registration File so that the Master Agent chooses itself a free UDP port number. But the SubAgent needs to know this UDP port number to dialog with the Master Agent. I thought the SubAgent could read it in the Status File of the Master Agent. BUT in fact, when the Master Agent invokes the SubAgent, its Status File isn't yet updated with the right port number value.
How may the SubAgent know the UDP port number chosen by the Master Agent ?
NB: I haven't use the SunOS SNMP toolkit to develop the SubAgent.

Hi ,
Good question.
The subagent only communicates via the port 161 with the master agent as per my understanding. It only listens for SNMP request on the port number mentioned in the <<agentname>>.rsrc file or the port assigned by the master agent. Please start the subgent with no options "-d 4" and then you can confirm the behaviour. Enclosed below is a snippet of that output for reference. Also the UserGuide at the following link will be helpful.
http://www.sun.com/software/entagents/docs.html
Thanks
Sujeet
<pre>
./init.snmpdx start
PDU:
version: 0
community: public
type: SET_REQ_MSG (0xa3)
request id: 0
error status: noError(0)
error index: 0
name: 1.3.6.1.4.1.42.2.15.5.0
type: OCTET STRING (0x4)
length: 8
value: snmpdemo ( 73 6e 6d 70 64 65 6d 6f )
PACKET:
30 30 02 01 00 04 06 70 75 62 6C 69 63 A3 23 02
01 00 02 01 00 02 01 00 30 18 30 16 06 0A 2B 06
01 04 01 2A 02 0F 05 00 04 08 73 6E 6D 70 64 65
6D 6F
sent 50 bytes to sump.161<< received 50 bytes from sump.161
PACKET:
30 30 02 01 00 04 06 70 75 62 6C 69 63 A2 23 02
01 00 02 01 00 02 01 00 30 18 30 16 06 0A 2B 06
01 04 01 2A 02 0F 05 00 04 08 73 6E 6D 70 64 65
6D 6F
PDU:
version: 0
community: public
type: GET_RSP_MSG (0xa2)
request id: 0
error status: noError(0)
error index: 0
name: 1.3.6.1.4.1.42.2.15.5.0
type: OCTET STRING (0x4)
length: 8
value: snmpdemo ( 73 6e 6d 70 64 65 6d 6f )
</pre>

SNMP Trap with Solaris 9

Hello,
I am looking for information on SNMP traps that can be generated by the SNMP installed with the OS.
How can I configure them and what is available?
I read the doc Solstice Enterprise Agents 1.0 User Guide but did not find anything to configure SNMP Traps.
Or which MIB should I use to get an event log that will report problem?
Any help would be great!
Thanks

Hi,
Even im facing this issue, for latest solaris 10 patches also.
Thanks,
Srikanth.

Core dump with simple sub-agent - Any idea

Hi,
I'm using SEA 1.03 on Solaris 7 with patch 107709-11.
I'm trying to build a simple sub-agent with a different enterprises MIB id (1.3.6.1.4.1.4315.20.1-2 as Integer).
I'm compiling it with Sun Workshop 5.0 C compiler.
When running in debug it starts and writes out:
SUBTREES: 1.3.6.1.4.1.4315.20.1 xpstestd 8000
1.3.6.1.4.1.4315.20.2 xpstestd 8000
When running the first SNMP GET request for OID
1.3.6.1.4.1.4315.20.1 creates the following:
Waiting for incoming SNMP requests on UDP port 8000
<< received 44 bytes from localhost.34132
PACKET:
30 2A 02 01 00 04 06 70 75 62 6C 69 63 A0 1D 02
03 06 87 00 02 01 00 02 01 00 30 10 30 0E 06 0A
2B 06 01 04 01 A1 5B 14 01 00 05 00
PDU:
version: 0
community: public
type: GET_REQ_MSG (0xa0)
request id: 427776
error status: noError(0)
error index: 0
name: 1.3.6.1.4.1.4315.20.1.0
type: NULL (0x5)
length: 0
value: ( )
node_find() returned xpsId with suffix 0
!! get(): processing the variable xpsId
Segmentation Fault (core dumped)
==============================
Any idea what is wrong?

Thats a problem with Solstice... all I did to fix that problem was to install the patch...
Find and install the latest patch (I used 108870-04).
Hope it helps.

The User-Agent "Java/1.5.0_06" is unknown;creating an agent with null agent

Hello,
We're currently on JDeveloper 10.1.3.4.0.4270. We just release a new version of our web app into production. This is an internal web application. application server is weblogic 10. The weblogic log is showing alot of these warning messages. I tried search on this forum and in google but unable to find any information. I really appreciate if anyone has any idea what could be causing these warning. Our users are constantly getting sent back to the login page to to user sessions lost.
<Jun 8, 2010 12:39:20 AM EDT> <Info> <Common> <BEA-000628> <Created "5" resources for pool "venusDS", out of which "5" are available and "0" are unavailable.>
Jun 8, 2010 12:39:20 AM oracle.adfinternal.view.faces.agent.AgentFactoryImpl _populateNullAgentImpl
WARNING: The User-Agent "Java/1.5.0_06" is unknown; creating an agent with null agent attributes.
Jun 8, 2010 12:39:20 AM oracle.adfinternal.view.faces.agent.AgentFactoryImpl _populateNullAgentImpl
WARNING: The User-Agent "Java/1.5.0_06" is unknown; creating an agent with null agent attributes.
Jun 8, 2010 12:39:21 AM oracle.adfinternal.view.faces.agent.AgentFactoryImpl _populateNullAgentImpl
WARNING: The User-Agent "Java/1.5.0_06" is unknown; creating an agent with null agent attributes.
Jun 8, 2010 12:39:21 AM oracle.adfinternal.view.faces.agent.AgentFactoryImpl _populateNullAgentImpl
WARNING: The User-Agent "Java/1.5.0_06" is unknown; creating an agent with null agent attributes.
Jun 8, 2010 12:42:21 AM oracle.adfinternal.view.faces.agent.AgentFactoryImpl _populateNullAgentImpl
WARNING: The User-Agent "Java/1.5.0_06" is unknown; creating an agent with null agent attributes.
Jun 8, 2010 12:42:21 AM oracle.adfinternal.view.faces.agent.AgentFactoryImpl _populateNullAgentImpl
WARNING: The User-Agent "Java/1.5.0_06" is unknown; creating an agent with null agent attributes.
Jun 8, 2010 12:42:21 AM oracle.adfinternal.view.faces.agent.AgentFactoryImpl _populateNullAgentImpl
WARNING: The User-Agent "Java/1.5.0_06" is unknown; creating an agent with null agent attributes.
1698656.832: [GC [PSYoungGen: 145280K->5811K(187264K)] 418915K->302441K(650112K), 0.1285455 secs]
Jun 8, 2010 12:42:22 AM oracle.adfinternal.view.faces.agent.AgentFactoryImpl _populateNullAgentImpl
WARNING: The User-Agent "Java/1.5.0_06" is unknown; creating an agent with null agent attributes.
Thanks,
Joe

Hi,
user agent is the browser users use. So what is the browser ?
Frank

Authorization issue with J2EE Policy Agent for AS7

Following the documentaion I have created a simple J2EE application with a servlet and 2 jsp's. The 2 JSP's customer.jsp and admin.jsp are mapped to /customer and /admin. The entire web application is subject to a filter like:
<filter>
<filter-name>Agent</filter-name>
<display-name>Agent</display-name>
<description>SunTM ONE Idenitity Server Policy Agent for SunTM ONE Application Server 7.0</description>
<filter-class>com.sun.amagent.as.filter.AgentFilter</filter-class>
</filter>
<filter-mapping>
<filter-name>Agent</filter-name>
<url-pattern>/*</url-pattern>
</filter-mapping>
The two resources /customer and /admin are subjected security constraints like:
<security-constraint>
<web-resource-collection>
<web-resource-name>col2</web-resource-name>
<url-pattern>/customer</url-pattern>
<http-method>GET</http-method>
<http-method>POST</http-method>
</web-resource-collection>
<auth-constraint>
<role-name>customer</role-name>
</auth-constraint>
<user-data-constraint>
<transport-guarantee>NONE</transport-guarantee>
</user-data-constraint>
</security-constraint>
The role-to-principal mapping is done in the sun-web.xml like:
<security-role-mapping>
<role-name>customer</role-name>
<group-name>customer</group-name>
<principal-name>amAdmin</principal-name>
</security-role-mapping>
<security-role-mapping>
<role-name>admin</role-name>
<group-name>admin</group-name>
<principal-name>amAdmin</principal-name>
</security-role-mapping>
Two roles 'customer' and admin are created via the identity server console and users are added to these roles.
The application deploys OK, when the app is accesed the user is redirected to the identity server and is authenticated fine. The user is directed to the main servlet and is allowed to access the the two jsp's. All is good till now, when the user access one these links say /customer, access is denied (403). The server logs prints out:
[21/May/2003:10:34:24] FINE ( 6036): servletPath = /customer
[21/May/2003:10:34:24] FINE ( 6036): pathInfo = null
[21/May/2003:10:34:24] FINE ( 6036): SingleSignOn[ids]: Process request for '/idssample/customer'
[21/May/2003:10:34:24] FINE ( 6036): SingleSignOn[ids]: Checking for SSO cookie
[21/May/2003:10:34:24] FINE ( 6036): SingleSignOn[ids]: SSO cookie is not present
[21/May/2003:10:34:24] FINE ( 6036): Authenticator[idssample]: Security checking request GET /idssample/customer
[21/May/2003:10:34:24] FINE ( 6036): Authenticator[idssample]: We have cached auth type PROGRAMMATIC for principal amAdmin
[21/May/2003:10:34:24] FINE ( 6036): Authenticator[idssample]: Checking constraint 'SecurityConstraint[col2]' against GET /customer --> false
[21/May/2003:10:34:24] FINE ( 6036): Authenticator[idssample]: Checking constraint 'SecurityConstraint[col2]' against GET /customer --> true
[21/May/2003:10:34:24] FINE ( 6036): Authenticator[idssample]: Subject to constraint SecurityConstraint[col2]
[21/May/2003:10:34:24] FINE ( 6036): Authenticator[idssample]: Calling checkUserData()
[21/May/2003:10:34:24] FINE ( 6036): Authenticator[idssample]: User data constraint has no restrictions
[21/May/2003:10:34:24] FINE ( 6036): Authenticator[idssample]: Calling authenticate()
[21/May/2003:10:34:24] FINE ( 6036): Authenticator[idssample]: User authentication is not required
[21/May/2003:10:34:24] FINE ( 6036): Authenticator[idssample]: Calling accessControl()
[21/May/2003:10:34:24] FINEST ( 6036): PRINCIPAL : amAdmin hasRole?: customer
[21/May/2003:10:34:24] FINEST ( 6036): PRINCIPAL TABLE: {}
[21/May/2003:10:34:24] FINE ( 6036): Authenticator[idssample]: Failed accessControl() test
[21/May/2003:10:34:24] WARNING ( 6036): CORE3283: stderr: <May 21, 2003 10:34:24 AM CDT> <Agent> <Info> AgentRealm.getGroupNames(amAdmin)
[21/May/2003:10:34:24] WARNING ( 6036): CORE3283: stderr: <May 21, 2003 10:34:24 AM CDT> <Agent> <Info> AgentRealm.getGroupNames(amAdmin) => java.util.Vector$1@bb60ad
Now, snooping around I have found that the AgentRealm.getGroupNames(userdn) does
return the correct grops viz. customer,admin,anyone.
PLEASE HELP

-- Second Update --
After policy installation I got several problems with PeopleSoft configuration. Which finally were solved.
1. Some URL's has to be defined as not enforced.
com.sun.am.policy.amFilter.notenforcedList[1]=/ps/images/*
com.sun.am.policy.amFilter.notenforcedList[2]=*.css
com.sun.am.policy.amFilter.notenforcedList[3]=*.ico
2. In versions older than PeopleSoft 8.4.2 the policy agent modified the file
/opt/fs/webserv/peoplesoft/applications/peoplesoft/PORTAL/WEB-INF/psftdocs/ps/configuration.properties to add the properties:
byPassSignon=TRUE
defaultUserid="DEFAULT_USER"
defaultPWD="your password"
signon_page=amsignin.html
signonError_page=amsignin.html
logout_page=amsignin.html
expire_page=amsignin.html
However, in the newer versions of PeopleSoft this properties are controled from the online Peoplesoft console. Which are set on:
PeopleTools --> WebProfile ---> WebProfileConfiguration --> [PROFILE] --> Security --> In section "Public Users" the parameters that has to be changed are:
Allow Public Access (cheked)
User ID : DEFAULT_USER
Password : your password
HTTP Session Inactivity : (SSO TIMEOUT)
and:
PeopleTools --> WebProfile ---> WebProfileConfiguration --> [PROFILE] --> Look and Feel -->
In section "SignOn/Logout" set the following values:
Signon Page : amsignin.html
Signon Error Page : amerror.html
Logout Page : amsignout.html
Note: After making any changes on the console; restart PIA (weblogic instance).
With this the SSO with PeopleSoft is working Ok.
Message was edited by:
LpzYlnd

Too Slow - Domino 6.5.4 with access manager agent 2.2 ?

I don't know how to tune Domino 6.5.4 with access manager agent 2.2?
I think AMAgent.properties is not good for SSO.
Please help me to tune it.
# $Id: AMAgent.properties,v 1.103 2005/09/19 22:08:34 madan Exp $
# Copyright ? 2002 Sun Microsystems, Inc. All rights reserved.
# U.S. Government Rights - Commercial software. Government users are
# subject to the Sun Microsystems, Inc. standard license agreement and
# applicable provisions of the FAR and its supplements. Use is subject to
# license terms. Sun, Sun Microsystems, the Sun logo and Sun ONE are
# trademarks or registered trademarks of Sun Microsystems, Inc. in the
# U.S. and other countries.
# Copyright ? 2002 Sun Microsystems, Inc. Tous droits r閟erv閟.
# Droits du gouvernement am閞icain, utlisateurs gouvernmentaux - logiciel
# commercial. Les utilisateurs gouvernmentaux sont soumis au contrat de
# licence standard de Sun Microsystems, Inc., ainsi qu aux dispositions en
# vigueur de la FAR [ (Federal Acquisition Regulations) et des suppl閙ents
# ? celles-ci.
# Distribu? par des licences qui en restreignent l'utilisation. Sun, Sun
# Microsystems, le logo Sun et Sun ONE sont des marques de fabrique ou des
# marques d閜os閑s de Sun Microsystems, Inc. aux Etats-Unis et dans
# d'autres pays.
# The syntax of this file is that of a standard Java properties file,
# see the documentation for the java.util.Properties.load method for a
# complete description. (CAVEAT: The SDK in the parser does not currently
# support any backslash escapes except for wrapping long lines.)
# All property names in this file are case-sensitive.
# NOTE: The value of a property that is specified multiple times is not
# defined.
# WARNING: The contents of this file are classified as an UNSTABLE
# interface by Sun Microsystems, Inc. As such, they are subject to
# significant, incompatible changes in any future release of the
# software.
# The name of the cookie passed between the Access Manager
# and the SDK.
# WARNING: Changing this property without making the corresponding change
# to the Access Manager will disable the SDK.
com.sun.am.cookie.name = iPlanetDirectoryPro
# The URL for the Access Manager Naming service.
com.sun.am.naming.url = http://sportal.yjy.dqyt.petrochina:80/amserver/namingservice
# The URL of the login page on the Access Manager.
com.sun.am.policy.am.login.url = http://sportal.yjy.dqyt.petrochina:80/amserver/UI/Login
# Name of the file to use for logging messages.
com.sun.am.policy.agents.config.local.log.file = c:/Sun/Access_Manager/Agents/2.2/debug/C__Lotus_Domino/amAgent
# This property is used for Log Rotation. The value of the property specifies
# whether the agent deployed on the server supports the feature of not. If set
# to false all log messages are written to the same file.
com.sun.am.policy.agents.config.local.log.rotate = true
# Name of the Access Manager log file to use for logging messages to
# Access Manager.
# Just the name of the file is needed. The directory of the file
# is determined by settings configured on the Access Manager.
com.sun.am.policy.agents.config.remote.log = amAuthLog.Dominoad.yjy.dqyt.petrochina.80
# Set the logging level for the specified logging categories.
# The format of the values is
#     <ModuleName>[:<Level>][,<ModuleName>[:<Level>]]*
# The currently used module names are: AuthService, NamingService,
# PolicyService, SessionService, PolicyEngine, ServiceEngine,
# Notification, PolicyAgent, RemoteLog and all.
# The all module can be used to set the logging level for all currently
# none logging modules. This will also establish the default level for
# all subsequently created modules.
# The meaning of the 'Level' value is described below:
#     0     Disable logging from specified module*
#     1     Log error messages
#     2     Log warning and error messages
#     3     Log info, warning, and error messages
#     4     Log debug, info, warning, and error messages
#     5     Like level 4, but with even more debugging messages
# 128     log url access to log file on AM server.
# 256     log url access to log file on local machine.
# If level is omitted, then the logging module will be created with
# the default logging level, which is the logging level associated with
# the 'all' module.
# for level of 128 and 256, you must also specify a logAccessType.
# *Even if the level is set to zero, some messages may be produced for
# a module if they are logged with the special level value of 'always'.
com.sun.am.log.level =
# The org, username and password for Agent to login to AM.
com.sun.am.policy.am.username = UrlAccessAgent
com.sun.am.policy.am.password = LYnKyOIgdWt404ivWY6HPQ==
# Name of the directory containing the certificate databases for SSL.
com.sun.am.sslcert.dir = c:/Sun/Access_Manager/Agents/2.2/domino/cert
# Set this property if the certificate databases in the directory specified
# by the previous property have a prefix.
com.sun.am.certdb.prefix =
# Should agent trust all server certificates when Access Manager
# is running SSL?
# Possible values are true or false.
com.sun.am.trust_server_certs = true
# Should the policy SDK use the Access Manager notification
# mechanism to maintain the consistency of its internal cache? If the value
# is false, then a polling mechanism is used to maintain cache consistency.
# Possible values are true or false.
com.sun.am.notification.enable = true
# URL to which notification messages should be sent if notification is
# enabled, see previous property.
com.sun.am.notification.url = http://Dominoad.yjy.dqyt.petrochina:80/amagent/UpdateAgentCacheServlet?shortcircuit=false
# This property determines whether URL string case sensitivity is
# obeyed during policy evaluation
com.sun.am.policy.am.url_comparison.case_ignore = true
# This property determines the amount of time (in minutes) an entry
# remains valid after it has been added to the cache. The default
# value for this property is 3 minutes.
com.sun.am.policy.am.polling.interval=3
# This property allows the user to configure the User Id parameter passed
# by the session information from the access manager. The value of User
# Id will be used by the agent to set the value of REMOTE_USER server
# variable. By default this parameter is set to "UserToken"
com.sun.am.policy.am.userid.param=UserToken
# Profile attributes fetch mode
# String attribute mode to specify if additional user profile attributes should
# be introduced into the request. Possible values are:
# NONE - no additional user profile attributes will be introduced.
# HTTP_HEADER - additional user profile attributes will be introduced into
# HTTP header.
# HTTP_COOKIE - additional user profile attributes will be introduced through
# cookies.
# If not within these values, it will be considered as NONE.
com.sun.am.policy.agents.config.profile.attribute.fetch.mode=NONE
# The user profile attributes to be added to the HTTP header. The
# specification is of the format ldap_attribute_name|http_header_name[,...].
# ldap_attribute_name is the attribute in data store to be fetched and
# http_header_name is the name of the header to which the value needs
# to be assigned.
# NOTE: In most cases, in a destination application where a "http_header_name"
# shows up as a request header, it will be prefixed by HTTP_, and all
# lower case letters will become upper case, and any - will become _;
# For example, "common-name" would become "HTTP_COMMON_NAME"
com.sun.am.policy.agents.config.profile.attribute.map=cn|common-name,ou|organizational-unit,o|organization,mail|email,employeenumber|employee-
number,c|country
# Session attributes mode
# String attribute mode to specify if additional user session attributes should
# be introduced into the request. Possible values are:
# NONE - no additional user session attributes will be introduced.
# HTTP_HEADER - additional user session attributes will be introduced into HTTP header.
# HTTP_COOKIE - additional user session attributes will be introduced through cookies.
# If not within these values, it will be considered as NONE.
com.sun.am.policy.agents.config.session.attribute.fetch.mode=NONE
# The session attributes to be added to the HTTP header. The specification is
# of the format session_attribute_name|http_header_name[,...].
# session_attribute_name is the attribute in session to be fetched and
# http_header_name is the name of the header to which the value needs to be
# assigned.
# NOTE: In most cases, in a destination application where a "http_header_name"
# shows up as a request header, it will be prefixed by HTTP_, and all
# lower case letters will become upper case, and any - will become _;
# For example, "common-name" would become "HTTP_COMMON_NAME"
com.sun.am.policy.agents.config.session.attribute.map=
# Response Attribute Fetch Mode
# String attribute mode to specify if additional user response attributes should
# be introduced into the request. Possible values are:
# NONE - no additional user response attributes will be introduced.
# HTTP_HEADER - additional user response attributes will be introduced into
# HTTP header.
# HTTP_COOKIE - additional user response attributes will be introduced through
# cookies.
# If not within these values, it will be considered as NONE.
com.sun.am.policy.agents.config.response.attribute.fetch.mode=NONE
# The response attributes to be added to the HTTP header. The specification is
# of the format response_attribute_name|http_header_name[,...].
# response_attribute_name is the attribute in policy response to be fetched and
# http_header_name is the name of the header to which the value needs to be
# assigned.
# NOTE: In most cases, in a destination application where a "http_header_name"
# shows up as a request header, it will be prefixed by HTTP_, and all
# lower case letters will become upper case, and any - will become _;
# For example, "common-name" would become "HTTP_COMMON_NAME"
com.sun.am.policy.agents.config.response.attribute.map=
# The cookie name used in iAS for sticky load balancing
com.sun.am.policy.am.lb.cookie.name = GX_jst
# indicate where a load balancer is used for Access Manager
# services.
# true | false
com.sun.am.load_balancer.enable = false
####Agent Configuration####
# this is for product versioning, please do not modify it
com.sun.am.policy.agents.config.version=2.2
# Set the url access logging level. the choices are
# LOG_NONE - do not log user access to url
# LOG_DENY - log url access that was denied.
# LOG_ALLOW - log url access that was allowed.
# LOG_BOTH - log url access that was allowed or denied.
com.sun.am.policy.agents.config.audit.accesstype = LOG_DENY
# Agent prefix
com.sun.am.policy.agents.config.agenturi.prefix = http://Dominoad.yjy.dqyt.petrochina:80/amagent
# Locale setting.
com.sun.am.policy.agents.config.locale = en_US
# The unique identifier for this agent instance.
com.sun.am.policy.agents.config.instance.name = unused
# Do SSO only
# Boolean attribute to indicate whether the agent will just enforce user
# authentication (SSO) without enforcing policies (authorization)
com.sun.am.policy.agents.config.do_sso_only = true
# The URL of the access denied page. If no value is specified, then
# the agent will return an HTTP status of 403 (Forbidden).
com.sun.am.policy.agents.config.accessdenied.url =
# This property indicates if FQDN checking is enabled or not.
com.sun.am.policy.agents.config.fqdn.check.enable = true
# Default FQDN is the fully qualified hostname that the users should use
# in order to access resources on this web server instance. This is a
# required configuration value without which the Web server may not
# startup correctly.
# The primary purpose of specifying this property is to ensure that if
# the users try to access protected resources on this web server
# instance without specifying the FQDN in the browser URL, the Agent
# can take corrective action and redirect the user to the URL that
# contains the correct FQDN.
# This property is set during the agent installation and need not be
# modified unless absolutely necessary to accommodate deployment
# requirements.
# WARNING: Invalid value for this property can result in the Web Server
# becoming unusable or the resources becoming inaccessible.
# See also: com.sun.am.policy.agents.config.fqdn.check.enable,
# com.sun.am.policy.agents.config.fqdn.map
com.sun.am.policy.agents.config.fqdn.default = Dominoad.yjy.dqyt.petrochina
# The FQDN Map is a simple map that enables the Agent to take corrective
# action in the case where the users may have typed in an incorrect URL
# such as by specifying partial hostname or using an IP address to
# access protected resources. It redirects the browser to the URL
# with fully qualified domain name so that cookies related to the domain
# are received by the agents.
# The format for this property is:
# com.sun.am.policy.agents.config.fqdn.map = [invalid_hostname|valid_hostname][,...]
# This property can also be used so that the agents use the name specified
# in this map instead of the web server's actual name. This can be
# accomplished by doing the following.
# Say you want your server to be addressed as xyz.hostname.com whereas the
# actual name of the server is abc.hostname.com. The browsers only knows
# xyz.hostname.com and you have specified polices using xyz.hostname.com at
# the Access Manager policy console, in this file set the mapping as
# com.sun.am.policy.agents.fqdn.map = valid|xyz.hostname.com
# Another example is if you have multiple virtual servers say rst.hostname.com,
# uvw.hostname.com and xyz.hostname.com pointing to the same actual server
# abc.hostname.com and each of the virtual servers have their own policies
# defined, then the fqdnMap should be defined as follows:
# com.sun.am.policy.agents.fqdn.map = valid1|rst.hostname.com,valid2|uvw.hostname.com,valid3|xyz.hostname.com
# WARNING: Invalid value for this property can result in the Web Server
# becoming unusable or the resources becoming inaccessible.
com.sun.am.policy.agents.config.fqdn.map =
# Cookie Reset
# This property must be set to true, if this agent needs to
# reset cookies in the response before redirecting to
# Access Manager for Authentication.
# By default this is set to false.
# Example : com.sun.am.policy.agents.config.cookie.reset.enable=true
com.sun.am.policy.agents.config.cookie.reset.enable=false
# This property gives the comma separated list of Cookies, that
# need to be included in the Redirect Response to Access Manager.
# This property is used only if the Cookie Reset feature is enabled.
# The Cookie details need to be specified in the following Format
# name[=value][;Domain=value]
# If "Domain" is not specified, then the default agent domain is
# used to set the Cookie.
# Example : com.sun.am.policy.agents.config.cookie.reset.list=LtpaToken,
# token=value;Domain=subdomain.domain.com
com.sun.am.policy.agents.config.cookie.reset.list=
# This property gives the space separated list of domains in
# which cookies have to be set in a CDSSO scenario. This property
# is used only if CDSSO is enabled.
# If this property is left blank then the fully qualified cookie
# domain for the agent server will be used for setting the cookie
# domain. In such case it is a host cookie instead of a domain cookie.
# Example : com.sun.am.policy.agents.config.cookie.domain.list=.sun.com .iplanet.com
com.sun.am.policy.agents.config.cookie.domain.list=
# user id returned if accessing global allow page and not authenticated
com.sun.am.policy.agents.config.anonymous_user=anonymous
# Enable/Disable REMOTE_USER processing for anonymous users
# true | false
com.sun.am.policy.agents.config.anonymous_user.enable=false
# Not enforced list is the list of URLs for which no authentication is
# required. Wildcards can be used to define a pattern of URLs.
# The URLs specified may not contain any query parameters.
# Each service have their own not enforced list. The service name is suffixed
# after "# com.sun.am.policy.agents.notenforcedList." to specify a list
# for a particular service. SPACE is the separator between the URL.
com.sun.am.policy.agents.config.notenforced_list = http://dominoad.yjy.dqyt.petrochina/*.nsf http://dominoad.yjy.dqyt.petrochina/teamroom.nsf/TROutline.gif?
OpenImageResource http://dominoad.yjy.dqyt.petrochina/icons/*.gif
# Boolean attribute to indicate whether the above list is a not enforced list
# or an enforced list; When the value is true, the list means enforced list,
# or in other words, the whole web site is open/accessible without
# authentication except for those URLs in the list.
com.sun.am.policy.agents.config.notenforced_list.invert = false
# Not enforced client IP address list is a list of client IP addresses.
# No authentication and authorization are required for the requests coming
# from these client IP addresses. The IP address must be in the form of
# eg: 192.168.12.2 1.1.1.1
com.sun.am.policy.agents.config.notenforced_client_ip_list =
# Enable POST data preservation; By default it is set to false
com.sun.am.policy.agents.config.postdata.preserve.enable = false
# POST data preservation : POST cache entry lifetime in minutes,
# After the specified interval, the entry will be dropped
com.sun.am.policy.agents.config.postcache.entry.lifetime = 10
# Cross-Domain Single Sign On URL
# Is CDSSO enabled.
com.sun.am.policy.agents.config.cdsso.enable=false
# This is the URL the user will be redirected to for authentication
# in a CDSSO Scenario.
com.sun.am.policy.agents.config.cdcservlet.url =
# Enable/Disable client IP address validation. This validate
# will check if the subsequent browser requests come from the
# same ip address that the SSO token is initially issued against
com.sun.am.policy.agents.config.client_ip_validation.enable = false
# Below properties are used to define cookie prefix and cookie max age
com.sun.am.policy.agents.config.profile.attribute.cookie.prefix = HTTP_
com.sun.am.policy.agents.config.profile.attribute.cookie.maxage = 300
# Logout URL - application's Logout URL.
# This URL is not enforced by policy.
# if set, agent will intercept this URL and destroy the user's session,
# if any. The application's logout URL will be allowed whether or not
# the session destroy is successful.
com.sun.am.policy.agents.config.logout.url=
#http://sportal.yjy.dqyt.petrochina/amserver/UI/Logout
# Any cookies to be reset upon logout in the same format as cookie_reset_list
com.sun.am.policy.agents.config.logout.cookie.reset.list =
# By default, when a policy decision for a resource is needed,
# agent gets and caches the policy decision of the resource and
# all resource from the root of the resource down, from the Access Manager.
# For example, if the resource is http://host/a/b/c, the the root of the
# resource is http://host/. This is because more resources from the
# same path are likely to be accessed subsequently.
# However this may take a long time the first time if there
# are many many policies defined under the root resource.
# To have agent get and cache the policy decision for the resource only,
# set the following property to false.
com.sun.am.policy.am.fetch_from_root_resource = true
# Whether to get the client's hostname through DNS reverse lookup for use
# in policy evaluation.
# It is true by default, if the property does not exist or if it is
# any value other than false.
com.sun.am.policy.agents.config.get_client_host_name = false
# The following property is to enable native encoding of
# ldap header attributes forwarded by agents. If set to true
# agent will encode the ldap header value in the default
# encoding of OS locale. If set to false ldap header values
# will be encoded in UTF-8
com.sun.am.policy.agents.config.convert_mbyte.enable = false
#When the not enforced list or policy has a wildcard '*' character, agent
#strips the path info from the request URI and uses the resulting request
#URI to check against the not enforced list or policy instead of the entire
#request URI, in order to prevent someone from getting access to any URI by
#simply appending the matching pattern in the policy or not enforced list.
#For example, if the not enforced list has the value http://host/*.gif,
#stripping the path info from the request URI will prevent someone from
#getting access to http://host/index.html by using the URL http://host/index.html?hack.gif.
#However when a web server (for exmample apache) is configured to be a reverse
#proxy server for a J2EE application server, path info is interpreted in a different
#manner since it maps to a resource on the proxy instead of the app server.
#This prevents the not enforced list or policy from being applied to part of
#the URI below the app serverpath if there is a wildcard character. For example,
#if the not enforced list has value http://host/webapp/servcontext/* and the
#request URL is http://host/webapp/servcontext/example.jsp the path info
#is /servcontext/example.jsp and the resulting request URL with path info stripped
#is http://host/webapp, which will not match the not enforced list. By setting the
#following property to true, the path info will not be stripped from the request URL
#even if there is a wild character in the not enforced list or policy.
#Be aware though that if this is set to true there should be nothing following the
#wildcard character '*' in the not enforced list or policy, or the
#security loophole described above may occur.
com.sun.am.policy.agents.config.ignore_path_info = false
# Override the request url given by the web server with
# the protocol, host or port of the agent's uri specified in
# the com.sun.am.policy.agents.agenturiprefix property.
# These may be needed if the agent is sitting behind a ssl off-loader,
# load balancer, or proxy, and either the protocol (HTTP scheme),
# hostname, or port of the machine in front of agent which users go through
# is different from the agent's protocol, host or port.
com.sun.am.policy.agents.config.override_protocol =
com.sun.am.policy.agents.config.override_host =
com.sun.am.policy.agents.config.override_port =
# Override the notification url in the same way as other request urls.
# Set this to true if any one of the override properties above is true,
# and if the notification url is coming through the proxy or load balancer
# in the same way as other request url's.
com.sun.am.policy.agents.config.override_notification.url =
# The following property defines how long to wait in attempting
# to connect to an Access Manager AUTH server.
# The default value is 2 seconds. This value needs to be increased
# when receiving the error "unable to find active Access Manager Auth server"
com.sun.am.policy.agents.config.connection_timeout =
# Time in milliseconds the agent will wait to receive the
# response from Access Manager. After the timeout, the connection
# will be drop.
# A value of 0 means that the agent will wait until receiving the response.
# WARNING: Invalid value for this property can result in
# the resources becoming inaccessible.
com.sun.am.receive_timeout = 0
# The three following properties are for IIS6 agent only.
# The two first properties allow to set a username and password that will be
# used by the authentication filter to pass the Windows challenge when the Basic
# Authentication option is selected in Microsoft IIS 6.0. The authentication
# filter is named amiis6auth.dll and is located in
# Agent_installation_directory/iis6/bin. It must be installed manually on
# the web site ("ISAPI Filters" tab in the properties of the web site).
# It must also be uninstalled manually when unintalling the agent.
# The last property defines the full path for the authentication filter log file.
com.sun.am.policy.agents.config.iis6.basicAuthentication.username =
com.sun.am.policy.agents.config.iis6.basicAuthentication.password =
com.sun.am.policy.agents.config.iis6.basicAuthentication.logFile = c:/Sun/Access_Manager/Agents/2.2/debug/C__Lotus_Domino/amAuthFilter

Hi,
I installed opensso (so Sun Java(TM) System Access Manager 7.5) and the agent for Domino 6.5.4 and I have the message in logs "amAgent"
2007-07-11 18:40:16.119 Error 1708:3dbcf768 PolicyAgent: render_response(): Entered.
I have the box to identify but it doesnot connect me on my opensso server.
It still identify with Domino's server
Thanks for your response
Thomas

SNMP integration with ISE 1.2

Hi Guys,
Did anyone have a hard time integrating ISE 1.2 with SNMP server for polling system parameters? I'm trying to add ISE 1.2.1 to solarwinds SNMP server but when adding the required parameters like IP address and community string and doing an SNMP test connection it returns a failure message. SNMP configuration on ISE is quit simple. Only two commands are needed which are the SNMP server IP and community string values. Searching on the web, i saw a bug CSCun42967 that documents SNMP problems with ISE 1.2. Could that be the problem? or if there is any limitations for this integration?
Thanks,
Mohammad

Here is the helpful link :
https://www.cisco.com/en/US/docs/security/ise/1.0/user_guide/ise10_sw_cnfg.pdf

Help required regarding Integrating Conversion Agent with SAP-XI

I want to run a simple File to File scenario which involves integrating conversion
agent. I gone through a webblog:Integrate SAP Conversion Agent by Itemfield with SAP XI
I deployed the module and I configured the channel in the same way what was specified in the webblog.
But when I run my scenario I found CM_TRANSFORMATION_ERROR as the error in communication channel monitoring.
Can u please provide me the solution for correcting the above error, this would be a great help for me..

HI,
see the below links
http://help.sap.com/saphelp_nw04/helpdata/en/43/6f1f39a08e6fcae10000000a1553f6/CMSUserGd.pdf
http://help.sap.com/saphelp_nw04/helpdata/en/ee/c9f0b4925af54cb17c454788d8e466/frameset.htm - cc
http://help.sap.com/saphelp_erp2005vp/helpdata/en/95/bb623c6369f454e10000000a114084/content.htm - fcc cOUNTER
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/da1e7c16-0c01-0010-278a-eaed5eae5a5f - conversion agent
with item fiels.
Regards
Chilla

ApplicationUnderTest.CloseOnPlaybackCleanup property doesn't work as intended with MS Test Agent 2010

Hi All,
I launch the application which I need to test by using ApplicationUnderTest.Launch() method and I need to keep the application open for the rest of the tests so I tried to set ApplicationUnderTest.CloseOnPlaybackCleanup = false to achieve that.
1) I use MS Test Agent 2010 to run my Coded UI Tests in a server machine and without running tests it threw an error which said "Method not found: 'Void Microsoft.VisualStudio.TestTools.UITesting.ApplicationUnderTest.set_CloseOnPlaybackCleanup(Boolean)".
Then I replaced UITesting.dll in the server machine with the one used by Visual Studio 2010 SP 1 which is located in my machine. Then it started to run tests.
2) Even though I have set ApplicationUnderTest.CloseOnPlaybackCleanup = false Coded UI Test closes the application at the end of the test which was really strange. It sounds like that disregard
of the value I have set, CUIT always close the application when running with MS Test Agent.
3) Then I noticed that on my machine it happens completely other way around most of the time. Irrelevant of the value it always keep the application open after the test. Which means even I set ApplicationUnderTest.CloseOnPlaybackCleanup = true that
will keep open the application. But if I can remember correctly this didnt happen when I first tried this approach, it worked perfectly.
Is this a a bug that should be fixed? Or am I missing something obvious?
Thanks in advance,
/Rakitha

Hi Rakitha,
As far as I know, this issue has been resolved in VS2012.
http://blogs.msdn.com/b/visualstudioalm/archive/2012/11/08/using-same-applicationundertest-browserwindow-across-multiple-tests.aspx
Best Regards,
Jack
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Issue with re-skilling agents in bulk

We tried to re-skill about 30 agents in bulk and change the competence level at the same time. Uccx took the change but, we noticed that agents were in a ready state even with calls were in the queue.
We went back and one by one re-skilled them again and at that point I'm told it worked...agents received calls.
Anyone ever had any issues with re-skilling agents in bulk?
We are on UCCX 8.5.1 SU3
Thanks,
Dan

Hi PARADOX-RED,
Based on the error messages that you provided, please remove the connector software from Control Panel completely. Then, in the problematic computer, please locate
to: Control Panel-> System-> select Change settings. And select the Computer Name tab in the System Properties dialog box, click
change button. Then in the Computer Name/Domain Changes dialog box, please take the computer out of the domain as a workgroup, and rejoin in new domain.
Please check if this issue can be solved. If it still exists, please don’t hesitate to let me know.
Hope this helps.
Best regards,
Justin Gu

Weblogic SNMP Agent with WindowsNT SNMP Agent

Similar Messages

Maybe you are looking for