On 5/4/2012 6:06 PM, chwjim wrote:
>
> Here's the deal:
> Had to rebuild my QA environment from scratch, and some of the
> configuration seems to have been missed in the rebuild. I've been over
> it a few times, but I can't explain why this problem is happening...


Double check when the RRSD loads that the config/GCV value for the
scoped container is correct. There is a stupid bug in Designer (Finally
fixed in 4.02) about DN attrs in the GCV/Config editors.

Then make sure the RRSD has the partition holding the User App driver
(since the Role Requests exist under the User App under the AppConfig
container).


> When I submit a request through User App, the request seems to go just
> fine, and the Resource shows in the 'Request Status' portlet just fine
> in the status of 'Running'.
> This is what I get for trace from the submission:
>
> 14:39:20,386 INFO [STDOUT] INFO [RBPM]
> [com.novell.idm.nrf.service.ResourceManagerService: requestResourceAssignment]
> [Resource_Request] Requested by
> cn=uaadmin,ou=ServiceAccounts,ou=RBPM,ou=Applicati ons,o=XYZidv, Target
> DN: cn=jchambers,ou=Users,o=XYZidv, Source
> DN:cn=CCM-SJHMC,cn=ResourceDefs,cn=RoleConfig,cn=AppConfig,c n=XYZUserApp,cn=IDVDriverset,o=XYZidv,
> Request
> DN:cn=20120504143920-b3d919653dcc42de9b23baeedda24ad2-0,cn=ResourceRequests,cn=RoleConfig,cn=AppConfig,c n=XYZUserApp,cn=IDVDriverset,o=XYZidv,
> Request Category: 10, Request Status: 0, Original Request Status: null,
> Correlation ID:
> UserApp#ResourceRequest#08f5baa9-57f9-496c-b7ef-30b9ed5ae74c
>
> 14:39:20,426 INFO [STDOUT] 82528716 [http-0.0.0.0-8543-3] INFO
> com.novell.idm.nrf.service.ResourceManagerService - [Resource_Request]
> Requested by
> cn=uaadmin,ou=ServiceAccounts,ou=RBPM,ou=Applicati ons,o=XYZidv, Target
> DN: cn=jchambers,ou=Users,o=XYZidv, Source
> DN:cn=CCM-SJHMC,cn=ResourceDefs,cn=RoleConfig,cn=AppConfig,c n=XYZUserApp,cn=IDVDriverset,o=XYZidv,
> Request
> DN:cn=20120504143920-b3d919653dcc42de9b23baeedda24ad2-0,cn=ResourceRequests,cn=RoleConfig,cn=AppConfig,c n=XYZUserApp,cn=IDVDriverset,o=XYZidv,
> Request Category: 10, Request Status: 0, Original Request Status: null,
> Correlation ID:
> UserApp#ResourceRequest#08f5baa9-57f9-496c-b7ef-30b9ed5ae74c
>
> The fact that the request seems to go in just fine, but ends up with
> the "Request Status: 0, Original Request Status: null" is particularly
> troubling. Is there somewhere that i can trace the status more closely,
> or more debug in userApp to turn on?
>
> We have a Role& Resource driver that is supposed to pick these up, and
> change the status, but this is all I get from the log when the Request
> is submitted:
> [05/04/12 14:39:00.222]:RR :TTL: Checking for expired role assignments
> for identities contained under: XYZidv
> [05/04/12 14:39:00.250]:RR :RES_TIMER: Checking for workflows to be
> retried...
> [05/04/12 14:40:00.019]:RR :TTL: Checking for pending role requests...
> [05/04/12 14:40:00.020]:RR :TTL: Checking for workflows to be
> retried...
> [05/04/12 14:40:00.021]:RR :TTL: Checking for expired role assignments
> for identities contained under: XYZidv
> [05/04/12 14:40:00.037]:RR :RES_TIMER: Checking for workflows to be
> retried...
>
> Anyone know what configuration of the RR driver controls its polling,
> where it looks, serialization, timestamping, or anything else that
> controls its picking up Resource Requests?
>
>