+

Search Tips   |   Advanced Search

Create business-level applications with the console

Create an empty business-level application and then add assets or business-level applications as composition units to the empty business-level application.

Before you create a business-level application, decide upon an application name. Optionally, determine which assets, shared libraries, or business-level applications that the new business-level application needs.

The steps describe how to create an empty business-level application and then add assets as composition units to the application using the administrative console. Alternatively, we can use the wsadmin tool.

We can add an asset or shared library composition unit to multiple business-level applications. However, each composition unit for the same asset must have a unique composition unit name. We can add a business-level application composition unit to more than one business-level application.


Tasks

  1. Create an empty business-level application.

    1. Click Applications > New application > New Business Level Application.

    2. On the New business-level application page, specify a unique name for the application and a description> OK.

    3. On the business-level application settings page, click Save.

    The name and description are shown in the list of applications on the Business-level applications page. Because the application is empty, its status is Unavailable.

  2. Optional: Add one or more assets, non-Java EE shared libraries, or business-level applications to a business-level application.

    The product adds these assets as composition units of our business-level application.

    • If the asset to add to a business-level application is a Java EE application or module that is not yet deployed, see step 3.

    • If the asset is a Java EE shared library, see step 4.

    1. Import the assets or create the business-level applications to add to the business-level application.
    2. Go to the business-level application settings page.

      Click Applications > Application Types > Business-level applications > application_name.

    3. On the business-level application settings page, specify the type of composition unit to add.

      • To add an asset, under Deployed assets, click Add > Add Asset.

      • To add a shared library, under Deployed assets, click Add > Add Shared Library.

      • To add a business-level application, under Business-level applications, click Add.

    4. On the Add page, select a unit from the list of available units, and then click Continue.

      If we are adding one or more deployable unit assets and we have multiple imported assets available, we can select more than one deployable unit.

    5. On the Set options page, change the composition unit settings as needed> Next.

      This page is not shown when we add a Java EE asset as a shared library or if we have multiple deployable unit assets. If the application installation or update wizard displays and we want to add a Java EE asset as a shared library, see step 4.

    6. On the Map composition unit to a target page, change the deployment target as needed> Next.

      This page is not shown when we add a business-level application.

    7. If we are adding one or more deployable unit assets, specify composition unit relationship options.

      See Relationship options settings.

    8. On the Summary page, click Finish. Several messages are displayed, indicating whether the product adds the unit to the business-level application successfully. A message having the format Completed res=[WebSphere:cuname=unit_name,cuedition=version] indicates that the addition is successful. Click Manage application.

      If the product adds the unit successfully, the name of the unit is shown on the list of composition units on the Add composition unit to the business-level application page.

      If the unit addition is not successful, read the messages and try adding the unit again. Correct the problems noted in the messages.

    9. On the Adding composition unit to the business-level application page, click Save.

    The product creates composition units for the asset, shared library, or business-level application. The unit names are shown in lists of composition units on the settings page of our business-level application. To view the settings page, click...

            Applications > Application Types > Business-level applications > your_application_name.

  3. Optional: Install a Java EE application or module, and add it as a composition unit to a business-level application.

    When installing an EAR file or a stand-alone Java EE module using the application installation wizard, we can specify a business-level application to which to add the EAR file or module. We can also specify relationships to any shared libraries that your Java EE application or module uses. The product creates composition units that represent those relationships.

    1. Click Applications > New application > New Enterprise Application.

    2. On the first Preparing for the application installation page, specify the Java EE application or module to install and click Next.

    3. On the second Preparing for the application installation page, select Detailed - Show all installation options and parameters, specify whether to generate default bindings and mappings as needed for the application or module, and click Next.

    4. On the Select installation options page of the wizard, select a business-level application for Business-level application name and click Next. The product creates a composition unit that has the same name as the Java EE application or module and adds the unit to a business-level application.

      If we do not specify a value for Business-level application name, then the product creates a default business-level application that has the same name as the Java EE application that we are installing. The product does not add the Java EE application as a composition unit to the business-level application that we created in step 1.

    5. Optional: On the Map shared library relationship page of the wizard, specify relationship identifiers and composition unit names for shared libraries that modules in your Java EE application use. The product creates a composition unit for each shared library relationship in a business-level application.

      We can map shared library relationships when installing Java EE application or module or, after installation, return to the Map shared library relationship page and specify shared library relationships. See step 4.

    6. Complete the other application installation wizard options as needed to install the Java EE application or module.

    The product creates composition units for the application, module, or shared library relationships. The unit names are shown in lists of composition units on the settings page of our business-level application. To view the settings page, click...

            Applications > Application Types > Business-level applications > your_application_name.

  4. Optional: After installation of a Java EE application or module, we can specify composition units for relationships to shared libraries used by a business-level application. Specify relationships to shared libraries on the Map shared library relationship page of the application installation or update wizard.

    1. If we have not done so already, import a Java EE asset such as an enterprise bean (EJB) or web module (WAR) that uses a shared library file.

      If the product displays javaarchive for Asset type aspects on the asset settings page, continue to step 4b.

      If the product does not display javaarchive for Asset type aspects on the asset settings page, then the asset is not a Java EE asset. Use step 2 to add a shared library to a business-level application.

    2. Go to a settings page for our business-level application.

      Click Applications > Application Types > Business-level applications > your_application_name.

    3. Under Deployed assets, click Add > Add Shared Library.

    4. On the Add composition unit page, select the Java EE asset that we imported and then click Continue.

      The Java EE application installation or update wizard displays. Select the Java EE application or module that uses the asset, and complete the steps in the wizard.

    5. On the Select installation options page of the wizard, select a business-level application for Business-level application name.

    6. On the Map shared library relationship page of the wizard, specify a relationship identifier and composition unit name for the asset.
    7. Complete the other wizard options as needed.

    The product creates a composition unit for the shared library relationship. The unit name is shown in the list of deployed asset composition units on the settings page of our business-level application.

The name of our business-level application is shown on the Business-level applications page in the list of applications.


What to do next

After creating the application, save the changes to the configuration and start the application as needed.


Subtopics


Related:

  • Business-level applications
  • Composition units
  • Example: Creating a business-level application
  • Add an EBA asset to a business-level application
  • Asset collection
  • Select installation options settings
  • Business-level application settings