This is "by design" (as discussed here: http://jira.rhq-project.org/browse/RHQ-323). There is no current way to uninventory services/ignore services permanently. This usually isn't an issue because in most cases, you'd just delete or ignore a _server_ and its services won't be inventories. But you do not have a choice with the platform services because you need to inventory the platform if you want to manage anything on that platform.
I doubt this will be fixed any time soon, but I created an enhancement JIRA on this - http://jira.rhq-project.org/browse/RHQ-1516 - this is something we've had discussions on in the past. Unsure if we want to allow uninventorying/ignoring services.
O.k. I think an option of services not being displayed to the user, again based on roles, would be good. For example, an operator would only want to see specific services on his screen which he is concerned of. So, it is only the view that is being changed.
Oh, well, that is different. You can do that today.
that's just setting up groups and roles and assigning those roles to users.
Read the docs regarding users and roles. You can have services hidden from view from users.
Here's some links to our new docs re: security:
You mentioned services being hidden from users. Do you mean to say, individual services or all the services at once. For example, an MBean Service, Threading, Compilation services exists in a JMX Server. I would want the user to view only the MBean Service and not the threading,compilation services.
I created an operator role, assigned it the inventory and control permissions.
Next I created a Mixed Group and added all the MBean Services to that group. And then, added the group to the operator role.
When I logged in as operator, I am still able to see the other services.
The "inventory" permission is a global permission for admin-type users only.
It gives a description of the permissions. Specifically it says this about the inventory permission:
*Allows the user to perform any task on any resource. Having a role with this permission grants the user to add, delete, configure, control and modify any resource, regardless of what other roles and associated groups of resources the user has been given access to.
So, if a user has that permission, they can do alot of things to all resources.
There is no special "view" permission - if a user is in a role that is assigned a group of resources, by definition, the user is allowed to view (read only) those resources. I think you confused the "inventory" permission with that.