Posts

Showing posts with the label bi

Three solutions from SAP Analytics portfolio

Image
OpenSAP has announced some new courses on SAP BusinessObjects Cloud and SAP Digital Boardroom powered by SAP BusinessObjects Cloud. While I am yet to learn about SAP BusinessObjects Enterprise, prospects of learning these new solutions created some confusion. So I took it upon myself to find out what these products are all about. SAP has been branding its products on analytics around BusinessObjects. BO has been a known brand name in analytics, so why rename and spoil that brand. Naturally BO is the name to go after. The on-premise solutions for analytics are delivered as  SAP BusinessObjects Enterprise . This product is available in three variants: Premium, Professional and Standard; in the decreasing order of functionalities delivered. Given the push for software-as-a-service or on-cloud products, SAP has introduced a cloud variant of BOE. They call it  SAP BusinessObjects Cloud . They originally called it  SAP Cloud for Analytics, but stuck to ...

Clearing Empty File Repositories in BI 4.x using Fileserver Prune Command

To cleanup empty folders from the file repositories Stop the input and output file repository server using CMC From windows command prompt, run the following command to clean up the input repositories "C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x64\ fileserver " -rootdir "c:/Program Files (x86)/SAP BusinessObjects/SAP BusinessObjects Enterprise XI 4.0/FileStore/ Input /" -prune -fg Now run the following command to cleanup output repositories "C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x64\ fileserver " -rootdir "c:/Program Files (x86)/SAP BusinessObjects/SAP BusinessObjects Enterprise XI 4.0/FileStore/ Output /" -prune -fg Start the file repository servers using CMC

Allowing HTTPS Connecton to SAP BI Explorer via iPad

When you call the SBO explorer in iPad to connect by using HTTPS, you may notice an error stating that the server did not accept the certificate. When an HTTPS call is made the server sends its certificate to the client (browser) the client verifies if this certificate can be trusted (if configured) the server asks for client certificate the client sends its certificate server verifies if this certificate can be trusted client and server complete the handshake The error that the server did not accept the server happens because there is no functionality to import the Safari client certificates into the iPad app and send them to the server. In order to continue with the handshake the server should be configured not to ask for client certificate (so that steps 3, 4 and 5 are avoided). You can disable the client certificate check process on Tomcat by setting  clientAuth=want in C:\Program Files (x86)\SAP BusinessObjects\Tomcat6\conf\server.xml