Documentation for Session Release Agent

Hi Experts,
I am searching for a deep documentation to the session release agent and/or the DSM-Component.
I have found some infromation in various OSS-Notes:
     SAP Note: 755947
     SAP Note: 1031159
and
     SAP Note: 892250
     SAP Note: 596698
But it seems to mee that an overall documentation is missing. (Actually I think I have read about it some time ago on help.sap.com but I cannot find it any more after some time of deeply searching...)
I found the following tool:
http://<HOST>:<PORT>/irj/servlet/prt/portal/prteventname/HtmlbEvent/prtroot/com.sap.portal.dsm.MonitorStoreGroups
But I can not fully understand the information there.
Does anybody knows exactly what and how I can work with it?
Do you have any information about the SRA or DSM and what and how you can configure it?
Can you please at least send me a link where the basic concepts are described (on help.sap.com I know it was there
Thanks and best regards,
Stefan Brauneis

Hi,
check below help link
http://help.sap.com/saphelp_nw04/helpdata/en/ca/a9a7408f031414e10000000a1550b0/frameset.htm
Koti Reddy

Similar Messages

HELP - Where to find BEA products documentations for earlier releases

HELP - Now that the BEA website is no longer available, where can someone find BEA's products documentations for earlier releases than the latest 10g versions of all products? (such as Tuxedo 8.1..., WebLogic 8.1... etc...)?

Hello,
The edocs site was temporarily unavailable while we worked through some technical issues.
edocs.com is now available. Thank you for your patience.
Regards,
Sabrina M. Reynoso
Sr. Product Manager - Oracle WebLogic Server

HANA documentation for old releases

Hi All,
At http://help.sap.com/hana_platform, I can only find the documentation for the recent HANA release.
Currently, I'am looking for Release Notes of older HANA Releases. Is there some kind of archive, where I can access them?
Thanks and Regards,
Steve

As it is written on the very page you mentioned:
"Note: The full documentation set for this and older support package stacks of the SAP HANA platform is available on SAP Service Marketplace ."
- Lars

Bad console export, worse documentation for session replication setup

Hi,
I'm having problem configuring config.xml/weblogic.xml to get in-memory session rep going for WL 6.0
sp1.
I already have everything up and running in 5.1 sp8; so I figure I can just export my
weblogic.properties settings to 6.0's config.xml via the console, right? Well, here's my original
properties:
weblogic.httpd.session.enable=true
weblogic.httpd.session.cookies.enable=true
weblogic.httpd.session.timeoutSecs=10000
weblogic.httpd.session.cookie.comment="Kiko session tracking cookie"
weblogic.httpd.session.cookie.domain=.kikotest.com
weblogic.httpd.session.cookie.maxAgeSecs=-1
weblogic.httpd.session.persistence=true
weblogic.httpd.session.cacheEntries=1024
weblogic.httpd.session.persistentStoreType=replicated
When I use the console export tool, I find NONE of these settings in config.xml!!! So I look
through the docs to see if I can do this manually, and the documents are just as confusing! This
mapping table:
http://e-docs.bea.com/wls/docs60///////config_xml/properties.html#1152226
seem to suggest that each session flag from weblogic.properties is mapped to two corresponding flags
in config.xml and weblogic.xml (e.g. persistentStoreType -> (config.xml) SessionPersistentStoreType
& (weblogic.xml) PersistentStoreType). Does this mean I have to set the flags for BOTH files? Or
just one? Which one???
As for config.xml flags which have "N/A" in the "Console Label" column, does this mean I just add
this flag as a top-most label, like:
<SessionPersistentStoreType>replicated</SessionPersistentStoreType>
And to further add to the confusion, when I look at the document for "Configuring In-Memory HTTP
Replication in a Cluster" http://e-docs.bea.com/wls/docs60/cluster/servlet.html#1009453, it tells me
to "set the property PersistentStoreType to replicated in the Web Application deployment descriptor,
web.xml."? I thought it was weblogic.xml???
I think all of these confusions can easily be alleviated by fixing any one of the following, if not
all three:
1) /console export of weblogic.properties to config.xml needs to translate these session flags
2) /console needs to have access to these session flags so we don't have to poke around config.xml!
3) Documents need to be less ambiguous about how to set these flags
Gene

Hi Gene,
I believe the documentation is incorrect - sessionPersistentStoreTyped doesn't need to be set in the
config.xml file (I don't believe this tag still exists). The file name should be weblogic.xml and has
the following general form:
<!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application 6.0//EN"
"http://www.bea.com/servers/wls600/dtd/weblogic-web-jar.dtd">
<weblogic-web-app>
... other stuff from the dtd if you like
<session-descriptor>
<session-param>
<param-name>PersistentStoreType</param-name>
<param-value>replicated</param-value>
</session-param>
</session-descriptor>
</weblogic-web-app>
weblogic.xml goes in the WEB-INF directory in your war file.
Hope this helps,
Glen
Gene Chuang wrote:
Hi,
I'm having problem configuring config.xml/weblogic.xml to get in-memory session rep going for WL 6.0
sp1.
I already have everything up and running in 5.1 sp8; so I figure I can just export my
weblogic.properties settings to 6.0's config.xml via the console, right? Well, here's my original
properties:
weblogic.httpd.session.enable=true
weblogic.httpd.session.cookies.enable=true
weblogic.httpd.session.timeoutSecs=10000
weblogic.httpd.session.cookie.comment="Kiko session tracking cookie"
weblogic.httpd.session.cookie.domain=.kikotest.com
weblogic.httpd.session.cookie.maxAgeSecs=-1
weblogic.httpd.session.persistence=true
weblogic.httpd.session.cacheEntries=1024
weblogic.httpd.session.persistentStoreType=replicated
When I use the console export tool, I find NONE of these settings in config.xml!!! So I look
through the docs to see if I can do this manually, and the documents are just as confusing! This
mapping table:
http://e-docs.bea.com/wls/docs60///////config_xml/properties.html#1152226
seem to suggest that each session flag from weblogic.properties is mapped to two corresponding flags
in config.xml and weblogic.xml (e.g. persistentStoreType -> (config.xml) SessionPersistentStoreType
& (weblogic.xml) PersistentStoreType). Does this mean I have to set the flags for BOTH files? Or
just one? Which one???
As for config.xml flags which have "N/A" in the "Console Label" column, does this mean I just add
this flag as a top-most label, like:
<SessionPersistentStoreType>replicated</SessionPersistentStoreType>
And to further add to the confusion, when I look at the document for "Configuring In-Memory HTTP
Replication in a Cluster" http://e-docs.bea.com/wls/docs60/cluster/servlet.html#1009453, it tells me
to "set the property PersistentStoreType to replicated in the Web Application deployment descriptor,
web.xml."? I thought it was weblogic.xml???
I think all of these confusions can easily be alleviated by fixing any one of the following, if not
all three:
1) /console export of weblogic.properties to config.xml needs to translate these session flags
2) /console needs to have access to these session flags so we don't have to poke around config.xml!
3) Documents need to be less ambiguous about how to set these flags
Gene

Workflow for PO release strategy agent not found

Hi all,
I m beginner in the workflow. i want to create a workflow for the PO. release strategy I have done all the settings in the SPRO for the release strategy. I have copied the standard workflow definition WS20000075 also done the binding with object type BUS2012. in the steps 'Release of purchase order' i have mentioned the task TS20000166 i.e. 'Release of purchase order' and also maintain the AC Rule 20000027 i.e. 'Person responsible for PO release' for agents. But still its not getting the agents. the workflow is getting triggered but its not getting the agent. What else setting I need to do to get this done.
Thanks a lot.
Regards.

Very well put Rick. In my case if i simulate this workflow from swdd transaction then it works fine but the same workflow when initiated from ME21N doesn't work and throws same error.
1. I have copied standard workflow and task 166 is throwing error.
"Resolution of rule AC20000027 for task TS20000166: no agent found"
2. I have recreated the step but still the workflow is throwing error.
3. If I execute the rule individually (PFAC_DIS) with a specific PO then the rule works fine. The rule executes the below mentioned exit successfully.
4. I am using exit to determine the agent, the workflow works fine if I don't use the exit. The exit is EXIT_SAPLEBNF_005. I am just pulling the agent from a ztable.
Please advise if you can help as I have not seen anyone answering.
by the way irrespective of the explicit rule update in the workflow the step executes AC20000027 by default.
Any help on above is appreciated.

Documentation for Package BCA_RELEASE (Release Tools)

Hi ABAPers,
does anybody know if there is somewhere documentation for package BCA_RELEASE? It's the release tool for the SAP workflow. I couldn't find anything so far.
Thanks in advance and regards,
Martin

Post Author: munrobasher
CA Forum: General
Ahh ignore me - I see it's unpacked as part of the mammoth 1GB+ download of release 2.
Thanks, Rob.

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.

Database Mail Fails For SQL Server Agent Jobs / Maintenace plans - Why ?

Database Mail Fails For SQL Server Agent Jobs / Maintenace plans - Why ?
This has been a very common question I have seen relatedt to Database mail and I thought will post here so if you run into this issue, it could be due to one of the following and also have mentioned below how to get around them. Bottom line is datbase mail works fine with SQL Agent jobs and maintenace plans in SP1 on all platforms.
1. If you see this on 64 bit platform and on RTM build, this is a bug that is addressed in SP1.
2. If you see the below error message, it is known issue and this is because of design that requires SQL Agent to restart, if SQL Agent was started before enabling databasemail and setting a new profile. We are evaluating to change this design of not requiring to restart agent for our future release.
Re: 264] An attempt was made to send an email when no email session has been established
This problem will go away after restarting SQL Server Agent in this case. Thanks,
Gops Dwarak, MSFT

This may be related to the fact that DBMail, by default, shuts itself down after 10 minutes of inactivty. If the mail service isn't running, you won't be able to queue up any mail messages.
There may be a built-in mechanism for addressing this problem, but I found that I can detect this situation and start the mail listener before sending db mail. I use the following in stored procs that need to send email.
You could increase the inactivity period for db mail shutdown from 600 seconds to some larger value.  It might not make sense to do so, since shutting it down releases its resources back to teh system; if your SQL server only sneds mail infrequently, it might be better to start the mail listener on demand. Someone with more experience than I might want to add their two cents' worth. :-)
/* Check the mail engine. Start the service if is is stopped         */
/* -- the DB Mail engine shuts down after 10 minutes (of inactivity) */
/* -- this setting can be changed, but we probably don't need to.    */
DECLARE @rc INT
IF NOT EXISTS (SELECT * FROM msdb.sys.service_queues
               WHERE name = N'ExternalMailQueue' AND is_receive_enabled = 1)
    EXEC @rc = msdb.dbo.sysmail_start_sp
    -- TODO: add handling and logging for any engine start issues

Where can I find Documentation for Oracle financial installation

Hi
Where can I find Documentation for Oracle financial
installation as which all modules to be downloaded for linuk server etc
here is what I have found
===================================
Oracle9i Application Server, Version 1.0.2.2.2 CD Pack for Linux x86 [Act as Server][to be installed on main linux server]
===================================
OracleÂ® Applications 11i Release 9 CD Pack for Linux x86 [Act as client][to be installed on client sean,AJ,Vinod]
===================================
Internet Developer Suite (1.0.2.4.1) CD Pack (with iAS Pack) for Microsoft Windows (32-bit)
===================================

user11872870 wrote:
Hi Tubby,
http://www.quest.com/documents/list.aspx?SearchOff=true&ContentTypeID=20&prod=1
This link has many pdf files but none has the useful information. Those pdf's are just 2 or 3 pages each.Sad Christmas for you then i suppose.
Perhaps you could contact the vendor (quest) and get them to help you in your search for whatever it is you're looking for. An Oracle SQL and PL/SQL forum is not the venue for this, please mark the question as answered, and good luck in your search.

ABAP/4 Keywords for all SAP R/3 Versions with Delta Documentation for abap

Hello Experts,
Do please provide me with the way to find out the Delta Documentations for ABAP for all version of SAP R/3 starting from 3.0 to 6.0
points will be awarded if helpful.
Thanks in Advance

Log on to SAP. Use transaction ABAP_DOCU. Click on Keyword Help. Don't enter an ABAP keyword, press cont. button.
In the window that opens, in the tree on the left handside, you'll see ABAP Changes By Release.
This contains all the information you need.
matt

JavaDoc documentation for new BC4J UI classes

Hi All
I could not find JavaDoc documentation for new UI packages (
oracle.jbo.uicli.*** ) in JDeveloper 9i RC. Does anybody have an
idea where can I find them?
Regards,
Shota

The Javadoc for the Release Candidate is not accessible directly from the help system. You can, however, open the javadoc by using the
"Browse Javadoc" command in the Code Editor: 1. Highlight the symbol in the Code Editor (for instance, type "JUApplication" anywhere in a
.java file that you open in the Code Editor), 2. Right click and choose "Browse Javadoc". JDev will open the javadoc for the highlighted symbol
and you can use the Prev link to traverse the tree until you find the desired package. In the Production release, the Javadoc will be
accessible directly from the HelpViewer Contents pane (and thus allow searches on the Javadoc). FYI: All Javadoc appears in the /jdev/doc/ohj/
folder in your installation.

SAP documentation for t.code F.05

Hi All,
could anyone paste here the SAP documentation for t.code F.05 (Foreign currency valuation) in 4.7 release?
Thanks a lot
G.

Hi,
the documentation is available in help.sap.com:
[Foreign Currency Valuation|http://help.sap.com/saphelp_470/helpdata/en/96/8b3c2d43ce11d189ee0000e81ddfac/frameset.htm]
(choose Foreign Currency Valuation in the left side of the screen)

Suggestion for future release

Where should I post suggestions for future releases of SQL Developer or/and Data Modeler?
Please give me a link.
Thanx,
Chris
One suggestion for Data Modeler:
In the "Model Properties" of a relational model, there should be a "scripts" folder like in the "Table Properties".
In this script I'd like to generate some global statements for the DDL generation,
for example:
before (=begin of generated script): set define off; alter session set nls_numeric_characters='.,'; nls-config
after (=end of generated script): commit; (when table inserts are used and no ddl-statement is following; otherwise you have to use 'commit' in each table-script; After the last table create (ddl-) statement there is no implicit 'commit')
I know, that I can edit the generated script to add my statements, but if you often generate code there is a good change to forget to change the script afterwards.

Hi,
You can submit any feature requests at Oracle SQL Developer Exchange - https://apex.oracle.com/pls/apex/f?p=43135:1:2266866887402592:::::

Finding releasing agent of purchase order

Hi experts!
I am trying to find out the releasing agent of a purchase order, following release using transaction ME29n. How can I find this data? I've tried using the object and the related tables, but to no avail.
Thanks in advance!
Sincerely,
Christian

Thanks for your replies!
Nazrin: We're using the release strategy concept only partially. In the WF rule, and the exit, approvers are attached based on accounting information, since this is common practice in this case. This is based on an extensive approval register table, which can not contain release codes. Therefore, we use only one such code in order to take advantage of the standard workflow, and "simulate" the process. When the release has taken place, I need to update the view with the user id of the approver, so I have to find this agent by other means.
Regarding Antony's reply, I'm trying that right now
By the way, does anyone know if it is possible to get the system to display multiple approvers in the grid in ME29n?
Thanks!

DOCUMENTATION FOR THE BENIFIT OF ALL QM CONSULTANTS u2013USER PROFILE

DOCUMENTATION FOR THE BENIFIT OF ALL QM CONSULTANTSu2013
USER PROFILE TO STOP THE UD, WHEN RR IS NOT DONE.
I faced problem in creating the User Profile to fulfill my user requirement.
SHYAMAL JOSHIJI and CRAIG took active participation in solving this issue.
Both of them richly deserve appreciation.
I want to thank CRAIG again, as he insisted me to prepare documentation and publish for the benefit of QM Consultants.
Requirement : User Profile is to be created to block the UD, if RR is not done.
Inspection Type used: 01 or Copy of 01.--> Z10 is used which is copy of Inspection Type 01.
Material Master: For all lab chemicals, Inspection Type Z10 are assigned.
Inspection Plan: For each Lab Chemical the Inspection Plan is created.
                           Usage is 5  Goods Receipt.
                          Status is 4  Released General.
Create one dummy selection set, and corresponding Code Group and Code.
Create one Qualitative Dummy MIC  INVDUMMY
Assign the Selection Set to the Dummy MIC.
Most important  the control parameter of Dummy Qualitative MIC is given below.
Control Parameter Details.
S.No.>Control Title>Requirement
1>Type>Characteristic Attribute
2>Sample>Sampling Procedure
3>Results Confirmation>Required Characteristic
                                       (This is a must)
3--> Results Confirmation --> Single Result
4>Inspection Scope>Fixed Scope
5>Documentation Confirmation>No Documentation
6>Miscellaneous>As per requirements
7>Print>As per requirements
This Dummy MIC has to be added to each and every material whose inspection type is 01 or Z10.
Preferably it must be the first MIC in the Inspection Plan.
Creation of User Profile
1. SAP defined status profile  QM_L_003 is used to stop Stock Posting before the UD.
2. Create user defined status  QM_UDZ10 by coping the SAP defined status Profile  QM_L_003.
3. Create the Status u201CINITu201D and Status u201CQFINu201D.
   Any meaningful name can be given to the user defined Status.
User Status has 9 columns.
FOR THE FIRST ROW VALUES ARE GIVEN BELOW.
Let us discuss for the status  u201CINITu201D
First Column Status Number 1.
Second Column Status  INIT.
Third Column  Short Text  RR NOT DONE
Fourth Column  Long Text Check Box  Do Not Activate
Fifth Column  Initial Status Check Box  Activate
Sixth Column  Lowest Status Number  1
Seventh Column  Highest Status Number  10
Eighth Column  Position  1
Nineth Column  Priority  1
FOR THE SECOND ROW VALUES ARE GIVEN BELOW.
Let us discuss for the status  u201CQFINu201D
First Column Status Number 2.
Second Column Status QFIN.
Third Column  Short Text  RR AND UD DONE
Fourth Column  Long Text Check Box  Do Not Activate
Fifth Column  Initial Status Check Box  Do Not Activate
Sixth Column  Lowest Status Number  2
Seventh Column  Highest Status Number  20
Eighth Column  Position  1
Nineth Column  Priority  1
Please note when multiple status exist, only one status has to be activated for the Initial Status(5th Column).
Initial Status check box can not be activated more than one status.
I have defined two statuses.
I have activated the u201CINITIAL STATUS CHECK BOXu201D for the user defined status u201CINITu201D only.
System will not ALLOW to activate the Initial STATUS CHECK BOX for the second status u201CQFINu201D.
NOW BUSINESS TRANSACTIONS HAVE TO BE DEFINED FOR EACH ROW
Double click the u201CRRCLu201D status.
The new screen appears  u201CChange Status Profile: Transaction Controlu201D.
Two Business Transactions are selected.
First one  u201CMake usage decisionu201D.
Second one  u201CRecord inspection resultsu201D.
First Row  u201CMake usage decisionu201D.
Select the first Business Transaction  u201CMake usage decisionu201D.
In this row there are 6 Radio Buttons exist.
Select the fourth button and fifth button.
Forth Radio Button  Forbidden.
Fifth Radio Button  No Action.
Second Row  u201CRecord inspection resultsu201D.
Select the second Business Transaction  u201CRecord inspection resultsu201D.
In this row there are 4 Radio Buttons exist.
Select the second radio button only.
Second Radio Button  Allowed.
Double click the u201CQFINu201D status.
The new screen appears  u201CChange Status Profile: Transaction Controlu201D.
Three Business Transactions are selected.
First Row  Close inspection u2013 complete
Second Row  Complete insp. - short-term
Third Row  Start inv. pstg bef. Usage Dec
First Row  Close inspection u2013 complete
First Row  Close inspection u2013 complete contains 6 radio buttons.
Select the Second and Sixth Radio Button.
Second Radio Button  u201CAllowedu201D.
Sixth Radio Button  u201CSetu201D.
Second Row  Complete insp. - short-term
Second Row  Complete insp. - short-term contains 6 radio buttons.
Select the Second and Sixth Radio Button.
Second Radio Button  u201CAllowedu201D.
Sixth Radio Button  u201CSetu201D.
Third Row  Start inv. pstg bef. Usage Dec
Third Row  Start inv. pstg bef. Usage Dec contains 6 radio buttons.
Select the fourth and fifth radio button.
Fourth Button  Forbidden.
Fifth Button  No Action.
Save.
Assign this u201CQM_UDZ10u201D to the Inspection Type in customization.
It is working fine for out client.
This document is written for the benefit of all QM Consultants.
Good Luck.

Dear Prasad,
Please change the User profile name as per your requirement.- meaningful name.
You have to create two statuses.
The first status is RRCL.
The Second status Is QFIN.
RRCL and QFIN - u can name them as u like.
There are two statuses.
is it clear?
First you have to create two statuses in the user profile.
You can name them as you like.
For example RRND --> Result recording not done (You can name the first status as RRND)
Second status UDCD --> Usage Decision Can be Done ( You can name the second status as UDCD.
It is your wish.
For each status you have to assign the business transactions .
Hope this is clear.
Best of luck.
Regards,

Documentation for Session Release Agent

Similar Messages

Maybe you are looking for