What Does Connecting To Dm Server Mean - T-Tees - Your Answers Await, Life's Questions Unraveled

This section describes the provisioning repository feature of SpringSource dm Server, the reasons for using it, and how to configure it.

You may be interested

In most use cases, your application has a dependency on one or more separate artifacts; these artifacts might include OSGi bundles, configuration artifacts, third-party libraries, PARs or plans. A typical example is a Spring application that depends on a third-party library such as Spring Framework or Hibernate.

You are viewing: What Does Connecting To Dm Server Mean

The way you express this dependency depends on the artifact. For example, a plan is by definition a list of dependent bundles.

Libraries are another example. Some third-party dependencies consist of multiple bundles but are logically one unit. To support this, the SpringSource dm Server introduces the concept of a library. A library is a collection of related bundles that can be referenced as a whole. You typically express the dependencies between your application and third-party libraries using the Import-Package or Import-Library manifest header in the MANIFEST.MF file of your application. The Import-Package header is standard to OSGi; Import-Library, however, is specific to SpringSource dm Server.

For additional details about the creation and usage of libraries, as well as general information about dependencies, see Programmer’s Guide.

In SpringSource dm Server, you store all third-party dependencies required by your applications, such as Spring Framework and Hibernate, as artifacts in the provisioning repository. As mentioned above, you can store the following types of artifacts in the repository:

Refer to more articles: What Is Considered Harassment By Code Enforcement

When you deploy your application, SpringSource dm Server installs the bundle in which it is packaged to the dm Server runtime; part of this internal installation procedure is to satisfy all the application’s dependencies. If your application has a dependency that cannot be satisfied from the bundles that you have already deployed (and dm Server has thus installed), the dm Server searches the provisioning repository for an artifact that can satisfy that dependency.

The provisioning repository for a particular instance of SpringSource dm Server can include artifacts in the following general locations:

You configure the provisioning repository using the SERVER_HOME/config/com.springsource.repository.properties file.

As previously described, a particular instance of SpringSource dm Server can itself also act as a repository host for remote server instances to use when satisfying the dependencies of the applications deployed to it. In this case, you configure a hosted repository using the SERVER_HOME/config/com.springsource.repository.hosted.properties file. Typically, only remote clients use hosted repositories and their contents; the SpringSource dm Server instance that actually hosts the repository does not typically use the artifacts in it. Rather, it uses artifacts in its local repository.

Making a third-party dependency available to your application is simply a matter of adding its artifact to the appropriate location in the provisioning repository. This could be either in the local directories or the remote ones if you are getting artifacts from a remotely-hosted repository.

Source: https://t-tees.com
Category: WHAT