Netcool/Impact XML DSA Guide 3.0 and Later - e IBM Tivoli ...

frontmatter.fm May 3, 2005
Netcool®/ImpactTM 3.0 and Later
Supporting Products
XML DSA Guide

© 2005 Micromuse Inc., Micromuse Ltd.
All rights reserved. No part of this work may be reproduced in any form or by any
person without prior written permission of the copyright owner. This document is
proprietary and confidential to Micromuse, and is subject to a confidentiality
agreement, as well as applicable common and statutory law.
Micromuse Disclaimer of Warranty and Statement of Limited Liability
Micromuse provides this document "as is", without warranty of any kind, either
express or implied, including, but not limited to, the implied warranties of
merchantability, fitness for a particular purpose or non-infringement. This
document may contain technical inaccuracies or typographical errors. Micromuse
may make improvements and changes to the programs described in this document
or this document at any time without notice. Micromuse assumes no responsibility
for the use of the programs or this document except as expressly set forth in the
applicable Micromuse agreement(s) and subject to terms and conditions set forth
therein. Micromuse does not warrant that the functions contained in the programs
will meet your requirements, or that the operation of the programs will be
uninterrupted or error-free. Micromuse shall not be liable for any indirect,
consequential or incidental damages arising out of the use or the ability to use the
programs or this document.
Micromuse specifically disclaims any express or implied warranty of fitness for high
risk activities.
Micromuse programs and this document are not certified for fault tolerance, and
are not designed, manufactured or intended for use or resale as on-line control
equipment in hazardous environments requiring fail-safe performance, such as in
the operation of nuclear facilities, aircraft navigation or communication systems,
air traffic control, direct life support machines, or weapons systems ("High Risk
Activities") in which the failure of programs could lead directly to death, personal
injury, or severe physical or environmental damage.
Compliance with Applicable Laws; Export Control Laws
Use of Micromuse programs and documents is governed by all applicable federal,
state and local laws. All information therein is subject to U.S. export control laws
and may also be subject to the laws of the country where you reside.
All Micromuse programs and documents are commercial in nature. Use,
duplication or disclosure by the United States Government is subject to the
restrictions set forth in DFARS 252.227-7015 and FAR 52.227-19.
Trademarks and Acknowledgements
Micromuse and Netcool are registered trademarks of Micromuse.
Other Micromuse trademarks include but are not limited to: Netcool/OMNIbus,
Netcool/OMNIbus for Voice Networks, Netcool/Reporter, Netcool/Internet
Service Monitors, Netcool/ISM, Netcool/ISM Global Perspective, Netcool/NT
Service Monitors, Netcool/Wireless Service Monitors, Netcool/WSM,
Netcool/Usage Service Monitors, Netcool/USM, Netcool/Telco Service
Monitors, Netcool/TSM, Netcool/Fusion, Netcool/Data Center Monitors,
Netcool DCM, Netcool/Impact, Netcool/Visionary, Netcool/Precision, Netcool
Probes & Monitors, Netcool Desktops, Netcool Gateways, Netcool Impact/Data
Source Adaptors, Netcool EventList, Netcool Map, Netcool Virtual Operator,
Netcool/Precision for IP Networks, Netcool/Precision for Transmission
Networks, Netcool/Firewall, Netcool/Wave, Netcool/Webtop, Netcool TopoViz,
Netcool/SM Operations, Netcool/SM Configuration, Netcool/OpCenter,
Netcool/System Service Monitors, Netcool/SSM, Netcool/Application Service
Monitors, Netcool/ASM, Netcool/ISM WAM, Netcool/SM Reporter, Netcool
for Asset Management, Netcool/Realtime Active Dashboards,
Netcool/Dashboards, Netcool/RAD, Netcool for Voice over IP, Netcool for
Security Management, Netcool Security Manager, Netcool/Portal 2.0 Premium
Edition, Netcool ObjectServer, Netcool/RAD, Netcool/Software Developers Kit,
Micromuse Alliance Program, Micromuse Channel Partner, Authorized Netcool
Reseller, Netcool Ready, Netcool Solutions, Netcool Certified, Netcool Certified
Consultant, Netcool Certified Trainer, Netcool CCAI Methodology, Micromuse
University, Microcorrelation, Acronym, Micromuse Design, Integration Module
for Netcool, The Netcool Company, VISIONETCOOL, and Network Slice.
Micromuse acknowledges the use of I/O Concepts Inc. X-Direct 3270 terminal
emulators and hardware components and documentation in Netcool/Fusion.
X-Direct ©1989-1999 I/O Concepts Inc. X-Direct and Win-Direct are
trademarks of I/O Concepts Inc.
Netcool/Fusion contains IBM Runtime Environment for AIX®, Java
Technology Edition Runtime Modules © Copyright IBM Corporation 1999. All
rights reserved.
Netcool/Precision IP includes software developed by the University of California,
Berkeley and its contributors.
Micromuse acknowledges the use of MySQL in Netcool/Precision for IP
Networks. Copyright © 1995, 1996 TcX AB & Monty Program KB & Detron
HB Stockholm SWEDEN, Helsingfors FINLAND and Uppsala SWEDEN. All
rights reserved.
Micromuse acknowledges the use of the UCD SNMP Library Netcool/ISM.
Copyright © 1989, 1991, 1992 by Carnegie Mellon University. Derivative Work
- Copyright © 1996, 1998, 1999, 2000 The Regents of the University of
California. All rights reserved.
Portions of the Netcool/ISM code are copyright ©2001, Cambridge Broadband
Ltd. All rights reserved.
Portions of the Netcool/ISM code are copyright © 2001, Networks Associates
Technology, Inc. All rights reserved.
Micromuse acknowledges the use of Viador Inc. software and documentation for
Netcool/Reporter. Viador © 1997-1999 is a trademark of Viador Inc.
Micromuse acknowledges the use of software developed by the Apache Group for
use in the Apache HTTP server project. Copyright © 1995-1999 The Apache
Group. Apache Server is a trademark of the Apache Software Foundation
(http://www.apache.org/). All rights reserved.
Micromuse acknowledges the use of software developed by Edge Technologies,
Inc. 2003 Edge Technologies, Inc. and Edge enPortal are trademarks or registered
trademarks of Edge Technologies Inc. All rights reserved.
Micromuse acknowledges the use of Merant drivers. Copyright © MERANT
Solutions Inc., 1991-1998.
The following product names are trademarks of Tivoli Systems or IBM
Corporation: AIX, IBM, OS/2, RISC System/6000, Tivoli Management
Environment, and TME10.
IBM, NetView/6000, Domino, Lotus, Lotus Notes, and WebSphere are either
trademarks or registered trademarks of IBM Corporation. VTAM is a trademark
of IBM Corporation.
Omegamon is a trademark of Candle Corporation.
Netspy is a trademark of Computer Associates International Inc.
The Sun logo, Sun Microsystems, SunOS, Solaris, SunNet Manager, Java are
trademarks of Sun Microsystems Inc.
SPARC is a registered trademark of SPARC International Inc. Programs bearing
the SPARC trademark are based on an architecture developed by Sun
Microsystems Inc. SPARCstation is a trademark of SPARC International Inc.,
licensed exclusively to Sun Microsystems Inc.
UNIX is a registered trademark of the X/Open Company Ltd.
Sybase is a registered trademark of Sybase Inc. Adaptive Server is a trademark of
Sybase Inc.
Action Request System and Remedy are registered trademarks of Remedy
Corporation.
Peregrine System and ServiceCenter are registered trademarks of Peregrine Systems
Inc.
HP, HP-UX and OpenView are trademarks of Hewlett-Packard Company.
InstallShield is a registered trademark of InstallShield Software Corporation.

Microsoft, Windows 95/98/Me/NT/2000/XP are either registered trademarks or
trademarks of Microsoft Corporation.
Microsoft Internet Information Server/Services (IIS), Microsoft Exchange Server,
Microsoft SQL Server, Microsoft perfmon and Microsoft Cluster Service are
registered trademarks of Microsoft Corporation.
BEA and WebLogic are registered trademarks of BEA Systems Inc.
FireWall-1 is a registered trademark of Check Point Software Technologies Ltd.
Netscape and Netscape Navigator are registered trademarks of Netscape
Communications Corporation in the United States and other countries.
Netscape's logos and Netscape product and service names are also trademarks of
Netscape Communications Corporation, which may be registered in other
countries.
Micromuse acknowledges the use of Xpm tool kit components.
SentinelLM is a trademark of Rainbow Technologies Inc.
GLOBEtrotter and FLEXlm are registered trademarks of Globetrotter Software
Inc.
Red Hat, the Red Hat "Shadow Man" logo, RPM, Maximum RPM, the RPM
logo, Linux Library, PowerTools, Linux Undercover, RHmember, RHmember
More, Rough Cuts, Rawhide and all Red Hat-based trademarks and logos are
trademarks or registered trademarks of Red Hat Inc. in the United States and other
countries.
Linux is a registered trademark of Linus Torvalds.
Nokia is a registered trademark of Nokia Corporation.
WAP Forum and all trademarks, service marks and logos based on these
designations (Trademarks) are marks of Wireless Application Protocol Forum Ltd.
Micromuse acknowledges the use of InstallAnywhere software in Netcool/WAP
Service Monitors. Copyright © Zero G Software Inc.
Orbix is a registered trademark of IONA Technologies PLC. Orbix 2000 is a
trademark of IONA Technologies PLC.
Micromuse acknowledges the use of Graph Layout Toolkit in Netcool/ Precision
for IP Networks. Copyright © 1992 - 2001, Tom Sawyer Software, Berkeley,
California. All rights reserved.
Portions of Netcool/Precision for IP Networks are © TIBCO Software, Inc.
1994-2003. All rights reserved. TIB and TIB/Rendezvous are trademarks of
TIBCO Software, Inc.
Portions of Netcool/Precision for IP Networks are Copyright © 1996-2003,
Daniel Stenberg, .
Micromuse acknowledges the use of Digital X11 in Netcool/Precision for IP
Networks. Copyright 1987, 1988 by Digital Equipment Corporation, Maynard,
Massachusetts, All Rights Reserved. DIGITAL DISCLAIMS ALL
WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN
NO EVENT SHALL DIGITAL BE LIABLE FOR ANY SPECIAL, INDIRECT
OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER
RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN
AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS
ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
PERFORMANCE OF THIS SOFTWARE.
Netcool/SM Operations, Netcool/SM Configuration and Netcool/OpCenter
include software developed by the OpenSSL Project for use in the OpenSSL
Toolkit (http://www.openssl.org/).
Micromuse acknowledges the use of software developed by ObjectPlanet. ©2003
ObjectPlanet, Inc, Ovre Slottsgate, 0157 Oslo, Norway.
Micromuse acknowledges the use of Expat in Netcool/ASM. Copyright 1998,
1999, 2000 Thai Open Source Software Center Ltd and Clark Cooper. Copyright
2001, 2002 Expat maintainers. THE EXPAT SOFTWARE IS PROVIDED
HEREUNDER "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
COPYRIGHT HOLDERS OF THE EXPAT SOFTWARE BE LIABLE FOR
ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN
ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE EXPAT SOFTWARE OR
THE USE OR OTHER DEALINGS IN THE SOFTWARE. Expat explicitly
grants its permission to any person obtaining a copy of any Expat software and
associated documentation files (the "Expat Software") to deal in the Expat
Software without restriction, including without limitation the rights to use, copy,
modify, merge, publish, distribute, sublicense, and/or sell copies of the Expat
Software. Expat's permission is subject to the following conditions: The above
copyright notice and this permission notice shall be included in all copies or
substantial portions of the Expat Software. Except as set forth hereunder, all
software provided by Micromuse hereunder is subject to the applicable license
agreement.
Micromuse acknowledges that Netcool Security Manager includes Hypersonic
SQL. Copyright (c) 2001-2002, The HSQL Development Group. All rights
reserved.
JABBER® is a registered trademark and its use is granted under a sublicense from
the Jabber Software Foundation.
Micromuse acknowledges the use of MySQL in Netcool/Precision for IP
Networks and in Netcool/Precision for Transmission Networks. Copyright ©
1995, 1996 TcX AB & Monty Program KB & Detron.
Micromuse acknowledges the use of Cryptix in Netcool/Precision IP. Copyright
(c) 1995-2004 The Cryptix Foundation Limited. All rights reserved.
Redistribution and use in source and binary forms, with or without modification,
are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the copyright notice, this list of
conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this
list of conditions and the following disclaimer in the documentation and/or other
materials provided with the distribution.
THIS SOFTWARE IS PROVIDED BY THE CRYPTIX FOUNDATION
LIMITED AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
CRYPTIX FOUNDATION LIMITED OR CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY,
OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED
TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
All other trademarks, registered trademarks and logos are the property of their
respective owners.
Micromuse Inc., 139 Townsend Street, San Francisco, USA CA 94107
www.micromuse.com
Document Version Number: 1.2

Contents
Netcool/Impact XML DSA Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
XML Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
XML DTD and XSD Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
XML Data Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Create Data Types Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
XML Configuration Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
XML Document and Data Type Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Setting Up the DSA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Installing the DSA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Contents
Installation Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Creating XML Data Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Running the Create Types Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Setting Up Data Type Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Setting Up Mappings for XML Files and Strings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Setting Up Mappings for XML Over HTTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Netcool/Impact 3.0 and Later XML DSA Guide i

Contents
ii
Reading XML Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Retrieving the Document Data Item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Retrieving the Root-Level Element Data Item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Retrieving Child Element Data Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Accessing Attribute Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Sample Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
XmlStringTestPolicy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
XmlFileTestPolicy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
XmlHttpTestPolicy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
XmlXsdFileTestPolicy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Contact Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Netcool/Impact 3.0 and Later XML DSA Guide

section.fm May 4, 2005
Netcool/Impact XML DSA Guide
This guide contains information on installing and using the Netcool/Impact XML DSA.
It contains the following sections:
• Introduction on page 2
Architecture on page 4
Concepts on page 5
XML Document and Data Type Mapping on page 7
Setting Up the DSA on page 9
Creating XML Data Types on page 11
Setting Up Data Type Mappings on page 13
Reading XML Documents on page 17
Sample Policies on page 21
Netcool/Impact 3.0 and Later XML DSA Guide 1

Netcool/Impact XML DSA Guide
Introduction
Overview
2
This section contains an introduction to the Netcool®/Impact XML DSA. It contains the following
topics:
Overview
System Requirements
Licensing
The XML DSA is an add-in component that allows Netcool/Impact to read XML data from strings, files,
and HTTP servers.
The DSA works by providing a mapping between an XML document and a set of Netcool/Impact data
types. The DSA uses the information in an XML DTD or XSD file to understand the structure of the XML
data and to map the data to the corresponding data types in Netcool/Impact.
To set up Netcool/Impact to read XML data, you run a script that creates the XML data types and then you
specify the associated mapping information in an XML configuration file. Once you have set up
Netcool/Impact, you can read the XML data in a policy using the GetByFilter and GetByLinks
functions.
System Requirements
Licensing
The XML DSA requires Netcool/Impact 3.0 or 3.1. Refer to the appropriate version of the Netcool/Impact
Administration Guide for a list of supported platforms.
The license file format and license feature codes have changed in Netcool/Impact 3.1 to provide support for
Quorum licensing.
For Netcool/Impact 3.0, the DSA for XML uses the nci_dsamediator_xml license feature
code.
For Netcool/Impact 3.1, the DSA for XML uses the cro_ncidsamediator_xml license feature
code.
Contact the Micromuse licensing team at
http://support.micromuse.com/helpdesk/licenses for more information on installing
licenses.
Netcool/Impact 3.0 and Later XML DSA Guide

Netcool/Impact 3.0 and Later XML DSA Guide
Introduction
To install licenses, follow the instructions for licensing Netcool/Impact components in the Netcool/Impact
Administration Guide.
3

Netcool/Impact XML DSA Guide
Architecture
4
The following figure shows the logical relationship between the Netcool/Impact server, the XML DSA, and
XML data sources.
Netcool/
Impact
Server
DSA
Figure 1: XML DSA Architecture
Internet or
Intranet
HTTP
Services
XML Files
XML Strings
Netcool/Impact 3.0 and Later XML DSA Guide

Concepts
This section contains information about concepts related to the DSA. It contains the following topics:
XML Documents
XML DTD Files
XML XSD Files
XML Data Types
XML Documents
Create Data Types Scripts
XML Configuration Files
Netcool/Impact 3.0 and Later XML DSA Guide
Concepts
The DSA considers an XML document to be any well-formed set of XML data that descends from a single
root element. This document can be located in a string, in a text file, or on an HTTP server.
XML DTD and XSD Files
XML DTD and XSD files contain a document type description. You must provide an XML DTD or XSD
file for each type of XML document that you want the DSA to read.
XML Data Types
XML data types are Netcool/Impact data types that represent XML documents and their contents. The DSA
uses the following XML data types:
Super data types
Element data types
Super Data Types
Super data types are data types that represent types of XML documents. The DSA uses one such data type
for each type of document that it reads.
A super data type contains a single data item, called the document data item. This data item represents the
instance of the document that is currently in use by the DSA. The display name of the document data item
is the same as the name of the super data type. The document data item contains a static link to the element
data item that represents the root-level element of the document.
5

Netcool/Impact XML DSA Guide
6
Element Data Types
Element data types represent the elements in an XML document. The DSA requires one such data type for
each type of XML element. An element data type contains one field for each attribute in the corresponding
XML element. In addition, the data type contains a field that corresponds to the element’s PCDATA value,
if any.
Element data types contain one or more data items called element data items. Each such data item represents
an instance of the element in the document.
The hierarchical relationship between XML elements is represented at the data item level by static links.
Element data items are statically linked in such a way that each data item contains links to other data items
that represent the child elements of the corresponding element in the XML document.
Element namespaces are a convention used by the DSA to show that a set of element data types are related
to a single XML document. The DSA uses element namespaces to avoid ambiguity in cases where more than
one type of XML document used by the DSA has an element of the same name.
Create Data Types Scripts
The XML DSA provides two scripts that you can use to create XML data types in Netcool/Impact. You use
one script to create data types from an XML DTD and the other to create data types from an XML XSD.
On UNIX platforms, these scripts are named CreateDtdTypes.sh and CreateXsdTypes.sh.
On Windows platforms, these scripts are named CreateDtdTypes.bat and
CreateXsdTypes.bat. These scripts are located in the $IMPACT_HOME/dsa/XmlDsa/bin
directory.
For more information on these scripts, see Creating XML Data Types on page 11.
XML Configuration Files
XML configuration files are text files that store mapping information for XML data types. The DSA reads
the configuration files at startup and uses the information during run time to locate the DTD or XSD file
and data source for each XML document. For more information about XML configuration files, see Setting
Up Data Type Mappings on page 13.
Netcool/Impact 3.0 and Later XML DSA Guide

XML Document and Data Type Mapping
Example
Netcool/Impact 3.0 and Later XML DSA Guide
XML Document and Data Type Mapping
The XML DSA works by providing a mapping between an XML document and a set of Netcool/Impact
data types. The DSA uses the information in an XML DTD or XSD file to understand the structure of the
XML data and to map the data to the corresponding data types in Netcool/Impact.
One aspect of the structure of the XML data is the hierarchical relationship between XML elements. The
DSA maps this relationship to the XML data types using static links, where each element data item is linked
to its logical child data item by a static link. When you read the XML data in a policy, you traverse the
resulting structure using the GetByLinks function. You can also traverse the structure using
Netcool/Impact’s embedded linking syntax.
This example shows an XML document and the linking relationship between the corresponding element
data items in Netcool/Impact.
The following is a sample partial XML document:
Micromuse
Alert
NodeXYZ
Node not responding
Figure 2 on page 8 and Figure 1 on page 4 show the linking relationship between the corresponding element
data items:
7

Netcool/Impact XML DSA Guide
8
Data Type:
XML_sender
PCDATA:
Micromuse
Data Type:
XML_head
Data Type:
XML_subject
PCDATA:
Alert
Data Type:
XML_alert
ID:
0123456789
Data Type:
XML_node
PCDATA:
NodeXYZ
Figure 2: Linking Relationships between Corresponding Element Data Items
Data Type:
XML_body
Data Type:
XML_summary
PCDATA:
Node not
responding
Netcool/Impact 3.0 and Later XML DSA Guide

Setting Up the DSA
To set up the XML DSA, do the following:
Install the DSA
Create the XML data types
Set up data type mapping
Installing the DSA
Netcool/Impact 3.0 and Later XML DSA Guide
Setting Up the DSA
To install the DSA, you run the install script and follow the on-screen prompts. On UNIX platforms, the
script is named is named installMediator.sh. On Windows platforms, the script is named
install.bat. Before you run the installation script, make sure the Netcool/Impact server is running.
The install script copies the DSA program files to the $IMPACT_HOME/dsa/XmlDsa directory, inserts
sample policies and the data types needed for the sample policies, and initializes the DSA.
The install script prompts you for the information in Table 1:
Table 1: DSA Install Script Prompts
Prompt Description
Netcool/Impact server name Name of the Netcool/Impact server where you want to
install the DSA. The default is NCI.
Username and password Valid Netcool Security Manager username and password.
Additional jar files Not used by the XML DSA installer.
Installing on UNIX Platforms
To install on UNIX platforms:
1. Obtain the DSA tar file from the Micromuse support site or product CD.
2. Copy the tar file to a temporary directory.
3. At a command prompt, unpack the tar file using the following command:
tar -xf XmlDsa*.tar
4. Run the install script by typing the following command:
./installMediator.sh
5. Follow the on-screen prompts.
9

Netcool/Impact XML DSA Guide
10
After installation, you must stop and restart the Netcool/Impact server.
Installing on Windows Platforms
To install on Windows platforms:
1. Obtain the DSA tar file from the Micromuse support site or product CD-ROM.
2. Copy the tar file to a temporary directory.
3. Extract the contents of the DSA tar file to a temporary directory using a file compression utility.
4. At a command prompt, change the current directory to the location where you extracted the files and
run the install script as follows:
cd C:\Windows\directory
install.bat
5. Follow the on-screen prompts.
After installation, you must stop and restart the Netcool/Impact server.
Installation Files
The following table shows the files installed by the install script:
Table 2: Installation Files
File Description
DSA jar file XmlDsadate.jar, where date is the build date for the DSA. Located in
$IMPACT_HOME/dsa/XmlDsa.
DSA properties file XmlDsa.properties. Located in $IMPACT_HOME/dsa/XmlDsa .
XML setup scripts Located in $IMPACT_HOME/dsa/XmlDsa/bin.
XML configuration
scripts
XmlFileTypes and XmlHttpTypes. Located in $IMPACT_HOME/dsa/XmlDsa.
Sample policies Installed on the target Netcool/Impact server.
Sample XML, DTD and
XSD files
TOC.xml,TOC.dtd, and TOC.xsd files. Located in $IMPACT_HOME/dsa/XmlDsa.
Netcool/Impact 3.0 and Later XML DSA Guide

Creating XML Data Types
Netcool/Impact 3.0 and Later XML DSA Guide
Creating XML Data Types
After you have installed the DSA, you must create a set of XML data types that corresponds to the structure
of the XML document you want to read using Netcool/Impact.
To create the XML data types, you run either the create DTD types script or the create XSD types script,
depending on which type of schema you are using.
On UNIX platforms, these scripts are named CreateDtdTypes.sh and CreateXsdTypes.sh.
On Windows platforms, these scripts are named CreateDtdTypes.bat and
CreateXsdTypes.bat. These scripts are located in the $IMPACT_HOME/dsa/XmlDsa/bin
directory.
When you run a create types script, it creates a super data type and then reads the XML DTD or XSD file
and creates one element data type for each type of element defined in the file, including the root-level
element. The script uses the names of the elements in the DTD or XSD file for the names of the element
data types. If you specify an element namespace, it is prepended to the name of each element data type. The
script then inserts the data types into Netcool/Impact using the command line service.
Note: The create types scripts replace any colon character that appears in XML element names with an
underscore when creating the data types. For example, if a DTD file contains an element named
netcool:alert, the create DTD types script creates a corresponding element data type named
netcool_alert.
Running the Create Types Scripts
You run the create types scripts from the command line and provide the required command line options.
Make sure that the Netcool/Impact server is running before you start the script.
The following table shows the command line options for the script:
Table 3: CreateTypes Options (1 of 2)
Option Description
server_name Name of the server where Netcool/Impact is running.
user Name of the Netcool/Impact user.
password Netcool/Impact user’s password.
dtdFileName Path and filename of the XML DTD file that describes the XML document. The
path is relative to the $IMPACT_HOME/dsa/XmlDsa/bin directory.
xsdFileName Path and filename of the XML XSD file that describes the XML document. The
path is relative to the $IMPACT_HOME/dsa/XmlDsa/bin directory.
11

Netcool/Impact XML DSA Guide
12
Table 3: CreateTypes Options (2 of 2)
Option Description
type_name Name of the resulting super data type. The string specified using the
NameSpacePrefix argument is not prepended to the name of the super data
type.
namespace_prefix Optional string prepended to the names of element data types.
To run the create data types scripts, do the following:
1. Make sure that the Netcool/Impact server is running.
2. At a command prompt, change the current directory to $IMPACT_HOME/dsa/XmlDsa/bin.
3. Enter the following:
./CreateDtdTypes.sh server_name user password dtdFile type_name
[namespace_prefix]
or
./CreateXsdTypes.sh server_name user password xsdFile type_name
[namespace_prefix]
where the command line arguments are as described in the table above.
Netcool/Impact 3.0 and Later XML DSA Guide

Setting Up Data Type Mappings
Overview
Netcool/Impact 3.0 and Later XML DSA Guide
Setting Up Data Type Mappings
This section contains information on setting up data type mappings. It contains the following topics:
Overview
Setting Up Mappings for XML Files and Strings
Setting Up Mappings for XML Over HTTP
After you have created XML data types, you must set up data type mappings. A data type mapping is a set
of information that shows the relationship between an XML data source, an XML document and XML data
types. The DSA uses this information to map the contents of an XML document to the data types in
Netcool/Impact. You must set up one data type mapping for each type of XML document you want
Netcool/Impact to read.
Data type mapping information is stored in XML configuration files. The DSA uses the following XML
configuration files:
XmlFileTypes
XmlHttpTypes
These files are located in the $IMPACT_HOME/dsa/XmlDsa directory.
Note: After you have edited the data types, you must stop and restart the Netcool/Impact server.
Setting Up Mappings for XML Files and Strings
For each XML string or file that you want the DSA to read, you must add the following mapping
information to the XmlFileTypes file:
Name of the super data type
Path and filename of the corresponding XML DTD/XSD file
Path and filename of the corresponding XML file (XML files only)
Namespace prefix used for the element data types (optional)
13

Netcool/Impact XML DSA Guide
14
You specify mapping information in the file using the following format:
XmlDsa.fileTypes.n.property .value
where n is a numeric value that identifies the mapping, property is the name of the mapping property,
and value is the value.
The following table shows the mapping properties in the XmlFileTypes file:
Table 4: XmlFileTypes Mapping Properties
Property Description
typeName Name of the corresponding super data type.
dtdFile Path and filename of a corresponding XML DTD file. The path can be an absolute
path or a path relative to the $IMPACT_HOME directory. Used only if the XML
schema is a DTD.
xsdFile Path and filename of a corresponding XML XSD file. The path can be an absolute
path or a path relative to the $IMPACT_HOME directory. Used only if the XML
schema is an XSD.
isXsd This boolean variable specifies whether the schema is defined in XSD or DTD
format. If it is not specified, the default is DTD format.
xmlFile For XML files, the path and filename of the corresponding file. The path is relative
to the $IMPACT_HOME directory. For XML strings, use the hyphen character as a
placeholder.
prefix Namespace prefix used to identify the corresponding element data types
(optional).
Examples
The following example shows a set of mapping properties for an XML document contained in a file.
XmlDsa.fileTypes.1.typeName XML_file_superType
XmlDsa.fileTypes.1.dtdFile dsa/XmlDsa/file.dtd
XmlDsa.fileTypes.1.xmlFile dsa/XmlDsa/file.xml
XmlDsa.fileTypes.1.prefix XML_
The following example shows a set of mapping properties for an XML document contained in a string.
XmlDsa.fileTypes.2.typeName XML_string_superType
XmlDsa.fileTypes.2.dtdFile dsa/XmlDsa/string.dtd
XmlDsa.fileTypes.2.xmlFile -
XmlDsa.fileTypes.2.prefix XML_
Note that this example uses the hyphen character (-) for the xmlFile property.
Netcool/Impact 3.0 and Later XML DSA Guide

Netcool/Impact 3.0 and Later XML DSA Guide
Setting Up Data Type Mappings
The following example shows an expression using the XmlFileTOC data type with isXsd set to true.
The name space prefix is FTEST. This prefix should be added to all data types that are a part of the XML file.
XmlDsa.fileTypes.1.typeName XmlFileTOC
XmlDsa.fileTypes.1.dtdFile dsa/XmlDsa/TOC.xsd
XmlDsa.fileTypes.1.xmlFile dsa/XmlDsa/TOC.xml
XmlDsa.fileTypes.1.prefix FTEST_
XmlDsa.fileTypes.1.isXsd true
Setting Up Mappings for XML Over HTTP
For each XML document that you want the DSA to read over HTTP, you must add the following mapping
information to the XmlHttpTypes file:
Name of the super data type.
Base URL for the HTTP server.
Username, password and authentication realm (optional). Required only if the XML document is
located in a password-protected area of the HTTP server.
Namespace prefix used for the element data types (optional).
You specify mapping information in the file using the following format:
XmlDsa.httpTypes.n.property value
where n is a numeric value that identifies the mapping, property is the name of the mapping property,
and value is the value.
The following table shows the mapping properties in the XmlHttpTypes file:
Table 5: XmlHttpTypes Mapping Properties (1 of 2)
Property Description
typeName Name of the corresponding super data type.
dtdFile Path and filename of the corresponding XML DTD file. The path can be an
absolute path or a path relative to the $IMPACT_HOME directory.
xsdFile Path and filename of a corresponding XML XSD file. The path can be an absolute
path or a path relative to the $IMPACT_HOME directory. Used only if the XML
schema is an XSD.
isXsd This boolean variable specifies whether the schema is defined in XSD or DTD
format. If it is not specified, the default is DTD format.
15

Netcool/Impact XML DSA Guide
16
Table 5: XmlHttpTypes Mapping Properties (2 of 2)
Property Description
url Base URL for the HTTP server. The base URL includes the server’s hostname, as
well as the path where the script or executable that provides the XML data is
located. You do not need to specify the trailing backslash in the base URL. This
URL is combined with the contents of the FilePath parameter to form the
complete URL when you retrieve the XML data in a policy.
user Username valid under HTTP server authentication (optional).
password Password valid under HTTP server authentication (optional).
realm Authentication realm on the HTTP server (optional).
prefix Namespace prefix used to identify the corresponding element data types
(optional).
Example
The following example shows a set of mapping properties for XML data provided by an HTTP server.
XmlDsa.httpTypes.1.typeName XML_http_superType
XmlDsa.httpTypes.1.dtdFile dsa/XmlDsa/http.dtd
XmlDsa.httpTypes.1.url http://localhost:8080/cgi-bin
XmlDsa.httpTypes.1.user jsmith
XmlDsa.httpTypes.1.password micromuse
XmlDsa.httpTypes.1.realm primary
Netcool/Impact 3.0 and Later XML DSA Guide

Reading XML Documents
Netcool/Impact 3.0 and Later XML DSA Guide
Reading XML Documents
This section contains information about reading XML documents from within a policy. It contains the
following topics:
Retrieving the Document Data Item
Retrieving the Root-Level Element Data Item
Retrieving the Child Element Data Item
Accessing Attribute Values
Retrieving the Document Data Item
The first step in reading an XML document is to retrieve the document data item. You retrieve the data item
by calling the GetByFilter function and passing the name of the super data type and a filter string. The
content of the filter string varies depending on whether the data source is an XML string, XML file, or XML
data located on an HTTP server.
XML Strings
For XML strings, the filter is the entire XML string that you want to read.
The following example shows how to retrieve the document data item associated with an XML string, where
the corresponding super type is named XML_string_SuperType.
// Call GetByFilter and pass the name of the super type
// and the filter string
Type = "XML_string_superType";
Filter = "Node1234Node not responding";
CountOnly = False;
DocDataItem = GetByFilter(Type, Filter, CountOnly);
17

Netcool/Impact XML DSA Guide
18
XML Files
For XML files, the filter is an empty string.
The following example shows how to retrieve the document data item associated with an XML file, where
the corresponding super type is named XML_file_superType.
// Call GetByFilter and pass the name of the super type
// and the filter string
Type = "XML_file_superType";
Filter = "";
CountOnly = False;
DocDataItem = GetByFilter(Type, Filter, CountOnly);
XML Over HTTP
For XML over HTTP, the filter string is an expression that specifies the method to use in retrieving the XML
data and the path to a script or executable that provides the data on the HTTP server. The XML DSA uses
either the GET or POST method to retrieve the XML data.
The syntax for the filter is:
Operation = 'method' AND FilePath = 'path'
where method is either GET or POST and path is the location of the script or executable relative to the
base URL. You specify the base URL when you set the mapping information for the document in the
XmlHttpTypes file.
Note: The FilePath specification can include query string values. This allows you to retrieve XML
documents from the HTTP server that are dynamically created depending on values sent by Netcool/Impact
as part of the HTTP request.
Netcool/Impact 3.0 and Later XML DSA Guide

Netcool/Impact 3.0 and Later XML DSA Guide
Reading XML Documents
The following example shows how to retrieve the document data item associated with XML data using an
HTTP GET request. In this example, the name of the super data type is XML_http_superType and
the location of the script that provides the XML data is getXMLdoc.pl.
// Call GetByFilter and pass the name of the super type
// and the filter string
Type = "XML_http_superType";
Filter = "Operation = 'GET' AND FilePath = 'getXMLdoc.pl?node=NodeXYZ'";
CountOnly = False;
DocDataItem = GetByFilter(Type, Filter, CountOnly);
Retrieving the Root-Level Element Data Item
After you have retrieved the document data item, you can retrieve the root-level element data item using the
GetByLinks function. When you call GetByLinks, you must pass the name of the root-level element
data type, an empty filter string and the document data item.
The following example shows how to retrieve the root-level element data item using
GetByLinks.
// Call GetByLinks and pass the name of the
DataTypes = {"XML_alert"};
Filter = "";
MaxNum = "10000";
DataItems = DocDataItem;
RootDataItem = GetByLinks(DataTypes, Filter, MaxNum, DataItems);
19

Netcool/Impact XML DSA Guide
Retrieving Child Element Data Items
20
After you have retrieved the root-level element data item, you can retrieve child element data items by
making successive calls to the GetByLinks function or by using the embedded linking syntax.
The following example shows how to use the linking syntax to retrieve the first child element data item
linked to the root-level element data item, where the data type of the child data item is XML_body.
ChildNode = RootDataItem[0].links.XML_body.first;
The following example shows how to retrieve an array that contains all child element data items linked to
the root-level element data item.
ChildNodes = RootDataItem[0].links.XML_body.array;
Accessing Attribute Values
Once you have retrieved an element data item, you can access its attribute values by referencing the
corresponding data type fields.
The following example shows how to log the value of the ID attribute associated with the current element
data item:
log(“The message ID is: “ + OrgNode.id);
The following example shows how to log the PCDATA value associated with the current element data item:
log(OrgNode.PCDATA);
Netcool/Impact 3.0 and Later XML DSA Guide

Sample Policies
The DSA provides the following sample policies:
XmlStringTestPolicy
XmlFileTestPolicy
XmlHttpTestPolicy
XmlXsdFileTestPolicy
These policies are configured to use the TOC.dtd, TOC.xsd and TOC.xml files located in the
$IMPACT_HOME/dsa/XmlDsa directory.
XmlStringTestPolicy
Netcool/Impact 3.0 and Later XML DSA Guide
Sample Policies
XmlStringTestPolicy shows how to use the XML DSA to read data from an XML string. The policy
reads the contents of an XML-formatted string and then prints the data to the policy log.
Before you use this policy, you must run the create DTD types script as follows:
./CreateDtdTypes.sh NCI admin netcool ../TOC.dtd XmlStringTOC STEST_
You do not need to edit the contents of the XmlFileTypes configuration file. By default, this file
contains the necessary data type mappings. The following are the data type mappings:
XmlDsa.fileTypes.2.typeName XMLStringTOC
XmlDsa.fileTypes.2.dtdFile dsa/XmlDsa/TOC.dtd
XmlDsa.fileTypes.2.xmlFile -
XmlDsa.fileTypes.2.prefix STEST_
XmlFileTestPolicy
XmlFileTestPolicy shows how to use the XML DSA to read data from an XML file. This policy reads
the contents of the TOC.xml file and then prints the data to the policy log.
Before you use this policy, you must run the create DTD types script as follows:
./CreateDtdTypes.sh NCI admin netcool ../TOC.dtd XmlFileTOC FTEST_
21

Netcool/Impact XML DSA Guide
22
You do not need to edit the contents of the XmlFileTypes configuration file. By default, this file
contains the necessary data source mappings. The following are the data type mappings:
XmlDsa.fileTypes.1.typeName XmlFileTOC
XmlDsa.fileTypes.1.dtdFile dsa/XmlDsa/TOC.dtd
XmlDsa.fileTypes.1.xmlFile dsa/XmlDsa/TOC.xml
XmlDsa.fileTypes.1.prefix FTEST_
XmlHttpTestPolicy
XmlHttpTestPolicy shows how to use the XML DSA to read data from a location on an HTTP
server. This policy reads the XML data from an HTTP server and then prints it to the policy log.
Before you use this policy, you must run the CreateDtdTypes script as follows:
./CreateDtdTypes.sh NCI admin netcool ../TOC.dtd XmlHttpTOC HTEST_
You must also install a Perl CGI script on the HTTP server that generates the XML output requested by the
DSA. This script is named xml.cgi and is located in $IMPACT_HOME/dsa/XmlDsa. You must
check to make sure that the first line of the script references the actual location of the Perl executable on the
system before you install the script. To install, copy the script into the cgi-bin directory used by the
HTTP server.
After you have installed the script, you must modify the XmlHttpTypes configuration file to reflect the
location of the script and to include a valid username and password for the authentication realm, if any.
The following are the data type mappings:
XmlDsa.httpTypes.1.typeName XmlHttpTOC
XmlDsa.httpTypes.1.dtdFile dsa/XmlDsa/TOC.dtd
XmlDsa.httpTypes.1.prefix HTEST_
XmlDsa.httpTypes.1.url http://localhost:8080
XmlDsa.httpTypes.1.user John
XmlDsa.httpTypes.1.password Smith
XmlDsa.httpTypes.1.realm basicrealm
Netcool/Impact 3.0 and Later XML DSA Guide

XmlXsdFileTestPolicy
Netcool/Impact 3.0 and Later XML DSA Guide
Sample Policies
XmlXsdFileTestPolicy shows how to use the XML DSA to read data from an XML file. This policy
reads XML data returned from a URL and then prints the data to the policy log.
Before you use this policy, you must run the create XSD script as follows:
./CreateXsdTypes.sh NCI admin netcool ../TOC.xsd XmlXsdFileTOC XSDFTEST_
where filename is the name and path of an XML file stored on the file system.
You do not need to edit the contents of the XmlFileTypes configuration file. By default, this file
contains the necessary data source mappings. The following are the data type mappings:
XmlDsa.fileTypes.2.typeName XmlXsdFileTOC
XmlDsa.fileTypes.2.xsdFile dsa/XmlDsa/TOC.xsd
XmlDsa.fileTypes.2.xmlFile dsa/XmlDsa/TOC.xml
XmlDsa.fileTypes.2.prefix XSDFTEST_
XmlDsa.fileTypes.2.isXsd true
23

Netcool/Impact XML DSA Guide
24
Netcool/Impact 3.0 and Later XML DSA Guide

ackmatter.fm May 4, 2005
Contact Information
Corporate
Region Address Telephone Fax World Wide Web
USA Micromuse Inc. (HQ)
139 Townsend Street
San Francisco
CA 94107
USA
Europe Micromuse Ltd.
Disraeli House
90 Putney Bridge Road
London SW18 1DA
United Kingdom
Asia-Pacific Micromuse Ltd.
Level 2
26 Colin Street
West Perth
Perth WA 6005
Australia
Technical Support
1-800-Netcool (638 2665)
+1 415 538 9090
Region Telephone Fax
USA 1-800-Netcool (800 638 2665)
+1 415 538 9090 (San Francisco)
+1 415 538 9091 http://www.micromuse.com
+44 (0) 20 8875 9500 +44 (0) 20 8875 9995 http://www.micromuse.co.uk
+61 (0) 8 9213 3400 +61 (0) 8 9486 1116 http://www.micromuse.com.au
+1 415 538 9091
Europe +44 (0) 20 8877 0073 (London, UK) +44 (0) 20 8875 0991
Asia-Pacific +61 (0) 8 9213 3470 (Perth, Australia)
Online
+10 800 852 1012 (North China)
+10 800 152 1012 (South China)
+61 (0) 8 9486 1116
Team E-Mail World Wide Web
Licensing Temporary Licenses: temp.licensing@micromuse.com
Permanent Licenses: perm.licensing@micromuse.com
support.micromuse.com/helpdesk/licenses
Support support@micromuse.com support.micromuse.com
Netcool/Impact 3.0 and Later XML DSA Guide 25

Contact Information
26
Netcool/Impact 3.0 and Later XML DSA Guide