About dm Server bundles dependencies in many server

[dr_pompeii]

Dear Members

How I can manage the follow situation

In one pc dedicated for development purposes ( Eclipse + dm Server Tools )
I can have a PAR project with many nested bundles projects,
but for some bundles was necessary download many bundles for dm server itself (i.e.bundles X,Y,Z), thats available in the section
(The bundle repository browser for the local dm Server - offered by dm server tools)


What happens If I export the PAR project (.par) for production environment for other machine , where I have of course other dm server installed, but the point is that bundles X,Y,Z never was download there

How I can manage this?

I hope you see my point

Thanks in advanced

[Glyn Normington]

In dm Server 1.0, it is necessary to copy the bundles that you downloaded, which are presumably in <dm Server home>/repository/bundles/usr, to the same directory in the servers you are trying to set up.

In dm Server 2.0, we will support repository sharing between dm Server instances. This will allow dependencies, such as the bundles you downloaded, to be provisioned automatically from the shared repository. An initial implementation of this support is available in 2.0.0.M1.

[dr_pompeii]

Hello Glyn

Thanks for the reply



In dm Server 1.0, it is necessary to copy the bundles that you downloaded, which are presumably in <dm Server home>/repository/bundles/usr, to the same directory in the servers you are trying to set up.

thats right, it seems mandatory keep an own special list of the bundles and even the libraries
(<dm Server home>/repository/libraries/usr) already installed



In dm Server 2.0, we will support repository sharing between dm Server instances. This will allow dependencies, such as the bundles you downloaded, to be provisioned automatically from the shared repository. An initial implementation of this support is available in 2.0.0.M1.

Just few minutes ago, I saw the Documentation section ( Getting Started Guide, User Guide , Programmer Guide) for 2.0.0.M1
but seems that documentation about this, is not available yet

Regards

[Glyn Normington]

Well spotted! Documentation writing is scheduled after coding and testing to reduce rewriting. The downside is that undocumented features are tricky for users to try out and provide feedback on.

Note that documentation tasks are visible on JIRA, e.g. https://issuetracker.springsource.com/browse/DMS-459. Since the 2.0 repository work is in its early stages, the corresponding documentation tasks are still to be raised.

[Glyn Normington]

https://issuetracker.springsource.com/browse/DMS-526 has been added to document the repository function in M1.

[dr_pompeii]

Hello Glyn

Thanks for both replies



Well spotted! Documentation writing is scheduled after coding and testing to reduce rewriting.

Sound good



The downside is that undocumented features are tricky for users to try out and provide feedback on.

Thats would be a problem, but let's do it

I will be watching very closely the JIRA links.

BTW, some plan to integrate dm server with terracotta?,
if this already exists(I dont think so), would be possible see some documentation?

Regards

[Glyn Normington]

We haven't done any work to integrate dm Server with Terracotta, but do feel free... ;-)