IBM Mashup Center: V1.1

More documents

Recommendations

Info

Richer widget deployment capabilitiesAdministrators now have more options when deploying widgets to Lotus Mashupsfrom the catalog. If a widget is already deployed, administrators can choose toreplace the existing widget or to deploy the new widget. In addition, users canspecify their credentials and target mashup server during the widget deploymentprocess.Move catalog objects between instances of MashupHub with the import-exportutilityUse the import-export command-line hubie utility to move individual catalogobjects between instances of MashupHub. You can move feeds, feed mashups,iWidget package files, or pages. You can also use the utility to move objects from adevelopment environment to a production environment or to store objects offline.The utility has an export option that creates an XML file that is used by the importoption to move the object into the catalog of another MashupHub instance.On Windows the import-export utility is hubie.bat. Run the utility from the\Hub\installedApps\Mashup Hub.ear\mashuphub-enterprise.wardirectory.On Linux the import-export utility is hubie.sh. Run the utility from the/Hub/installedApps/Mashup Hub.ear/mashuphub-enterprise.wardirectory.Restrictions:v If your catalog is on the embedded Derby database in WebSphere, whereMashupHub is initially installed, you must stop the server before you export orimport objects. Because the embedded Derby database can handle only one JVMprocess at a time, the MashupHub server must be down before you run thehubie utility.v To import or to export an object, you must have administrator access to theMashupHub server.v The import-export utility requires MashupHub, version 1.1 for both the importand the export options.v Imported objects have Public permissions.Exporting an object from a catalog:Syntaxhubie.bat|sh export|e objectid [encryptkey]The export or e option requires a valid objectid parameter from the source catalog.The export option creates an objectid.xml file (for example, 9.xml) in the samedirectory as the hubie utility. Include an encryptkey parameter if the object requiresauthentication. The encryptkey parameter encrypts the password on export. Whenthe object is imported, you must use the same key to decrypt the password.Examples of the export option:hubie.bat e 2364hubie.bat export 2364 encryptkeyImporting an object into a catalog:6 IBM Mashup Center: V1.1
Syntaxhubie.bat|sh import|i objectid.xml ownername [encryptkey]The import or i option requires the objectid.xml filename that you created with theexport option. You must also include an ownername parameter, which specifies theadministrator of the target MashupHub instance. Include the encryptkey parameterif it was specified when the file was exported.Examples of the import option:hubie.sh i 2364.xml hubadminhubie.sh import 2364.xml hubadmin encryptkeyOnline help for the import-export utility is available using the following syntax:hubie.bat|sh -help|-hThe text for the help is only available in the English.Oracle and Microsoft SQL Server databases can be used for the catalog databaseIn addition IBM DB2 and IBM Informix Dynamic Server (IDS), you can migrate thedefault embedded Apache Derby catalog database to Oracle or to Microsoft SQLServer. Following are the new databases and versions that are supported:v Oracle 10 or laterv Microsoft SQL Server 2005 or laterMigrating the catalog from the default embedded Apache Derby catalog databasehas the following limitations and prerequisites:v As with DB2 and Informix, the database that you migrate to must already exist,and schema must be empty.v You must have Write permission on the database that you want to migrate to.v Migration has a timeout of 20 minutes. If the migration fails, check theJavaMashupHub.log file.v Migration is supported only one time from the default embedded Apache Derbycatalog database to DB2, IDS, Microsoft SQL Server, or to Oracle. You should notmigrate between the non-default databases, for example between DB2 andOracle.v As with DB2 and Informix, the database that you migrate to must be createdwith the UTF-8 code set, otherwise double-byte character sets are not supported.– Microsoft SQL Server does not directly support UTF-8 encoding. If theMicrosoft SQL Server database that you want to migrate to uses double-bytecharacters, you should not migrate to Microsoft SQL Server. See Migratingthe catalog database in the Known issues and workarounds in MashupHubsection of this document.– For Oracle, the steps for creating a database with a Unicode character set canbe found in the Oracle Database Globalization Support Guide:http://download-west.oracle.com/docs/cd/B19306_01/server.102/b14225/ch6unicode.htm#sthref686.v On Microsoft SQL Server the database must be set to case-insensitive collation.You can check the collation setting from the SQL Server management studio byright-clicking the database and choosing Properties. Alternatively, you can runthe following query:SELECT CONVERT(sysname,DatabasePropertyEx(’database_name’, ’Collation’))What’s new? 7
Page 4 and 5: iv IBM Mashup Center: V1.1
Page 7 and 8: What’s new?This chapter describes
Page 9: More friendly widget event namesThe
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 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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?