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.
Before you begin
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.
About this task
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, you can use the wsadmin tool.
You 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. You can add a business-level application composition unit to more than one business-level application.
Procedure
- Create an empty business-level application.
- Click Applications > New application > New Business Level Application.
- On the New business-level application page, specify a unique name for the application and a description, and then click OK.
- On the business-level application settings page, click Save.
- 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.
- Import the assets or create the business-level applications that you want to add to the business-level application.
- Go to the business-level application
settings page.
Click Applications > Application Types > Business-level applications > application_name.
- 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.
- 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.
- 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.
- 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.
- If you are adding one or more deployable unit assets, specify composition unit relationship options.
- 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.
- On the Adding composition unit to the business-level application page, click Save.
- 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.
- Click Applications > New application > New Enterprise Application.
- On the first Preparing for the application installation page, specify the Java EE application or module to install and click Next.
- 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.
- 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.
- 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.
- Complete the other application installation wizard options as needed to install the Java EE application or module.
- 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.
- 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.
- Go to a settings page for your business-level application.
Click Applications > Application Types > Business-level applications > your_application_name.
- Under Deployed assets, click Add > Add Shared Library.
- 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.
- On the Select installation options page of the wizard, select your business-level application for Business-level application name.
- On the Map shared library relationship page of the wizard, specify a relationship identifier and composition unit name for the asset.
- Complete the other wizard options as needed.
- 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.
Results
The name of your business-level application is shown on the Business-level applications page in the list of applications.
What to do next
After you create the application, save the changes to your configuration and start the application as needed.
Subtopics
Business-level application collection
Use this page to view and manage business-level applications.New business-level application settings
Use this page to name and describe a new business-level application.Shared library relationship and mapping settings
Use the Shared library relationship and Shared library relationship mapping pages to specify relationship identifiers and composition unit names for shared libraries that modules in your enterprise application reference. When installing your enterprise application, the product creates a composition unit for each shared library relationship in the business-level application that you specified on the Select installation options page of the application installation wizard.Add composition unit settings
Use this page to specify options for the composition unit to be added to the business-level application. The product assigns a default value for an option when you do not specify a value.Add asset settings
Use this page to add one or more assets to a business-level application.Set options settings
Use this page to specify options for the composition unit to be added to the business-level application. The product supplies default values for the options if you do not specify a value.Map target settings
Use this page to map a composition unit to a deployment target. The product assigns a default target when you do not specify a target.Relationship options settings
Use this page to specify relationship options for deployable or composition units in an asset deployed as part of a business-level application. Specifying a relationship declares a dependency relationship that a deployable unit or composition unit has on another asset deployed as a shared library in the same business-level application.


File name: trun_app_bla_install_console.html