Business Intelligence with SAP Business Objects 4.3

 Scheduling reports error -  source file error. [Invalid argument]: [CrystalEnterprise.DiskUnmanaged]  Environment SAP BI 4 SP8  The BI 4 server is not in windows domain  but SIA service is runned by a domain user As suggested in other B.O. forum we perfomed the following steps: in CMC,  the Job Server  must use a NETWORK SERVICE user that has all the permissions to read/write, that run's as a service, log on as service account etc. ( admin user) ; user has full read/write access to the folders.  we are following  the UNC naming conventions while specifying the folder name including the sub-directories. So when we scheduled reports in order to create acrobat files on a network folder such as \\ServerName\Path  directories. the scheduled istance Fails  and raises the error source file error. [Invalid argument]: [CrystalEnterprise.DiskUnmanaged]  Solution: In our case we decide to move the server in the Windows Domain and this solved the p

Query Builder:queries for extract reports refreshed after o before a specific date which could be useful to extract Webi reports in a specific folder with their name , owner, cuid, update date that have been refreshed since a date select si_name, SI_NAME, SI_OWNER,  SI_CUID, SI_PARENT_FOLDER_CUID, SI_UPDATE_TS FROM CI_INFOOBJECTS where SI_KIND='WEBI' and  SI_NAME NOT like '%Nuovo documento Web Intelligence%' and SI_INSTANCE='false' and SI_UPDATE_TS > '2013.01.01.00.00.00' and SI_PARENT_FOLDER = 851970 order by SI_UPDATE_TS asc Removing   SI_KIND='WEBI' you can extract also other document kind select si_name, SI_NAME, SI_OWNER,  SI_CUID, SI_PARENT_FOLDER_CUID, SI_UPDATE_TS FROM CI_INFOOBJECTS where  and SI_INSTANCE='false' and SI_UPDATE_TS > '2013.01.01.00.00.00' and SI_PARENT_FOLDER = 851970 order by SI_UPDATE_TS asc You can also exclude Administrator as owner  select si_

Maximum binary output size limit reached (ERR_WIS_30271) Environment SAP BI 4 SP 8 While exporting a huge  Web Intelligence report in Excel format BO raised the error: Max Binary file size limit exceeded. The document is too large to be processed by the server. Error WIS 30271  Cause This error message appears because BusinessObjects Enterprise allows documents to be saved with the limit specified for Web Intelligence Report server settings in the Central Management Console(CMC). To resolve the error follow the below steps: - Login to Central Management Console (CMC) using BusinessObjects Enterprise "Administrator". - Navigate to "Home >> Servers". - Click on "WebIntelligenceProcessingServer" to open its properties. Increase: Maximum Character Stream Size (MB) which specifies the maximum character stream size sent to the Web Intelligence client. Default value is 5. The valid range is 1 to 65535 MB. Bin

Visual Difference SAP BusinessObjects  Business Intelligence 4.0  - Version 4.0 SP2 Fixpack 5 Features - Visual Difference framework allows easy identification of changes - Comparison plug ins and viewers for each BI content type. (Eventually…) - LCMBIAR viewer answers: “How is this version of the BI application different from a previous version?” - Future service packs will provide comparison viewers for universes and other content types - For example, will answer: “What is different between these two versions of a universe? Can I easily merge changes?” - Impact Analysis - Understanding which objects in a universe have changed allows tester to focus only on reports which use changed objects. See Also Visual Difference Overview

Lifecycle management console features SAP BusinessObjects  Business Intelligence 4.0  - Version 4.0 SP2 Fixpack 5 Lifecycle management console is now included in SAP BusinessObjects Business Intelligence servers install package. New Visual Difference capabilities allow easy identification of changes. Scriptable promotions supported via a command line interface. • Central Management Console– Visual Difference, Promotion and Version Mgmt. Lifecycle management is now in CMC: New Objects supported Categories based promotion is now supported. Server group promotion is supported however the servers are not promoted. LCM is now localized. • Job is copied • Job is migrated Update Source system of job when Overrides no longer job specific  Supports new improved BI platform Audit infrastructure There are 2 new features specifically for integrated deployments with BW: • SAP Authentication is now supported. • Integration with the SAP standar

LCMBIAR Overview - LCM Command Line Tool SAP BusinessObjects  Business Intelligence 4.0 Version 4.0 SP2 Fixpack 5 Allows to: Promote content between Development, Test, and Production SAP BusinessObjects BI 4.0 environments. Allows you to use scripting to automate the import of objects. Terms BIAR and LCMBIAR:   BIAR :(BI Archive) is a collection of any binaries associated with a BI object and its associated metadata, all materialized in a zip file. An LCMBIAR file is the same idea, but each object is stored in an individual BIAR. Considerations:  Lifecycle management tool is to promote objects from BI platform 4.x to BI platform 4.X version only.  Upgrades from a previous BO version to BI 4.0 must be done using the Upgrade management tool. To rollback a job you need to use the UI, not command line  LCM Command Line tool is not used when CTS+ is available. What can you do with LCM Cmd line tool?  Report developer creates LCM Job with cont

SAP NOTE 1634962 - BI4 - How to import or export a LifeCycle Manager BIAR file using command line utility If you need to export or import a Life Cycle Manager (LCM) BIAR in BI 4 using command line utility. Environment l SAP BusinessObjects Business Intelligence Platform (BI) 4.0 l SAP BusinessObjects Business Intelligence Platform (BI) 4.1 Follow these steps: 1. Create a Properties file: Start by creating a properties file (Example c:\lcm1.properties) as below. Note that the names of properties and lcmbiar files are not specific and can be anything. While the below examples are provided with Windows syntax, they are applicable to unix environments as well with minor changes to file path locations. Here is an example of a properties file to EXPORT to an lcmbiar file: exportLocation=C:/lcm1.lcmbiar action=export LCM_CMS=localhost:6400 LCM_userName=Administrator LCM_password=password LCM_authentication=secEnterprise Source_CMS=localhost:6400