Assigning CfgAccessGroup to CfgPerson - Platform SDK 7.6.200.08

[jamesmurphyau]

Hey Guys,

I have this code:

CfgID cID = new CfgID(this.cServ,newPerson);
cID.DBID = newPerson.DBID;
cID.Type = CfgObjectType.CFGPerson;
foreach(CfgAccessGroup acg in oaGroups) {
acg.MemberIDs.Add(cID);
acg.Save();
}

It is working on one config server but not the other... It doesn't throw an error it just hangs.

Both config servers are 7.6.000.06

Any ideas?

Thanks

[René]

Hi,

Hard to say what went wrong without any log... How many Access Groups are on each Config server? Are there any Access Group with high number of members (hundreds, thousands...?)

R.

[jamesmurphyau]

Yeah we have one access group 'Users' with more then 11,000 people

[René]

That's quite a lot users (objects) so time to update AccessGroup will take some time.

Have you tried to measure how long it takes to add new person to that Access Group using CME?

R.

[Adam G.]

Rene is right. Not only does Config Server have to update all the objects but these changes get sent to all the applications with registrations on that Config Server (including CCPulse). Thus your 'hang' time is the C.S. just doing its job.

[jamesmurphyau]

Doing the same task (adding one person to the access group) takes around 1-2 seconds with CME - I've waited for 10mins+ and got nothing from the platform SDK.

I've looked into it a bit more and it seems to be this:

"private static void CreateDiffStructList" in "CfgObjectUpdateHelper.cs"

it pretty much creates XML that will just have one person in the AddedMemberIds section, but to do this it needs to loop thru 11,000+ people about 4 times it seems, and it uses XML objects when looping which makes it slower.

[René]

Hi,

That sounds strange and seems to be bug in COM. There is no reason for reading list of existing members of an Access Group when adding new one... Could you see in the ConfigServer log that COM sends a request to get list of all Access Group members?

I read release notes of Configuration Object Model (COM) Application Block and there are some fixed errors related to operations over Access Group in the release 7.6.200.10. Could you try that version?

R.

[jamesmurphyau]

I just realised I posted the wrong version in the title. We actually have 7.6.200.08 PSDK

I'll get 7.6.200.10, give that a shot and post back.

Thanks

[jamesmurphyau]

I updated to 7.6.201.01 and the issue still exists.

[René]

Hi,

In that case I would recommend you to open ticket with Genesys TechSupport as COM AB is fully supported product.

In the meantime...

A/ You can try to describe your issue on official Genesys Forum (https://devcommunity.genesyslab.com/forums/) as well. That forum is monitored by guys responsible for SDKs products and they are able to help in most cases.

B/ If it's bug in COM AB then you can try to use "pure" Configuration PSDK only.

R.

[jamesmurphyau]

I've opened a ticket and its with tier 3 support.

Will update with what happens when I hear something.

[Pol74]

If they are good, I can take all the credit. ,