1 of 1 people found this helpful
The fact that there is a ‘PS’ in the command name means that this was a command developed by ProServ or someone else and not part of the product install. so there may be an xml file you need to copy from the old install to the new one. is this being used in a script? there is a unreleased version of the command – RBACRole isRoleExists
ProServ = Proxy Server or Professional Services?
Is we want to use this command to check is the Role Exists, can we use simply as below?
blcli RBACRole isRoleExists $RBAC_Role
Where can that XML present? we are yet to upgrade the Production Env and it should be present on the PROD.
This is currently being used in a NSH Script for AD Sync
Professional services… it would be in the NSH/br/xml/cli directory. but if someone edited the stock xml, that is overwritten during the upgrade (which is why you put customized commands in new xml files).
Blcli_execute RBACRole isRoleExists $role
It’s still unreleased.
Found the XML.. and its created by your name only
The XML is found and is the same as it was in the previous version.
Question : How different is the isRoleExists different from the isRoleExistsPS ?
Is the PS only a tag/signature to find this was done by a Prof Serv or is there something more to it?
w/o the original command definition for the isRoleExistsPS i have no idea. why can’t you use the other one ?
Got this working now.. thanks