This tool is designed to ease compliance in CIM (Common Information Model) client programming in Java™. Because CIM is an object-based standard, this tool provides a way to map all the CIM objects to corresponding Java objects based on the CIM class definitions. The Java developer can then create, modify, or delete the appropriate CIM objects by manipulating Java instances. This tool makes the development process easier for the developer who is competent in Java programming but less familiar with CIM standards.

This tool is integrated with both CIM client function and MOF language compiling (Managed Object Format, a language based on the Object Management Group's Interface Definition Language); therefore, users can generate the Java mapping source code either from an existing CIMOM (CIM Object Manager) or from MOF files. The Java mapping source code generated from this tool complies with the JSR 48 specification (Java Specification Requests for WBEM Services). The mapping between CIM and Java is designed to strongly integrate the CIM and corresponding Java objects.

How does it work?

A typical work flow is as follows:

1. Put the MOF definition from the source (MOF files or CIMOM) into this tool.
2. Compile the information into the memory.
3. Using the template tool, map the CIM information in memory to Java mapping source code files in disk.

After that, users merely need to integrate the resultant Java files and required third-party libraries into their target project.

The Java mapping architecture uses two separate layers: a mapping layer and a communication layer. In the mapping layer, the equivalent Java class corresponding to the appropriate CIM class calls the communication layer to begin a dialog with the CIMOM. The communication layer is based on the CIM-XML protocol and the SBLIM (Standards-Based Linux® Instrumentation) client library. Because the communication layer is called directly from the mapping layer, it is not revealed to a developer; therefore, the developer does not have to deal with the communication layer and can focus solely on the mapping layer.

Working solely with the mapping layer greatly simplifies development because the APIs provided with this tool can handle requirements for using OO (object-oriented) features that are compliant with the JSR 48 standard. This tool is both powerful and easy to use.