IBM Mashup Center: V1.1

More documents

Recommendations

Info

The output tags from relational database feed queries have the followingmodifications from the source tables:v Uppercase characters in column names are changed to lowercase characters.v Colon characters (:) are changed to underscore characters (_).v Blank spaces are changed to underscore characters (_).SQL column names must begin with an alphabetic characterColumn names used for a relational database query feed must begin with aalphabetic character. Column names beginning with a number will result in ansql.columnname.invalid.error error.Informix user-defined data types are not supportedFeeds from an Informix Dynamic Server (IDS) relational database query cannotinclude columns that contain user-defined data types (UDTs). You must use built-indata types in IDS relational database queries.Editing a TDI feed requires re-entering the passwordYou must re-enter the password when you edit a feed created from a TivoliDirectory Integrator (TDI) service that requires a login and password to connect tothe underlying feed source.FunctionsComparing two values of different data types in the Filter operator returns falseWhen you use the Filter operator to compare two values, the Feed Mashup Builderattempts to convert both values to the same data type. If this attempt fails, theFeed Mashup Builder returns false for that comparison and the entry is droppedfrom the results. Sometimes this can cause confusion. For example, consider anExcel spreadsheet with numeric values in a column that you want to filter, butthere are some text labels in the column. Entries with the text labels are ignored. Ifyou enable DEBUG for MashupHub log output, the CDHEN2070W warning appearsin the MashupHub log file and shows the values that cannot be compared; forexample:CDHEN2070W: Input types are not comparable: ’500’, ’Sales Q4’When you filter mixed numeric types, for example integer and float, the FeedMashup Builder again tries to convert both arguments to the same numeric type.You might notice that error CDHEN3065E in the MashupHub log file:CDHEN3065E: Unrecognized integer value ’1.0’.You can ignore error CDHEN3065E when it occurs for the Filter operator becausefalse is returned if the values cannot be converted to the same numeric type andcompared. However, CDHEN3065E should be treated as an actual error for otheroperators, such as the Transform operator.Migrating the catalog databaseMicrosoft SQL Server does not directly support UTF-8 encodingDouble-byte characters in the feeds details will not be rendered properly.28 IBM Mashup Center: V1.1
Clearing tracked data fails after migrating to IDS, Microsoft SQL Server, or toOracleAfter migrating the catalog database to IDS, Microsoft SQL Server, or to Oracle, theClear Tracking Information action does not delete tracked data. Be aware thatenabling tracked data can use excessive disk space on these databases. Instead oftracking all cataloged objects, you can turn tracking on for selected feeds that arevery important and require tracking so as to reduce tracking entries and save diskspace.Values entered in the Schema field are ignored for migration to Informix,Oracle, or to Microsoft SQL ServerWhen migrating to Informix, Oracle, or to Microsoft SQL Server, the value enteredin the Schema field in the Migrate MashupHub Database screen is ignored andthe value from the Username field is used as the default schema instead. TheSchema field is applicable only for migrating to DB2.When you are migrating the catalog to another database, you cannot prevent auser from creating or running objects in the catalogTracking data can be lost if a tracked object is run during migration. Object datacan be lost if a user updates or creates a new feed while migration is in progress.The Administrator should migrate the database when the machine is not in use, orperform the migration locally with the network disabled to prevent users fromaccessing MashupHub while migration is in progress.UpgradingCREATE and DROP permissions required for schema updates for DB2 and IDScatalog databases for fixpack 1.1If you previously migrated the catalog to either DB2 or to Informix DynamicServer (IDS), in order to update the database schema for version 1.1 the databaseuser id that MashupHub uses to connect to the database must have CREATETABLE and DROP TABLE permissions for those databases. The schema updatesautomatically when you apply the fixpack.Tracking data requires edit to mmms.config.ini file to enable cache afterupgradingIf you have usage tracking enabled or plan to enable it, edit the mmms.config.inifile to enable the caching of the tracked data after you upgrade to MashupHub,V1.1. Caching tracked data improves MashupHub performance.1. Use the WebSphere Administration Console to stop MashupHub.2. Go to the /Hub/installedApps/mashuphub.ear/mashuphubenterprise.war/META-INF/config/directory.3. Open the mmms.config.ini file in a text editor.4. Enter the following text in the file:mmms.cache.region=mmmsRegion5. Save and close the mmms.config.ini file.6. Use the WebSphere Administration Console to restart MashupHub.Known issues and workarounds in MashupHub 29
Page 4 and 5: iv IBM Mashup Center: V1.1
Page 7 and 8: What’s new?This chapter describes
Page 9 and 10: More friendly widget event namesThe
Page 11 and 12: Syntaxhubie.bat|sh import|i objecti
Page 13 and 14: If you add a feed for an existing e
Page 15 and 16: The numeric datetime formats have t
Page 17 and 18: The statement will be interpreted a
Page 19 and 20: v Offload locationv Flush to diskv
Page 21 and 22: General known issues and workaround
Page 23 and 24: Known issues and workarounds in Lot
Page 25 and 26: https://hostname:port/mashuphub/cli
Page 27 and 28: Switching mashup pages in the page
Page 29 and 30: Known issues and workarounds in Mas
Page 31: With the Source operator, when you
Page 35 and 36: Performance characteristics of Mash
Page 37 and 38: Fixed problems in MashupHubThis cha
Page 39 and 40: NoticesThis information was develop
Page 41 and 42: If you are viewing this information
Page 44: Printed in USA

IBM Mashup Center: V1.1

Create successful ePaper yourself

Delete template?

Save as template?