You must register application business logic such as Java Platform,
Enterprise Edition (Java EE) archives, libraries, and other resource files
with the product configuration as assets before you can add the assets to
one or more business-level applications. Importing an asset registers it with
the product configuration.
Before you begin
This topic assumes that you have one or more application binary files
that you want to add to a business-level application. You must register those
binary files as assets before you can add them to the business-level application.
About this task
Before a business-level application that uses an asset can be started
on the target run time, the asset binaries must be extracted to a deployer-defined
location on the file system that is local to the target run time. Importing
an asset extracts binaries to a location that is local to the target run time.
The
application server run time that reads the asset binaries either at application
start time or while serving an incoming client request determines the extraction
format of the asset binaries. The extraction format might include unzipping
of Java archive (JAR) or compressed (zip) files.
This topic describes
how to import an asset using the administrative console. Alternatively, you
can use the wsadmin tool or programming.
Procedure
- Click in the
console navigation tree.
- On the Upload
asset page, specify the asset package to import.
- Specify the full path name of the asset.
- Click Next.
- On the Select
options for importing an asset panel, specify asset settings.
You typically can click Next and use the default
values.
- Optional: For Asset description,
specify a brief description of the asset.
- Optional: For Asset binaries destination
URL, specify the target location of the asset.
This
setting specifies the location to which the product extracts the asset. After
an asset is imported, the product looks for the asset in this location when
a running application uses the asset.
If you do not specify a value,
the product installs the asset to the default location, ${profile_root}/installedAssets/asset_name/BASE/.
- Optional: For Asset type aspects,
examine the asset content type and version specified by the product. You cannot
change this setting value.
The type aspect typically denotes
the type of application contents, such as a specification to which the application
is written. For example, an enterprise bean (EJB) that supports the EJB Version
2.0 specification has the aspects type=EJB,version=2.0.
If
the type aspect is none and if the asset is a JAR file, then
the product associates a javarchive type aspect with the
asset by default.
- For File permissions, specify any file
permissions that are set on asset binary files so the target run time can
read or run the asset. Importing the asset extracts its binary files on the
disk local to the target runtime environment.
Try importing
the asset using the default value. For detailed information on the File
permissions setting, refer to the Select options for importing an asset panel online
help.
- For Current asset relationships, add
assets that the asset you are importing needs to run or remove assets that
are not needed.
When the product imports a JAR asset, the product
detects asset relationships automatically by matching the dependencies defined
in the JAR manifest with the assets that are already imported into the administrative
domain.
- For Validate asset, specify whether the
product validates the asset.
The setting is deselected by default.
This false (no) value is appropriate
for most assets. Only select true (yes)
to validate an asset when needed.
The product does not save the value
specified for Validate asset. Thus, if you select to
validate the asset (yes) now and later update the asset,
when you update the asset you must enable this setting again for the product
to validate the updated files.
- Click Next.
- On the Summary page, click Finish.
Results
Several messages are displayed, indicating whether your asset is imported
successfully.
An asset can contain multiple deployable objects as defined
by the application contents of that asset. A deployable object is a
part of the asset that you can map to a deployment target such as an application
server or a cluster. If the
product imports the asset successfully, then appropriate deployable objects
are identified in the asset and are further used when a composition unit is
created from that asset.
If the asset importing is not successful, read
the messages and try importing the asset again. Correct the values noted in
the messages.
What to do next
If the product imports the asset successfully and displays the
list of assets on the Assets
page, then click Save.
Add a composition
unit to a business-level application using the asset that you imported. An
asset included in a business-level application is represented by a composition
unit.