wkplc_comp.properties

+

Search Tips   |   Advanced Search

  The Workplace Component Configuration File (wkplc_comp.properties): 


##### WP.EAR PROPERTIES 

# WP.EAR loaded from:
#
#    /opt/WAS_HOME/PortalServer/installer/wp.ear/wp.ear.properties


# Property:  WpsDefaultHome
#
#   Create the HCL WebSphere Portal default home URL.
#
#    Default:  portal
#    Examples: 
#       If you specify "portal" as the value for this property, the following is the URL for  
#       the HCL WebSphere Portal server:  http://localhost:80/wps/portal. In this example
#       localhost is the Websphere Portal host name (WpsHostName),
#       80 is the Websphere Portal host port (WpsHostPort), and
#       wps is the context root (WpsContextRoot). 

WpsDefaultHome=portal


# Property:  WpsPersonalizedHome
#
#   The personalized home is for users that have already logged in to the portal and 
#   cannot be accessed by anonymous users. The value specified is used to create the 
#   HCL WebSphere Portal URL for logged in users.
#
#    Default:  myportal
#    Examples: 
#       If you specify "myportal" as the value for this property, the following URL is the page that logged
#       in users are directed to: http://localhost:80/wps/myportal. In this example
#       localhost is the Websphere Portal host name (WpsHostName),
#       80 is the Websphere Portal host port (WpsHostPort), and
#       wps is the context root (WpsContextRoot). 

WpsPersonalizedHome=myportal


##### WP.PROCESSINTEGRATION.CONFIG PROPERTIES 

# WP.PROCESSINTEGRATION.CONFIG loaded from:
#
#    /opt/WAS_HOME/PortalServer/installer/wp.processintegration.config/wp.processintegration.config.properties

# 1) Properties for HCL WebSphere Portal integration with IBM Process Server
#
#    Provide information about the already installed WebSphere Process Server.
#


# Property:  pi.IsCrossCell
#
#    Default:  true
#    Examples:  None available

pi.IsCrossCell=true


# Property:  pi.ProcessServerHostAddress
#
#   Used only if the pi.IsCrossCell value is set to true. The server 
#   host name address of the WebSphere Process Server installation located in another cell.
#
#    Default:  No default value
#    Examples:  None available

pi.ProcessServerHostAddress=


# Property:  pi.ProcessServerBootstrapPort
#
#   Used only if the pi.IsCrossCell value is set to true. The 
#   bootstrap port of the WebSphere Process Server installation located in another 
#   cell.
#
#    Default:  No default value
#    Examples:  None available

pi.ProcessServerBootstrapPort=


# Property:  pi.ProcessArtifactsLocation
#
#   Used only if the pi.IsCrossCell value is set to true. The 
#   directory in which the process artifacts are located.
#
#    Default:  ${USER_INSTALL_ROOT}/processArtifacts
#    Examples:  None available

pi.ProcessArtifactsLocation=${USER_INSTALL_ROOT}/processArtifacts


# Property:  pi.IsWPSCluster
#
#   Used only if the pi.IsCrossCell value is set to false.
#
#    Default:  No default value
#    Examples:  None available

pi.IsWPSCluster=


# Property:  pi.ClusterName
#
#   Used only if the pi.IsCrossCell value is set to false AND 
#   pi.IsWPSCluster value is set to true. The name of the WebSphere Process Server 
#   cluster.
#
#    Default:  No default value
#    Examples:  None available

pi.ClusterName=


# Property:  pi.NodeName
#
#   Used only if the pi.IsCrossCell value is set to false AND 
#   pi.IsWPSCluster value is set to false. The name of the node of the WebSphere 
#   Process Server server.
#
#    Default:  No default value
#    Examples:  None available

pi.NodeName=


# Property:  pi.ServerName
#
#   Used only if the pi.IsCrossCell value is set to false AND 
#   pi.IsWPSCluster value is set to false. This value is the name of the WebSphere 
#   Process Server server.
#
#    Default:  No default value
#    Examples:  None available

pi.ServerName=


##### WP.XML.CLIENT PROPERTIES 

# WP.XML.CLIENT loaded from:
#
#    /opt/WAS_HOME/PortalServer/base/wp.xml.client/wp.xml.client.properties


# 1) XMLAccess properties

# Property:  XmlAccessHost
#
#   The local host name of HCL WebSphere Portal. We do not need to modify this value.
#
#    Default:  localhost
#
#    Examples:  None available

XmlAccessHost=localhost


# Property:  XmlAccessPort
#
#   The port used by XML Access ConfigEngine tasks to connect to the XMLAccess server 
#   Do not use this parameter to reconfigure the XmlAccessPort port. The value is set 
#   by the basic HCL WebSphere Portal configuration task.
#
#    Default:  10040
#
#     Example:  10040

XmlAccessPort=10039


# Property:  XmlAccessProtocol
#
#   The protocol used to connect to the XMLAccess server.
#
#    Default:  http
#
#    Examples:  None available

XmlAccessProtocol=http


##### WP.AC.IMPL PROPERTIES 

# WP.AC.IMPL loaded from:
#
#    /opt/WAS_HOME/PortalServer/base/wp.ac.impl/wp.ac.impl.properties


#  1. Advanced Security Configuration using External Security Managers
#  2. Security Access Manager: AMJRTE connection parameters
#  3. Security Access Manager: PDJrteCfg command and filesystem parameters
#  4. Security Access Manager: SvrSslCfg command parameters
#  5. Security Access Manager: WebSphere Application Server WebSEAL TAI parameters
#  6. Security Access Manager: Portal authorization parameters
#  7. Security Access Manager: Portal vault parameters
#  8. Netegrity SiteMinder:  Portal/SiteMinder authorization parameters

#
# 1) Advanced Security Configuration using External Security Managers
#
#    The following parameters are used for advanced security configuration using external security 
#    managers. Use the properties to specify namespace management parameters that are common to ISAM 
#    and SiteMinder
#


# Property:  wp.ac.impl.EACserverName
#
#   (Optional) We can set different "contexts" to further distinguish externalized 
#   role names from other role names in the Security Access Manager namespace. This 
#   context information will be added to the namespace entry created upon role 
#   externalization. If any of the three context values (EACserverName, EACcellName, or 
#   EACappName) are null, none will be used.
#
#    Default:  WebSphere_Portal
#
#    Examples:  None available

wp.ac.impl.EACserverName=WebSphere_Portal


# Property:  wp.ac.impl.EACcellName
#
#   One of the three context values used to set a different context to further 
#   distinguish the externalized role name
#
#    Default:  No default value
#
#    Examples:  None available

wp.ac.impl.EACcellName=


# Property:  wp.ac.impl.EACappName
#
#   One of the three context values used to set a different context to further 
#   distinguish the externalized role name
#
#    Default:  wps
#
#     Example:  wps

wp.ac.impl.EACappName=wps


# Property:  wp.ac.impl.reorderRoles
#
#   Allows us to either have your externalized Portal rolenames displayed with the 
#   resource type first, or the role types first.
#
#    Default:  false
#
#    Examples: 
#       1) true example: /WPv80/wps.CONTENT_NODE/Welcome_Page/10_2E@Aministrator/app/server/cell 
#       2) true example: /WPv80/wps.CONTENT_NODE/Welcome_Page/10_2E@Editor/app/server/cell 
#       3) true example: /WPv80/wps.CONTENT_NODE/Administration/15_AF@Aministrator/app/server/cell 
#       4) true example: /WPv80/wps.PORTLET_APPLICATION/Welcome_Portlet/09_2Q@Aministrator/app/server/cell
#       5) true example: /WPv80/wps.PORTLET_APPLICATION/Welcome_Portlet/09_2Q@User/app/server/cell
#       6) false example: /WPv80/Aministrator@wps.CONTENT_NODE/Welcome_Page/10_2E/app/server/cell
#       7) false example: /WPv80/Administrator@wps.CONTENT_NODE/Administration/15_AF/app/server/cell 
#       8) false example: /WPv80/Administrator@wps.PORTLET_APPLICATION/Welcome_Portlet/09_2Q/app/server/cell
#       9) false example: /WPv80/Editor@wps.CONTENT_NODE/Welcome_Page/10_2E/app/server/cell
#       10) false example: /WPv80/User@wps.PORTLET_APPLICATION/Welcome_Portlet/09_2Q/app/server/cell  

wp.ac.impl.reorderRoles=false

#
# 2) Security Access Manager: AMJRTE connection parameters
#
#    Provide authentication information to enable HCL WebSphere Portal to connect with ISAM.
#


# Property:  wp.ac.impl.PDAdminId
#
#   An administrative user ID for Security Access Manager (ISAM) that has access to create 
#   new ISAM servers, new Tivoli protected objectspaces, and new Tivoli protected 
#   objects.
#
#    Default:  sec_master
#     Example:  sec_master

wp.ac.impl.PDAdminId=sec_master


# Property:  wp.ac.impl.PDAdminPwd
#
#   This value is the password for the administrative ISAM user ID.
#
#    Default:  ReplaceWithYourISAMAdminPwd
#    Examples:  None available

wp.ac.impl.PDAdminPwd=ReplaceWithYourPwd


# Property:  wp.ac.impl.PDPermPath
#
#   This value is the location of the ISAM AMJRTE properties file. This properties file 
#   is created by the ISAM SvrSslCfg command and contains information such as: Policy 
#   Server host name, ports vemycoon of AMJRTE path to encryption keys.
#
#    Default:  ${WasHome}/tivoli/tam/PdPerm.properties
#    Examples:  None available

wp.ac.impl.PDPermPath=${WasHome}/tivoli/tam/PdPerm.properties

#
# 3) Security Access Manager: PDJrteCfg command and filesystem parameters
#
#    The following parameter locations depend on the WebSphere Application Server installation 
#    structure. For more information or detail on the individual parameters, refer to: 
#    http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/topic/com.ibm.websphere.nd.doc/info/ae/ae/
#    rsec_tampdjrtecfg.html
#


# Property:  wp.ac.impl.PDClasspath
#
#   The location of the ISAM PD.jar file, which contains the classes required to 
#   establish a connection to the policy server and is passed into the classpath of the 
#   command.
#
#    Default:  ${WasHome}/tivoli/tam/PD.jar
#     Example:  No examples are available.

wp.ac.impl.PDClasspath=${WasHome}/tivoli/tam/PD.jar


# Property:  wp.ac.impl.PDHome
#
#   This value is the location of the ISAM AMJRTE, which is the same as the pd.home 
#   system property in a manual execution.
#
#    Default:  ${WasHome}/tivoli/tam/PolicyDirector
#    Examples:  None available

wp.ac.impl.PDHome=${WasHome}/tivoli/tam/PolicyDirector


# Property:  wp.ac.impl.JavaHome
#
#   This value is the location of the Java runtime in which to configure, which is the 
#   same as the -java_home command line argument in a manual execution.
#
#    Default:  ${WasHome}/java/jre/
#    Examples:  None available

wp.ac.impl.JavaHome=${WasHome}/java/jre/


# Property:  wp.ac.impl.CfgFilesPath
#
#   This value is the required filesystem directory location of the generated ISAM 
#   AMJRTE properties. The properties files are created by the ISAM PdjrteCfg command, 
#   which is the same as the -cfgfiles_path command line argument in a manual 
#   execution.
#
#    Default:  ${WasHome}/tivoli/tam
#     Example:  No examples are available.

wp.ac.impl.CfgFilesPath=${WasHome}/tivoli/tam


# Property:  wp.ac.impl.TamHost
#
#   This value defines the ISAM Policy Server used when running PDJrteCfg.
#
#    Default:  your.ISAM.Policy.Server.hostname
#    Examples:  None available

wp.ac.impl.TamHost=your.ISAM.Policy.Server.hostname

#
# 4) Security Access Manager: SvrSslCfg command parameters
#
#    HCL WebSphere Portal requires the following information to run the SvrSslCfg command
#


# Property:  wp.ac.impl.PDServerName
#
#   The unique application name and will be used to create a new Tivoli server in the 
#   Access Manager Policy Server. This server will appear in the pdadmin server list 
#   after running the SvrSslCfg command. If a server with the same name appears in the 
#   server list command, the SvrSslCfg command will fail.
#
#    Default:  amwp80
#     Example:  No examples are available.

wp.ac.impl.PDServerName=amwp80


# Property:  wp.ac.impl.SvrSslCfgPort
#
#   This value is the configuration port for the application name. This parameter is 
#   currently ignored by the SvrSslCfg command.
#
#    Default:  7223
#     Example:  No examples are available.

wp.ac.impl.SvrSslCfgPort=7223


# Property:  wp.ac.impl.SvrSslCfgMode
#
#   This value is the configuration mode of the SvrSslCfg command. Currently, the only 
#   valid value is remote.
#
#    Default:  remote
#    Examples:  None available

wp.ac.impl.SvrSslCfgMode=remote


# Property:  wp.ac.impl.PDPolicyServerList
#
#   This value defines host name, port, and priority combinations for your ISAM Policy 
#   servers used when running SvrSslCfg.
#
#    Default:  your.ISAM.Policy.Server.hostname:7135:1
#     Example:  hosta.ibm.com:7135:1 or host1.ibm.com:7135:1, hostb.7135:2

wp.ac.impl.PDPolicyServerList=your.ISAM.Policy.Server.hostname:7135:1


# Property:  wp.ac.impl.PDAuthzServerList
#
#   This value defines host name, port, and priority combination for your ISAM 
#   authorization servers.
#
#    Default:  your.ISAM.Authorization.Server.hostname:7136:1
#     Example:  hosta.ibm.com:7136:1

wp.ac.impl.PDAuthzServerList=your.ISAM.Authorization.Server.hostname:7136:1


# Property:  wp.ac.impl.PDKeyPath
#
#   This value is the file used to store encryption keys used for the SSL communication 
#   between AMJRTE and Tivoli Access manager. This file is generated as a result of the 
#   SvrSslCfg command.
#
#    Default:  ${WasHome}/tivoli/tam/pdperm.ks
#    Examples:  None available

wp.ac.impl.PDKeyPath=${WasHome}/tivoli/tam/pdperm.ks

#
# 5) Security Access Manager: WebSphere Application Server WebSEAL TAI parameters
#
#    HCL WebSphere Portal uses the following information for WebSEAL.
#


# Property:  wp.ac.impl.hostnames
#
#   (Optional) This value sets the WebSEAL TAI's hostnames parameter. You should 
#   include the host name you provided when configuring the WebSEAL instance. The 
#   default behavior when configuring a WebSEAL instance is to use the network short 
#   name. For example, hosta.mycompany.com may be represented as hosta. When the 
#   WebSEAL instance is configured and if any additional proxies are included, their 
#   host names must be added as well. Presence of this parameter will cause the TAI to 
#   evaluate the VIA header and only handle those requests that contain one of the 
#   provided host name, and port combinations.
#
#    Default:  No default value
#     Example:  hosta.mycompany.com or hosta

wp.ac.impl.hostnames=


# Property:  wp.ac.impl.ports
#
#   (Optional) This value sets the WebSEAL TAI's ports parameter. You should include 
#   the WebSEAL ports in this comma-delimited list. The default WebSEAL port is 443. 
#   Presence of this parameter will cause the TAI to evaluate the VIA header and only 
#   handle those requests that contain one of the provided host name and port 
#   combinations.
#
#    Default:  No default value
#     Example:  443

wp.ac.impl.ports=


# Property:  wp.ac.impl.loginId
#
#   When you create a TCP junction, this value is WebSEAL identity representing the 
#   reverse proxy on every request. WebSphere Application Server will use this identity 
#   to establish the "trust" that is required to validate the WebSEAL iv-* headers. The 
#   password for this user should be set in the WebSEAL instance's webseald.conf on the 
#   basicauth-dummy-passwd property.
#
#    Default:  wpsadmin
#     Example:  No examples are available.

wp.ac.impl.loginId=wpsadmin


# Property:  wp.ac.impl.TAICreds
#
#   This value is the headers inserted by WebSEAL that the TAI uses to identify the 
#   request as originating from WebSEAL. Inclusion of these headers is associated with 
#   the headers used by the WebSphere Application Server TAI to identify the request as 
#   one from WebSEAL. If you are configuring Portal to use ISAM as an external 
#   authorization engine, we must include at least the iv-user and iv-creds headers.
#
#    Default:  iv-user,iv-creds
#     Example:  No examples are available.

wp.ac.impl.TAICreds=iv-user,iv-creds


# Property:  wp.ac.impl.checkViaHeader
#
#   We can configure TAI so that the VIA header can be ignored when validating trust 
#   for a request. Set this property to false if none of the hosts in the VIA header 
#   need to be evaluated. When this value is false, you do not need to set the 
#   wp.ac.impl.hostnames and wp.ac.impl.ports properties. The only mandatory property 
#   to set when this value is false is wp.ac.impl.loginId.
#
#    Default:  false
#    Examples:  None available

wp.ac.impl.checkViaHeader=false


# Property:  wp.ac.impl.viaDepth
#
#   This value is a positive integer that specifies the number of source hosts in the 
#   VIA header to check for trust. By default, every host in the VIA header is checked, 
#   and if any host is not trusted, trust cannot be established. The VIA depth property 
#   is used when only some of the hosts in the VIA header have to be trusted. The 
#   setting indicates the number of hosts that are required to be trusted.
#
#    Default:  0
#     Example:  No examples are available.

wp.ac.impl.viaDepth=0


# Property:  wp.ac.impl.ssoPwdExpiry
#
#   After trust is established for a request, the single sign-on user password is 
#   cached, eliminating the need to have the TAI re-authenticate the single sign-on 
#   user with Security Access Manager for every request. We can modify the cache timeout 
#   period by setting the single sign-on password expiry property to the required time 
#   in seconds. If the password expiry property is set to 0, the cached password never 
#   expires.
#
#    Default:  600
#    Examples:  None available

wp.ac.impl.ssoPwdExpiry=600


# Property:  wp.ac.impl.ignoreProxy
#
#   This property can be used to tell the TAI to ignore proxies as trusted hosts. If 
#   set to true the comments field of the hosts entry in the VIA header is checked to 
#   determine if a host is a proxy. Remember that not all proxies insert comments in 
#   the via header indicating that they are proxies. If the checkViaHeader property is 
#   set to false, then the ignoreProxy property has no influence in establishing trust.
#
#    Default:  false
#     Example:  No examples are available.

wp.ac.impl.ignoreProxy=false

#
# 6) Security Access Manager: Portal authorization parameters
#
#    The following information is used to authenticate with ISAM.
#


# Property:  wp.ac.impl.PDRoot
#
#   This value is the root objectspace entry in the ISAM namespace. All Portal roles 
#   will be installed under this objectspace entry.
#
#    Default:  /WPv80
#    Examples:  None available

wp.ac.impl.PDRoot=/WPv80


# Property:  wp.ac.impl.PDAction
#
#   When the Security Access Manager external authorization plugin is started, it will 
#   detect and, if necessary, create a custom action in Security Access Manager. The 
#   combination of the action group and the action determines the ISAM permission string 
#   required to assign membership to externalized Portal roles.
#
#    Default:  m
#     Example:  No examples are available.

wp.ac.impl.PDAction=m


# Property:  wp.ac.impl.PDActionGroup
#
#   When the Security Access Manager external authorization plugin is started, it will 
#   detect and, if necessary, create a custom action group in Security Access Manager. 
#   The combination of the action group and the action determines the ISAM permission 
#   string required to assign membership to externalized Portal roles.
#
#    Default:  [WP80]
#     Example:  No examples are available.

wp.ac.impl.PDActionGroup=[WP80]


# Property:  wp.ac.impl.PDCreateAcl
#
#   When Portal externalizes a role, it can automatically create and attach a ISAM ACL 
#   granting membership to the user doing the role. If we select false, the ISAM 
#   administrator will be responsible for creating ISAM ACLs to allow access to Portal 
#   roles.
#
#    Default:  true
#    Examples:  None available

wp.ac.impl.PDCreateAcl=true

#
# 7) Security Access Manager: Portal vault parameters
#
#    The following information is used to confgure a vault for Security Access Manager.
#


# Property:  wp.ac.impl.vaultType
#
#   This value is the new vault type identifier representing the Tivoli GSO lockbox 
#   vault.
#
#    Default:  AccessManager
#    Examples:  None available

wp.ac.impl.vaultType=AccessManager


# Property:  wp.ac.impl.vaultProperties
#
#   This value defines a properties file used to configure the vault with ISAM specific 
#   user and SSL connection information. This file will automatically be created in the 
#   wp_profile/shared/app/config subdirectory and populated by the ant task based on 
#   previous task execution.
#
#    Default:  accessmanagervault.properties
#     Example:  No examples are available.

wp.ac.impl.vaultProperties=accessmanagervault.properties


# Property:  wp.ac.impl.manageResources
#
#   This value determines if the portal credential vault or any custom portlet is 
#   allowed to create new resource objects in ISAM. If you set this value to false, your 
#   Tivoli administrator must define the accessible resources to associate users with 
#   using the Tivoli command line or GUI.
#
#    Default:  true
#     Example:  No examples are available.

wp.ac.impl.manageResources=true


# Property:  wp.ac.impl.readOnly
#
#   This value determines if the portal credential vault or any custom portlet is 
#   allowed to modify the secrets stored in ISAM. If you set this value to true ("Read 
#   Only"), the Tivoli administrator must change the credentials associated with 
#   resources using the Tivoli command line or GUI.
#
#    Default:  false
#    Examples:  None available

wp.ac.impl.readOnly=false

#
# 8) Netegrity SiteMinder:  Portal/SiteMinder authorization parameters
#
#    The following parameters enables HCL WebSphere Portal to authenticate wit Netegrity SiteMinder.
#


# Property:  wp.ac.impl.SMDomain
#
#   This value is the SiteMinder Domain containing all externalized portal resources.
#
#    Default:  HCL WebSphere Portal v80
#    Examples:  None available

wp.ac.impl.SMDomain=HCL WebSphere Portal v80


# Property:  wp.ac.impl.SMScheme
#
#   This value is the SiteMinder Authentication scheme object name to use when creating 
#   realms.
#
#    Default:  Basic
#    Examples:  None available

wp.ac.impl.SMScheme=Basic


# Property:  wp.ac.impl.SMAgent
#
#   This value is the SiteMinder custom or 4.x web agent created to allow communication 
#   between HCL WebSphere Portal and SiteMinder.
#
#    Default:  ReplaceWithYourSiteMinderAgentName
#    Examples:  None available

wp.ac.impl.SMAgent=ReplaceWithYourSiteMinderAgentName


# Property:  wp.ac.impl.SMAgentPwd
#
#   This value is the SiteMinder custom or 4.x agent password.
#
#    Default:  ReplaceWithYourSiteMinderAgentPwd
#    Examples:  None available

wp.ac.impl.SMAgentPwd=ReplaceWithYourPwd


# Property:  wp.ac.impl.SMAgentGroup
#
#   An externalized portal resource is assigned to a SiteMinder custom agent for 
#   SiteMinder isProtected and isAuthorized calls. In a non-cluster, the agent 
#   specified in the wp.ac.impl.SMAgent parameter is used. However, in a cluster, you 
#   must specify a common SiteMinder Agent Group to be assigned to the resource.
#
#    Default:  No default value
#    Examples:  None available

wp.ac.impl.SMAgentGroup=


# Property:  wp.ac.impl.SMAdminId
#
#   This value is the SiteMinder administrator who must have a scope of System because 
#   new SiteMinder domains and realms will be created, as well as the realms 
#   representing Portal roles and reference to the webagent.
#
#    Default:  siteminder
#    Examples:  None available

wp.ac.impl.SMAdminId=siteminder


# Property:  wp.ac.impl.SMAdminPwd
#
#   This value is the password for the SiteMinder administrative user.
#
#    Default:  ReplaceWithYourSiteMinderAdminPwd
#    Examples:  None available

wp.ac.impl.SMAdminPwd=ReplaceWithYourPwd


# Property:  wp.ac.impl.SMUserDir
#
#   This value is the SiteMinder User Directory object referencing the LDAP server used 
#   for Portal users and groups.
#
#    Default:  ReplaceWithYourSiteMinderUserDirectoryObject
#    Examples:  None available

wp.ac.impl.SMUserDir=ReplaceWithYourSiteMinderUserDirectoryObject


# Property:  wp.ac.impl.SMFailover
#
#   This value is the failover mode for the Siteminder Policy Server. SMFailover must 
#   be set to true if more than 1 policy server is listed in the SMServers property 
#   below.
#
#    Default:  false
#    Examples:  None available

wp.ac.impl.SMFailover=false


# Property:  wp.ac.impl.SMServers
#
#   This value is a comma delimited list of server for the SiteMinder agent. Important: 
#   If your Policy Servers are listening on non-default ports (for example: not 
#   44441,44442,44443), we must add the port property for each policy server manually 
#   in the ExternalAccessControlService.properties file.
#
#    Default:  your.Policy.Server.ipaddress
#    Examples:  None available

wp.ac.impl.SMServers=your.Policy.Server.ipaddress


##### WP.WSRP.COMMON PROPERTIES 

# WP.WSRP.COMMON loaded from:
#
#    /opt/WAS_HOME/PortalServer/base/wp.wsrp.common/wp.wsrp.common.properties


# Property:  WsrpContextRoot
#
#   The context root for web services for remote portlets. In the following 
#   URL,wps/wsrp; is the context root: http://localhost:80/wps/wsrp
#
#    Default:  wps/wsrp
#    Examples:  None available

WsrpContextRoot=wps/wsrp


##### WP.AUTH.TAI PROPERTIES 

# WP.AUTH.TAI loaded from:
#
#    /opt/WAS_HOME/PortalServer/base/wp.auth.tai/wp.auth.tai.properties


#  1. Advanced Security Configuration using External Security Managers
#  2. HTTP Basic Authentication Trust Association Interceptor (TAI) settings
#
    

#
# 1) Advanced Security Configuration using External Security Managers
#
#    The following parameters are used for advanced security configuration using external security 
#    managers. Use the properties to specify namespace management parameters that are common to ISAM 
#    and SiteMinder
#


# Property:  wp.auth.tai.facebook_app_secret_alias
#
#   Do not change the value of this attribute unless specifically directed to do so by 
#   IBM Support.
#
#    Default:  facebook_app_secret
#    Examples:  None available

wp.auth.tai.facebook_app_secret_alias=facebook_app_secret

#
# 2) HTTP Basic Authentication Trust Association Interceptor (TAI) settings
#
#    HCL WebSphere Portal uses the following information to configure an HTTP Basic Authentication 
#    Trust Association Interceptor (TAI) to authenticate incoming requests using the HTTP Basic 
#    Authentication Protocol described in RFC 2617.
#


# Property:  wp.auth.tai.BasicAuthEnabled
#
#   Defines whether the basic authentication TAI is active (authenticates requests) or 
#   not.
#
#    Default:  true
#    Examples:  None available

wp.auth.tai.BasicAuthEnabled=true


# Property:  wp.auth.tai.BasicAuthRealm
#
#   The name of an authentication realm as defined in RFC 2617. The TAI 
#   challenges the client to authenticate against this realm. The default value for 
#   this property is the same authentication realm name as the one that is used by 
#   portal HTTP form based login.
#
#    Default:  WPS
#    Examples:  None available

wp.auth.tai.BasicAuthRealm=WPS


# Property:  wp.auth.tai.BasicAuthUseRegExp
#
#   This value determines whether or not the patterns that you specified for the black 
#   list and white list properties are to be interpreted as Java regular expressions. 
#   For more information see: 
#   http://java.sun.com/j2se/1.4.2/docs/api/java/util/regex/Pattern.html. If Java 
#   regular expressions are not used, then only astericks are supported as wild cards. 
#   The following applies to astericks:
#
#     The asterisk ( * ) wildcard can appear anywhere in the pattern.
#     We can use multiple asterisk ( * ) wildcards within the same pattern.
#     If you want to represent an asterisk as an actual character for matches in the 
#     pattern instead of using it as a wildcard, prefix it with a backslash like this: 
#     \* .
#     To represent the backslash as a character for matching, code it using a double 
#     backslash: \\ .
#
#    Default:  false
#
#    Examples: 
#       1) Java regular expressions examples: 
#       2) * [^X]* will match every user agent that does not contain an uppercase X in its product name.
#       3) * .*my_browser.* will match every user agent that contains my_browser in its product name.
#       4) * .*%5bX%5d is URL encoded for .*[X] and will match every URL that ends with X.
#       5) Examples using astericks:
#       6) * *my_browser* will match every user agent that contains my_browser in its product name.
#       7) * /myprefix*mysuffix will match every URL that starts with /myprefix and ends with mysuffix.
#       8) * Fun\* Ag\\ent will only match a user agent hat has Fun* Ag\ent as product name.

wp.auth.tai.BasicAuthUseRegExp=false


# Property:  wp.auth.tai.BasicAuthLoginTarget
#
#   This value is the alias of the JAAS login configuration that is used by the TAI. 
#   The default value is the same JAAS login configuration as the one that is used by 
#   portal HTTP form based login. The value is the target to execute to populate the 
#   Subject with portal specific Principals when logging on using the TAI.
#
#    Default:  Portal_LTPA
#    Examples:  None available

wp.auth.tai.BasicAuthLoginTarget=Portal_LTPA


# Property:  wp.auth.tai.BasicAuthUserAgentBlackList
#
#   The list of patterns for which you do not want the TAI to handle the 
#   requests. Separate the patterns using a whitespaces. Every product name in the HTTP 
#   header field User-Agent of incoming requests is compared with each of the patterns 
#   specified for this property. If the TAI is enabled and the URL matches at least one 
#   of the patterns specified for the userAgentBlackList property, the TAI will not 
#   handle the request. To use Java regular expressions, we must set the property 
#   wp.auth.tai.BasicAuthUseRegExp = true.
#
#    Default:  AllAgentsAllowed
#    Examples:  None available

wp.auth.tai.BasicAuthUserAgentBlackList=AllAgentsAllowed


# Property:  wp.auth.tai.BasicAuthUserAgentWhiteList
#
#   The list of patterns for which you want the TAI to handle the requests. 
#   Separate the patterns by whitespaces. Every product name in the HTTP header field 
#   User-Agent of the incoming request is compared with each of the patterns specified 
#   for this property.If the TAI is enabled and the pattern specified for this property 
#   has at least one match and neither of the userAgentBlackList or the urlBlackList 
#   have a match, then the TAI handles the request. To use Java regular expressions, 
#   we must set the property wp.auth.tai.BasicAuthUseRegExp = true We can specify the 
#   patterns with an asterisk ( * ) as a wild card character. We can also define the 
#   patterns as Java regular expressions.
#
#    Default:  NoAgentSpecified
#    Examples:  None available

wp.auth.tai.BasicAuthUserAgentWhiteList=NoAgentSpecified


# Property:  wp.auth.tai.BasicAuthUrlBlackList
#
#   The list of URI patterns this TAI will never handle. Separate the patterns 
#   by whitespaces. The full path information of the URL of the incoming request is 
#   compared with each of the patterns specified for this parameter. Before comparing 
#   the URL to the patterns, the protocol, server, port, and query information is 
#   removed from the URL. If the TAI is enabled and the URL matches at least one of the 
#   patterns specified for the urlBlackList property, the TAI will not handle the 
#   request. To use Java regular expressions, we must set the property 
#   wp.auth.tai.BasicAuthUseRegExp = true.
#
#    Default:  /${WpsContextRoot}/myportal*
#    Examples:  None available

wp.auth.tai.BasicAuthUrlBlackList=/${WpsContextRoot}/myportal*


# Property:  wp.auth.tai.BasicAuthUrlWhiteList
#
#   The list of patterns for which you want the TAI to handle the requests. 
#   Separate the patterns by whitespaces. The full path information of the URL of the 
#   incoming request is compared with each of the patterns specified for this 
#   parameter. Before comparing the URL to the patterns, the protocol, server, port, 
#   and query information is removed from the URL. If the TAI is enabled and the 
#   pattern specified for this property has at least one match and neither of the 
#   userAgentBlackList or the urlBlackList have a match, then the TAI handles the 
#   request. To use Java regular expressions, we must set the property 
#   wp.auth.tai.BasicAuthUseRegExp = true.
#
#    Default:  /${WpsContextRoot}/mycontenthandler*
#    Examples:  None available

wp.auth.tai.BasicAuthUrlWhiteList=/${WpsContextRoot}/mycontenthandler*


##### WP.SI PROPERTIES 

# WP.SI loaded from:
#
#    /opt/WAS_HOME/PortalServer/solutionInstaller/wp.si/wp.si.properties


#
# 1) Solution Installer settings
#
#    HCL WebSphere Portal using the following information to configure the Solution Installer
#

# Property:  wp.si.offeringName
#
#   Defines the name of paa offering directory
#
#    Default:  paa
#
#    Examples: 
#       1) C:/PaaLocation
#       2) /opt/IBM/WebSphere
#       3) paa

wp.si.offeringName=paa


# Property:  wp.si.configInstallExtensionList
#
#   Defines extension for applying SI feature pack
#
#    Default:  -applySIFeaturePack
#     Example:  -applySIFeaturePack

wp.si.configInstallExtensionList=-applySIFeaturePack


# Property:  wp.si.configRemoveExtensionList
#
#   Defines extension for removing SI feature pack
#
#    Default:  -removeSIFeaturePack
#     Example:  -removeSIFeaturePack

wp.si.configRemoveExtensionList=-removeSIFeaturePack


# Property:  wp.si.FunctionalArea
#
#   Defines SI feature pack function area
#
#    Default:  featurepackSI
#     Example:  featurepackSI

wp.si.FunctionalArea=featurepackSI


# Property:  wp.si.deleteIntermediateFileOnExit
#
#   Defines if you want to delete the intermediate xml file generated for XSLT
#
#    Default:  true
#    Examples:  None available

wp.si.deleteIntermediateFileOnExit=true


# Property:  wp.si.offlineMode
#
#   Set wp.si.offlineMode to true if you are running solution installer on a machine 
#   that does not have an internet connection Otherwise, set it to false
#
#    Default:  true
#    Examples:  None available

wp.si.offlineMode=true