Technical Blog Post
Abstract
MDM Post Install Configuration Targets - redeploy_native_ear
Body
Target redeploy_native_ear
Uninstalls and installs the native engine which is the core virtual MDM component
When to use:
In cases where native engine deployment failed during MDM configuration.
Invocation:
When the operating system is Windows:
- Go to <MDM_INSTALL_DIR>/mds/scripts
- Invoke madconfig redeploy_native_ear
In other operating systems
- Go to <MDM_INSTALL_DIR>/mds/scripts
- Invoke ./madconfig.sh redeploy_native_ear
Inputs obtained:
- The WebSphere Application Server administrator user password
- The database password
Other details on application configuration are obtained from mdm_install.properties found in <MDM_INSTALL_DIR>/properties folder. (In MDM v11.4 FP3 and MDM v11.5, other details are obtained from <MDM_INSTALL_DIR>/properties/app.properties)
Tasks performed:
The native engine is the core virtual MDM component and has certain configuration files including ODBC data source configuration file.
This target:
- Provides details on the WebSphere Application Server environment
- Obtains user consent to proceed with native ear redeployment
- Checks the server status
- Uninstalls the native engine
- Installs the native engine and generates the configuration files
Logs:
Logs can be found at
- <MDM_INSTALL_DIR>/logs/madconfig
- <MDM_INSTALL_DIR>/logs/madconfig/java
Available in:
- MDM v11.4 FP3
- MDM v11.5
- MDM v11.6
Note:
- The configuration files can be found at <WAS_PROFILE_DIR>/installedApps/<CELL>/MDM-native-<INSTANCE_ID>.ear/native.war/conf folder.
- Please restart the application server after invoking redeploy_native_ear.
UID
ibm11142092