Create business-level applications

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 v7.0 or later server or cluster.

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

Create business-level applications using the administrative console or wsadmin.sh.

Tasks

1. Select a way to create the business level application.

   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. WAS v9 creates a new business-level application with the enterprise application that we 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.
   wsadmin scripts See Set up business-level applications .	Use the wsadmin scripting tool to create an empty business-level application.

2. Create a business-level application using the administrative console 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.

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 a 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 wanted, edit the application configuration, then save and run it again.

Subtopics

• 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.
• Business-level application settings
  Configure a business-level application.
• Composition unit settings
  View composition unit settings and to change the configuration properties of a composition unit. The specific settings 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 uni is an OSGi application.
• Example: Creating 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.

Administer application servers

Set up business-level applications

Starting business-level applications using scripting

Deploy and administering business-level applications