+

Search Tips   |   Advanced Search

Asset settings


To specify options for the registration of an asset with the asset repository. Default values for the options are used if we do not specify a value.

To view this admin console page, click Applications > Application Types > Assets > asset_name . This page is similar to the Select options for importing an asset panel on the asset import and update wizards.

Asset name

Logical name for the asset. An asset name must be unique within a cell and cannot contain an unsupported character.

An asset name cannot begin with a period (.), cannot contain leading or trailing spaces, and cannot contain any of the following characters:


Table 1. Characters that we cannot use in a name

Unsupported characters
/  forward slash $   dollar sign '  single quote mark
\  backslash =   equal sign " double quote mark
* asterisk % percent sign |   vertical bar
,  comma +   plus sign <  left angle bracket
:  colon @ at sign >  right angle bracket
;  semi-colon #   hash mark & ampersand (and sign)
? question mark ]]> No specific name exists for this character combination

This Asset name field is the same as the Name setting on an Assets page.

Data type String

Asset description

Description for the asset.

Asset binaries destination URL

Directory to which WAS imports the asset file.

Data type String
Units Full path name

Asset type aspects

Type of asset content. Examples of asset type include Java™ archive (JAR) files, shared libraries, and EAR files.

The asset type suggests the content of the asset. For example, an asset packaged as a JAR file might contain a Web module, portlet and Web service.

This setting is read-only. We cannot edit this setting.

Data type String
Units File type
Default none

File permissions

Specifies access permissions for asset binaries that WAS ND expands to the asset binaries destination URL.

We can specify file permissions in the text field. We can also set some of the commonly used file permissions by selecting them from the list. List selections overwrite file permissions set in the text field.

We can set one or more of the following file permission strings in the list. Selecting multiple options combines the file permission strings.


Table 2. File permission string sets for list options

Multiple-selection list option File permission string set
Allow all files to be read but not written to .*=755
Allow executables to execute .*\.dll=755#.*\.so=755#.*\.a=755#.*\.sl=755
Allow HTML and image files to be read by everyone .*\.htm=755#.*\.html=755#.*\.gif=755#.*\.jpg=755

Instead of using the multiple-selection list to specify file permissions, we can specify a file permission string in the text field. File permissions use a string that has the following format: 

file_name_pattern=permission#file_name_pattern=permission

where file_name_pattern is a regular expression file name filter (for example, .*\\.jsp for all JSPs), permission provides the file access control lists (ACLs), and # is the separator between multiple entries of file_name_pattern and permission. If # is a character in a file_name_pattern string, use \# instead.

If multiple file name patterns and file permissions in the string match a uniform resource identifier (URI) within the asset, then WAS uses the most stringent applicable file permission for the file. For example, if the file permission string is .*\\.jsp=775#a.*\\.jsp=754, then the abc.jsp file has file permission 754.

Tip: Using regular expressions for file matching pattern compares an entire string URI against the specified file permission pattern. You must provide more precise matching patterns using regular expressions as defined by Java programming API. For example, suppose WAS processes the following directory and file URIs during a file permission operation:


Table 3. Example URIs for file permission operations

1 /opt/WebSphere/profiles/AppSrv01/installedApps/MyCell/MyApp.ear/MyWarModule.war
2 /opt/WebSphere/profiles/AppSrv01/installedApps/MyCell/MyApp.ear/MyWarModule.war/MyJsp.jsp
3 /opt/WebSphere/profiles/AppSrv01/installedApps/MyCell/MyApp.ear/MyWarModule.war/META-INF/MANIFEST.MF
4 /opt/WebSphere/profiles/AppSrv01/installedApps/MyCell/MyApp.ear/MyWarModule.war/WEB-INF/classes/MyClass.class
5 /opt/WebSphere/profiles/AppSrv01/installedApps/MyCell/MyApp.ear/MyWarModule.war/mydir/MyClass2.class
6 /opt/WebSphere/profiles/AppSrv01/installedApps/MyCell/MyApp.ear/MyWarModule.war/META-INF

The file pattern matching results are:

  • MyWarModule.war does not match any of the URIs

  • .*MyWarModule.war.* matches all URIs

  • .*MyWarModule.war$ matches only URI 1

  • .*\\.jsp=755 matches only URI 2

  • .*META-INF.* matches URIs 3 and 6

  • .*MyWarModule.war/.*/.*\.class matches URIs 4 and 5

If we specify a directory name pattern for File permissions, then the directory permission is set based on the value specified. Otherwise, the File permissions value set on the directory is the same as its parent. For example, suppose we have the following file and directory structure: 

/opt/WebSphere/profiles/AppSrv01/installedApps/MyCell/MyApp.ear/MyWarModule.war/MyJsp.jsp
and specify the following file pattern string: 

.*MyApp.ear$=755#.*\.jsp=644
The file pattern matching results are:

  • Directory MyApp.ear is set to 755

  • Directory MyWarModule.war is set to 755

  • Directory MyWarModule.war is set to 755

Regardless of the operation system, always use a forward slash (/) as a file path separator in file patterns.

(Windows) We cannot unset read permission on a file on Windows operating systems. With POSIX style permission bits, the bit for denoting readable on a file is 4, writable is 2, and executable is 1. Thus, permission of a file on a Windows operating system is either 5 or 7. Also, in POSIX style there are user, group and world permissions. We can only set the user permission for a file on Windows operating systems. The group and world permission bits are ignored.

Access permissions specified here are at the asset level. We can also specify access permissions for asset binaries in the node-level configuration. The node-level file permissions specify the maximum (most lenient) permissions that can be given to asset binaries. Access permissions specified here at asset level can only be the same as or more restrictive than those specified at the node level.

Data type String

Current asset relationships

Assets to which this asset is related.

To add or remove a relationship, use the Manage relationships panel:

  1. Click Manage Relationships to access the Manage relationships panel. The Selected list on the right lists the current asset relationships.

  2. To add a relationship, select an asset in the Available list on the left and click >>.

  3. To remove a relationship, select an asset in the Selected list on the right and click <<.

  4. Click OK.

Data type String
Default none

Validate asset

Whether WAS examines the asset references specified during asset importing or updating and, if validation is enabled, warns you of incorrect references or fails the operation.

An asset typically refers to resources using data sources for container-managed persistence (CMP) beans or using resource references or resource environment references defined in deployment descriptors. The validation checks whether the resource referred to by the asset is defined in the scope of the deployment target of that asset.

Select true (enable the check box) for resource validation and to stop operations that fail as a result of incorrect resource references. Select false (empty check box) for no resource validation.

Data type String
Default false (empty check box)




Related concepts


Business-level applications

 

Related tasks


Importing assets

 

Related


Asset collection
Upload asset settings

 

Related information


Administrative console buttons