Business Intelligence with SAP Business Objects 4.3

To consume a query as a web service inside Xcelsius, use the Web Service Connector The Web Service Connector component allows a Flash document created in Xcelsius to communicate with Query as a Web Service through SOAP, using point and click. The Xcelsius Flash document is self-contained and communicates with the web service to display data visually. The only prerequisite is that there be a SOAP-based web service available to the Flash document. The Web Service Connector component, when activated, creates a SOAP-based message (basically an XML document) and sends it to the web service. The web service responds with a SOAP-based message of its own. The Web Service Connector component then sends this data to all the other components, resulting in a live visual representation of your data. There are many public web services available, and many different toolkits and packages for SOAP-based web services. To use public web services and packages that already have a web service on t

This kind of query  is useful because can be used it to consume data into Xcelsius Dashboards in alternative to connecting through Live Office. See: Sap BO Dashboards 4.0 - Xcelsius 2008 Query as a Web Service is used with a Central Management System (CMS) The CMS contains the server component that stores the Query as a Web Service catalog and hosts the published Web Services. When you start Query as a Web Service for the first time, you must define the host server before starting. Each successive time you start Query as a Web Service you select an available host server, then log into the CMS. Once you are logged in, the Query as a Web Service startup Query Catalog page appears.  From this page you can start the query creation and publication wizard to publish a new query and edit existing published queries. How To define a query in Publish as a Web Service Wizard The "Query" page of the "Publish as a Web Service Wizard" allows you to use a quer

Tutorial  In order to activate auditing in BO XI R3.1 ( procedure it's similiar on BI 4 CMC ) you must follow these steps: Logon  into CMC Go to servers page Chose the BO server on which you want to activate auditing, for example let's open Web Intelligence server, and select WebIntelligenceProcessingServer click the right button in order to select: Audit Events here you will choose the events you want to audit The procedure is similar also on all the other Business Objects Servers you want to audit. For detail  about the new CMC BI 4 auditing page: CMC in Business Objects BI 4 - New features

SAP HANA Data Management You use the SAP HANA modeler , which is accessible as a perspective of the SAP HANA studio , for modeling and managing SAP HANA data . It allows technical users to create new or modify existing models of data. In addition, the initial configuration of the data replication is done in the SAP HANA modeler. Let see how to configure data replication to provide the necessary metadata and data to the SAP HANA box.  You need to perform the following steps: 1. Load table metadata from the data provider systems (source systems) into the SAP HANA database (target system) for all tables of the source system or for a subset of tables 2. Load data (initial load) from the data provider systems (source systems) into the SAP HANA database (target system) for a selection of tables 3. Start continuous replication of data changes from the data provider systems (source systems) into the SAP HANA database (target system) for a selected subset of tables Once t

SAP Visual Intelligence  can Acquire data from different data sources SAP Visual Intelligence 1.0.6 You can acquire data from the following data sources: - C.S.V file - SAP HANA cube - MS Excel - Freehand SQL - SAP BusinessObjects Universe Each data source can be adapted before acquisition to include or remove columns. For certain data sources you have other options, for example data formatting, column naming and trimming, and specifying column name prefixes. The acquisition options are described for each individual data source. Note: For data that is acquired to manipulate locally the maximum number of cells that can be acquired is 15 million. Spreadsheets with more than this maximum are cut off at this point. Read also: Using SAP Visual Intelligence SAP Visual Intelligence SAP VISUAL INTELLIGENCE FEATURES SAP HANA Introduction

Environment: BO XI R3.1 SP 4 on WindowsServer 2008 R2 An error occurred during document utilization. This might be due to insufficient memory or an I/O error. Action Ensure that there is sufficient memory available. Also check for any webi.properties customization. That is: look for  ..: \Business Objects XI 31\Tomcat55\webapps\dswsbobje\WEB-INF\classes #WID_FAILOVER_SIZE=10 #WID_STORAGE_TOKEN_STACK_SIZE=10 #REP_FAILOVER_SIZE=10 – DeskI documents #REP_STORAGE_TOKEN_STACK_SIZE=10 >> Change all the values to 0 (no limit) >>Remove the # symbol - uncomment  More Intrusive solution  Add a request Timeout in the WebI and WebJob Servers (36000 for example)  Modify the CCM settings for Webi Server:  Add -port ServerIP  Add : -requesttimeout 36000  Modify -ns ServerIP After that restart Tomcat and all servers. See also: BUSINESS OBJECTS ERRORS LIST

In order to migrate  a universe from a prior CMS release (XI R3.1 and XI r2)  to a BI 4 CMS, you must use the Upgrade management tool  (UMT)  that is provided with BI 4. SAP Business Objects 4.0 BI 4 includes two universe development tools: - The universe design too l, which is an upgraded release of the Universe Designer tool you are familiar with if you are an existing Business Objects customer wich creates a UNV file . - and the new Information design tool (IDT) , which is the new universe authoring tool provided with BI 4 that produces a UNX file . A UNX universe file is published on the CMS  is the result of a merge of three components that are designed in the information design tool.: -  CNX files for connections -  DFX files for data foundations -  BLX files for business layers A UNX is the result of CNX + DFX + BLX where: the data foundation    (DFX )  contains a schema  of tables and joins from one or more relational databases ,  through connections (CNX), th