MashZone NextGen Administration : MashZone NextGen Server Administration : Deploying MashZone NextGen Instances, Clusters or Artifacts : Exporting Mashable and Mashup MetaData
Exporting Mashable and Mashup MetaData
Exporting mashables or mashups exports their metadata from one MashZone NextGen Repository to a file. You can then import this file to another MashZone NextGen Repository.
Typically, you export and import mashables and mashups to move new artifacts to production or to replicate data for a new instance of the MashZone NextGen Server.
Important:  
This command has specific limitations for what it exports. See Table 10 for details.
1. If it is not running, start the MashZone NextGen Server for the MashZone NextGen Repository that is the source for the mashables or mashups that you wish to export. See Start and Stop the MashZone NextGen Server for instructions.
2. Open a command window and move to the MashZoneNG-install/prestocli/bin folder.
3. Enter this command:
padmin exportServices -q filter -f output-file
[-l prestoURL] -u username -w password
[-v]
*-q filter: defines which mashables or mashups to export. It can be one of:
*"all" = export all mashables and mashups from this MashZone NextGen Repository. You can also use "ALL" or "*".
*"ids=list-of-artifact-ids" is a comma-separated list, with no spaces, of the exact IDs of the mashables or mashups that you wish to export.
*"name=artifact-name-pattern or list-of-artifact-names" is one specific artifact name, a portion of an artifact name with wildcards, such as Yah* or*Yah, or a comma-separated list of artifact names, with no spaces.
*"tag=some-tag" is the name of a user-defined tag. This selects all mashables or mashups that have that tag. You can also use wildcards to select by partial tag name, such as News* or *News. Use * to export all mashables and mashups that have tags. Mashables and mashups with no tags are excluded.
*"type=artifact-type" = ATOM, DATABASE, MASHUP, RSS, REST, SHAREPOINT, SPREADSHEET or WSDL. This selects all artifacts of that type.
*-f output-file: is the path and name of the export file to hold the metadata.
*-l prestoUrl: is optional. Use this if the MashZone NextGen Server is remote or if it is not running in Tomcat on the default Tomcat port. If you omit this option, this defaults to http://localhost:8080/presto/edge/api.
*-u username: is the MashZone NextGen username to log in with. This account must have MashZone NextGen administrator permissions.
*-w password: is the MashZone NextGen password to log in with.
*-v: is an optional flag to turn on verbose logging.
General messages and errors from the export process are sent to the command window (stdout). Messages for specific artifact failures are included in the export file in <FailedExport> elements. Once the export command completes successfully, you can use the output file to import mashables or mashups to another MashZone NextGen Repository.
Example
The following example from a Windows environment, exports data for all REST mashables from the localhost to a file named localRestSvcs.xml and logs all messages or errors from the export process to a file named localRestExport.log.
c:\MashZone NextGenversion\prestocli> padmin exportServices
-q "type=REST" -f localRESTSvcs.xml -u Administrator -w manage
>> localRestExport.log
Copyright © 2013-2016 Software AG, Darmstadt, Germany.
Product LogoContact Support   |   Community   |   Feedback