- Create an empty business-level
application.
You typically create an empty business-level
application and then add assets or business-level applications as
composition
units to the empty business-level application.
- Import an asset.
You can import an asset to register the asset with the product
and
optionally store the asset in the product repository so that you can
later
use the asset in a business-level application. An asset represents
at least
one binary file that implements business logic.
- Add a composition
unit.
You can add an asset to a business-level
application by creating
a composition unit for the asset. A composition unit is typically
created
from an asset and contains configuration information that makes the
asset
runnable.
- Start a business-level application.
You can start a business-level application, which starts
each composition
unit in that business-level application. Each composition unit is
started
on the respective targets on which the business-level application
is deployed.
- Stop a business-level application.
You can stop a business-level application, which stops each
composition
unit in that business-level application. Each composition unit is
stopped
on the respective targets on which the business-level application
is deployed.
- Check the status of a business-level
application.
You can check the status of an entire
business-level
application. You can also limit the status to a particular composition
unit
of a business-level application, a specific deployment target, or
check the
status of the composition unit and the deployment target at the same
time.
- Delete
a business-level application.
You can delete
a business-level application using programming. You
might delete a business-level application if the application is not
functioning
correctly, no longer needed, and so on.
-
Delete an asset.
You can delete an asset from a business-level application
using programming
if the asset is not functioning corrctly, the asset is no longer needed,
and
so on. An asset represents at least one binary file that implements
business
logic.
- Delete a composition
unit.
You can delete a composition unit from
a business-level
application if the composition unit is not functioning correctly,
the composition
unit is no longer needed, and so on. A composition unit is typically
created
from a business-level application or an asset and contains configuration
information
that makes the asset runnable.
- Export an asset.
You
can export an asset from the current session so that you can
back up the asset, import the asset to another session, and so on.
An asset
represents at least one binary file that implements business logic.
- List assets.
You can list the assets that have been imported to the current
workspace
so that you can do further asset administration, such as deleting
or exporting
assets. An asset represents at least one binary file that implements
business
logic.
- List composition units.
You can list the composition units for a specific business-level
application in a session so that you can do further composition unit
administration,
such as deleting or adding composition units. A composition unit is
typically
created from a business-level application or an asset and contains
configuration
information that makes the asset runnable.
-
List business-level applications.
You can list the business-level applications of a session
so that
you can do further business-level application administration such
as deleting
a business-level application. A business-level application is an administrative
model that captures the definition of an enterprise-level application
so that
you can perform specific business functions, such as accounting.
- Edit
a composition unit.
You can edit the configuration
information in a composition unit
of a business-level application if, for example, you want to change
which
modules in the composition unit are configured to run in which targets.
A
composition unit is typically created from a business-level application
or
an asset and contains configuration information that makes the asset
runnable.
- Edit an asset.
You
can edit the information of an asset, for example, its destination
location, its relationship with other assets, and so on. An asset
represents
at least one binary file that implements business logic
- Edit a business-level
application.
You can edit the information of
a business-level application such
as its description. A business-level application is an administrative
model
that captures the entire definition of an enterprise-level application.
- Update
an asset.
You can update an asset by adding,
deleting, or updating a single
file or Java Platform, Enterprise Edition
(Java EE)
module, or by merging multiple files or Java EE
modules into an asset. You can also
update an asset by replacing the entire asset.
- View a composition
unit.
You can view the composition unit information
so that you can do
other tasks associated with the composition unit, such as editing
an asset
or deleting a composition unit. A composition unit is typically created
from
a business-level application or an asset and contains configuration
information
that makes the asset runnable.
- View an asset.
You
can view the asset information so that you can do other tasks
associated with the asset, such as editing or exporting an asset.
An asset
represents at least one binary file that implements business logic.
- View a business-level
application.
You can view business-level application
information such as the description
so that you can do other tasks associated with the business-level
application,
such as editing the business-level application. A business-level application
is an administrative model that captures the entire definition of
an enterprise-level
application.
- List control operations.
You can list the control operations of a business-level application
or a composition unit for a session. You use control operations, such
as start
or stop, to change or query the runtime environment of a business-level
application
or a composition unit.