WAS v8.5 > Administer applications and their environment

Deploy business-level applications

Deploying a business-level application consists of creating the business-level application on a v7.0 or later server.

A business-level application is an administration model that provides the entire definition of an application as it makes sense to the business. It is a WebSphere configuration artifact, similar to a server, stored in the product configuration repository. A business-level application can contain artifacts such as Java EE applications or modules, shared libraries, data files, and other business-level applications. You might use a business-level application to group related artifacts or to add capability to an existing application. For example, suppose to add capability provided in a JAR to a Java EE application already deployed on a product server. We can add that capability by creating a new business-level application and adding the JAR file and the deployed Java EE application to the business-level application. In some cases, we do not even need to change the deployed Java EE application configuration to add the capability.

Before creating a business-level application, you must develop the artifacts to go in the application and configure the target server. Before choosing a deployment target for the application, ensure the target version is 7.0 or later. When creating a business-level application, we can configure the application enough to enable it to run on the server. Later, we can configure the application and its contents further, start or stop the application, and otherwise manage its activity.

The topics in this section describe how to deploy and administer a business-level application or its contents using the dmgr console. We can also use programming or wsadmin scripting.

• Import assets to a repository.
• View, delete, update, or export assets.
• Create a business-level application.
• Create a SCA business-level application that has SCA assets, shared libraries, or business-level applications.
• Start the application.
• Stop the application.
• Update the application and its configuration units.
• Update SCA composite artifacts.
• View the composite definition of an SCA asset composition unit.
• View SCA domain information.
• View or edit JMS bindings on references and services of SCA composites
  
• Delete the application.

After making changes to administrative configurations of the applications in the dmgr console, ensure that you save the changes.

Subtopics

• Business-level applications
  A business-level application is an administration model that provides the entire definition of an application as it makes sense to the business. A business-level application is a WebSphere configuration artifact, similar to a server or cluster, stored in the product configuration repository.
• Assets
  An asset represents one or more application binary files stored in an asset repository. Typical assets include application business logic such as Java EE archives, library files, and other resource files.
• Composition units
  A composition unit represents a configured asset in a business-level application. A composition unit enables the asset contents to interact with other assets in the application. It also enables the product run time to load and run asset contents.
• Importing assets
  You must register application business logic such as Java EE archives, libraries, and other resource files with the product configuration as assets before we can add the assets to one or more business-level applications. Importing an asset registers it with the product configuration.
• Manage assets
  After application binary files are imported and registered with the product management domain as assets, we can view, update and export those assets.
• Create business-level applications
  We can create an empty business-level application and then add assets, shared libraries, business-level applications, and other artifacts as composition units to the empty business-level application.
• Start business-level applications
  We can start a business-level application not running (has a status of Stopped). The application must contain code that can run on a server to start.
• Stopping business-level applications
  We can stop a business-level application that is running and has a status of Started).
• Update business-level applications
  We can update business-level applications by deleting or changing composition units, or by mapping composition units to different deployment targets.
• Delete business-level applications
  After an application no longer is needed, we can delete it.
• Business-level applications
  A business-level application is an administration model that provides the entire definition of an application as it makes sense to the business. A business-level application is a WebSphere configuration artifact, similar to a server or cluster, stored in the product configuration repository.
• Importing assets
  You must register application business logic such as Java EE archives, libraries, and other resource files with the product configuration as assets before we can add the assets to one or more business-level applications. Importing an asset registers it with the product configuration.
• Manage assets
  After application binary files are imported and registered with the product management domain as assets, we can view, update and export those assets.
• Create business-level applications
  We can create an empty business-level application and then add assets, shared libraries, business-level applications, and other artifacts as composition units to the empty business-level application.
• SCA application package deployment
  WAS v8.5 supports deployment of many types of Service Component Architecture (SCA) artifacts as composition units of business-level applications. Typical artifacts include JAR files, compressed .zip files, and web application archive (WAR) files.
• Create SCA business-level applications
  We can create an empty business-level application and then add SCA assets, shared libraries, business-level applications, and other artifacts as composition units to the empty business-level application.
• Start business-level applications
  We can start a business-level application not running (has a status of Stopped). The application must contain code that can run on a server to start.
• Stopping business-level applications
  We can stop a business-level application that is running and has a status of Started).
• Update business-level applications
  We can update business-level applications by deleting or changing composition units, or by mapping composition units to different deployment targets.
• Update SCA composite artifacts
  We can view and update Service Component Architecture (SCA) composite artifacts in business-level applications.
• View SCA composite definitions
  We can view information on the definition of a Service Component Architecture (SCA) composite in the dmgr console.
• View SCA domain information
  We can view information on Service Component Architecture (SCA) composites in an SCA domain in the dmgr console.
• View and editing JMS bindings on references and services of SCA composites
  We can view information on a JMS binding for a SCA composite in the dmgr console. The JMS bindings page of the console displays the settings of a binding.jms element. We can use the console page to edit resource and response resource settings.
• Export WSDL and XSD documents
  We can export Web Services Description Language (WSDL) and XML schema definition (XSD) documents used by a Service Component Architecture (SCA) composition unit to a location of your choice.
• Delete business-level applications
  After an application no longer is needed, we can delete it.

Related concepts:

SCA composites
SCA contributions
SCA application package deployment

Related

Administer business-level applications using programming
Administer applications using wsadmin.sh
Administer application servers
Create SCA business-level applications
Update SCA composite artifacts
View SCA composite definitions
View SCA domain information
View and editing JMS bindings on references and services of SCA composites

Reference:

Business-level application page

+

Search Tips   |   Advanced Search