Import assets

 

+

Search Tips   |   Advanced Search

 

1. Go to...

   Applications > New Application > New Asset

2. On the Upload asset page, specify the asset package to import.

3. Specify the full path name of the asset.

4. Click Next.

5. On the Select options for importing an asset panel, specify asset settings.

   You typically can click Next and use the default values.

   1. For Asset description, specify a brief description of the asset.

   2. For Asset binaries destination URL, specify the target location of the asset.

      This setting specifies the location to which WAS extracts the asset. After an asset is imported, WAS looks for the asset in this location when a running application uses the asset.

      If we do not specify a value, WAS installs the asset to the default location...

      ${$WP_PROFILE}/installedAssets/asset_name/BASE/

   3. For Asset type aspects, examine the asset content type and version specified by WAS ND. We cannot change this setting value.

      The type aspect typically denotes the type of application contents, such as a spec to which the application is written. For example, an EJB that supports the EJB V2.0 spec has the aspects type=EJB,version=2.0.

      If the type aspect is none and if the asset is a JAR file, then WAS associates a javarchive type aspect with the asset by default.

   4. 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.

   5. For Current asset relationships, add assets that the asset we are importing needs to run or remove assets that are not needed.

      When WAS imports a JAR asset, WAS ND detects asset relationships automatically by matching the dependencies defined in the JAR manifest with the assets that are already imported into the admin domain.

   6. For Validate asset, specify whether WAS ND 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.

      WAS ND v7.0 does not save the value specified for Validate asset. Thus, if we select to validate the asset (yes) now and later update the asset, when you update the asset enable this setting again for WAS ND to validate the updated files.

   7. Click Next.

6. On the Summary page, click Finish.

 

Results

Several messages are displayed, indicating whether the 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 we can map to a deployment target such as an appserver or a cluster. If WAS ND 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.

 

Next steps

If WAS 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.

Upload asset settings
Asset settings

 

Related concepts

Assets

 

Related tasks

Create business-level applications
Deploy business-level applications
Importing an asset using programming

 

Related

Asset collection