ace-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sibla Wilfried <>
Subject ACE Agent deployment after renaming/changing the agent.identification.agentid property
Date Tue, 04 Feb 2014 16:13:27 GMT

I tried to prepare a default target runtime for initial installation.
My uses was: creating multiple target environments upfront and initial startup with predeployed
DP and avoiding immediate deployment after first connection to the ACE server (efficient target
replication and provisioning).

I chose the following proceeding:

1.) start my target with ID: default
2.) copied the whole osgi runtime including the bundle cache and its configuration to new
3.) changed the agent.identification.agentid property to e.g. myExampleID
4.) start the new target osgi container with ID myExampleID.

But this does not work.
The reason is that the ACE server is writing the ID of the target into the DP manifest as
the DeploymentPackage-SymbolicName.
And on the other side this value is used by the DeploymentAdmin to enable the installation
of multiple DPs on a target.

Using a fake value as DeploymentPackage-SymbolicName (within the StreamGeneratorImpl) and
ignoring the identification/target ID in DeploymentHandlerImpl.getInstalledVersion() (line
212) could support this use case.

Could this be a valuable use case for ACE? E.g. in a configurable manner (property "use dummy
DP-BSN": true/false; as a server and target property).

Thanks a lot in advance.


View raw message