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 this utility to move objects into the catalog of another Mashup Center instance (for example, from a development environment to a production environment), or to auxiliary storage.
Use this 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 for either export or for import.
- If your catalog is located on an embedded Derby database in WebSphere®, stop the server before running the utility.
- The plug-in for the source feed type must already be installed in the target MashupHub instance.
- To export a web service that 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 catalog. The STS information must be re-created in the remote catalog for the web service feed to continue to work.
- The Import-Export utility is supported between catalogs of the same version of Mashup Center or between catalogs of Mashup Center v126.96.36.199 or higher.
- An enterprise database feed that accesses the local Derby database cannot be added to a remote catalog.
- After you export a feed that is based on a JNDI data source, you must manually configure the corresponding JNDI data source in the remote catalog.
The utility is installed in these directories:
AIX® and Linux™
Exporting pages with widgets
Exported pages that include widgets require manual configuration to add to the target mashup builder.
Exporting a DB2 pureXML feed
After exporting a DB2® pureXML® feed, the pureXML® metadata URLs still point to the source server.
Exported object attributes
When you export or re-export an object to a remote catalog, certain object attributes are also exported to the remote catalog.
Parent topic: Catalog management
Exporting a catalog object
About this task
When you export an object, certain object attributes are also exported. For information, see Exported object attributes
To export a catalog object:
From the directory in which the utility is installed, run the appropriate export command, such as this example for Windows, where xxxx
is the optional encryption key:
AIX and Linux
hubie.sh export|e objectid [encryptkey]
hubie.bat export|e objectid [encryptkey]
Table 1. Export syntax elements
export or e
Requires a valid objectid parameter from the source catalog.
Choose an identifier to distinguish the object. You can use the object ID in the object's permalink or the universally unique identifier (UUID) for the object.
The object ID is unique within a specific server and changes when the object is imported into another server. The object ID is in the permalink URL listed in the object Details page. For example, in the following permalink URL, the object ID is 31:
The UUID is unique across all Mashup Center instances and remains associated with the object when it is imported into other servers. The UUID is in the object URL. In the following URL, the UUID is e7552f4c-4222-4c5e-83e8-e27ba5784dcd:
Encrypts the password on export. This parameter 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 is created in the directory where the Import-Export utility is located. This file contains the object definition. The file name is based on the object ID (not the UUID). You can rename the file. Make note of the file name. You will use this file if you import the object into another catalog.
Importing a catalog object
About this task
To import an object, run the Import-Export utility on the target server.
To import a catalog object:
From the directory in which the utility is installed, run the appropriate import command, such as this example for AIX, where xxxx
is the encryption key:
AIX and Linux
hubie.sh import 9.xml HubAdmin Pwd4HubAdmin xxxx -conflictResult ignore
hubie.sh import|i object.xml ownername Password [encryptkey]
hubie.bat import|i object.xml ownername Password [encryptkey]
Table 2. Import syntax elements
import or i
Requires the objectid.xml file name created during the export.
The file name that contains the exported object definition.
The administrator of the target Mashup Center instance.
The administrator password for the Mashup Center installation.
For systems that have migrated 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.
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.
This option only applies when you import the same object to the same catalog a second or subsequent time. This option specifies how to handle conflicts. If an object that was previously imported is later modified on the target server and saved with a new revision, then subsequent attempts to re-import that object will result in a conflict. Users specify revisions manually when editing the details of the object.
If you do not specify the -conflictResult argument, the default is -conflictResult error.
Cancel importing the object and any of its provider feeds.
Import and create a revision of the object in the target catalog.
Regardless of which option that you select, when a conflict occurs, a warning is written to the javamashuphub.log file if the default log level WARN is enabled. The log file is located in the target server at installDir/Hub/installedApps/Mashup Hub.ear/mashuphub-enterprise.war/META-INF/logs.
All objects defined in the objectid
.xml input file are imported into the target catalog. If an object already exists due to a previous import, and if the existing target object is different from the object defined in the objectid
.xml file, then a new revision of that object is created. The revision number for the object in the source catalog might differ from the revision number for the object in the target catalog. For more information on revisions, see the Object History
section in Editing objects and adding objects to other applications: imc3001