Directory structures
There are three directories you want to understand when you install and use InfoSphere® MDM: the installation directory, the shared directory, and the application server directory.
When you run IBM® Installation Manager, you choose an installation path. This path and root directory are defined in the installation topics as MDM_INSTALL_HOME. MDM_INSTALL_HOME contains resources that are unique to the installed package. Within this directory are subdirectories for each of the components that you selected for installation. It also has directories that are specific to the operating system on which you install.
The MDMShared directory contains resource files that are shared by multiple installed package groups. The contents can include resources that are needed to run IBM Installation Manager scripts, Java™ custom code libraries, and IBM Rational® Application Developer for example. For more information about this directory, see the online documentation for IBM Installation Manager.
The application server path to which the installed components are deployed is defined in the installation topics as WAS_PROFILE_HOME.
MDM_INSTALL_HOME
Contents of the installation directory includes, but is not limited to, the subdirectories that are listed in the following table. The specific directories that you see depends on the features that you install.
| Directory | Description |
|---|---|
| aix, linux, solaris, win32, win64, zlinux | These directories contain operating system-specific files. |
| BatchProcessor | Contains subdirectories and files that are required to run the Batch Processor tool. The Batch Processor is designed primarily to work with physical MDM data. |
| com.ibm.mdm.tools | Contains OSGi bundles. An MDM Workbench workspace can be configured to use these bundles so that reference models and Java class references can be resolved. |
| database | Contains static schema files. |
| documentation | Contains a messages.properties file in the /nl/ subdirectory, which is used by the installer during run time. For example, it contains messages that are used by the installer progress monitor. |
| EnterpriseIntegrator | Contains subdirectories and files that are required to configure and use the InfoSphere MDM Healthcare Point of Service Integrator search application. |
| eventManagmentClient | Contains subdirectories and files to support the Event Manager component. The Event Manager is a triggering component that can detect events and activities in MDM. |
| InstallableApps | Contains subdirectories and files for any installed user applications. Applications include, but are not limited to, Business Administration UI, Inspector, and Web Reports. |
| IVT | Contains subdirectories and scripts that are used to run the installation verification tests. |
| logs | Contains the logs that are recorded during the installation process. |
| ManagementAgent | Contains subdirectories and files that are used to run the configuration management agent, which is used to configure and manage several MDM features. |
| ManagementConsole | Contains subdirectories and files that are used by the Management Console. The Management Console is the user interface that supports the management agent. |
| MDMCollector | Contains subdirectories and files that are used to run IBM Support Assistant Data Collector. |
| mds | This directory contains files for virtual MDM
(formerly IBM Initiate Master Data Service®). Java and Web Service SDK examples
are installed in the /lib/sdk/examples directory. It also contains utilities in the /scripts directory, like the madconfig utility. |
| MessageBrokerSuite | Contains subdirectories and configuration files that are used to implement and manage the Message Broker components. Message Broker components are typically used in virtual implementations to support messaging between source systems and the operational server and MDM database. |
| PCDS | Contains subdirectories and files that support the Patient Clinical Data Search user interface. |
| properties | Contents in this directory provide input parameters that are used when you reset the MDM database and server from MDM Workbench. |
| Samples | Contains mappings and source code files that can be used in development environments. |
| temp | Contains all database logs. After installation, if you reset the database, this directory is used to copy all temporary SQL files. |
| tmp | Contains temporary files that are used during the installation process. |
| Uninstall | This directory contains the scripts that are needed to uninstall the MDM components. |
| utils | Contains common entity name instance private key generator assets. |