ConfigEngine validation targets | HCL Digital Experience
Some configurations can cause conflicts between Portal resources or with other web modules deployed into the WebSphere Application Server. You can check for conflicts by using ConfigEngine validation targets.
Conflicts can occur when the same value is specified for different resources. For example, a friendly name can conflict with a virtual portal context or a vanity URL. Conflicts are more likely when Portal is configured to use an empty context root and default home.
Portal includes three ConfigEngine targets to detect and prevent such conflicts:
path-conflict-check-full
- This target checks whether there are any conflicts between Portal resources and other servlets that are deployed into WebSphere.
path-conflict-check-path
- Required parameter: checkPath (for example /path/to/check)
path-conflict-check-uri
- Required parameter: checkURI
- Conflicts that exist only in a project or that occur when a project is published.
- Conflicts that exist in resources to which the user does not have access.
- Conflicts that occur when you add servlet filters to the request processing that change the path of the URL.
- assumeWpsContextRoot
- Performs the check as if the WpsContextRoot is set to the specified value.
- assumeWpsDefaultHome
- Performs the check as if the WpsDefaultHome is set to the specified value.
- assumeWpsPersonalizedHome
- Performs the check as if the WpsPersonalizedHome is set to the specified value.
- assumeWsrpContextRoot
- Performs the check as if the WsrpContextRoot is set to the specified value.
[wsadmin] path conflict report:
[wsadmin] ---------------------
[wsadmin]
[wsadmin] /wps/myportal/Home
[wsadmin] virtual portal URL context
[wsadmin] friendly name
[wsadmin]
[wsadmin] /wps/portal/Home
[wsadmin] friendly name
[wsadmin] virtual portal URL context
In this example, a conflict was found between a friendly name and virtual portal mapping.