Partial application configuration deployment

This function allows you to add configuration items defined in a jar file to an existing InfoSphere® MDM configuration application deployment.

You can use the partial deploy to add customized additional configuration items to a deployed configuration. Each JAR file for a partial deploy can only contain one module and its associated items and values. If you want to add multiple modules you must deploy them individually in separate files. This functionality supports adding items under the existing root node, for example, IBM, or adding a new root node, for example, CLIENT.

You can run this function either in scripted mode or through the console menu.

The JAR file must contain a folder named META-INF, which must contain the three following files:

dwl-config.xml
dwl-config.xsd

Manifest.MF

The Mainifest.MF file must contain the following information:
- Application-Version:XXXX
- Application-Name:XXXXXX

Here is an example of a Manifest.MF file:

Manifest-Version: 1.0
Created-By: 2.3 (IBM Corporation)
Application-Version: 8.0.0.0
Application-Name: WebSphere Customer Center
Ant-Version: Apache Ant 1.6.1

Here is an example of dwl-config.xml that adds the new configuration under a new node called CLIENT rather than under the existing IBM node:

<?xml version="1.0"?>
<!-- ***************************************************** {COPYRIGHT-TOP} ***
* Licensed Materials - Property of IBM
* 5724-N18
*
* (C) Copyright IBM Corp. 2006, 2008 All Rights Reserved.
*
* US Government Users Restricted Rights - Use, duplication, or
* disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
	********************************************************** {COPYRIGHT-END} -->
<!--Version 6.5.0-->
<CLIENT xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="dwl-config.xsd">
	<ELMDM>
		<IIS enableCleasing="true">
			<StandardizeAddress RejectOnFail="yes" PhoneticCodingType="yes"/>
			<StandardizePersonName RejectOnFail="yes" PhoneticCodingType="yes"/>
			<StandardizeOrganizationName RejectOnFail="yes" PhoneticCodingType="yes"/>			
		</IIS>
	</ELMDM>
</CLIENT>

Here is an example of a dwl-config.xsd:

<?xml version="1.0" encoding="UTF-8"?>
<!-- ***************************************************** {COPYRIGHT-TOP} ***
* Licensed Materials - Property of IBM
* 5724-N18
*
* (C) Copyright IBM Corp. 2006, 2008 All Rights Reserved.
*
* US Government Users Restricted Rights - Use, duplication, or
* disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
	********************************************************** {COPYRIGHT-END} -->
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
	<xsd:element name="CLIENT">
		<xsd:complexType>
			<xsd:all>
				<xsd:element name="ELMDM" minOccurs="0">
					<xsd:complexType>
						<xsd:all>
							<xsd:element name="IIS" minOccurs="0">
								<xsd:complexType>
									<xsd:all>
										<xsd:element name="StandardizeAddress" minOccurs="0">
											<xsd:complexType>
												<xsd:attribute name="RejectOnFail" type="xsd:string">
													<xsd:annotation>
														<xsd:appinfo>
															<dynamic value="true"/>
														</xsd:appinfo>
													</xsd:annotation>
												</xsd:attribute>
												<xsd:attribute name="PhoneticCodingType" type="xsd:string">
													<xsd:annotation>
														<xsd:appinfo>
															<dynamic value="false"/>
														</xsd:appinfo>
													</xsd:annotation>
												</xsd:attribute>
											</xsd:complexType>
										</xsd:element>
										<xsd:element name="StandardizePersonName" minOccurs="0">
											<xsd:complexType>
												<xsd:attribute name="RejectOnFail" type="xsd:string">
													<xsd:annotation>
														<xsd:appinfo>
															<dynamic value="false"/>
														</xsd:appinfo>
													</xsd:annotation>
												</xsd:attribute>
												<xsd:attribute name="PhoneticCodingType" type="xsd:string">
													<xsd:annotation>
														<xsd:appinfo>
															<dynamic value="false"/>
														</xsd:appinfo>
													</xsd:annotation>
												</xsd:attribute>
											</xsd:complexType>
										</xsd:element>
										<xsd:element name="StandardizeOrganizationName" minOccurs="0">
											<xsd:complexType>
												<xsd:attribute name="RejectOnFail" type="xsd:string">
													<xsd:annotation>
														<xsd:appinfo>
															<dynamic value="false"/>
														</xsd:appinfo>
													</xsd:annotation>
												</xsd:attribute>
												<xsd:attribute name="PhoneticCodingType" type="xsd:string">
													<xsd:annotation>
														<xsd:appinfo>
															<dynamic value="false"/>
														</xsd:appinfo>
													</xsd:annotation>
												</xsd:attribute>
											</xsd:complexType>
										</xsd:element>
									</xsd:all>
									<xsd:attribute name="enableCleasing" type="xsd:boolean">
										<xsd:annotation>
											<xsd:appinfo>
												<dynamic value="false"/>
											</xsd:appinfo>
										</xsd:annotation>
									</xsd:attribute>								
								</xsd:complexType>
							</xsd:element>
						</xsd:all>
					</xsd:complexType>
				</xsd:element>
			</xsd:all>
		</xsd:complexType>
	</xsd:element>
</xsd:schema>

A partial application configuration deployment does not refresh the InfoSphere MDM automatically, so you must restart the application to pick up the new deployed partial application configuration.