Veritas InfoScale™ Operations Manager 7.3.1 Add-ons User's Guide
- Section I. VCS Utilities Add-on 7.3.1
- Section II. Distribution Manager Add-on 7.3.1
- Section III. Fabric Insight Add-on 7.3.1
- Section IV. Patch Installer Add-on 7.3.1
- Introduction to Patch Installer Add-on
- Using Patch Installer Add-on
- Section V. Storage Insight Add-on 7.3.1
- Performing the deep discovery of enclosures
- About Storage Insight Add-on
- Adding HITACHI storage enclosures for deep discovery
- Editing the deep discovery configuration for an enclosure
- Monitoring the usage of thin pools
- Monitoring storage array metering data
- Managing LUN classifications
- Appendix A. Enclosure configuration prerequisites
- HITACHI enclosure configuration prerequisites
- EMC Symmetrix storage array configuration prerequisites
- Device setup requirements for EMC Symmetrix arrays
- IBM XIV enclosure configuration prerequisites
- NetApp storage enclosure configuration prerequisites
- EMC CLARiiON storage enclosures configuration prerequisites
- Hewlett-Packard Enterprise Virtual Array (HP EVA) configuration prerequisites
- IBM System Storage DS enclosure configuration prerequisites
- IBM SVC enclosure configuration prerequisites
- EMC Celerra enclosure configuration prerequisites
- EMC VNX storage enclosure configuration prerequisites
- EMC VPLEX storage enclosure configuration prerequisites
- Appendix B. Commands used by Management Server for deep discovery of enclosures
- Performing the deep discovery of enclosures
- Section VI. Storage Insight SDK Add-on 7.3.1
- Overview of Storage Insight SDK Add-on 7.3.1
- Managing Veritas InfoScale Operations Manager Storage Insight plug-ins
- About creating Storage Insight plug-in
- About discovery script
- About the enclosure discovery command output
- Creating a Storage Insight plug-in
- Editing a Storage Insight plug-in
- Testing a Storage Insight plug-in
- About creating Storage Insight plug-in
- Section VII. Storage Provisioning and Enclosure Migration Add-on 7.3.1
- Provisioning storage
- Creating a storage template using VxFS file systems
- Migrating volumes
- Provisioning storage
- Section VIII. Veritas HA Plug-in for VMware vSphere Web Client
- Introduction to Veritas HA Plug-in for vSphere Web Client
- Installation and uninstallation of Veritas HA Plug-in for vSphere Web Client
- Configurations for Veritas HA Plug-in for vSphere Web Client
- Section IX. Application Migration Add-on
- Introduction to Application Migration Add-on
- Creating and managing an application migration plan
- Understanding application migration operations
XML API servlet and XML API server configuration properties
Both the XML API Servlet and XML API Server share a set of configuration parameters. All parameters are located in the properties file, $NAS_DB/sys/xml_api.conf, which typically resolves to /nas/sys/xml_api.conf.
Among the list of properties, there are some debug flags. EMC has listed the XML API configuration properties for application development and not deployment. So many of the flags are set to true (debug mode).
Table: XML API Servlet and XML API Server configuration properties
Property | Description |
---|---|
xml.api.server.log | The location of the XML API Server log is relative to the $NAS_DB (usually set to /nas) directory. Currently, the value is set to log/cel_api.log, which normally results in the log file being recorded in the /nas/log/cel_api.log file. The value of this property affects the XML API Server. |
xml.api.servlet.log | The location of the XML API Servlet log is relative to the $NAS_DB directory. Currently the value is set to log/webui/cel_api.log, which normally results in the log file being recorded in the /nas/log/webui/cel_api.log file. The value of this property affects the Tomcat server. |
xml.api.servlet.logmask | This property switches on and off certain servlet log profiles. The default value for the mask is zero, which means that the servlet does not log anything. Do not change this value, unless you do it temporarily at the request from EMC Support engineers and then reset it to zero. The value of this property affects the Tomcat server. |
xml.api.user.request.validation.flag | If true, this property performs a full user request validation. In the case of improperly formatted request packets, it returns more meaningful diagnostic messages to the user. EMC suggests you set this property to false when the application is deployed since it adds to CPU and memory overhead. The value of this property affects the XML API Server. |
xml.api.enable.indications.ext | If true, user applications can receive indications for configuration changes. Indications on task completions and statistics are always delivered (regardless of the value of the flag). The value of this property affects the XML API Server. |
xml.api.trace.apl.calls | This property logs APL requests and responses in the XML API server log (property xml.api.server.log). This property is set to true; however, at the time of application deployment, it should be set to false. The value of this property affects the XML API Server. |
xml.api.trace.apl.indications | This property logs APL indications in the XML API server log (property xml.api.server.log). This property is set to true; however, at the time of application deployment, it should be set to false. The value of this property affects the XML API Server. |
xml.api.trace.user.requests | This property records user application requests in the XML API server log (property xml.api.server.log). This property is set to true; however, at the time of application deployment, set it to false. The value of this property affects the XML API Server. |
xml.api.quota.poll.offset | This property affects the exact time of the poll. By default, the tree quota cache is populated once a day. The time is specified in minutes, starting at midnight (Control Station local time) when the poll starts. The value of this property affects the XML API Server. |