The DFSMSrmm CIM provider application programming interface uses the DFSMSrmm Web service by means of a proxy integrated with the provider. Thus, you must implement the Web service and, optionally, publish it in a local UDDI registry. This enables the provider application programming interface to find the DFSMSrmm system that can return details about volumes, data sets, their associations, and other resources managed by DFSMSrmm.

If you do not use a UDDI registry, you must define the URL of any DFSMSrmm Web service in the rmmcust.properties file. Each system (one per RMMplex) that you want the provider application programming interface to query must have a separate Web service and each must be either published in a UDDI or defined in the rmmcust.properties file. The DFSMSrmm CIM provider finds each Web service and calls each to ensure that all resources across all DFSMSrmm systems can be reported. The first subcommand determines the settings in use for the DFSMSrmm subsystem, such as CDSID and DATEFORM. The CDSID value is used to uniquely identify each RMMplex. Thus, make sure the CDSID is unique. If a duplicate system is found, only the first occurrence of that system is used. The DATEFORM value is used to ensure that date values are interpreted correctly and then correctly converted to date attributes in the CIM classes.

http://sourceforge.net/project/showfiles.php?group_id=128809