WAS v8.5 > Administer applications and their environment

Administer business-level applications using programming

We can use the command framework programming to create, edit, update, start, stop, delete, export, import, and query information about business-level applications. A business-level application defines an enterprise-level application.

This task assumes a basic familiarity with the command framework. Read about the command framework in the application programming interfaces documentation. Besides creating, editing, updating, starting, stopping, deleting, exporting, importing, and querying information about business-level applications using programming, we can do these tasks using the dmgr console or the wsadmin scripting tool.

  1. Perform any of the following tasks to administer your business-level applications using programming.

    1. 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.

    2. Import an asset.

      We can import an asset to register the asset with the product and optionally store the asset in the product repository so that we can later use the asset in a business-level application. An asset represents at least one binary file that implements business logic.

    3. Add a composition unit.

      We 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.

    4. Start a business-level application.

      We 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.

    5. Stop a business-level application.

      We 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.

    6. Check the status of a business-level application.

      We can check the status of an entire business-level application. We 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.

    7. Delete a business-level application.

      We 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.

    8. Delete an asset.

      We 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.

    9. Delete a composition unit.

      We 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.

    10. Export an asset.

      We can export an asset from the current session so that we 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.

    11. List assets.

      We can list the assets that have been imported to the current workspace so that we can do further asset administration, such as deleting or exporting assets. An asset represents at least one binary file that implements business logic.

    12. List composition units.

      We can list the composition units for a specific business-level application in a session so that we 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.

    13. List business-level applications.

      We can list the business-level applications of a session so that we 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 we can perform specific business functions, such as accounting.

    14. Edit a composition unit.

      We can edit the configuration information in a composition unit of a business-level application if, for example, 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.

    15. Edit an asset.

      We 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

    16. Edit a business-level application.

      We 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.

    17. Update an asset.

      We can update an asset by adding, deleting, or updating a single file or Java EE module, or by merging multiple files or Java EE modules into an asset. We can also update an asset by replacing the entire asset.

    18. View a composition unit.

      We can view the composition unit information so that we 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.

    19. View an asset.

      We can view the asset information so that we 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.

    20. View a business-level application.

      We can view business-level application information such as the description so that we 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.

    21. List control operations.

      We 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.

  2. Save your changes to the master configuration repository.
  3. Synchronize changes to the master configuration across the nodes for the changes to take effect.


Results

Depending on which tasks you complete, we have created, edited, updated, started, stopped, deleted, exported, imported, or queried information about business-level applications.

If we have further business-level application updates, we can do the updates through programming, the dmgr console, or the wsadmin scripting tool.


Subtopics


Related


Deploy business-level applications


+

Search Tips   |   Advanced Search