IBM Mashup Center: V1.1

More documents

Recommendations

Info

Input parameterNumeric value.Returned valueSingle numeric value.ExampleThe input value 3.7 returns the value 4.Floor function addedThe Numeric Floor function returns the largest (closest to positive infinity) integerthat is smaller than or equal to its single argument.Input parameterNumeric value.Returned valueSingle numeric value.ExampleThe input value 3.7 returns the value 3.Replace function addedThe Replace function compares the set of characters within the Input string to thepattern in the Pattern string, and then replaces the characters that match thepattern with the set of characters in the Replacement string.Input parametersInput, Pattern, and Replacement.Returned valueString value.ExampleIf you use input parameters: Input game, Pattern ame, Replacement lad, thereturn value is glad.Translate function addedThe Translate function returns the Input string’s characters with any of thecharacters in the Map string replaced by the characters at the correspondingposition in the Translate string.Input parametersInput, Map String, Translate String.Returned valueString value.ExampleIf you use input parameters: Input game, Map String sgom, Translate StringuJtn, the return value is Jane.Parameter behavior within an SQL IN clause changedIn a relational database feed query, the behavior of an SQL query within an INclause has changed. For example, given the following statement:SELECT * FROM status a WHERE a.id IN (’:airports’);12 IBM Mashup Center: V1.1
The statement will be interpreted as follows:SELECT * FROM status a WHERE a.id IN (?);The parameter is not interpreted as a list.Workarounds:v Use an inner query within the IN clause. For example:SELECT * FROM status a WHERE a.id IN(SELECT code FROM table WHERE column = value);v Use the exact number of parameters within the IN clause. For example:SELECT * FROM status a WHERE a.id IN(’:airports1’, ’:airports2’, ’:airports3’);Restrictions added to parameter names in relational database feed queriesEffective with MashupHub, Version 1.1, for both integer and string parameternames, the leading character following the colon (:) must begin with an alphabeticcharacter. Subsequent characters can be a combination of alphanumeric charactersor underscore characters (_). For example, :dept_2 for an integer parameter nameand ’:price_2’ for a string parameter name.Integer parameters are not allowed inside string parametersEffective with MashupHub, Version 1.1, integer parameters are not allowed withinstrings in relational database feed queries. Strings that start with a colon and areenclosed within single quotation marks are string parameters, for example,’:text’. Strings that start with a colon and are not enclosed within quotationmarks are integer parameters, for example, :number. However, the string :number isno longer treated as parameter marker in the following code ’text :number text’.Username is displayed on Logout buttonThe name of the currently logged-in user is displayed when you hover the mouseover the Logout button in the upper-right of the InfoSphere MashupHub screen.Use this enhancement to identify which username you are using if you use morethan one login for a MashupHub instance.″Deploy to Lotus Mashups″ action addedThe Deploy to Lotus Mashups action is available to users who have aMashupHub Administrator role. The Deploy to Lotus Mashups action is displayedin the Details page for an iWidget Package (.war) file, if the deployIWidgetPackagesetting is set to admin-only in server.config.ini file. (See next item.) The Deploy toLotus Mashups action only deploys an iWidget to Lotus Mashups. The iWidget isnot displayed in the Lotus Mashups palette. To add an iWidget to the LotusMashups palette, use the Add to Lotus Mashups action.New configuration settings control adding and deploying iWidget packages toLotus MashupsMashupHub V1.1 introduces new security settings for adding and deployingiWidget WAR packages to Lotus Mashups. The settings do not affect iWidgets thathave been registered in the catalog by specifying a URL, nor do the settings affectgeneric (non-WAR) widgets.What’s new? 13
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: The numeric datetime formats have t
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 and 32: With the Source operator, when you
Page 33 and 34: Clearing tracked data fails after m
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?