As an administration requirement we have to extract list of users within our BO server. I looked upon the forum and found that we can use query builder for the purpose.
I used query builder and ran query " Select SI_NAME from CI_SYSTEMOBJECTS where SI_NAMEDUSER=1 AND SI_KIND='User' " to list down the users. No issues till this point, the query ran fine and gave list of users in the server but I couldn't find a way to take export of this list. Then I thought of creating a webi report on top of CMS database pulling column "dbo.CMS_Aliases6.Alias" into report but that shows some ids for all enterprise users.
Please let me know if there is any other method that I can implement to take export of user list from server. I know this can be achieved using SDK but I want to try it at last.
Thanks Ravi for your prompt response .
I am using version 3.1 sp2. As suggested by you I tried looking to create query under 'Query Result' but couldn't create any such query that can bring user list. I might be missing something here as I am new to 'QueryRresult'.
Pls let me know the right way of creating the desired query so that I can get the user list.
I got the query now. I choose "Everone" in first section i.e. "Query Principal",in second section I selected "Don Not Quey by permission" and in last section i.e. "Query Context" I choose "Users" and this way I got the whole list of users including administrator and guest.
But, now when I am trying to take export of this output nothing is happening . It is not asking me any folder to store csv file.
Does it store the exported file to some default location??
After clicking the Export .
1.Go folders>administration tools folder
2.Right click on Administrator tools >Security query export >
3.Click on History
4 In the History tab ,you will see the program Object schedule(See screen shot2)
5.Now clicking on the Instance Time link will open a .txt file and shows you the rights
6. while saveing this file save as in CSV format.
If you want to see only users after saveing the csv , Just apply the filter on Rights collections check only system . It will dis play only the users.
Useing Query Builder also We can do
After Genrated the Report go to file and save as html in your local .
Select the HTML Page and Right click Open with Excel . The report will open in excel .
I am able to take excel output of user list by opening hlml file in excel (the second option that you had suggested).
Though it serve my purpose, still I am curious to know about the "Query result" option.
I could not find "Security query export" on right click on "Administrator Tools" folder. The only files that are present there are "Update Window AD Group Graph" and "Update Window AD Group Graph and Aliases". There is no other file available under the folder.
Would really appreciate if somebody help me to explore this option as well.
you can find the admistration tools folder under the All folders. in side that folder you can see the Security Query Export Program object. Right click on that object see the History .
May be you deteled that object it comes with the bo Istalation. if you have anther environment please checkit there.
Here is a little excel file with a bit of VBA code to extract from a CMS the complete list of user and the list of groups each user is member of. Quite useful when you need to check group membership.
1. Goto below link:
2. Scroll down and download an excel file namely "BOXI UserListV3.xls".
3. Open the file in MS Exel.
4. Enable Macro settings
5. Specify your CMS credentials and pull the data.
NOTE: BO Client tools needs to be installed on the machine where you are executing the macro, so it can communicate with CMS.
If BusinessObjects product is installed on Windows Server platform, you can directly execute the macro on the BO server; however in case of Linux/UNIX deployment, we need to execute the script on our Windows XP or 7 machine.
In such cases, one of the BusinessObjects Client tools [like Crystal Reports 2008, Web Intelligence Rich Client, etc...] needs to be installed on your local machine, so macro can communicate with BO.
Otherwise macro would throw an error.