Assuming there are no custom properties defined in current plugin-cfg.xml file, what should be done before running the GenPluginCfg command?
Assuming there are no custom properties defined in current plugin-cfg.xml file, what should be done before running the GenPluginCfg command?
A . Delete the globalplugin-cfg.xmlin the<profile_root>/config/cellsdirectory.
B . Delete the currentplugin-cfg.xmlin the<profile_root>/config/cellsdirectory.
C . CleartheEnable automated web server configuration processingoption in the web server plugin configuration service.
D . Use either the Integrated Solutions Console or theConfigurewebServerDefinition.jaclscript to create a web server definition.
Answer: B
Explanation:
Delete the plugin-cfg.xml file in the profile_root/config/cells directory before you use theGenPluginCfgcommand. Otherwise, configuration changes do not persist to the plugin-cfg.xml file. However, do not delete the plugin-cfg.xml file if you have custom properties that you previously set in it that you need to persist.
Note:You can update the global plugin-cfg.xml file using the administrative console or running the GenPluginCfg command for all of the clusters in a cell. However, you must delete the config/cells/plugin-cfg.xml file before you update the global plugin-cfg.xml file. If you do not delete the config/cells/plugin-cfg.xml file, only the new properties and their values are added to the global plugin-cfg.xml file. Any updates to existing plug-in property values are not added to the global plugin-cfg.xml file.
References:https://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/rxml_genplugincfg1.html
Latest C9510-418 Dumps Valid Version with 128 Q&As
Latest And Valid Q&A | Instant Download | Once Fail, Full Refund