Cluster agent for DSEE 7.0

Hi,
I see in the DSEE 7.0 released notes that the Solaris Cluster agent has been removed from the DSEE 7.0 distribution. Where can I find a cluster agent for 7.0?
Thanks.

Hi,
To access Reporting Agent or in BI 7.0 type REPORTING_AGENT
GoTo T-Code RSA1OLD -> Click Reporting Agent-> Click Print :This will show all the query and reports
Drill down to a particular Report
-> HighLight this report
-> Create New Reporting Agent Setting
-> Give name & Description
-> Check Fill OLAP Cache if possible
->Save and Activaate
->Go Back : You will see one Reporting Agent create
-> Select the newly created Reporting Agent
-> on the Right Hand side Column
->Create New Scheduling Package by clicking on Create Button
-> Give name and Description
->Save
Now Drag the Reporting Agent to the right Hand side the Scheduling Package Windows.
->Save.
->Schedule Immediately.
http://help.sap.com/saphelp_nw70/helpdata/en/28/734d3caa70ea6fe10000000a114084/content.htm
But, I would suggest to use Information broadcasting instead of Reporting agent.
hope this helps...
Sonal...
Edited by: Sonal Patel on Dec 11, 2009 11:36 AM

Similar Messages

Need input on developing cluster agent for java application

I am new to Sun Cluster and i wanted to develop agent for failover for one of my Java application which sits on one of the node of sun cluster 3.1. Can you guys help me in this.
My Java application is based on n-tier client server model. and this needs to failover.
I have two sun machine having solaris 9, which is clustered with 3.1 sun cluster software.
As i know there are two mwthods for developing the agent for your application.
1) Generic Data services
2) Sun Plex agent builder
i wanted to use Sunplex agent builder with Ksh. Can you please tell me what all things required for starting it and how do i proceed.
thanks in advance.

Using GDS will be the simplest solution.
You can write atleast one script - to start application:
say '/MYAPP/start'
This script can setup JAVA_HOME and other environment variables and start the application in background.
# scrgadm -a -t SUNW.gds
# scrgadm -a -g rg1
# scrgadm -a -L -g rg1 -l hhead
# scrgadm -a -t SUNW.gds -g rg1 -j app-rs \
-x Start_command="/MYAPP/start"
# scswitch -Z -g rg1
# scstat -g
Refer to GDS man page http://docs.sun.com/app/docs/doc/819-0582/6n30g7il4?q=GDS+&a=view
and Data services developer's guide http://docs.sun.com/app/docs/doc/819-0581/6n30f91v4?a=view
If you want custome probe or you want to stop application gracefully, then you can write stop and probe scripts and provide them in 'scrgadm' command as described in SUNW.gds man page.
If you want to productize the agent, then you can consider using agent builder.

SUN cluster 3.1 Agent for Siebel Server

Hi All
I dont have the CD for the Sun Cluster 3.1 agent . Please suggest me a link from where i can download the agent for Sun HA For Siebel Server,
Thanks/Regards

Hi,
the agent should be part of the latest JAS release, which is SC3.1 8/05.
Mark the Java Availability Suite checkbox on
www.sun.comhttp://www.sun.com/software/swportfolio/get.jsp
and hit "Get downloads". That should lead you to the download section.
Regards
Hartmut

How to set property for Cluster Environment for JMS Adapter

Hi All,
I am moving from DEV to Prod environment which is cluster.
Can you Please explain me what property I need to Set for Cluster Environment for JMS Adapter, so that I could avoid race condition for Dequeue/enqueue.
I am using soa suite 10.1..3.4
Thanks in Advance.
Edited by: vikky123 on Jul 12, 2010 7:03 AM

put something like this
<activationAgents>
      <activationAgent className="oracle.tip.adapter.fw.agent.jca.JCAActivationAgent" partnerLink="PARNERLINKNAME">
        <property name="clusterGroupId">SOMEUNIQUEVALUE</property>
        <property name="portType">PARTNERLINK_PORTTYPE</property>
      </activationAgent>
    </activationAgents>

Converting Standalone Agents to CLuster Agents

Greetings,
I have been reading about converting STandalone Agents to Cluster Agents and again am suffering a bit of confusion. Using the Enterprise Manager 12c Upgrade Console to upgrade from 11g to 12c via the 2-System method I have deployed and configured some agents on clusters. I do not know how all of the agents on these clusters were originally installed. After deploying, when converting the 12c agents I did specify the related targets for the clusters.
My question is whether or not the agents on these clusters is indeed configured correctly for a clustered environment. This is based on the fact that some appear to behave incorrectly (status pending is one issue). Is there a way from within the 12c console (or any other way) to determine if these agents are in fact properly configured for a clustered environment? My initial hope was that they would have been but given some of the differences between 11g and 12c I would like to verify that.
I would appreciate knowing if that is possible.
Thank you.
Bill Wagman

Hi Bill,
In 12c, there are no special settings or steps for deploying agents to a cluster. You simply deploy an agent to every node of the cluster, just like you would on an individual server. Once the agent is deployed, the data collected about these nodes will be used to construct the cluster targets in EM. Unfortunately, any issues with data collections or dynamic properties or associations, etc can cause these clusters or its nodes to show incorrect status, or not be formed as complete targets.
Best to file an SR and have support look at your environment.

Tmboot fails started by a Sun Cluster Agent (Data Service)

Hi,
we are using TUXEDO 6.5 in conjunction with ADC's Singl.eView.
Starting TUXEDO by calling tmboot -y works fine in the command prompt.
Starting TUXEDO within a Sun Cluster Agent, which internaly calls tmboot -y as
well, fails with the foolowing error messages:
004859.lbgas1!GWTDOMAIN.5762: 08022002: TUXEDO Version 6.5 SunOS 5.5.1 Generic_103640-29
sun4u sparc SUNW,Ultra-1.
004859.lbgas1!GWTDOMAIN.5762: LIBTUX_CAT:262: INFO: Standard main starting
004901.lbgas1!GWTDOMAIN.5762: LIBGWT_CAT:1223: WARN: Reach system open max(0)
limit
004901.lbgas1!GWTDOMAIN.5762: LIBGWT_CAT:1122: ERROR: Unable to allocate free
fd structure
004901.lbgas1!GWTDOMAIN.5762: LIBGWT_CAT:1124: ERROR: Unable to open listening
endpoint
004901.lbgas1!GWTDOMAIN.5762: LIBTUX_CAT:250: ERROR: tpsvrinit() failed
ubbconfig entries for GWTDOMAIN:
GWTDOMAIN SRVGRP="GWADMGROUP" SRVID=2
REPLYQ = N
RESTART = Y
GRACE = 0
MAXGEN = 5
CLOPT = ""
RQADDR = "GWADMGROUP"
What configuration do I have to change, a TUXEDO one or Sun ?
Can I drop an application server in ubbconfig ?
Lutz

Patch #232, CR041488 seems to address this:
GWTDOMAIN connection problem when maxfiles kernel parm set > 32K
Perhaps the Cluster Agent sets a higher ulimit when it runs.
See if you are running the latest patch.
Scott Orshan
Lutz wrote:
>
Hi,
we are using TUXEDO 6.5 in conjunction with ADC's Singl.eView.
Starting TUXEDO by calling tmboot -y works fine in the command prompt.
Starting TUXEDO within a Sun Cluster Agent, which internaly calls tmboot -y as
well, fails with the foolowing error messages:
004859.lbgas1!GWTDOMAIN.5762: 08022002: TUXEDO Version 6.5 SunOS 5.5.1 Generic_103640-29
sun4u sparc SUNW,Ultra-1.
004859.lbgas1!GWTDOMAIN.5762: LIBTUX_CAT:262: INFO: Standard main starting
004901.lbgas1!GWTDOMAIN.5762: LIBGWT_CAT:1223: WARN: Reach system open max(0)
limit
004901.lbgas1!GWTDOMAIN.5762: LIBGWT_CAT:1122: ERROR: Unable to allocate free
fd structure
004901.lbgas1!GWTDOMAIN.5762: LIBGWT_CAT:1124: ERROR: Unable to open listening
endpoint
004901.lbgas1!GWTDOMAIN.5762: LIBTUX_CAT:250: ERROR: tpsvrinit() failed
ubbconfig entries for GWTDOMAIN:
GWTDOMAIN SRVGRP="GWADMGROUP" SRVID=2
REPLYQ = N
RESTART = Y
GRACE = 0
MAXGEN = 5
CLOPT = ""
RQADDR = "GWADMGROUP"
What configuration do I have to change, a TUXEDO one or Sun ?
Can I drop an application server in ubbconfig ?
Lutz

Sun Cluster dataservice for Webspher MQ

Is Sun Cluster dataservice for Websphere MQ available for
Sun Cluster 3.0?
Should a Sun Cluster 3.0 be upgraded to 3.1 in order to install the Websphere MQ dataservice?
Thanks in advance.

The Sun Cluster dataservice for WebSphere MQ is available for SC3.0 update 3 onwards.
However the agent is only distributed on the SC3.1 Agents CD, please contact Sun for the CD or Agent.
Updating to SC3.1 is not required. MQ 5.2/5.3 are supported, although only MQ 5.2 on Solaris 8, with MQ 5.3 on either Solaris 8 or 9.
Regards
Neil

IPlanet Agent for VCS detects bogus OFFLINE

We've been running iMS 5.2 since November 2004, and it's been working just fine. Today, though, we saw the service group failover because the iPlanet agent detected an OFFLINE Msg resource. That offline status wasn't reflected in the logs, though. What was reported in the veritas logs though was the output of the clean operation. That showed all the processes being shut down normally, and successfully. Which means they must have been running before the clean. So why did the iPlanet MS agent report an offline?
Now, ultimate strangeness. When the service group failed over, none of the processes were started for iMS. All the other resources were there - IP, Disk Group, Volumes, Mount Points, everything. Yet the iMS resource simply failed to start any processes. Starting the processes manually using start-msg <list of services> (start-msg on its own refuses to run because of the HA environment) and flushing/probing the group/resource made no difference whatsoever. The cluster now thinks the resource is offline, despite the running processes and happy users.
Anybody got any ideas why the agent might suddenly cr4p itself and start reporting bogus offline faults?
We're running iMS 5.2 Patch 2 on a VCS3.5 cluster under Solaris 8.

We do have an internal whitepaper that is titled, "how to get Cluster to tell you why it failed over". . . .
Currently the iMS cluster agent treats all of iMS as one component. If it finds a problem with any part of iMS, its recourse is to restart all of iMS. Also, by default, the log level is such that you get no info about what the problem was or even what component had the problem.
If you have any case where you need to follow the instructions below, please add the the customer to bug 4919531.
First step: enable the debug logging
Subject: Re: iMS failover/restart on cluster
Date: Fri, 10 Jan 2003 13:17:21 -0500 (EST)
Customer reports, "iMS restarted all by itself".
How can we make the cluster tell us what component of iMS failed???About the only additional info you can get besides the iMS logs would be
in syslog. You can turn on extra debug as described on:
<< an internal web page, for Suncluster, anyway >>
Note: iMS needs daemon.debug (it's in the fine print).
HTH,
Rich
Second step: look at the normal iMS logs
If there was a problem with some component of iMS, there should be some indication in some iMS log file. While it would be nice if the cluster agent would give some hint about where to start looking, we can still start by looking at all the normal iMS log files and see if they indicate any problem. They may not. The problem may be with the overall system or something configured incorrectly about the cluster or the iMS agent. But you need to start by looking at the normal iMS log files.

Agents for database and application servers

hi all,
I have to go to a client site this week to install Gagents onto some database servers, some will be RAC and some application servers. it is on AIX. are there different agents for database and applications? In a RAC cluster do I need an agent per node?
rgds
alan

When installing agents in a cluster (read - RAC), during the installation, on one of the screens, you will have the option of picking up all the nodes in the cluster. Else, if you are using a push or agent deploy method, you just have to pass the correct flag (can't remember) and then list all the nodes in the cluster.
To your other questions, you do not need different agents for database, and app servers etc. The only time you would need different agents is when you are installing on different platforms.

How to use scheduled agent for query in database

Hi there I'm working with database on my app and when use the query for search in the database the application freeze for a maximum of one minute I want change that why I want what runs ok and I wonder if I can use a background agent for do that manage
the queries .
But I don't know how can I call the queries from the other project if the files are in the main project.

Hi OzkarLeo,
Background task provides functionality to do work when your app not in foreground, it need some conditions to trigger.
https://msdn.microsoft.com/en-us/library/windows/apps/xaml/Hh977056(v=win.10).aspx. If you need scheduled query when app is active in foreground, then it’s no need to use background task.
Regards,
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.

No log for am policy agent for iis6

Hello!
Im trying to get Policy Agent for IIS to run on my Win Srv 2003 with IIS6 and Sharepoint Services.
I am running the OpenSSO version of Access Manager.
I have installed the agent and done the initial cofiguration.
When i try to browse the resource i get a login prompt (IIS Basic Auth)and cannot login followed by "Not Authorized 401.3"
I should get redirected to the AM Login page, shouldn't I?
I tried to look for answers in the log file but the /debug/<id> directory i empty.
Anyone know what to do?
The amAgent.properties file:
# $Id: AMAgent.properties,v 1.103 2005/09/19 22:08:34 madan Exp $
# 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://login.lta.mil.se:8080/opensso/namingservice
# The URL of the login page on the Access Manager.
com.sun.am.policy.am.login.url = http://login.lta.mil.se:8080/opensso/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/Identifier_1414639615/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.sharepoint.lta.mil.se.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 = 5
# The org, username and password for Agent to login to AM.
com.sun.am.policy.am.username = UrlAccessAgent
com.sun.am.policy.am.password = PN4rEZ1uhx1404ivWY6HPQ==
# Name of the directory containing the certificate databases for SSL.
com.sun.am.sslcert.dir = C:/Sun/Access_Manager/Agents/2.2/iis6/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://sharepoint.lta.mil.se: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|organiz ational-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_BOTH
# Agent prefix
com.sun.am.policy.agents.config.agenturi.prefix = http://sharepoint.lta.mil.se: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 = sharepoint.lta.mil.se
# 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 = SERVER_PROTO://SERVER_HOST:SERVER_PORTSERVER_DEPLOY_URI/UI/* SERVER_PROTO://SERVER_HOST:SERVER_PORTCONSOLE_DEPLOY_URI/* SERVER_PROTO://SERVER_HOST:SERVER_PORTSERVER_DEPLOY_URI/login_images/* SERVER_PROTO://SERVER_HOST:SERVER_PORT/docs* SERVER_PROTO://SERVER_HOST:SERVER_PORTSERVER_DEPLOY_URI/namingservice SERVER_PROTO://SERVER_HOST:SERVER_PORTSERVER_DEPLOY_URI/sessionservice SERVER_PROTO://SERVER_HOST:SERVER_PORTSERVER_DEPLOY_URI/loggingservice SERVER_PROTO://SERVER_HOST:SERVER_PORTSERVER_DEPLOY_URI/profileservice SERVER_PROTO://SERVER_HOST:SERVER_PORTSERVER_DEPLOY_URI/policyservice SERVER_PROTO://SERVER_HOST:SERVER_PORTSERVER_DEPLOY_URI/config* SERVER_PROTO://SERVER_HOST:SERVER_PORTSERVER_DEPLOY_URI/js/* SERVER_PROTO://SERVER_HOST:SERVER_PORTSERVER_DEPLOY_URI/css/* SERVER_PROTO://SERVER_HOST:SERVER_PORTSERVER_DEPLOY_URI/authservice SERVER_PROTO://SERVER_HOST:SERVER_PORTSERVER_DEPLOY_URI/SAMLAwareServlet SERVER_PROTO://SERVER_HOST:SERVER_PORTSERVER_DEPLOY_URI/SAMLSOAPReceiver SERVER_PROTO://SERVER_HOST:SERVER_PORTSERVER_DEPLOY_URI/SAMLPOSTProfileServlet
# 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=
# 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 = true
# 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 = true
# 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/Identifier_1414639615/amAuthFilter

If the agent doesnot start properly you would always get redirected to com.sun.am.policy.agents.config.accessdenied.url , if thats not specified you will get a 403.
For the agent itself check that the naming.url is correct. the agent username and passwords are correct, and see that the user has priviledges to write to the agent log files. Apart from these post the windows event logs.

Does the 2.1 web policy agent for Windows 2003 work on a 64 bit OS ?

Does the 2.1 web policy agent for Windows 2003 work on a 64 bit OS ?
I have a customer having a world of issues getting the agent to start.
Jeff Courtade

No. 64bit support is not there for 2.1 agents on Windows.
-Subba

How to run multiple CodedUI Ordered Tests over multiple Test Agents for parallel execution using Test Controller

we are using VS 2013, I need to run multiple Coded UI Ordered Tests in parallel on different agents.
My requirement :
Example: I have 40 Coded UI Test scripts in single solution/project. i want to run in different OS environments(example 5 OS ). I have created 5 Ordered tests with the same 40 test cases.
I have one Controller machine and 5 test agent machines. Now I want my tests to be distributed in a way that every agent gets 1 Ordered test to execute.
Machine_C = Controller (Controls Machine_1,2,3,4,5)
Machine_1 = Test Agent 1 (Should execute Ordered Test 1 (ex: OS - WIN 7) )
Machine_2 = Test Agent 2 (Should execute Ordered Test 2 (ex:
OS - WIN 8) )
Machine_3 = Test Agent 3 (Should execute Ordered Test 3
(ex: OS - WIN 2008 server) )
Machine_4 = Test Agent 4 (Should execute Ordered Test 4 (ex:
OS - WIN 2012 server) )
Machine_5 = Test Agent 5 (Should execute Ordered Test 5 (ex:
OS - WIN 2003 server) )
I have changed the “MinimumTestsPerAgent” app setting value
as '1' in controller’s configuration file (QTController.exe.config).
When I run the Ordered tests from the test explorer all Test agent running with each Ordered test and showing the status as running. but with in the 5 Test Agents only 2 Agents executing the test cases remaining all 3 agents not executing the test cases but
status showing as 'running' still for long time (exp: More then 3 hr) after that all so its not responding.
I need to know how I can configure my controller or how I can tell it to execute these tests in parallel on different test agents. This will help me reducing the script execution time.
I am not sure what steps I am missing.
It will be of great help if someone can guide me how this can be achieved.
-- > One more thing Can I Run one Coded UI Ordered Test on One Specific Test Agent?
ex: Need to run ordered Test 1 in Win 7 OS (Test Agent 1) only.
Thanks in Advance.

Hi Divakar,
Thank you for posting in MSDN forum.
As far as I know, we cannot specify coded UI ordered test run on specific test agent. And it is mainly that test controller determine which coded UI ordered test assign to which test agent.
Generally, I know that if we want to run multiple CodedUI Ordered Tests over multiple Test Agents for parallel execution using Test Controller.
We will need to change the MinimumTestsPerAgent property to 1 in the test controller configuration file (QTControllerConfig.exe.config) as you said.
And then we will need to change the bucketSize number of tests/number of machines in the test settings.
For more information about how to set this bucketSize value, please refer the following blog.
http://blogs.msdn.com/b/aseemb/archive/2010/08/11/how-to-run-automated-tests-on-different-machines-in-parallel.aspx
You can refer this Jack's suggestion to run your coded UI ordered test in lab Environment or load test.
https://social.msdn.microsoft.com/Forums/vstudio/en-US/661e73da-5a08-4c9b-8e5a-fc08c5962783/run-different-codedui-tests-simultaneously-on-different-test-agents-from-a-single-test-controller?forum=vstest
Best Regards,
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.

How to setup the cluster environment for BPM using weblogic

want to setup the cluster environment for BPM using weblogic....
i have installed the oracle weblogic server 10gr3 and oracle BPM enterprise for weblogic 10gR3
i have used the Admin tools from the "oracle BPM enterprise for weblogic" to setup the configuration and create the weblogic domain servers.
i can launch the process administrator and import the project exp file to domain server.
but what should i do to setup cluster environment using weblogic?
what i want to do is :
setup one admin machine..
setup two product machine..
enable the cluster so the admin machine can monitor the status of the product machine..
thanks a lot ...

The install guide at http://download-llnw.oracle.com/docs/cd/E13154_01/bpm/docs65/config_guide/index.html gives a reasonable amount of info on how to do this.
Personally I have not used the OBPM option to configure WebLogic instead I've used the information in the above install guide to create the weblogic domain in advance of configuring OBPM.
Once you've setup WebLogic configure OBPM using the values I mention in the following thread: How to set the JMX Engine parameter in Process Administation?
Let me know any specific config questions and I'll do my best to answer them for you.
Thanks,
Mike

Examples.cluster.rmi for WebLogic Server 11g

How can I get package examples.cluster.rmi for WebLogic Server 11g?
I would like to perform a similiar test like the following:
https://freepaper.taichung.gov.tw/examplesWebApp/examples/src/examples/cluster/rmi/package-summary.html
Thanks a lot

Hi,
I have just now installed WLS via the net installer, and the default examples server password of welcome1 does indeed work for me.
However, I note from your post that you are using port 7101, not 7001. Could that be the issue?
http://localhost:7101/console/login/LoginForm.jspKevin

Cluster agent for DSEE 7.0

Similar Messages

Maybe you are looking for