The RAS asset is a zipped file that stores the files that make up the asset. Every asset must contain at least one manifest file. The manifest file organizes and maintains the data needed to restore the RAS asset structure and files in the RAS asset consumer's workspace. It also provides documentation for the RAS asset consumer. It is the file that is searched for matching search keys when a consumer searches a repository for assets. All RAS asset manifest files must be named with a .rmd (RAS manifest document) extension.
When a manifest file is created at export it will always use the default profile. You must use an existing manifest file to get a custom profile type. We recommend that you use the New RAS Manifest wizard to create your custom manifest files.
Four types of RAS profiles are supported: Default, Default Web Service, Default Component, and Pattern. You select the appropriate RAS profile when the asset is packaged. If using a profile other than Default or Pattern, you must create it using the Manifest wizard. The Default Web Service profile and Default Component profile are extensions of the Default profile; they have the same basic structure, plus additional custom sections. The Pattern profile is a special type that is automatically assigned and cannot be selected by the user.
During the RAS asset export process, you can include essential information about the RAS asset in the manifest file. This information assists the RAS asset consumer in selecting and using the asset. Provide the following:
In addition to the manifest's required and optional information, you can incorporate many types of documentation in the RAS asset, such as diagrams that illustrate its structure and sample screen captures.
You can create a template manifest file and reuse it instead of creating a new one each time you perform a RAS export. Thus, you can establish standard values, establish information formats, and eliminate redundant input. Ensure that your template manifest file supports the profile you need for the type of asset you are creating.
Rational® design pattern authors use the RAS export utility as part of the process to create design pattern assets. When the pattern design is complete and the pattern has been tested, the pattern author exports the pattern as a deployable asset. A pattern plug-in is created and stored as a RAS asset on the file system or in a repository as determined by the pattern author.
Pattern assets are unique. Unlike other assets, they always have more than one manifest file. The pattern structure consists of a pattern library and one or more patterns. A manifest file is generated for the library and for each pattern. Patterns have their own pattern profile and pattern repository. Although patterns can be stored as RAS assets in any repository, the pattern repository consists only of pattern plug-ins that are installed and ready for use.
Pattern assets that are exported as nondeployable assets are assigned a default profile manifest for packaging the pattern project in the same way as other projects are exported.
Parent topic: RAS assets
Related tasks
Creating customized manifest files
Previewing RAS asset manifest files
Editing manifest files
Selecting manifest files