WEB_ROLE_NAME And WEB_PRINCIPAL_NAME Not Applying Correctly To Ejb-jar.xml and Weblogic.ejb-jar.xml
(Doc ID 1591951.1)
Last updated on OCTOBER 01, 2020
Applies to:Oracle Utilities Mobile Workforce Management - Version 184.108.40.206 and later
Information in this document applies to any platform.
AD - Active Directory
LDAP - Lightweight Directory Access Protocol
MWM - Oracle Utilities Mobile Workforce Management
EJB - Enterprise Java Beans
CM - Customer Modification
When trying to implement AD/LDAP integration with MWM 220.127.116.11 by following the LDAP Integration for Oracle Utilities Application Framework based products whitepaper (774783.1), the WEB_ROLE_NAME and WEB_PRINCIPAL_NAME doesn't appear to correctly configured for the ejb-jar.xml and weblogic.ejb-jar.xml when the value has been changed to something other than cisusers.
The SPLService.ear and SPLWeb.ear files fail to deploy.
There are errors in the weblogic (myserver) logs:
The security-role cisusers, defined in ejb-jar.xml or corresponding annotation, is not correctly mapped to a security principal. Make sure the security-role has a corresponding security-role-assignment element in the weblogic-ejb-jar.xml descriptor or corresponding annotation.
When looking at the above template files, the weblogic-ejb-jar.xml.template appears to have the correct section.
When looking at the ejb-jar.xml.template file, there is no section. Instead there are some #ifdef conditions that don't appear to have appropriate .include files in the file structure. They are missing.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!