Technical Blog Post
Abstract
MDM Post Install Configuration Targets - redeploy_EBA
Body
Target redeploy_EBA
Uninstalls and installs the Enterprise Business Application (EBA) and performs security configuration for the EBA.
Note:
Before running the redeploy_EBA, you should first go to your JVM properties under Was Admin console >
Application servers > YOUR_SERVER > Process definition > Java Virtual Machine > Custom properties
and remove the two properties below. Once the redeploy_EBA completes, re-add them back in.
1 - com.ibm.ws.eba.bla.concurrency
2 - com.ibm.ws.eba.bla.proxies.archiveCacheSize
Invocation:
When the operating system is Windows:
- Go to <MDM_INSTALL_DIR>/mds/scripts
- Invoke madconfig redeploy_EBA
In other operating systems
- Go to <MDM_INSTALL_DIR>/mds/scripts
- Invoke ./madconfig.sh redeploy_EBA
Inputs obtained:
- The WebSphere Application Server administrator user password
- MDM Administrator user 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 MDM Operational Server is a Business Level Application that comprises of the EBA and a jar file that contains crucial property files that determine the MDM application's functionality.
This target:
- Provides details on the WebSphere Application Server environment
- Obtains user consent to proceed with OSGI bundles redeployment
- Checks the server status
- Uninstalls the jar file that holds properties files
- Uninstalls the enterprise business application
- Installs the enterprise business application
- Install the jar file that contains property files
- Performs security configuration for the enterprise business application
- Restarts the application server
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
UID
ibm11142098