Network Deployment (Distributed operating systems), v8.0 > Reference > Sets
Upload asset settings
Use this page to specify the asset to register with the asset repository. We can add registered assets to a business-level application. From the console...
Applications > New application > New Asset.
Import an asset registers the asset with the asset repository.
The product manages the contents of a registered asset as a single entity. The contents of a registered asset must be accessible to application servers, web servers and other runtime environments that use the asset.
During asset importing, asset files typically are uploaded from a client workstation running the browser to the server running the admin console, where they are registered. In such cases, use the web browser running the admin console to select files to upload to the server.
Path to the asset
Fully qualified path to the asset.
Specify one of the following supported assets:
- A single file, such as an enterprise bean (EJB) file
- An archive of files, such as a JAR or a compressed .zip file
- An archive of archives, such as an EAR or shared library file
Use Local file system if the browser and asset files are on the same machine (whether or not the server is on that machine, too).
Use Remote file system if the asset file resides on any node in the current cell context. Only supported assets are shown during the browsing. Also use Remote file system to specify an asset file that is already residing on the machine running the application server. For example, the field value might be PROFILE_ROOT/installableApps/my_bean.ejb. After the asset file is transferred, the Remote file system value shows the path of the temporary location on the server.
Business-level applications
Import assets
Related
Asset collection
Asset settings