webMethods Deployer 10.3 | webMethods Deployer Documentation 10.3 | Deployable Assets | Application Platform Assets
 
Application Platform Assets
This section identifies the Application Platform assets that you can deploy using Deployer.
The Application Platform assets types can be:
*Bundle - An OSGi bundle.
*Service - An OSGi service.
*WebApp - A web application.
*Config - An OSGi dynamic configuration because these assets represent an OSGi-specific item unlike the web application.
*JndiResource - A JNDI resource injection. This asset defines how to inject an OSGi dynamic configuration into the JNDI space of a web application. This asset does not represent the configuration itself.
Application Platform composites may contain the following assets:
*bundle composite: Bundle, WebApp, Service
*war composite: WebApp
*properties composite: Config, JndiResource
Note: You can deploy Application Platform assets in repository-based deployment only.
The following table lists:
*The assets that you can export
*The asset type ID for each asset
*Asset dependencies
Asset
Asset Type ID
Dependencies, Substitutions, and Other Considerations
OSGi Bundle
Bundle
Each "bundle" composite always contains exactly one Bundle asset. The Bundle asset can depend on zero or more Service assets that are almost always provided by other "bundle" composites.
OSGi Service
Service
Each "bundle" composite can contain zero or more Service assets. The Service asset does not have any dependencies on other assets.
OSGi Dynamic Configuration
Config
Each "properties" composite always contains exactly one Config asset. The Config asset does not have any dependencies on other assets. By default, all properties in the "properties" file represented by the "properties" composite are translated to substitutions for the Config asset.
JNDI resource injection
JndiResource
When a "properties" composite defines a JNDI resource that needs to be injected into a web application, it will contain exactly one JndiResource asset in addition to the main Config asset.
When the JndiResource asset defines an injection of an OSGi Service into the web application, it will have a dependency on the respective Service asset. JndiResource assets that do not define a Service injection can never have dependencies on other assets. When a "properties" composite contains a JndiResource, all properties of the respective properties file except those that describe the JNDI name and target web application context, are translated to substitutions for the Config asset of the "properties" composite.
Web Application
WebApp
The "war" composite always contains exactly one WebApp asset. The "bundle" composite can contain a single WebApp asset if the composite represents a "web bundle" (WAB). The WebApp asset can have dependencies on one or more JndiResource assets - one for every JNDI resource described in the web.xml.
Copyright © 2013-2018 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.