WebSphere Application Server V8.5 Administration and Configuration Guide for the Full Profile

912 WebSphere Application Server V8.5 Administration and Configuration Guide for the Full Profile

3. Select the project to export (Figure 25-13), and click Finish.

Figure 25-13 Exporting project

Now, you can deploy the RAD8AtomFeeds.jar SCA archive file.

25.4 Deploying an SCA application

A typical SCA solution consists of a combination of web, EJB, and SCA applications. The web

and EJB modules are deployed as enterprise applications, and the SCA composites are

deployed as assets in a business-level application.

This section describes how to deploy an SCA composite as an asset in a business-level

application.

25.4.1 Importing the SCA archive file as an asset

The first step in deploying the application is to import the SCA archive file into the application

server environment as an asset.

Chapter 25. Working with SCA applications 913

Complete the following steps to import an asset:

1. Click Applications  Application Types  Assets. In the Assets window, shown in

Figure 25-14, click Import.

Figure 25-14 Import an asset

2. Select the SCA archive file, as shown in Figure 25-15 and then click Next.

Figure 25-15 Identify the jar file location

914 WebSphere Application Server V8.5 Administration and Configuration Guide for the Full Profile

3. Provide the required options. In this example, take the default values, as shown in

Figure 25-16.

Figure 25-16 Options for importing an asset

The following lists explains the fields of note from Figure 25-16:

– Asset binaries destination URL: When the asset is imported, the binaries are extracted

by default to profile_root/installedAssets/asset_name/BASE. You can change this

location by specifying a new one here.

– File permissions: The default setting for the file permissions to be assigned to the

extracted asset binaries is the

Allow executables to execute setting. You can select

another option or provide a customized setting.

– Asset relationships: Click the Manage Relationships button to specify assets to which

this asset is related.

– Validate asset: Selecting this option enables validation of the references specified in

the asset when it is imported. The asset is examined to ensure that references are

defined in the scope of the deployment target of the asset. Some examples of these

references are data sources or references contained in deployment descriptors (such

as resource and resource environment references).

Click Next.

Chapter 25. Working with SCA applications 915

4. In the Summary page, click Finish to import the file and save the modification to the

master configuration. The new SCA archive file is now listed as an asset, as shown in

Figure 25-17.

Figure 25-17 Asset imported

25.4.2 Creating a new business-level application

To create a new business-level application:

1. Click Applications  Application Types  Business-level applications. In the

Business-level applications window, shown in Figure 25-18, click New.

Figure 25-18 Business-level application window

916 WebSphere Application Server V8.5 Administration and Configuration Guide for the Full Profile

2. Enter a new name for the business-level application, as shown in Figure 25-19. Click

Apply. Save the change to the master configuration.

Figure 25-19 Create a new business-level application

25.4.3 Adding the new asset to the business-level application

Add the new asset, as a composition unit, to the RAD8AtomFeed business-level application

by completing the following steps:

1. Click Applications  Application Types  Business-level applications and then click

RAD8AtomFeeds, as shown in Figure 25-20.

Figure 25-20 Click the business-level application

2. In the Deploy assets section, click Add  Add Asset, as shown in Figure 25-21.

Figure 25-21 Add asset