IBM Clarity 7 Server v7.2.1 FP1 New Features

Transcription

1 IBM Clarity 7 Server v7.2.1 FP1 New Features Microsoft Internet Explorer 9 Support IBM Clarity 7 v7.2.1 Fix Pack 1 (FP1) now supports Microsoft Internet Explorer 9 (IE9). The web interface (Planning & Analysis, Consolidations, Visualizer) supports IE9 using the same settings required for IE7 and IE8. Please refer to the installation guide for the IE7 and IE8 settings. TM1 OLAP Support IBM Clarity 7 v7.2.1 FP1 now supports IBM Cognos TM1 as an OLAP Data Source. Customers should now be discussing the merits of moving their OLAP data store to IBM Cognos TM1. Please note that TM1 support only pertains to IBM Clarity 7 Server and IBM Clarity 7 Studio. Visualizer, MDM and Consolidations have not been extended to support TM1 as an OLAP source. For information on Clarity 7 Studio integration with TM1, please refer to the Studio section later in this document. Installation for TM1 Delta Check Beginning with Clarity Server Fix Pack 1, the installer requires that a previous version of Clarity Server be installed. If a previous version is detected, the installer will prompt you with the following message and you can click yes to continue or no to stop the installer.

2 If a previous version of Clarity Server was not detected you will be prompted with the following message and will not be able to continue. New OLAP Provider The installer now includes a new OLAP Provider to choose from for TM1.

3 TM1 Runtime Folder Similar to Essbase, when the TM1 provider is selected and the next button is clicked, an additional screen will be displayed where the path to the TM1 runtime client will need to be entered. Sample Templates and Reports There are no sample templates and reports for TM1; therefore the option to install those has been disabled.

4 OLAP Server information and Demo Cube When entering an OLAP server in the OLAP Server text box, it should be entered in the format of <admin host>:<tm1 server name>. Typically, the <admin host> is the name of the actual server that TM1 is installed on. The <tm1 server name> is the name of the TM1 instance that is running on the admin host. There is no Clarity demo OLAP cube for TM1; therefore the option to install a demo cube has been disabled. Configuration Settings Once installation is complete, the following TM1 specific configuration settings are updated. Web\config.xml autologincredentials source: loginpage The default configuration of loginpage assumes that Native TM1 security has been configured. If TM1 has been configured to use Windows authentication then the source attribute should be changed to windows and the IIS website should be configured for Windows Authentication provider: TM1 server: olapservername:claritydemo Web\config\AppSettings.config Tm1RuntimePath: <Path to the TM1 runtime client> i.e. C:\Program Files\Cognos\TM1

5 Security Configuration TM1 Native Security vs. Windows Authentication By default, TM1 supports native security. This means that user credentials are managed by TM1. TM1 also supports Windows authentication. This means that a user can use their Windows credentials to log into a TM1 server. In order for TM1 to be configured for Windows Authentication, a list of Windows users needs to be imported into TM1. This is typically done using the etldap tool that is installed when installing TM1 NOTE: Clarity Server supports both Native and Windows Authentication. However, for Windows Authentication, only one user is supported. This is the user that is used for the Application Pool identity in IIS. The ability to impersonate the currently logged on user in IE is currently not supported. Support for Multiple OLAP Providers Clarity Server supports multiple OLAP Providers at the same time. This means that you can have templates that point to different OLAP providers within one installation. You can also point to different OLAP providers within the same template. There is no additional configuration for this to work, however you have to ensure that your credentials match between the various OLAP Providers. For example, if using native authentication in Essbase and TM1, the usernames and passwords must be the same. OLAP Manager The OLAP Manager screen supports the ability to add TM1 cubes. When adding a new server, select TM1 as the provider. The following entries have different meaning with respect to TM1: Server: The Admin Host name as described above Application: The TM1 Server name Database: The TM1 Cube on the TM1 Server Retrieve and Save Strings in a OLAP Template TM1 supports the saving and retrieving of strings to the OLAP Cube. A new property has been added to the template schema to configure the ability to save strings back to the cube. Please see the Studio section which describes how to configure the template or report in Studio. Support for TM1 String Attributes A new setting Filter Value Type is available when creating a rule for properties as part of a TM1 OLAP Data Map query or a TM1 OLAP Member List query. This setting has two options String or Numeric and was introduced because of TM1 s ability to create attributes that are either string based or numeric based. Please see the Studio section below for a screen shot of the setting. Turbo Integrator (TI) TM1 provides TI scripts to perform operations on the TM1 Server. TI scripts can now be executed from a Clarity template by adding a new Server Job in the Advanced Pane. Please see the Studio section for more.

6 Application Server Configuration Clarity now supports the configuration of a proxy user for saving data to TM1. When a proxy user is configured, all template saves are done using the proxy credentials in place of the current user's credentials. This allows reduced access on individual user accounts, since users are not saving directly to the database. Clarity also supports the configuration of a proxy user for running calculations. When configured, this user account is used when running Turbo Integrator processes as server jobs from a template. Proxy users must be authenticated using basic authentication. Note that IIS Reset is necessary after setting either user through the Application Server Configuration page Administration Screens These administration screens operate as they have in the past when interacting with TM1. It is of note that these screens have always only supported a single node root for the tree view dialog. TM1 supports dimensions with multiple roots. When multiple roots are defined in TM1, the first root will only be displayed on administrative tree dialogs. The alternate solution is to create a single root for the dimension in TM1.

7 Import from Excel with Line Item Details Enabled Clarity 6 templates with Line Item Details enabled supported the ability to Import from Excel. With the redesign of Line Item Detail functionality in Clarity 7, Import from Excel was not available for templates with writable Line Item Detail ranges. As of FP1, templates with writable Line Item Detail ranges support Import from Excel functionality with restrictions. On a template with LID enabled, on Import from Excel, only row ranges without LID enabled will be imported. Row ranges with LID enabled will be ignored. Example: User has an OLAP template with a single OLAP data map. The OLAP Data map consists of three column groups and 3 row groups. The template has Import from Excel and mandatory Line Item Detail enabled. The following chart displays the configuration of Line Item Detail. Column 1 Column 2 Column 3 Row 1 LID Row 2 Row 3 LID On using Import from Excel, only data from Row 2 is imported. Row 1 and Row 3 are ignored. Bottom Level Descendants Business Rules and Report Books When selecting cascading book options for your Report Book or Business Rule, the Bottom Level Descendants option (previously only available through code) is now available in the Member Selection Dialog.

8 No Separators A new setting has been added to the template schema to assist with templates that suffer from poor performance related to separators used in the query between each row range. The default value for the NoSeparators setting is false and when set to false the typical behaviour of Clarity 7 is executed. When the setting is set to false or not present, Clarity 7 Server will execute one query for all the row groups and column groups that are part of the Olap Data Query. The single query is possible due to separators that Clarity 7 Server inserts to identify where each row and column group are delineated. In some scenarios, the row group separators can create performance issues for the query. The No Separators attribute, when set to true, eliminates the single query architecture and executes a query for each row group present in the OLAP Data Query. This architecture is similar to the Clarity 6 data query architecture and can be helpful when upgrading when performance in Clarity 7 for the same template is not as good as Clarity 6.

9 IBM Clarity 7 Consolidations FP1 New Features Microsoft Internet Explorer 9 Support IBM Clarity 7 Consolidations v7.2.1 Fix Pack 1 (FP1) now supports Microsoft Internet Explorer 9 (IE9). The web interface (Planning & Analysis, Consolidations, Visualizer) supports IE9 using the same settings required for IE7 and IE8. Please refer to the installation guide for the IE7 and IE8 settings. Recurring Journals - Editing the End Period Users are now able to change the end date of a recurring journal series to an earlier or later date after it is created. When the end date is extended for the recurring journal series, new journals will be created for each additional period with a status of In-Progress. The end date for a recurring journal series can only be shortened to a date when the new end date will not cross over the date of a journal in the series that does not have a status of In-Progress. When the recurring journal series end date is successfully shortened, the journals are deleted never to be used again. The Journals screen has now been updated to allow users to click the recurring journal symbol to view the list of journals that are part of the recurring series. In this dialog, users have the ability to edit the end time of the recurring journal series.

10 Recurring Journals Selecting Elimination Entries in the Interco Dimension Users are now able to select only Entity type members in the Intercompany dimension if the user selected an Entity type member in the Entity dimension while creating or updating a journal entry. Users are now able to select only Elimination type members from the Intercompany dimension if the user selected an Elimination type member in the Entity dimension while creating or updating a journal entry. Blueprint Journals Debit and Credit values now optional Users are now able to create or modify blueprint entries without debit or credit values. Since journals are validated before they are saved, a blueprint doesn't need to be checked whether it is balanced or not since the blueprint records will be inserted to a journal where the validation will take place. Custom Partition Query Support Cube Builder Utility The cube builder utility now supports the custom partition query support added in Consolidations Custom Dimension Support on Reconciliation Report The Intercompany Reconciliation Report has been updated to support custom dimensions. The report has an additional parameter which accepts a comma delimited list of dimensions to be included in the report. Customers on upgraded will not be impacted as their reports will continue to use the following stored procedures as part of their reports: Proc_CS_SYS_RunReport_IntercompanyReconciliation Proc_CS_Report_IntercompanyReconciliation New reports that require the use of custom dimensions should use the following stored procedures: Proc_CS_SYS_RunReport_IntercompanyReconciliation_Custom Proc_CS_Report_IntercompanyReconciliation_Custom Collation Requirements removed SQL Server Collation requirements from previous versions of Consolidations have been removed.

11 IBM Clarity 7 Studio FP1 New Features Collection Manager for Row and Column Ranges In the Row Ranges and Column Ranges design screen a collection manager has been added as per the screenshot below: With the collection manager it is possible to work with all the row or column ranges in a single screen, including enabling Insert Additional and Delete Unused properties. It is also possible to sort the ranges according to the Excel address. Toolbox Items Automatically enabled when Feature is added When adding a feature to a document the corresponding tool is now enabled for the following feature\toolbox items: Zoom-In and Zoom-Out Add Row - Add OLAP Row Linked Documents Cell Notes Template Notes

12 Renaming Row and Column Groups When working with OLAP Data Maps in the past, the Row and Column Group names were non-editable and were automatically set to Group1, Group2, etc. The automatic naming convention provided no description of business use and weren t user friendly. It is now possible to edit the Row and Column Group names to give it meaningful business names as per the screenshot below:

13 Linked Document from Current Row or Variable IBM Clarity 7 Server v7.2.1 introduced the option to support the passing of variables or any value from the current row to the target document. This allows for better linking of documents when the source document is relational in nature. Studio v7.2.1 FP1 now supports the ability to configure the link using either a current row or a variable. When mapping target page options to the source, the drop list will now include variables and an option for Current Row. When selecting Current Row, the user will be prompted to select a column range that will be used to intersect with the currently selected row (in the web user interface) to get the source value.

14 Support for IN Operator The Studio user interface now supports the IN operator when creating a rule for properties as part of an OLAP Data Map query or an OLAP Member List query. The operator drop down list now includes the IN option. The IN operator can be used for partial string matching.

15 Support to Enable Validation on both On Save and On Pop-Up OK In previous versions, when configuring Fields as part of the Advanced Editing feature, the design screen only allowed validations to be run either On Save or On Pop-Up OK but not both (even though it was supported). The design screen has now been updated to allow the configuration of both by replacing a drop down list with two checkboxes.

16 Improvement to OLAP Data Map Properties Design Screen When working with the Properties design screen for an OLAP Data Map, the Only send changed rows settings is now only selectable when the Allow Update setting has been enabled. Sorting Ability to Clear a Rule In the design screen for the Sorting feature, users are now able to clear Sort By and Then By rules.

17 List of Available Custom Script Files Now Displayed In the Scripts design screen, the user can now select from a list of files in the custom scripts directory. Previously the user would need to know the type and name of the script file to successfully configure this feature. Custom Toolbox Items Design Screen Now shows Category ID in Hover When adding a custom toolbox item, the drop down list will now have a hover indicating the category ID of the category.

18 Relational Map Updates to Design Screen The Preserve Formulas setting is now configurable in the Relational Map design screen. This feature will enable the preservation of any grid formulas existing in the map area, instead of overwriting them with the resultant database data. This feature has always been available via the code window in Studio. The No Key Field setting is no longer available and had been replaced with the ability to de-select a column range Key radio button. Relational Query Update to Design Screen The relational query timeout setting is now available and configurable in the Relational Query Design Screen. The timeout attribute for a relational query is an optional attribute that determines the number of seconds the query is allowed to run before being timed out. The default setting is unchecked for new relational queries. Once enabled the value displayed in the number stepper is 0 seconds, which the user can increase.

19 Suppression Rule Update to Design Screen The Unhide rows/columns using Add Row check box is disabled when the Action setting for a suppression rule is set to Delete. Suppression rules with a delete action do not support the Add Row feature.

20 TM1 Support Saving Strings to the TM1 Cube TM1 supports the saving and retrieving of strings to the OLAP Cube. A new property has been added to the template schema to configure the ability to save strings back to the cube. The Properties design screen has been updated and includes an Allow Send Text Data button to configure the new feature. Support for TM1 String Attributes A new setting Filter Value Type is available when creating a rule for properties as part of a TM1 OLAP Data Map query or a TM1 OLAP Member List query. This setting has two options String or Numeric and was introduced because of TM1 s ability to create attributes that are either string based or numeric based.

21 Turbo Integrator (TI) Jobs TM1 provides TI scripts to perform operations on the TM1 Server. TI scripts can now be executed from a Clarity template by adding a new Server Job in the Advanced Pane. After selecting the source, a list of available TI scripts on the Server will be available for selection. After picking a TI script, a list of parameters (if any) for the TI Script will be shown; the user can specify a value for each parameter using a variable, page option or a fixed value.

22 IBM Clarity 7 MDM FP1 New Features ETL supports use of Natural Keys MDM ETL commands used to require the natural key, even if UseNaturalKey was set to False. This has been changed so that the MDM ETL commands now support the use of member names where you would use the natural key if UseNaturalKey is set to False. ETL command to generate MDM schema A new ETL commands has been introduced to generate the MDM schema. Usage for this command is below: "Clarity MDM ETL.exe" -m CreateSchema -f true -l Budgeting_Clarity -c "Server=localhost; Database=Budgeting_Clarity; Integrated Security=true" Parameter f, indicates whether the schema is to be overwritten. The default value, if this parameter is not specified is false. If f=true and the database specified in the connection string already exists and the MDM schema tables are an older version, the schema tables will be updated and data in these tables will be preserved. If f=false and the database specified in the connection string already exists the MDM schema tables will not be created. This functionality is useful in the scenario where you programmatically need to generate an MDM instance or OLAP database. ETL command to set a default member To set a default member using ETL, add a record with the following values to the MDM_ETL_COMMANDS table: Command = U (Update) ModelType = M (Member) Name: <MemberName> ParentDimensionName: <DimensionName> MemberKey: <Member's Natural Key> (mandatory If UseNaturalKey is true, otherwise ignore it) PropertyName: IsDefaultMember PropertyValue: True After this, the Delta Operation needs to be executed, either through the command line or by adding an action through the MDM user interface.

23 ETL to Add Parent-Child dimension With the release the ability to add parent-child dimensions was added. At the time, it was only possible to do so through the MDM user interface. It is now possible to add parent-child dimensions using an ETL command. This proves helpful for the scenario where you have to programmatically add dimensions. ETL command to set data source name It is now possible to rename the OLAP database. Enter a record in the MDM_ETL_COMMANDS table with the following values: Command U ModelType O Name old OLAP Database Name (case sensitive) NewName new OLAP Database Name After this, the Delta Operation needs to be executed, either through the command line or by adding an action through the MDM user interface. ETL Command to Create Actions and Action Timing It is now possible to create actions and configure action timings through ETL commands. Users will be able to setup the following actions through ETL Custom Action Dimension Load Action Execute ETL Action Users will be able to define the following Action timings After Save Before Data Source Deploy After Data Source Deploy Before OLAP Deploy After OLAP Deploy Users will be able to configure actions and their timing using the ETL Command Execute. Enter records defining the action and action timing in MDM_ETL_COMMAND Run Command Execute Operation from the command line: "Clarity MDM ETL.exe" -m DeltaOperation -c "Server=localhost;Database=mdm_ue;Integrated Security=true"

24 Please note that after an action is added and the timing configured, the action will not be executed. At this point if a user opens up MDM they will see a new node for the action and a new node for the action timing. It is only after a Save/Update/Deploy is the action executed. Configurable Decimal Precision It is now possible to configure the decimal precision for each measure. Once set, the data type for the measure column in the fact able will be Decimal (18, x) where x is the decimal precision value set in MDM, and the format string for the measure in SSAS will be #,#.xxxx where xxxx is the number of decimal places as set in MDM for the measure. MDM Update Operation: MDM Update operations will only update the data type and format string if no data exists in the fact table. After a user alters the decimal places for a measure and selects the MDM UPDATE operation, a check for data in the fact table for that measure is performed. If there is data, the user is messaged that the operation cannot be completed because the fact table contains data. This rule is in place because if the product alters the fact data by altering the decimal places in the amount column, the data gets altered to have additional zeroes (e.g would get changed to ) - which is false precision. MDM Deploy Operation: If a user alters the decimal places for a measure and selects DEPLOY MDM will proceed with dropping and recreating fact table and OLAP database and changing the decimal places on fact table and OLAP database. Upgrade: When users upgrade from an older version of MDM to MDM v we do not alter the number of decimal places. IBM Clarity 7 Visualizer FP1 New Features Microsoft Internet Explorer 9 Support IBM Clarity 7 Visualizer v7.2.1 Fix Pack 1 (FP1) now supports Microsoft Internet Explorer 9 (IE9). The web interface (Planning & Analysis, Consolidations, Visualizer) supports IE9 using the same settings required for IE7 and IE8. Please refer to the installation guide for the IE7 and IE8 settings.