BI 4.2 – My first look on Administrator Cockpit
Just got a chance to look at BI 4.2 post GA. Every new feature added in this release looks promising and it will definitely going to add advantage to Platform support teams also it will be a big relief for every administrator/Architect for platform management.
Administrator’s cockpit is one among the impressive feature I can think of. However with the current capability we may not be able to achieve all our day to day monitoring/troubleshooting/Support activities. To know more about Administrator’s cockpit you can view the video here.
You can see 4 different sections when you navigate to Administrator’s cockpit in BI 4.2 CMC
With the current features we can get the overall summary of the Servers status along with an ability to start the server in case if it is down.
It would be good if we have the ability to navigate to Server/Server groups page of the CMC itself as we may required to perform other activities such as Stopping / Disabling currently running services in few scenarios. Along with this if we have the server running pattern over a period of time (time range as in other sections), it might have been very useful as it may help us to do the downtime analysis of each individual server.
Again this is similar to servers with over all summary of schedules with a time range.
Monitoring schedules is one among the key activity in BI platform as it is business critical. The typical expectation would be something like hour by hour analysis as below which will give a complete picture about the report schedules over a period of time. This will also give us the busiest times which will again help us to fine tune the environment/Adjust the report schedule times/size the BO services accordingly etc.…
Content usage and Applications
I don’t have much expectation from Content usage and Applications sections as of now, however I appreciate comments from other as well.
Disclaimer: I have written this blog in a view to share my expectation based on my experience and this doesn’t mean that these features will be incorporated in future releases. This blog is neither endorsed by SAP nor by my employer. Please don’t hesitate to comment on your ideas based on your experience.
I am planning to create a Idea place entry based on the response received here. Thanks for reading.
In the schedules, probably adding the top 10 long run report(s) might also be helpful. This gives an insight of which reports to focus on for query tuning.
This has been already covered in Audit report samples provided by Matt here Unlock the Auditing database with a new Universe and Web Intelligence Documents for BI4.1
Hello Mani, I have BI 4.2 installed for the first time. so far so good, but the administrator cockpit tells me "Network error occurred". What can I do? I could not find any configuration instructions.
ou need to validate your WACS and RESTFUL Webservices.
Please refer the KBA here
2267509 - Network error occurred in BI Administrators' Cockpit
thanks for the quick reply. but now I have a new error message that I can not explain. Make it a valid entry???
I have tried and found something that when I work with secEnterprise "Administrator" Administrator cockpit. With a user as a member of the administrator group WinAD logs, it does not work. How should I configure the WACS, so both work?
We have exactly the same issue (using BI 4.2 SP3 Patch 1).
This even happens when using a secEnterprise user, which is Member of a group,
which is again member of the built-in Administrators group.
Thanks for the hint to use the Administrator user, that works for us, too.
Could you find any solution for the issue itself?
we resolved “Network error occurred” by unlocking firewall port 6405
netsh advfirewall firewall add rule dir=in action=allow protocol=TCP localport=6405 name="TCP6405 wacs-cockpit"
I was having a similar issue where we have sub groups of the Administrator group, if you were a member of these the cockpit didn't work. However when the user is moved into the Admin group the access worked.
Does anyone know of a solution to this issue?