An asset can represent a server, a portlet, a URL, or a resource in the back-end system, such as a database table.
Table 3-5 describes the permissions you must have to manage assets.
Action |
Permissions required |
|---|---|
Create an asset |
WRITE on the asset controlling asset. |
List the assets in a domain |
LIST on the asset controlling asset. |
View the properties of an asset |
READ on the asset controlling asset. |
Update the properties of an asset |
UPDATE on the asset controlling asset. |
Move an asset to a different organization |
If the new organization is in the same domain, you need READ, DELETE, and WRITE on the asset controlling asset. If the organization is in a different domain, you need READ and DELETE on the asset controlling asset in the current domain, and WRITE on the asset controlling asset in the new domain. |
Delete an asset |
READ and DELETE on the asset controlling asset. |
Creating an asset
Use unique names when you create assets. Do not use the name of an existing root object for a new asset; for example, do not create an asset named “User”.
In the Organization Manager tree view, select the organization, and highlight Assets.
Click New. The Create New Asset dialog box displays.
Enter the asset name, and optionally, enter a description. If the asset is a URL, select URL as the Asset Type.
Click OK. The name of the new asset displays in the right pane.
