Create business-level applications

We can create an empty business-level application and then add assets, shared libraries, business-level applications, and other artifacts as composition units to the empty business-level application.

Configure each target application server as needed. We must deploy a business-level application to a Version 7.0 or later server or cluster.

Optionally, determine what assets or other files to add to the business-level application and whether the application files can run on the deployment targets.

We can create business-level applications using the console, programming, or wsadmin.sh.

1. Select a way to create the business level application.
   level applications. We can create business-level applications

   Option	Method
   Administrative console business-level application creation wizard See Create business-level applications with the console.	Click Applications > New application > New Business-level Application and follow instructions in the wizard.
   Administrative console Java EE application installation wizard See Install enterprise application files with the console.	Click Applications > New application > New Enterprise Application and follow instructions in the wizard. The product creates a new business-level application with the enterprise application that you install or makes the enterprise application a composition unit of an existing business-level application. See the Business-level application name setting on the Select installation options wizard page.
   Java APIs See Create an empty business-level application using programming.	Use programming to create an empty business-level application.
   wsadmin scripts See Set up business-level applications .	Use the wsadmin scripting tool to create an empty business-level application.

2. Create the business-level application using the console, programming or wsadmin.

3. Save the changes to the administrative configuration.

   When saving the configuration, synchronize the configuration with the nodes where the application is expected to run.

Results

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

What to do next

After creating a business-level application, we can do the following to add composition units to it:

1. Import any assets needed by the business-level application.

2. Add assets, shared libraries, or other business-level applications as composition units.

3. Save the changes to the administrative configuration.

4. Start the business-level application.

If the application does not run as desired, edit the application configuration, then save and run it again.

Subtopics

• Create business-level applications with the console
  We can create an empty business-level application and then add assets or business-level applications as composition units to the empty business-level application.

• Business-level application settings
  Use this page to configure a business-level application.

• Composition unit settings
  Use this page to view composition unit settings and to change the configuration properties of a composition unit. The specific settings that are available for configuration can vary, depending upon the contents of the composition unit. For example, there are additional configuration settings if the asset contained in the composition unit is an SCA composite, or an OSGi application.

• Example: Create a business-level application
  We can add many different types of artifacts to business-level applications. For example, we can add Java EE applications or modules, Java archives (JAR files), data in compressed files, and other business-level applications.

Related tasks

Administer application servers

Create an empty business-level application using programming

Start a business-level application using programming

Set up business-level applications

Start business-level applications

Deploy and administering business-level applications