Limitations

The following are some limitations of the Export and Import feature:

DAAs not Exported After System is Upgraded

If you have upgraded from TIBCO ActiveMatrix 3.1.5 or an earlier release, DAA files uploaded prior to the upgrade to the current release do not display in the DAA tab of ActiveMatrix Administrator. For the same reason, since they are not available to download from ActiveMatrix Administrator GUI, export process cannot download them.

Failure after Application is Upgrade (New DAA has New Components)

During import process, if an application was upgraded but the new application had new components that were originally not there in the old application version, starting this app results in an error. The reason for this is that the new (additional) components are not mapped to any node. To resolve the error, you must manually map (distribute) them through ActiveMatrix Administrator GUI and then re-deploy the application.

Bindings from DAA Removed from Administrator

Using ActiveMatrix Administrator, you can delete bindings from an existing application. Originally, the DAA application had certain bindings but later in ActiveMatrix Administrator one or more bindings were deleted from that application. Now, if user exports the application and imports it in the target ActiveMatrix Administrator, the deleted binding reappears.

Messaging Bus for Existing Environment is not Updated During Import

At the time of import, if an environment exists in the target system, the import option import.treatment.for.existing.objects is ignored and the messaging bus is NOT updated. This is a limitation because setting or updating of a messaging bus of an environment requires all applications to be stopped and this cannot be done through exported CLI script.

Notification Server Information is Never Updated During Import

Notification server is used by ActiveMatrix Administrator to receive all sorts of notifications from remote Hosts and Nodes. If import process is allowed to change value of notification server, that can cause unforeseen problems with ActiveMatrix Administrator. At the time of import irrespective of the value of import.treatment.for.existing.objects, import does not change notification server information.

Export process does exports this information in export archive (found at AdminConfig\admin_config_data.xml) but that information is never used to make changes on target ActiveMatrix Administrator.

Limitation of import.treatment.for.existing.objects=skip

If the top level object is skipped, the child objects are not created even if they do not exist in the target environment. For example, if Environment is skipped, the following child objects are NOT added even if they do not exist in the target ActiveMatrix Administrator:
Top level object Child Object
Environment
  • Environment level substitution variables
  • Environment scoped resource templates
Node
  • Resource Instances
  • Node level substitution variables
  • Features
  • Loggers and Logging appenders
Application
  • Application level substitution variables
  • Application scoped resource templates
  • Loggers and Logging appenders
Host
  • Host level substitution variables
  • Loggers and Logging appenders

Shared Library / Custom Feature that Needs 'Resolve' Mode

If your Shared library needs to be enabled with Resolve mode, it might fail sometimes during "start" target for Node.

While installing resource instance and feature, first install resource instance with options="auto-resolve" and then enable the feature. If enabling of feature fails (because it needs "resolve" mode), the build fails (only for that node's build file). To resolve this issue, add "resolve" mode to that particular feature and re-run or manually enable/provision that feature.

AMX Host Needs Secure Communication that are not set During Import

While using the create target to create a Host, if it finds that this host needs a secure communication (secure JMX), it is not set by the create action. A warning is displayed on the console.

To do this manually:

  1. Navigate to the directory for the Host that needs to be secure.
  2. Run the following ant command.

>ant -f host_build.xml secureJMX

AMX Objects That are not Exported

  • UDDI Servers
  • Policy objects
Note: Policy set properties are exported as those are part of the DAA file itself.
  • Target Object Group
  • ActiveMatrix Administrator Plugins

Runtime State of ActiveMatrix Objects

As of now, export process does not record the runtime state of exported object. For example, let us say, you have one node in a stopped state. After running export, if you look at exported data file, you will not find any information related to Runtime state in that data file.

Since there is no runtime state preserved in exported data files, while you run create and start target, import starts everything that it knows it can start.