Importing and exporting catalog objects: imc3Added by IBM on November 23, 2010 | Version 1 (Original)
|Use the Import-Export command line utility to copy feeds, data mashups, iWidget package files, spaces, or pages definitions to or from an operating system file. You can also use the utility to move objects into the catalog of another Mashup Center instance (for example, from a development environment to a production environment), or to offline storage.
Use the Import-Export command line utility to copy feeds, data mashups, iWidget package files, spaces, or pages definitions to or from an operating system file. You can also use the utility to move objects into the catalog of another Mashup Center instance (for example, from a development environment to a production environment), or to offline storage.
Use the utility when the source and the target servers are across firewalls or when the Add to Remote Catalog
option does not work.
- You must have administrative access to the Mashup Center server.
- If your catalog is located on an embedded Derby database in WebSphere®, stop the server before running the utility.
- You can import or export objects between these versions of the source and target Mashup Center catalogs: From catalogs of the same version or from version 18.104.22.168 to version 3.x.
- All imported objects must have Public permissions.
- The plug-in for the source feed type must already be installed on the target MashupHub instance.
The utility is installed in these directories:
AIX® and Linux®
Exporting pages with widgets: imc3
Exported pages that include widgets require manual configuration to add to the target mashup builder.
Exporting a DB2 pureXML feed: imc3
After exporting a DB2® pureXML® feed, the pureXML® metadata URLs still point to the source server.
Parent topic: Catalog management: imc3
Importing a catalog object
- To import a catalog object
- From the directory in which the utility is installed, run the appropriate import syntax, such as this AIX example, where xxxx is the encryption key:
AIX and Linux
hubie.sh import 9.xml HubAdmin Pwd4HubAdmin xxxx
hubie.sh import|i object.xml ownername Password [encryptkey]
Table 1. Import syntax elements
hubie.bat import|i object.xml ownername Password [encryptkey]
|import or i||Requires the objectid.xml file name created during the initial export.|
|object.xml||The file name containing the exported object definition.|
|ownername||Specifies the administrator of the target Mashup Center instance.|
|password||The administrator password for the Mashup Center installation. |
For systems that have migrated away from Derby as the DBMS supporting the catalog, the DBMS password specified when the migration was performed can be used as an alternative to the administrator password for imports.
|encryptkey ||If the encryptkey parameter was specified in the export syntax, it must also be included in the import syntax. If the encryptkey parameter is not required, but a value is supplied, that value is ignored. |
Exporting a catalog object
- To export a catalog object
- From the directory in which the utility is installed, run the appropriate export syntax, such as this Windows example, where xxxx is the optional encryption key:
AIX and Linux Windows
hubie.sh export|e objectid [encryptkey]
Table 2. Export syntax elements
hubie.bat export|e objectid [encryptkey]
|export or e||Requires a valid objectid parameter from the source catalog.|
|objectid||The object id of the object URL listed in the catalog on the object details page. |
In the following url, the objectid is 31: http://server.company.com:9080/mashuphub/client/plugin/generate/entryid/31/pluginid/5
|encryptkey||Encrypts the password on export and is required for any objects that potentially require password information to be present as part of the export. The encryptkey parameter must be provided for feed configurations, which often contain passwords. Pages, spaces, and widgets do not require the encryptkey parameter.|
If the encryptkey parameter is not required, but a value is supplied, that value is ignored. When the object that requires authentication is imported, you must use the key specified on export to decrypt the password.
file with the object definition is created in the directory where the Import-Export utility is located. This file contains the object definition, and can be renamed.
After you export a feed that is based on a JNDI data source, you must manually configure the corresponding JNDI data source on the target server.
When you export a web service which uses the Requires WS-Security Token Service (STS)
option, the Administrator of the remote catalog must first add the STS Binding and Mapping properties to the remote server. The STS related information is not exported by the Import-Export utility, and must be re-created on the remote server for the web service feed to continue to work.