Integrate Software AG Products Using Digital Event Services 10.4 | Integrate Software AG Products Using Digital Event Services | MashZone NextGen Help | Appendix | Administration | MashZone NextGen Server Administration | Deploying MashZone NextGen Instances, Clusters or Artifacts | Deploying MashZone NextGen Artifacts and Other Metadata | Deploying MashZone NextGen Artifacts and Other Metadata
 
Deploying MashZone NextGen Artifacts and Other Metadata
You deploy specific artifacts (mashables, mashups or apps) and other metadata from a source MashZone NextGen Server to a target MashZone NextGen Server using the export and import commands.
Important: You cannot use export and import commands when the MashZone NextGen version for the source and target MashZone NextGen Servers are different:
*For major upgrades, use the migrate command instead.
*For minor upgrades, please contact Technical Support or your Software AG representative.
In addition to the basic metadata for an artifact, a successful deployment must include related metadata, related files, extensions the artifact may use and any other artifacts that the artifact depends on.
The export and import commands automate deployment for most of this data, with some specific limitations that require manual deployment steps.
1. Export the specific mashable, mashup or app artifacts that you want to deploy to another MashZone NextGen Server and any macros, pluggable views or pluggable libraries that they may use.
See the following topics for instructions using these MashZone NextGen export commands:
*Exporting Mashable and Mashup MetaData
*Exporting Macros
*Exporting App MetaData
*Exporting Pluggable Views or Libraries
*Exporting MashZone NextGen Global Attributes
*Exporting Users, User Metadata and Groups
The data that is exported and known limitations for these commands include:
Table 16. Known Export/Import Limitations
Exported
Not Exported
Artifact Metadata
*Basic metadata such as provider, category, tags and description.
*Ownership (who created the artifact).
*On/off status.
*Run permissions.
*Views.
*Artifact attributes.
*For apps, the AppDepot status.
*User rating and feedback.
*Snapshots.
*Snapshot schedules.
*Caching configuration.
Related Metatdata/ User Metadata
*Providers.
*Categories.
*Global and user MashZone NextGen attributes.
*Users, groups and user group assignments if this data is tracked in the default MashZone NextGen User Repository and not in your LDAP Directory.
*Datasources and their JDBC drivers that are used by database mashables or by mashups.
Datasources must be added to the target MashZone NextGen Server before you import any artifacts that use them or the import will fail.
*For apps that are published to the AppDepot, any user preferences for Favorite Apps.
*User preferences for apps in Mashboard or the Mashboard state for workspace apps.
Resource Files
*Thumbnails for apps or pluggable views.
*Screenshots for apps.
*HTML, JavaScript, CSS, images or any other file uploaded in the package for a custom app.
Thumbnails for mashables or mashups.
Dependencies
Optionally can export dependent artifacts:
*For workspace apps, this always exports all the apps used in the workspace.
*For individual apps, you can choose to also export any mashables or mashups explicitly declared and used by those apps.
If you choose to include dependencies, all dependencies for basic apps are handled because MashZone NextGen automatically declares dependencies for basic apps.
For custom apps, export handles any dependencies that are explicitly declared with a <dependson> element in the App Specification. App developers must supply this information.
*For mashups, this always exports any other mashups or mashables that are used by the mashup.
*For pluggable views or pluggable libraries you can choose to export any library dependencies.
Any snapshots used by apps.
Extensions
*Registered macros, for use in mashups.
*HTML, JavaScript, CSS, images or any other file uploaded in the package for a pluggable view or pluggable library.
*Attribute definitions for extension attributes in artifacts.
*Any of the file-based extensions such as custom XPath functions. See for a complete list.
MashZone NextGen Server Configuration
Configuration for the MashZone NextGen Server.
2. Copy the files for any extensions used by the exported artifacts from the MashZoneNG-config folder for the source MashZone NextGen Server to the MashZoneNG-config folder for the target MashZone NextGen Server. See for a list of potential file-based extensions.
Note: The MashZoneNG-config folder may be an external configuration folder outside of the source and target MashZone NextGen Servers or it may be in the default locations. See Setting Up an External MashZone NextGen Configuration Folder for more information on MashZoneNG-config locations.
3. Define datasources in the Admin Console for the target MashZone NextGen Server with matching names and JDBC drivers to the datasources in the source MashZone NextGen Server. If these are not present, import of database mashables or mashups that use datasources fails.
See Manage data sources and drivers for instructions.
4. Use the export files created earlier to import mashables, mashups, apps, macros, pluggable views, pluggable libraries, MashZone NextGen global and user attributes, users, groups and user group assignments from the source MashZone NextGen Server.
See the following topics for information on using these commands:
*Importing Macros
*Importing Mashable or Mashup MetaData
*Importing Pluggable Views or Libraries
*Importing App Metadata
*Importing MashZone NextGen Global Attributes
*Importing Users, User Metadata and Groups
5. If needed, Update Mashable Endpoints or Update Mashable Security Profiles.
Copyright © 2019 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.
Innovation Release