Creating Your First Custom Rule - Novell ADMINSTUDIO 9.5 User Manual

Table 9-10 • Example of Fingerprint and Action in Sample Custom Rule
Item
Action

Creating Your First Custom Rule

To create a custom rule for use in virtual package testing and conversion using Windows Installer Converter,
perform the following steps. These instructions assume that you are familiar with some of the basic concepts of
XML.
To ensure that as new versions of
is recommended that you add your custom rules to your own XML file and not to the
You should create one XML file for each application or a common set of applications.
Tip • The rule XML definition has a schema file. If you use an editor that is schema-aware, it can significantly
improve the ease with which rule files are created.
Task: To create a custom rule:
1. Create an XML file in the
MyRules.xml
<?xml version="1.0" encoding="utf-8"?>
<AdminStudioRules xmlns="http://adminstudio.com/AdminStudio.Rules.xsd"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://adminstudio.com/AdminStudio.Rules.xsd AdminStudio.Rules.xsd">
</AdminStudioRules>
2. Add a
rule. If you wanted to define multiple rules, you would simply create multiple
<Rule title="My Rule Title" description="My Rule Description" author="Author" provider="Any">
</Rule>
3. Add a
rule. First add an empty Fingerprint. When a Fingerprint is empty it will always be satisfied and thus the rule
will always be applied to every package you build.
<Fingerprint name="Always Satisfied" description="">
</Fingerprint>
4. Add an
satisfied.
<Action description="My First Action">
<Message id="12000" text="I will automate my knowledge" severity="Warning"/>
AdminStudio 9.5 User Guide
Description
If the Fingerprint condition is met, an Action named
implemented, which excludes the Registry key of
Distiller\AdobePDFSettings\*
AdminStudio.Default.xml
C:\Program Files\AdminStudio\9.5\Repackager\System\Rules
and define the following root element:
element as a child element of
Rule
element as a child element to the rule. A
Fingerprint
element as a child element to the rule. An Action is what happens when the rule Fingerprint is
Action
ADS-0950-UG00
Chapter 9: Converting Windows Installer Packages to Virtual Applications
Testing Windows Installer Packages for Virtualization Compatibility
in the
HKEY_CURRENT_USER
are released, your custom rules are not overwritten, it
AdminStudioRules
Exclude AdobePDFSettings
Software\Adobe\Acrobat
Registry hive for that application.
AdminStudio.Default.xml
. This element is the basic definition for your first
elements.
Rule
is the condition associated with the
Fingerprint
will be
file.
folder called
673