madconfig utility targets for InfoSphere MDM

Use the madconfig utility to manually install the MDM operational server and database components for physical and virtual implementations. IBM® Installation Manager uses the utility targets during InfoSphere® MDM installation.

This utility is run from the operational server installation MDM_INSTALL_HOME/mds/scripts directory.

This following tables list the madconfig targets for InfoSphere MDM and their usage.

Operational server installation

The following table lists the targets that are related to installing the operational server. Each target requests values for parameters that pertain to the server and database. The server targets are used to configure the server on which InfoSphere MDM is installed.

Table 1. madconfig utility targets for operational server installation
Command	Description
`-install_native_engine_ear`	Installs the native operational server (engine) for a virtual MDM implementation.
`-install_server_config`	Configures the application server for physical and virtual components; including JDBC, class path, and environment variables.
`-stop_server`	Stops an operational server in WebSphere® Application Server Network Deployment. Stopping and starting the server is required after you install an operational server configuration. The option `-stop_base_server` must be used when the server is unmanaged (Base server).
`-start_server`	Starts an operational server in a managed application server deployment. Use the option `-start_base_server` when the application server is unmanaged.
`-install_mdm_old_ws_ear`	Installs the physical MDM web services JAR in the application server.
`-install_mdm_eba`	Installs the InfoSphere MDM OSGi.
`-install_prop_file_jar`	Installs the property file JAR required by InfoSphere MDM applications.
`-install_mdm_ws_ear`	Installs the InfoSphere MDM web services enterprise archive.
`-install_mds_ws_api`	Installs the API for virtual MDM.
`-enable_app_security`	Creates users, creates groups, adds users to groups, creates policy set, and creates policy set binding for web services EAR file.
`-map_roles_to_users`	Creates the Security role mapping and RunAs role mapping for the EBA and web services EAR file.
`-full_sync`	Synchronizes nodes in a managed server deployment to reflect the user security for InfoSphere MDM. This target must be run after you run the `map_roles_to_users` target.
`-enable_deployment_target`	Checks the status of the operational server; if the server is stopped you can use this target to restart the server.

InfoSphere MDM database installation

The following table lists the targets that are used to install and configure physical and virtual schemas for the MDM database.

Table 2. madconfig utility targets for database installation
Command	Description
`-install_core_db_db2`	Creates tables, triggers, constraints, and functions for the InfoSphere MDM core database that is installed on IBM DB2®.
`-install_domain_db_db2`	Creates tables, triggers, constraints, and functions for InfoSphere MDM domains on a DB2 database.
`-install_core_db_ora`	Creates tables, triggers, constraints, and functions for an InfoSphere MDM core database on Oracle.
`-install_domain_db_ora`	Creates tables, triggers, constraints, and functions for InfoSphere MDM domains on an Oracle database.
`-install_core_db_sql`	Creates tables, triggers, constraints, and functions for the InfoSphere MDM core database on Microsoft SQL Server.
`-Update_configelement_matching`	Updates the Configelement table for the selected matching type.
`-Update_appsoftware_eba`	Updates the appsoftware table by providing the appropriate name of the EBA in the software name column.
`-create_datasource`	Creates the data source that is used by a virtual MDM.
`-create_odbc`	Creates an ODBC for use by virtual MDM.
`-register_odbc`	Registers ODBC for virtual MDM.
`-bootstrap_datasource`	Creates the tables for virtual MDM.
`-test_datasource`	To test your data source, you must provide the database name and DSN name. The DSN name can be found in the odbc.ini file in the mds/conf directory, or you can use the ./madconfig.sh list_datasources command. Provide the database name and DSN name as follows: `./madconfig.sh test_datasource -Dmad.db.name=dbname -Dmad.db.dsn=DSNname`

InfoSphere MDM web UI installations

The madconfig utility supports the installation of the InfoSphere MDM web-based user interfaces.

Important: Before running any of the web UI installation targets, you must first run the appropriate target to create and start the application server:

For WebSphere Application Server Network Deployment Edition, run -enable_deployment_target.
For WebSphere Application Server Base Edition, run -start_base_server.

The following table describes the targets that are used to install and configure the web interfaces.

Table 3. madconfig utility targets for web-based user interfaces
Command	Description
`-config_mdm_web_app`	Configures the following: Adds the port defined by `WC_defaulthost_secure` into the `default_host` as the host alias. Adds the custom property com.ibm.CORBA.RequestTimeout into the ORB Service. Sets Requires SSL to `true` in the Global Security > Single sign-on settings.
`-mds_ui_prop_config`	Configures the properties files for the virtual MDM web applications, including Inspector, Web Reports, and Enterprise Viewer.
`-mdm_ui_prop_config`	Configures the properties files for the physical MDM web applications, including Data Stewardship UI, Business Administration UI, and Product Maintenance UI.
`-install_mds_web_app`	Deploys the virtual MDM web applications. For Inspector and Web Reports, this target sets the class loader mode to PARENT_LAST and the policy to SINGLE.
`-install_mdm_web_app`	Deploys the physical MDM web applications.
`-import_ssl_certificate`	Imports the SSL certificate. This target is required when: Installing the virtual MDM web interfaces. Enabling SSL for the virtual MDM web interfaces. Deploying the virtual MDM web interfaces and operational server are deployed to different application server cells.

To install the physical MDM web interfaces, run the following madconfig targets in sequence:

mdm_ui_prop_config
config_mdm_web_app
install_mdm_web_app

To install the virtual MDM web interfaces, run the following madconfig targets in sequence:

mds_ui_prop_config
config_mdm_web_app
install_mds_web_app

Flexible Search configuration

The madconfig utility supports the configuration and management of Flexible Search.

The following table describes the targets that are used to configure and manage Flexible Search.

Table 4. madconfig utility targets for Flexible Search
Command	Description
`-flexsearch_config`	Configures Flexible Search to index InfoSphere MDM attributes in Data Explorer as entities that are composed of these attributes are created/updated/deleted.
`-flexsearch_syncdb`	Indexes entities to Data Explorer by specifying entrecno (entity id) range values to index from the operational server database.
`-flexsearch_sync_svc_enable`	Enables the Flexible Search index synchronization service.
`-flexsearch_sync_svc_disable`	Disables the Flexible Search index synchronization service.

InfoSphere MDM uninstall

The madconfig utility also supports uninstalling the application server and database.

Attention: Reset of the MDM operational server and database components is supported by the Test Environment tool in InfoSphere MDM Workbench. Even though madconfig targets are available for reset, the best practice is to always use the workbench tool.

Table 5. madconfig utility targets for uninstall
Command	Description
`-uninstall_mds_ws_api`	Uninstalls the API for virtual MDM.
`-uninstall_mdm_ws_ear`	Uninstalls the InfoSphere MDM web services enterprise archive.
`-uninstall_mdm_web_app`	Uninstalls the InfoSphere MDM web interfaces: Business Administration UI Data Stewardship UI Product Maintenance UI Inspector Web Reports Enterprise Viewer
`-uninstall_prop_file_jar`	Uninstalls the property file JAR required by an InfoSphere MDM application.
`-uninstall_mdm_eba`	Uninstalls the InfoSphere MDM OSGi.
`-uninstall_mdm_old_ws_ear`	Uninstalls the physical MDM web services JAR in the application server.
`-uninstall_server_config`	Removes the InfoSphere MDM-related configuration changes made to the application server.
`-uninstall_native_engine_ear`	Uninstalls the native operational server (engine) for virtual MDM.
`-remove_datasource`	Removes the data source that is used by a virtual MDM.
`-unregister_odbc`	Unregisters ODBC used by virtual MDM.