Search results

1 - 10 of 179 items found* NextModified date

5 column nested results data table

Number	Key	Space	Headline	Date
1.			Fixed problems in Mashup Center V2.0 The following problems have been fixed in Mashup Center 2.0. [ More items like this found in Mashup Development ]	2009-11-20
2.			OpenSearch parameters are case-sensitive The MashupHub search API is an OpenSearch-conformant REST interface. OpenSearch parameter names are case-sensitive. For example, "startIndex", "itemsPerPage", and "totalResults". [ More items like this found in Mashup Development ]	2009-11-20
3.			Group operator might return different results after upgrade If you have a data mashup that includes a Group operator that specifies a "Group expression" and an "Associated data expression" that both point to the same input node, then the results for the data mashup might change after you upgrade to version 2.0. [ More items like this found in Mashup Development ]	2009-11-20
4.			Object statistics return incorrect results after upgrade When you upgrade from version 1.1.0.1 to version 2.0, the catalog and object statistics data from user-created feeds is migrated along with the feeds. However, catalog and object statistics data from the 1.x preinstalled examples is also migrated even though the examples are deleted and replaced with version 2.0 examples. [ More items like this found in Mashup Development ]	2009-11-20
5.			Editing a Tivoli Directory Integrator (TDI) feed shows the parameters in the locale of the browser that was used to create the feed If you edit a feed using a browser with a different locale than the locale used to create the feed, the feed will show the parameters in the original locale used to create the feed. For example, if a feed is created using an English browser and later opened for edit in a Korean browser, the parameters will be displayed in English. [ More items like this found in Mashup Development ]	2009-11-20
6.			DB2 XML Column (pureXML) feeds use the "atm:" prefix in the output When you create a feed from DB2 XML Columns (pureXML), all elements in the output have the atm: prefix. The feed is in Atom format. [ More items like this found in Mashup Development ]	2009-11-20
7.			Space character not allowed as a delimiter in CSV feeds Space characters are not allowed as a delimiter in CSV feeds. [ More items like this found in Mashup Development ]	2009-11-20
8.			Mashup Center supports Optim Version 6.5.0 with Attunity Server 4.8.2 The MashupHub User and Administrator Guide and the online help incorrectly lists Optim Archive, Version 3.0 as the supported database version for creating feeds for Mashup Center V2.0. The correct Optim version is Version 6.5.0 with Attunity Server 4.8.2. [ More items like this found in Mashup Development ]	2009-11-20
9.			JNDI connections are not supported for IBM Optim archive feeds The MashupHub online help and the MashupHub User and Administrator Guide give instructions for creating a feed for an Optim archive with a JNDI (Managed Connection). The option to create a feed using a JNDI connection is not available for Optim archives. Only the Driver Manager (Non-managed Connection) is available. [ More items like this found in Mashup Development ]	2009-11-20
10.			SQL queries with INSERT, UPDATE, or DELETE statements use "GET" as the default HTTP POST method The "Building an SQL query" topic in the online help and in the MashupHub User and Administrator Guide states that enterprise feeds that use INSERT, UPDATE, or DELETE statements will, by default, allow access to data only with the HTTP POST method. [ More items like this found in Mashup Development ]	2009-11-20

1 - 10 of 179 items found* NextModified date

IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.