Missing Role&Policy defined in DD during migration WL8.5 to WL9.2

Question

I'm in the midst of migrating our application to WL9.2. We are using roles and policy defined in the Deployment Descriptors (working fine under WL8.5).
In WL9.2 I've configured the Security Realm with "DD Only" option, so the role & policy will get loaded during the startup.
However, I'm getting the following warnings:
<4-May-2007 1:46:59 o'clock PM EDT> <Warning> <Security> <BEA-090669> <Ignored deployment of policy for resource "type=<ejb>, application=ARIS, module=CommonApp_wl.jar, ejb=PartyService, method=viewParty, methodInterface=Remote, signature={long,long}">
<4-May-2007 1:46:59 o'clock PM EDT> <Warning> <Security> <BEA-090669> <Ignored deployment of policy for resource "type=<ejb>, application=ARIS, module=CommonApp_wl.jar, ejb=PartyService, method=addParty, methodInterface=Remote, signature={long,ca.on.gov.mto.rus.clientManagement.business.service.PartyValue,ca.on.gov.mto.rus.clientManagement.business.service.PartyRelationshipValue}">
<4-May-2007 1:46:59 o'clock PM EDT> <Warning> <Security> <BEA-090669> <Ignored deployment of policy for resource "type=<ejb>, application=ARIS, module=CommonApp_wl.jar, ejb=PartyService, method=updateParty, methodInterface=Remote, signature={long,ca.on.gov.mto.rus.clientManagement.business.service.PartyValue}">
<4-May-2007 1:46:59 o'clock PM EDT> <Warning> <Security> <BEA-090668> <Ignored deployment of role "createParty" for resource "type=<ejb>, application=ARIS, module=CommonApp_wl.jar">
<4-May-2007 1:46:59 o'clock PM EDT> <Warning> <Security> <BEA-090668> <Ignored deployment of role "viewParty" for resource "type=<ejb>, application=ARIS, module=CommonApp_wl.jar">
<4-May-2007 1:46:59 o'clock PM EDT> <Warning> <Security> <BEA-090668> <Ignored deployment of role "viewAddress" for resource "type=<ejb>, application=ARIS, module=CommonApp_wl.jar">

Answer 1

Does the account get provisioned when you try to provision the same resource manually (via 'Add/Provision Resource') ? ?
If your role is getting assigned correctly then their is atleast no problem with the membership rules. Is the role tied to the Access Policy correctly. This is a basic and clean configuration which should work. Verify your system configurations again.
- Access Policy should have ResObj1 in the Resources to be provisioned by this access policy section
- Access policy should also have BasicRole in the Roles for this access policy section