Posts

Business Objects HTTP 404 errors

 HTTP 404 errors in Business Objects XI R 3.1 The HTTP 404 error may happen for one of the following reasons: 1. The requested page was deleted in error. Check the deployment folder of the web application to make sure that the requested page exists. 2. The web application is not properly configured. Try to access other pages in this web application. If there are other pages in this web application that are not accessible, then there is a problem with the web application configuration. Consult the web application deployment instructions to check that the configuration files are valid, or redeploy the web application. 3. A system setting is incorrect. For example, the memory limit was reached or an ODBC DSN was not correctly configured. As a result, an exception was thrown and the expected page was not generated. Check the web server log or the web application log for error or exception records. 4. An environment variable is not properly set. This environment variable can

SAP Dashboards for IPAD

Image
The last SAP Dashboards SP05 for Mobile (Ipad -Iphone) The last SP05 SAP Dashboards  allows going on mobile (IPAD)  through HTML5  With this last SP you can verify old dashboards you developed in order to use them on Ipad. In this version you cano select  the right size for an iPad screen (1024x768) Beside you have to check the components/parameters in order to verify that are supported for HTML5, this check  is easy to do through a new functionality  for analayze dashboards components compatibility panel. A plus is the chance to choose iOS compatible fonts (Arial, etc. – otherwise, the embedded browser will try to use the best font). Before exporting the reviewed dashboard you can preview it using the mobile viewer option to see how its layout on an iPad: you can choose between: - Fit to screen - Original size Finally you can export  to the server the dashboard and you can  open it  using the SAP BusinessObjects mobile application on the iPad. Mobile co

Configuring BO Analysis on SAP HANA

You can also create an BO Analysis OLAP connection with SAP HANA as provider. With this HANA OLAP connection, you can use Analysis directly on top of a SAP HANA database. Configuration for SAP HANA If you use the SAP HANA appliance software, you can analyze SAP HANA data sources with Analysis. If you use SAP NetWeaver Business Warehouse, powered by SAP HANA, you can analyze BW queries, query views and InfoProvider with Analysis. You can connect and use a BW system, powered by SAP HANA, like other BW systems with Analysis. You have the following options to connect to SAP HANA:  - You can use an OLAP connection to connect via SAP BusinessObjects Business Intelligence platform. This connection can be created directly in the CMC of the SAP BusinessObjects BI platform like BW system connections to the platform. The SAP HANA OLAP connections are currently not SSO compatible. - You can use a JDBC connection to connect via SAP BusinessObjects Business Intelligence platform .

BO Analysis - Creating and managing BW system connections in SAP BusinessObjects BI4 - BOE

You can use Analysis with SAP BusinessObjects Business Intelligence XI 4.0 or SAP BusinessObjects Enterprise XI 3.1   as the central content management system for Analysis workbooks  and presentations and as platform for managing data source connections. Before users can begin working with business data in Analysis, you have to create connections to BW systems so they can add data sources to their Analysis workbooks. You create new connection objects and manage existing connection objects in the module OLAP Connections in the Central Management Console (CMC) of the business intelligence platform. To create a connection to a BW system, you define a connection to any object of the BW system. You also have to make sure that the client PCs can communicate with the connected BW systems. If the BW system uses a message server the client PCs must specify the service name of the message server in the system services file at :\WINDOWS\system32\drivers\etc\services.  Config

Error RWI 00323 - Cannot retrieve the document with the passed obsolete token.

Cannot retrieve the document with the passed obsolete token. (RWI 00323) Cause An error occurred during document state deserialization. This might be caused by a storage token that identifies a document state, which is no longer available in the storage tokens stack. Action In the webi.properties file, increase the value of storage tokens stack size. Also, ensure that the storage token is valid before using it. In BO XI R3.1 environment this problem could be also fixed installing the latest fixpack/service pack. See also: BUSINESS OBJECTS ERRORS LIST

Error RWI 00239 - Connection failed. The server has reached the maximum number of simultaneous connections

Connection failed. The server has reached the maximum number of simultaneous connections. (RWI 00239) Cause The maximum number of server connections allowed has been reached. Action Either raise the value of the maximum connections server parameter, or add another server instance. To modify the maximum connections value: 1. Log on to BusinessObjects Enterprise Central Management Console. 2. Click on Servers. 3. Expand Server Categories, and click on Web Intelligence. 4. Under Server name, double-click on WebIntelligenceProcessingServer. The Properties window appears. 5. In Properties window, under Web Intelligence Processing Service, enter a greater value for Maximum Connections. In our customer case environment BO XI R3.1 on windows server 2008 R2, with 4 cpu, 16 GB Ram and more then 300 BO users   we inserted a 100 connections value  and this value fixed the problem. See also: BUSINESS OBJECTS ERRORS LIST

QaaWs and customized Authentication in Xcelsius

Xcelsius provides an authentication mechanism that enables you to avoid logging into InfoView twice with the same session ID. Take note of following rules if you customize authentication: - An existing session ID is used only if the user name and password are blank (if they are not hard coded or not passed as input values captured by a dialog). This occurs when Query as a Web Service is running in InfoView or Dashboard Manager. - If the user name and password are not blank, then use these values to authenticate the user. No session is created. This is the most scalable scenario and is the preferred option for large-scale usage. - If there is no pre-existing session (and username and password are blank), Xcelsius displays the standard security dialog, in which a session is created. This occurs when Xcelsius designers do not build their own security dialog. See also: Consuming a query as a web service in Xcelsius How to start Query as a Web Service