Blog Entry

(View Disclaimer)

In a recent Identity Management project I found myself reading information from an HR system via JDBC, then needing to write it into the Identity Vault. From there it would disperse to other systems, one of which was GroupWise.

The HR system stored all information in a capitalised fashion. It's quite obviously undesirable for all entries in a GroupWise address book to be capitalised, so I needed to transform the data.

I wrote two ECMAScript functions to handle this.

The two scripts were added to the Driver Set Library and added to the JDBC Driver's configuration.

In an input transformation policy, the following rules were added. Only two example rules have been added here for the sake of brevity. Obviously if you use them you would need to adjust the class and attribute names.

	<rule>
		<description>Capitalise SURNAME correctly</description>
		<conditions>
			<and>
				<if-class-name mode="nocase" op="equal">IDM_EMPLIST</if-class-name>
				<if-op-attr name="SURNAME" op="available"/>
			</and>
		</conditions>
		<actions>
			<do-reformat-op-attr name="SURNAME">
				<arg-value>
					<token-xpath expression="es:nameCapitalise($current-value)"/>
				</arg-value>
			</do-reformat-op-attr>
		</actions>
	</rule>
	<rule>
		<description>Capitalise POS_TITLE correctly</description>
		<conditions>
			<and>
				<if-class-name mode="nocase" op="equal">IDM_EMPLIST</if-class-name>
				<if-op-attr name="POS_TITLE" op="available"/>
			</and>
		</conditions>
		<actions>
			<do-reformat-op-attr name="POS_TITLE">
				<arg-value>
					<token-xpath expression="es:toTitleCase($current-value)"/>
				</arg-value>
			</do-reformat-op-attr>
		</actions>
	</rule>

I hope that the scripts (being in the wiki) will be contributed to over time to make them more robust and to cater for more situations.

Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).

It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.