Deploy and administering business-level applications
Deploy a business-level application consists of creating the business-level application on a Version 7.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 or cluster, 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. We 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 or cluster. Before choosing a deployment target for the application, ensure that 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 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.
- (dist)(zos) Create a Service Component Architecture (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.
- (dist)(zos) Update SCA composite artifacts.
- (dist)(zos) View the composite definition of an SCA asset composition unit.
- (dist)(zos) View SCA domain information.
- (dist)(zos) View or edit JMS bindings on references and services of SCA composites
- Delete the application.
What to do next
After making changes to administrative configurations of the applications in the 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.
- Import assets
We 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.
- (dist)(zos) SCA application package deployment
The product 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 WAR files.
- (dist)(zos) Create SCA business-level applications
We can create an empty business-level application and then add Service Component Architecture (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 that is 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 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.
- (dist)(zos) Update SCA composite artifacts
We can view and update Service Component Architecture (SCA) composite artifacts in business-level applications.
- (dist)(zos) View SCA composite definitions
We can view information on the definition of a Service Component Architecture (SCA) composite in the console.
- (dist)(zos) View SCA domain information
We can view information on Service Component Architecture (SCA) composites in an SCA domain in the console.
- (dist)(zos) View and editing JMS bindings on references and services of SCA composites
We can view information on a Java Message Service (JMS) binding for a Service Component Architecture (SCA) composite in the console. The JMS bindings page of the console displays the settings of a binding.jms element. Use the console page to edit resource and response resource settings.
- (dist)(zos) Export WSDL and XSD documents
We can export WSDL and XML schema definition (XSD) documents used by a Service Component Architecture (SCA) composition unit to a location of the choice.
- Delete business-level applications
After an application no longer is needed, we can delete it.
Related concepts
Assets Composition units (dist)(zos) SCA composites
(dist)(zos) SCA contributions
Related tasks
Administer business-level applications using programming Administer applications Administer application servers
Business-level application collection