This action might not be possible to undo. Are you sure you want to continue?
Product(s): IBM Cognos 10; Area of Interest: Infrastructure
Daniel Wagemann Cognos Proven Practices Advisor IBM Rich Borucki Solution Specialist IBM Pierre Valiquette Software Engineer IBM This document is intended to provide a single point of reference for techniques and product behaviours when dealing with SAP® NetWeaver® Business Warehouse® (SAP BW) as a data source in IBM Cognos 10. View more content in this series Contributors This effort would not have been possible without contributions from Patricia Defosse, Linda Whitney, and Agnes Chau. Skill Level: Advanced Date: 07 Jan 2011
Purpose This document is intended to provide a single point of reference for techniques and product behaviours when dealing with SAP® NetWeaver® Business Warehouse® (SAP BW) as a data source in IBM Cognos 10. Applicability Generally speaking, the practices and methods noted within the IBM Cookbook for IBM Cognos 8.4 for use with SAP NetWeaver Business Warehouse are applicable to
© Copyright IBM Corporation 2011 IBM Cognos Proven Practices: IBM Cookbook for IBM Cognos 10 for use with SAP NetWeaver Business Warehouse™ Trademarks Page 1 of 25
your IBM Cognos 10 on SAP BW environment. Hence the guidelines mentioned in this document can be considered an addendum, or delta practices, and are specific to IBM Cognos 10 with SAP BW. The techniques and product behaviours outlined in this document apply to: 1. IBM® Cognos 10® version 10.1 2. SAP BW Query Designer® version 7.0 Exclusions and Exceptions The techniques and product behaviours outlined in this document may not be applicable to previous or future releases.
SAP BW Objects and Queries
IBM Cognos 10 leverages the SAP BW investment within your organization by providing access to the SAP BW metadata and business content. The guidelines and practices for the design and use of SAP BW objects and queries can be found within the document entitled IBM Cookbook for IBM Cognos 8.4 for use with SAP NetWeaver Business Warehouse located at http://www.ibm.com/developerworks/ data/library/cognos/page468.html, and are generally applicable when accessing SAP BW with IBM Cognos 10. In addition to the guidelines noted within the SAP BW objects and queries section of the above referenced cookbook, IBM Cognos 10 provides support for time-dependent hierarchy structures. The following describes time-dependent hierarchy structures, and how they are depicted in IBM Cognos 10. Time-Dependent Hierarchy Structures Some SAP BW users require the ability to create reports depicting hierarchy structures that are valid for a specific time period; therefore they need to create the hierarchy structure as a time-dependent. For example, assign retailers to different geographies at different times within the context of a hierarchy.
IBM Cognos Proven Practices: IBM Cookbook for IBM Cognos 10 for use with SAP NetWeaver Business Warehouse™
Page 2 of 25
ibm. this SAP hierarchy represents retailers in different geographic locations. This illustration shows how the retailer located in the country of Algeria from the time period 01-01-2000 to 31-12-2004 has ceased operations at the end of 2004. under the Hierarchy tab. IBM Cognos Proven Practices: IBM Cookbook for IBM Cognos 10 for use with SAP NetWeaver Business Warehouse™ Page 3 of 25 . which started to log transactions in 01-01-2005. and was replaced by new dealer located in Morocco. Notice in “Figure 2”. the option “Time-Dependent Hierarchy Structure” has been selected.com/developerWorks/ developerWorks® Figure 1: This image shows time-dependent structures Algeria and Morocco As the example above illustrates. for the characteristic ZD_CCUST (Retailer) in SAP BW.
IBM Cognos Proven Practices: IBM Cookbook for IBM Cognos 10 for use with SAP NetWeaver Business Warehouse™ Page 4 of 25 . we can see in “Figure 3” that for the hierarchy named “Retailer TimeDep1”.com/developerWorks/ Figure 2: Time-Dependent Hierarchy Structure is defined within the SAP BW InfoObject Since ZD_CCUST (Retailer) contains a time-dependent hierarchy structure. different validity dates are assigned for countries “Algeria” and “Morocco”.developerWorks® ibm.
IBM Cognos Proven Practices: IBM Cookbook for IBM Cognos 10 for use with SAP NetWeaver Business Warehouse™ Page 5 of 25 .com/developerWorks/ developerWorks® Figure 3: Time-dependent structures defined with different validity dates IBM Cognos 10 allows users to visualize and interact with the SAP BW timedependent hierarchy structures. and can be leveraged as alternate hierarchies within IBM Cognos 10 BI. how the timedependent hierarchy structures are depicted in the IBM Cognos 10 Framework Manager model. Notice in the image “Figure 4”.ibm.
and is the starting point for IBM Cognos 10 and SAP BW integration. IBM Cognos Proven Practices: IBM Cookbook for IBM Cognos 10 for use with SAP NetWeaver Business Warehouse™ Page 6 of 25 . This will help to optimize the IBM Framework Manager import process when accessing metadata from SAP BW. In addition to the guidelines noted within the metadata modelling section of the above referenced cookbook.ibm.com/developerWorks/ Figure 4: Alternate hierarchies are arranged by validity dates General Principles when Accessing Time-Dependent Hierarchy Structures Since the time-dependent hierarchy structures are depicted in the IBM Cognos 10 Framework Manager as alternate hierarchies.4 for use with SAP NetWeaver Business Warehouse located at http://www. The guidelines and practices to leverage SAP BW metadata within IBM Cognos Framework Manager can be found within the document entitled IBM Cookbook for IBM Cognos 8.com/developerworks/data/library/cognos/page468. IBM Cognos 10 Framework Manager IBM Cognos 10 Framework Manager provides the metadata model development environment in IBM Cognos 10. import only the definitions of the hierarchies you need.developerWorks® ibm.html. IBM Cognos 10 Framework Manager provides the ability to define a package to use Dynamic Query Mode (DQM). and are generally applicable when accessing SAP BW metadata with IBM Cognos 10 Framework Manager.
• Ease of maintenance with query visualization. This mode is the default processing method for a package unless DQM is specifically defined for the package in IBM Cognos 10 Framework Manager. To better understand the benefits of the Dynamic Query Mode and the steps necessary to implement the DQM. through the SAP BW OLAP BAPI interface to access SAP BW data. Requirements for connectivity to all supported OLAP data sources. and users of this mode can expect similar or slightly improved response times in IBM Cognos 10. Both the Compatible and Dynamic query modes in IBM Cognos 10 utilize patented MDX technology to send optimized Multi-dimensional Expressions (MDX) specifically for SAP BW. Definitions and variances between Compatibility and Dynamic Query Modes. • Significant improvement for complex OLAP queries through intelligent combination of local and remote processing and better MDX generation. and is SAP® Certified Integration with SAP NetWeaver®. Page 7 of 25 IBM Cognos Proven Practices: IBM Cookbook for IBM Cognos 10 for use with SAP NetWeaver Business Warehouse™ . Dynamic Query Mode is enabled at the package level using IBM Cognos 10 Framework Manager or Self-Service Package Wizard and is leveraged by IBM Cognos 10 solutions such as Reports Studio. and timeliness expectations with improved query execution techniques.ibm. • Security-aware caching. The IBM Cognos 10 Dynamic Query Cookbook will contain additional information for the following topics: • • • • IBM Cognos 10 architecture.com/developerWorks/ developerWorks® Dynamic Query Mode The IBM Cognos 10 architecture provides the ability to utilize two query modes: • Compatible Query Mode • Dynamic Query Mode Compatible Query Mode triggers the traditional query methods as utilized in IBM Cognos 8.ibm. Java-based query mode which offers the following key capabilities: • Query optimizations to address query complexity.html. Business Insight Advanced. • New data Interfaces leveraging 64 bit processing. and Query Studio.4. DQM is an enhanced. Process to define a package to use DQM with IBM Cognos Framework Manager. refer to the Dynamic Query Guide provided in the IBM Cognos 10 installation documentation or the IBM Cognos 10 Dynamic Query Cookbook located at: http://www. data volumes.com/developerworks/data/library/cognos/ infrastructure/cognos_specific/page529.
locate this section of the configuration file: IBM Cognos Proven Practices: IBM Cookbook for IBM Cognos 10 for use with SAP NetWeaver Business Warehouse™ Page 8 of 25 . SAP BW Specific Configuration Files within IBM Cognos 10 When accessing SAP BW using Dynamic Query Mode. In order to perform this level of tracing. many of the principles which applied to IBM Cognos 8.xml. Tracing The XQEODP. xqeodp.xml in earlier versions of the product.com/developerWorks/ IBM Cognos 10 configuration settings for all supported data sources.1 are still in effect. The two main configuration files for Dynamic Query Mode are xqeodp.CONFIG.CONFIG.4.developerWorks® • • • • ibm. and their usage has not altered since then.xml and qfs_config.config.xml will be suffixed by “– example”. By default. Simply remove the “-example” and the file will take effect upon startup of the query service. and bw. It should be noted however that the configuration entries are located in different configuration files.properties.config. located under the configuration directory. The configurations which should be of concern include: • • • • • useFastGetMembers useMDXToRetrieveMembersFor useMDXToRetrieveMembersLimit displayProperty detectSAPVariableUniqueness These configuration entries resided in both sapbw_config. IBM Cognos 10 caching.4 for use with SAP NetWeaver Business Warehouse located at http://www. XQEODP.com/ developerworks/data/library/cognos/page468. All other entries should be left unaltered unless specifically instructed by IBM Cognos Customer Support or Development. located under configuration\xqe directory.ibm.XML file also contains the mechanism to trace some of the communications between the Query Service and SAP BW such as MDX statements and BAPI (Business Application Programming Interface) function calls used to retrieve metadata and data from the underlying systems. Some new entries have been added and some entries are no longer required for DQM. Administration features specific to DQM.XML This file contains the main configuration file which most will be familiar with and their explanation can be found within the IBM Cookbook for IBM Cognos 8.html. Debugging and troubleshooting the DQM.
This limit will easily be reached. two entries can be altered. BW. we can increase the potential limit to 150. The second entry which some may be interested in leveraging is use. it must be stated that entries in this file should not be altered unless specifically instructed by Customer Support or Development. a new file is created. This will dictate whether the “From” date or the “To” date will be utilized when setting the KEYDATE for time-dependant hierarchies.valid.xml. Should the potential size of the result exceed this limit.e.000. These other heuristics will avoid storing results which would be slower to write/read from the cache then reading directly from SAP BW (i.from=true. With that said. This sets the maximum potential size of a tuple which we will store in the cache. They are meant for very specific scenarios and their applications are server wide.000. The potential is calculated by multiplying the members received from each dimension requested from SAP BW.PROPERTIES This file contains some of the entries dictating the default behavior of the query engine specifically for SAP BW.000 will be stored in the cache as other heuristics are also considered by the engine. this value is set to 150. By default. in order to trace some of the outgoing MDX statements.000. very large dense reports). you would set the following entry: <component name="SBWODP"> <eventGroup name="Configuration"/> <eventGroup name="Connection"/> <eventGroup name="Function"/> <eventGroup name="Metadata"/> <eventGroup name="DataQuery" level=”info”/> <eventGroup name="Timing"/> <eventGroup name="Exception"/> </component> The most frequently used entries are “DataQuery” and “Function”. Please note this only affects data cache (tuple storage) and not metadata cache. Each timeIBM Cognos Proven Practices: IBM Cookbook for IBM Cognos 10 for use with SAP NetWeaver Business Warehouse™ Page 9 of 25 . The log files are prefixed with xqelog-<timestamp>.com/developerWorks/ developerWorks® <component name="SBWODP"> <eventGroup name="Configuration"/> <eventGroup name="Connection"/> <eventGroup name="Function"/> <eventGroup name="Metadata"/> <eventGroup name="DataQuery"/> <eventGroup name="Timing"/> <eventGroup name="Exception"/> </component> Add level=”info” to an entry and restart the query service. Those two entries will show most of the pertinent calls made to SAP BW which should be of concern. The first entry is lolap. Each time the query service starts. First and foremost. and this will start recording the requested entries to the log file which is located under the logs\xqe directory.000. then IBM Cognos will not be caching the data results.tupleStorageThreshold. This does not mean that all tuples up to 150. For example.ibm. therefore.
PROMPT. Figure 5: IBM Cognos Administration for Dispatchers and Services IBM Cognos Proven Practices: IBM Cookbook for IBM Cognos 10 for use with SAP NetWeaver Business Warehouse™ Page 10 of 25 .developerWorks® ibm. However. the “From” date will be used. Advanced Environment Settings In IBM Cognos 10. perform the following steps. Step by Step for changing the Advanced Environment Settings To change the default parameter value. and all will be revealed in an IBM Cognos prompt page unless they are explicitly called and hidden from an IBM Cognos report. 1. all optional SAP prompts of a SAP BW InfoQuery are prompted by default. select the concerned hierarchy and note the two properties: “Valid_From” and “Valid_To”. Go to IBM Cognos Administration -> Configuration -> Dispatchers and Services. When authoring a report against such hierarchies.FORCEDATASOURCEPARAMETERPROMPT must be set to FALSE to hide the optional SAP variables. IBM Cognos will set the key date based on these stored periods.com/developerWorks/ dependant hierarchy contains a validity period which is stored in the model /package. Changing the value to “false” will have the following effect: 1. 2. Values exist for both “From” and “To” -> “To” date is used as key date. Values exist only for “To” -> “To” date is used as key date. and set the parameter to FALSE. If no values exist for “To” -> the current date is used as key date. In the left hand pane. The validity period of time-dependant hierarchies can be found in the IBM Cognos Framework Manager model. The property called RSVP. prior to executing a report. By default (true). 3. you do have the ability to change this default behavior with an advanced server property that will hide the optional variables without having to explicitly call the optional SAP variables in an IBM Cognos report.
choose ‘Edit’. Set the following parameter to FALSE to hide optional SAP variables. Figure 6: View the properties of the ReportService 4. Click ‘OK’. Click on the dispatcher URL. Select the ‘Settings’ tab. 7. RSVP. Click the checkbox option to ‘Override the settings acquired from the parent entry’. and ‘OK’ again.com/developerWorks/ developerWorks® 2. 3. Figure 8: Edit the advanced settings 6.ibm. IBM Cognos Proven Practices: IBM Cookbook for IBM Cognos 10 for use with SAP NetWeaver Business Warehouse™ Page 11 of 25 . choose the ‘Properties’ link. For the ReportService.FORCEDATASOURCEPARAMETERPROMPT (default is TRUE) Figure 9: Setting this parameter to FALSE will hide optional SAP variables 8.PROMPT. Figure 7: View Settings 5. For the row labeled ‘Environment’. ‘Advanced Settings’. A parameter input screen will then appear.
3. 5. and push filtering of the data to the SAP BW data source. Performance of analysis capabilities can be improved substantially with DQM when accessing SAP BW data. a new capability introduced in IBM Cognos 10. Performance of analysis capabilities can be improved substantially with DQM when accessing SAP BW data. or changes made to the variable definition in IBM Cognos Framework Manager or the Self-Service Package Wizard.developerWorks® 9.com/developerWorks/ IBM Cognos 10 Report Studio In addition to the guidelines noted within the IBM Cookbook for IBM Cognos 8. To re-prompt for SAP variables in Business Insight Advanced. The following statements provide general statements which can be applied within the Business Insight Advanced (BIA) environment when working with SAP BW data. 3. The user interface is designed for business users to get insight into their business. 2.Use SAP BW queries with variables and filters to restrict the data set from BW to help limit the size of data passed from SAP BW. IBM Cognos 10 Business Insight Advanced Business Insight Advanced is a Web-based tool used to author reports and analyze data. The following statements should be considered when using IBM Cognos 10 Report Studio over a SAP BW data source. consult the IBM Cognos Business Insight Advanced User Guide provided in the IBM Cognos 10 installation directory. 1. The format of the SAP BW variables will be determined by the definition of the variable within the SAP BW query.4 for use with SAP NetWeaver Business Warehouse for professional report-writing with SAP BW. . IBM Cognos Proven Practices: IBM Cookbook for IBM Cognos 10 for use with SAP NetWeaver Business Warehouse™ Page 12 of 25 . Refer to the IBM Cognos 10 Dynamic Query Cookbook to better understand the benefits of the Dynamic Query Mode. Access SAP BW data with DQM-enabled packages whenever possible. No formatting of the variable display format is done within Business Insight Advanced. Leverage SAP BW InfoQuery optional variables as opposed to filtering within Business Insight Advanced where appropriate. can be built to access data from SAP BW. Stop and restart the ReportService. ibm. 4. 6. This approach will leverage the processing power of the SAP BW server. 2. For more information on how to use Business Insight Advanced. Access SAP BW data with DQM-enabled packages whenever possible. 4. Use SAP BW queries with variables and filters to restrict the data set from BW to help limit the size of data passed from SAP BW. click the refresh icon at the bottom of the page. 1. Active Reports.
build a IBM Cognos Framework Manager package ‘fit for purpose’ with only one data source. which they do not need. and request that users only choose one or two objects at a time per package. making the process a longer experience. For example. However. Consider updating the default settings to limit how many SAP BW queries or cubes a user can import for metadata. model. 8. if the same display attribute is requested later. and help to limit the size of the IBM Cognos Content Store.com/developerWorks/ developerWorks® Figure 10: Refresh in Business Insight Advanced 7. 1. 9. However. create the reports in ‘Page Design’ mode found in the View menu. such as several alternate hierarchies. This approach will help to alleviate user-confusion and mitigate the probability that users will attempt to view unnecessarily high volumes of data which may provide slower performance. When building a report and you do not want data to refresh as each column is brought in. And consider hiding or omitting elements. assist with an optimized import of the SAP BW metadata. 2. the user can select a maximum of two SAP BW cubes and five SAP BW InfoQueries. To simplify reporting for end users. This will help to limit and control the number of objects which are imported at one time. they still need to rely on IT resources to import. business users do not have data modeling skills nor are they required to model their SAP BW information. There is a limit to the number of objects a user can select. performance should be greatly improved as the data will reside in the DQM cache for users who have the same SAP BW security profiles. rather than allowing them to see all available content. (View -> Page Design). But consider starting small.ibm. deliver a package that delivers only what the users need from a data source. Often. The Self-Service Package Wizard helps business users by providing direct access to their information in SAP BW by enabling them to create their own IBM Cognos packages based on the SAP BW source. Bring dimension levels into the report as opposed to display attributes to improve the initial response from SAP BW when the data is not cached with DQM. These parameters may be updated IBM Cognos Proven Practices: IBM Cookbook for IBM Cognos 10 for use with SAP NetWeaver Business Warehouse™ Page 13 of 25 . Consider these general statements when working with the Self-Service Package Wizard in IBM Cognos 10. and package a data source. By default. Self-Service Package Wizard The IBM Cognos 10 Self-Service Package Wizard (SSPW) allows users to create connections directly from IBM Cognos Connection to pre-modeled SAP BW data sources without using IBM Cognos 10 Framework Manager.
5. This practice is aligned with the proven practices as stated for IBM Cognos Framework Manager and SAP BW. there could be ramifications to existing reports that were built on the package. 4. you have the option to select at the cube or SAP BW query level. IBM Cognos Proven Practices: IBM Cookbook for IBM Cognos 10 for use with SAP NetWeaver Business Warehouse™ Page 14 of 25 . When publishing a new package. within Cognos Administration and the steps to change are noted below in this section. consider importing SAP BW metadata using IBM Cognos Framework Manager where you have the option to select only the hierarchies that you need. Also note that in this case. the Cognos Administrator must update the SAP BW connection properties to ‘allow personal packages’. To change an existing package with SSPW. 7. and definitions of any objects under those levels will be imported. It may be necessary to re-import the SAP BW InfoQuery with SSPW or IBM Cognos Framework Manager to get the latest definitions. With SSPW. In the event it is required that updates to the package will be necessary on a iterative basis.com/developerWorks/ 3. Import metadata from SAP BW queries rather than selecting the cube. This will provide users the ability to leverage SAP BW objects not otherwise available from the cube. and variables. development. select the option ‘Use Dynamic Query Mode’. consider using IBM Cognos Framework Manager where there is more control to include or omit objects that are necessary for the package and reports. This practice could help to accelerate requirements gathering. To enable this feature. Any package created using the SSPW cannot be changed with IBM Cognos Framework Manager after the package is published. Using the Self-Service Package Wizard The following section provides a step by step overview of using the Self-Service Package Wizard to create a package. and then over-write the existing package. 1. For those SAP BW queries that call several alternate hierarchies or dimensions that are not necessary for reporting. Consider use by IT and business users within test environments to enable users to build their own models and assist with requirements gathering. This step is done in IBM Cognos Administration -> Configuration -> Data Source Connections. existing reports should be analyzed to see if changes are necessary. SSPW users should strongly consider saving their packages to their ‘My Folders’ directory or other dedicated directories to avoid package clutter in the ‘Public Folders’ directory. a user will need to re-import the SAP BW InfoQuery and then over-write the existing package. This method can help expedite the import process. such as calculated and restricted key figures.developerWorks® ibm. filters. and regression testing processes for required SAP BW reports and analysis as business users could be more involved. 6. 9. query structures. 8. Another option is to recreate and overwrite the package using IBM Cognos Framework Manager. In the event a package has been created with SSPW where the SAP BW InfoQuery is changed after the package was created.
com/developerWorks/ developerWorks® Figure 11: Data source connection properties in IBM Cognos Administration Figure 12: 'Allow personal packages' is checked 2. IBM Cognos Proven Practices: IBM Cookbook for IBM Cognos 10 for use with SAP NetWeaver Business Warehouse™ Page 15 of 25 . Click on the Self Service Package Wizard blue folder icon.ibm.
developerWorks® Figure 13: The SSPW Wizard icon ibm. It is recommended that users save their packages to ‘My Folders’ to avoid user confusion and clutter in the ‘Public Folders’.com/developerWorks/ 3. Select the SAP BW data source containing the data required. A window opens showing all SAP BW data sources available. IBM Cognos Proven Practices: IBM Cookbook for IBM Cognos 10 for use with SAP NetWeaver Business Warehouse™ Page 16 of 25 . Figure 14: The SAP BW connection appears within the wizard 4. Specify the name and location of the new package. and click ‘OK’.
Find and select the appropriate SAP BW InfoQuery required.ibm. and variables. such as calculated and restricted key figures. query structures. filters.com/developerWorks/ developerWorks® Figure 15: The user has chosen to save the package to ‘My Folders’ 5. Click ‘Next’. and leave the default option to ‘Enable SAP BW Dual Structures support’. IBM Cognos Proven Practices: IBM Cookbook for IBM Cognos 10 for use with SAP NetWeaver Business Warehouse™ Page 17 of 25 . This provides users the ability to leverage SAP BW objects not otherwise available from the cube. It is recommended to choose a query rather than the cube.
developerWorks® ibm. and click ‘Next’.com/developerWorks/ Figure 16: The user has selected the SAP BW InfoQueries for the package 6. Confirm the design language. Choose to import any languages that are supported within your SAP BW environment. IBM Cognos Proven Practices: IBM Cookbook for IBM Cognos 10 for use with SAP NetWeaver Business Warehouse™ Page 18 of 25 .
And to have objects in the model organized the same way that they are organized in SAP Business Explorer Query Designer. Choose the option for ‘Use Dynamic Query Mode’ to leverage DQM and its query caching capabilities for improved response times and performance. select the ‘Enhance model for SAP BW organization of objects’ option.com/developerWorks/ developerWorks® Figure 17: English is imported from SAP BW 7. Note the display name chosen should be supported and available within your SAP BW data source. You may choose this option to accommodate those users who are familiar with the SAP Business Explorer tools. Optionally choose the ‘Object display name’ of your choice. Click ‘Finish’. Note this selection is purely optional for visual purposes only. You will then have a folder for each dimension. and is a matter of personal preference. IBM Cognos Proven Practices: IBM Cookbook for IBM Cognos 10 for use with SAP NetWeaver Business Warehouse™ Page 19 of 25 .ibm.
IBM Cognos Proven Practices: IBM Cookbook for IBM Cognos 10 for use with SAP NetWeaver Business Warehouse™ Page 20 of 25 . If the SAP BW InfoQuery contains variables. and then click ‘Close’. Do this by choosing the option to ‘Edit the SAP BW variables for the package after closing this dialog’ . you can choose to edit its properties by selecting to launch the SAP BW Edit Variables page.developerWorks® ibm.com/developerWorks/ Figure 18: The user has chosen to 'Use Dynamic Query Mode' for better performance 8.
ibm.com/developerWorks/ developerWorks® Figure 19: Edit SAP BW variables for the package 9. If required. you can change the behavior of the variables via the ‘Prompt Type’ property by using the dropdown menu. IBM Cognos Proven Practices: IBM Cookbook for IBM Cognos 10 for use with SAP NetWeaver Business Warehouse™ Page 21 of 25 .
developerWorks® ibm. a user can select a maximum of two SAP BW cubes and five SAP BW InfoQueries. which will help to control the number of objects that are imported at one time for a package. Figure 21: The new package appears in 'My Folders' as defined Update Default Settings to Control Import Limits IBM Cognos Administrators may want to reduce the number of SAP BW queries or cubes a user can select to import SAP BW metadata beyond the default settings. and promote an optimized import of the SAP BW metadata. These governors can be set within the ‘Dispatchers and Services’ tasks within IBM Cognos Administration. The following section outlines the steps necessary to reduce the limits. By default. IBM Cognos Proven Practices: IBM Cookbook for IBM Cognos 10 for use with SAP NetWeaver Business Warehouse™ Page 22 of 25 .com/developerWorks/ Figure 20: Change the SAP BW variable properties as necessary A new package is ready to be used within IBM Cognos 10 so users may access data from SAP BW.
Figure 22: IBM Cognos Administration for Dispatchers and Services 2. Figure 23: View Settings 5. Figure 24: Edit the advanced settings 6. Add the following parameters to specify the value for maximum number of SAP BW cubes or SAP BW InfoQueries.cognos. ‘Advanced Settings’.maxcubes (default value is 2) com. choose the ‘More’ link. A parameter input screen will appear.ibm. and then the ‘Settings’ tab.com/developerWorks/ developerWorks® 1.ibm. 7. 4. com.sap.maxInfoQueries (default value is 5) IBM Cognos Proven Practices: IBM Cookbook for IBM Cognos 10 for use with SAP NetWeaver Business Warehouse™ Page 23 of 25 . For the MetadataService. For the row labeled ‘Environment’.metadatauiservice. choose ‘Edit’. Select ‘Set Properties’. Click on the dispatcher URL.ibm. 3.cognos.metadatauiservice. Click the checkbox option to ‘Override the settings acquired from the parent entry’.sap. Go to IBM Cognos Administration -> Configuration -> Dispatchers and Services.
com/developerWorks/ Figure 25: Insert parameters to define the limit for SAP BW InfoQueries and cubes 8. Stop and restart the service ‘MetadataService’. 9. IBM Cognos Proven Practices: IBM Cookbook for IBM Cognos 10 for use with SAP NetWeaver Business Warehouse™ Page 24 of 25 .developerWorks® ibm. Click the ‘OK’ twice.
com/developerworks/ibm/trademarks/) IBM Cognos Proven Practices: IBM Cookbook for IBM Cognos 10 for use with SAP NetWeaver Business Warehouse™ Page 25 of 25 . he has also served as a SAP BW developer and managing consultant delivering SAP BW implementations to IBM customers.com/developerWorks/ developerWorks® About the authors Daniel Wagemann Daniel Wagemann is an IBM Cognos Proven Practice Advisor for Business Analytics in Canada.com/legal/copytrade. Pierre Valiquette Pierre Valiquette is a Software Engineer within the IBM Cognos SAP BW development team. One of his roles for the past two years is to drive customer successes and help Cognos customers by developing materials such as this cookbook as support for their IBM Cognos implementations with SAP applications. IBM Cognos Support organization.ibm. consulting and customer support. His areas of expertise include course development. In his combined 10 years at IBM.shtml) Trademarks (www.ibm. Pierre has been involved for 13 years in the Ottawa Lab in various capacities from Customer Support to Development. His work can be found within almost all areas of the Proven Practices Site. Rich Borucki Rich Borucki is a Cognos Solution Specialist with SAP subject matter expertise in which he has a detailed understanding of the technical integration of IBM Cognos with SAP applications. His primary role consists of bridging the gap between the SAP BW development team. His main focus throughout has always been a customer facing one. he has established a vast understanding of all areas of an IBM Cognos deployment. © Copyright IBM Corporation 2011 (www. and the customer base.ibm. technical writing. In his 11 years working with the IBM Cognos product Suite.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue listening from where you left off, or restart the preview.