MSE added to WCS, cannot assign services to controller

Question

I have a 30 day trial license of WCS and have added my WLC controller and APs.
I installed the new MSE virtual appliance and added it to the WCS, it shows up fine however I see no services.
When I SSH to the MSE and do a /etc/init.d/msed status I see that the CAS is up and running!
However when I try to synchronize services and add mobility services to a controller CAS is greyed out and won't let me check it
Where should I go from here?

Answer 1

Hello Pavel,
I can provide some background for what you've faced - it's on my blog to-do list, but hasn't come out yet to have helped you.
There was a change in the internals of User-UserGroup relationship handling between XI Release 2 and XI 3.x.
Previously, the relationship was exposed via the SI_GROUP_MEMBERS property for the UserGroup InfoObject, tied to the Users property in BIPlatform Web Services.
Now, the SI_GROUP_MEMBERS is read-only, listing all the members, but trying to change the value using getUsers() is ignored.
New properties (all properties named SI_ENT_* for both User and UserGroup, check the Query Builder for their names) have been defined for User and UserGroup InfoObjects, specifically for Enterprise authentication UserGroups.  This is to separate the handling of Enterprise UserGroups from those created for third-party authentication UserGroups (such as Windows AD user groups), such that you can add/remove memberships only for Enterprise UserGroups.
The Enterprise SDKs have been modified internally to make this change invisible when migrating from XI Release 2 -> XI 3.x.
However, since the BIPlatform Web Services work more directly with the InfoObject properties (via the BIAR API), it exposes the SI_ENT_* properties explicitly.
The gist is that, to affect User-UserGroup memberships, you have to use the getEnt*() methods for either User or UserGroup.
Sincerely,
Ted Ueda