{section}
{column}
h1. Introduction
The Petals ESB "Artifact repository" is an extension providing (un)installation/(un)deployment service of artifacts from a local repository.
To install/deploy a JBI artifact previously put in the Artifact Repository, use the service {{[InstallationService|Petals ESB "WS API"#InstallationService]}} or {{[DeploymentService|Petals ESB "WS API"#DeploymentService]}} of the [Petals ESB WS API|Petals ESB "WS API"].
To put an artifact into the Artifact Repository, just copy yours JBI archives in the right directory or use the service {{[ArtifactRepository|Petals ESB "WS API"#ArtifactRepositoryService]}} of the [Petals ESB WS API|Petals ESB "WS API"].
{column}
{column:width=35%}
{panel:title=Table of contents}{toc:outline=true}{panel}
{panel:title=Contributors}{contributors:order=name|mode=list|showAnonymous=true|showCount=true|showLastTime=true}{panel}
{column}
{section}
h1. Installation
This extension is embedded into the ZIP archive and automatically install when installing Petals ESB using this archive.
This extension is also available as a Debian package, see "[Installing Petals ESB using the Debian packages]" to install the package "{{petals-esb-artifact-repository}}".
h1. Using the Petals ESB Artifact repository
Before to install or deploy JBI archives using the Petals ESB Artifact Repository, it should be filled with JBI archives.
h2. Putting JBI archives into the Artifact Repository
Two ways are available to fill the artifact repository:
* a basic way, based on the filesystem: using filesystem operations, you can copy yours JBI archives into the right sub-directory of the artifact repository root directory:
** {{sl}}, if your archive is a shared library,
** {components}}, if your archive is a component,
** ans, {{sa}}, is your archive is a service assembly.
* an uploading way, based on the [Petals ESB WS API|Petals ESB "WS API"]. Using the service {{[ArtifactRepositoryService|Petals ESB "WS API"#ArtifactRepositoryService]}} of the WS API you can upload your JBI archive into the artifact repository. It will be placed in the right sub-directory according to its nature defined in the JBI descriptor of the uploaded JBI archive.
h2. Installing or deploying JBI artifacts from the Artifact Repository
Installing or deploying a JBI artifact from the Artifact Repository is only available through the [Petals ESB WS API|Petals ESB "WS API"].
To install a component, use the service {{[InstallationService|Petals ESB "WS API"#InstallationService]}}.
To deploy a service assembly, use the service {{[DeploymentService|Petals ESB "WS API"#DeploymentService]}}.
{warning}Nowadays, the installation of a shared library is not supported{warning}
{anchor:Configuration}
h1. Configuration
h2. Runtime configuration parameters
Configuration parameters of the Petals ESB Artifact repository are available into the container local configuration (ie. into the file {{server.properties}}:
|| Parameter/Property name || Default value || Description ||
| {{petals.artifact-repository}} | {{true}} | Flag enabling/disabling the Artifact Repository |
| {{petals.artifact-repository.path}} | {{$\{[petals.data.basedir|Container Configuration#ContainerConfigRef]}/artifacts}} | The root directory of the artifact repository |
h2. Logging configuration parameters
The Petals ESB Artifact Repository uses the following logger to trace its execution: {{Petals.Extensions.ArtifactRepositoryService}}.
As the Petals ESB Artifact Repository is provided into the ZIP Archive of Petals ESB, its logging configuration is already configured. If you install this extension through Debian or RPM package, just add something like the following lines to your {{loggers.properties}}:
{code}
Petals.Extensions.ArtifactRepositoryService.level=FINEST
{code}
{column}
h1. Introduction
The Petals ESB "Artifact repository" is an extension providing (un)installation/(un)deployment service of artifacts from a local repository.
To install/deploy a JBI artifact previously put in the Artifact Repository, use the service {{[InstallationService|Petals ESB "WS API"#InstallationService]}} or {{[DeploymentService|Petals ESB "WS API"#DeploymentService]}} of the [Petals ESB WS API|Petals ESB "WS API"].
To put an artifact into the Artifact Repository, just copy yours JBI archives in the right directory or use the service {{[ArtifactRepository|Petals ESB "WS API"#ArtifactRepositoryService]}} of the [Petals ESB WS API|Petals ESB "WS API"].
{column}
{column:width=35%}
{panel:title=Table of contents}{toc:outline=true}{panel}
{panel:title=Contributors}{contributors:order=name|mode=list|showAnonymous=true|showCount=true|showLastTime=true}{panel}
{column}
{section}
h1. Installation
This extension is embedded into the ZIP archive and automatically install when installing Petals ESB using this archive.
This extension is also available as a Debian package, see "[Installing Petals ESB using the Debian packages]" to install the package "{{petals-esb-artifact-repository}}".
h1. Using the Petals ESB Artifact repository
Before to install or deploy JBI archives using the Petals ESB Artifact Repository, it should be filled with JBI archives.
h2. Putting JBI archives into the Artifact Repository
Two ways are available to fill the artifact repository:
* a basic way, based on the filesystem: using filesystem operations, you can copy yours JBI archives into the right sub-directory of the artifact repository root directory:
** {{sl}}, if your archive is a shared library,
** {components}}, if your archive is a component,
** ans, {{sa}}, is your archive is a service assembly.
* an uploading way, based on the [Petals ESB WS API|Petals ESB "WS API"]. Using the service {{[ArtifactRepositoryService|Petals ESB "WS API"#ArtifactRepositoryService]}} of the WS API you can upload your JBI archive into the artifact repository. It will be placed in the right sub-directory according to its nature defined in the JBI descriptor of the uploaded JBI archive.
h2. Installing or deploying JBI artifacts from the Artifact Repository
Installing or deploying a JBI artifact from the Artifact Repository is only available through the [Petals ESB WS API|Petals ESB "WS API"].
To install a component, use the service {{[InstallationService|Petals ESB "WS API"#InstallationService]}}.
To deploy a service assembly, use the service {{[DeploymentService|Petals ESB "WS API"#DeploymentService]}}.
{warning}Nowadays, the installation of a shared library is not supported{warning}
{anchor:Configuration}
h1. Configuration
h2. Runtime configuration parameters
Configuration parameters of the Petals ESB Artifact repository are available into the container local configuration (ie. into the file {{server.properties}}:
|| Parameter/Property name || Default value || Description ||
| {{petals.artifact-repository}} | {{true}} | Flag enabling/disabling the Artifact Repository |
| {{petals.artifact-repository.path}} | {{$\{[petals.data.basedir|Container Configuration#ContainerConfigRef]}/artifacts}} | The root directory of the artifact repository |
h2. Logging configuration parameters
The Petals ESB Artifact Repository uses the following logger to trace its execution: {{Petals.Extensions.ArtifactRepositoryService}}.
As the Petals ESB Artifact Repository is provided into the ZIP Archive of Petals ESB, its logging configuration is already configured. If you install this extension through Debian or RPM package, just add something like the following lines to your {{loggers.properties}}:
{code}
Petals.Extensions.ArtifactRepositoryService.level=FINEST
{code}