Creating business-level applications with the console

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

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, and then click 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 your business-level application.

   • If the asset that you want to add to your business-level application is a Java Platform, Enterprise Edition (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 that you want 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 you are adding one or more deployable unit assets and you have multiple imported assets available, you can select more than one deployable unit.

   5. On the Set options page, change the composition unit settings as needed, and then click Next.

      This page is not shown when you add a Java EE asset as a shared library or if you have multiple deployable unit assets. If the application installation or update wizard displays and you 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, and then click Next.

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

   7. If you 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 Adding 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 your 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 your business-level application.

   When installing an enterprise archive (EAR) file or a stand-alone Java EE module using the application installation wizard, you can specify a business-level application to which to add the EAR file or module. You 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 your 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 your business-level application.

      If you 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 you are installing. The product does not add the Java EE application as a composition unit to the business-level application that you 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 your business-level application.

      You can map shared library relationships when installing your 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 your 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, you can specify composition units for relationships to shared libraries that are used by your business-level application. Specify relationships to shared libraries on the Map shared library relationship page of the application installation or update wizard.
   1. If you 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 your business-level application.

   2. Go to a settings page for your 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 you 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 your 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 your business-level application.