This is a short tutorial about adding new applications (palette entries) to the Designer palette. After an application is added to the palette it becomes quite easy to create a driver for that application. All you need to do is drag the application icon from the palette and drop it in the modeler. Designer then detects which entry has been dropped in the modeler and displays the driver creation wizard with the appropriate base package already selected.

Please see below for the details or the attached pdf file.

How does it work?

The palette consists of multiple Palette Groups each with a set of Palette Entries. Each Palette Entry has an icon, a label, and a tool-tip. There is more internal information associated with a Palette Entry which is may not be directly visible to the user, such as: palette ID, the shim-module name, label and icon to be displayed over the driver connector line, and a few other things.

In order to create a new Palette Entry you’ll need to create a few XML, properties, and icon files under specific directories in Designer. The rest of this tutorial talks about the structure and location of the required files.

The files mentioned below are required to add a new palette entry in designer. You have to decide the palette group that the palette entry belongs to and depending on that create these files in the appropriate directory under the “Applications” directory. The names of the sub-directories under “Application” correspond to the palette groups. The eDirectory palette entry is used here as an example to explain the structure of the files.

The application xml file

This file defines the labels and icons to use for the application in the palette


The Application properties file

The name of this file should match that of the application xml file


Name = eDirectory
Tip = Novell eDirectory

The Application Icons

The medium sized icon that is displayed in the modeler


The small sized icon that is displayed in the palette


The Driver files

The Driver XML file

This file defines the palette ID and the shim module name. It also defines the icons and tool-tip to use
for the driver connector line.


The Driver properties file

The name of this file should match that of the Driver xml file

Name = eDir Driver
Tip = eDirectory Driver

The Driver iManager icon

The name of this file should match that of the driver xml file.


Base templates for the icons

Application regular icon:

Application small icon:

Driver iManager icon:

1 vote, average: 5.00 out of 51 vote, average: 5.00 out of 51 vote, average: 5.00 out of 51 vote, average: 5.00 out of 51 vote, average: 5.00 out of 5 (1 votes, average: 5.00 out of 5)
You need to be a registered member to rate this post.

Disclaimer: As with everything else at NetIQ Cool Solutions, this content is definitely not supported by NetIQ, so Customer Support will not be able to help you if it has any adverse effect on your environment.  It just worked for at least one person, and perhaps it will be useful for you too.  Be sure to test in a non-production environment.

Leave a Reply

No Comments
By: tvivek
Apr 30, 2012
3:00 pm
Active Directory Authentication Automation Cloud Computing Cloud Security Configuration Customizing Data Breach DirXML Drivers End User Management Identity Manager Importing-Exporting / ICE/ LDIF Intelligent Workload Management IT Security Knowledge Depot LDAP Monitoring Open Enterprise Server Passwords Reporting Secure Access Supported Troubleshooting Workflow