CN111722846B - A method and device for CIM interface customization compatible with multiple OEM products - Google Patents

Abstract

The invention provides a method and equipment for customizing a CIM interface compatible with multiple OEM products, wherein the method comprises the following steps: defining a compiling configuration file; carrying out macro control on OEM custom fields in each CIM interface, and compiling the OEM custom fields according to the macro control; modifying OEM information of a static file in a CIM interface code library according to the compiling configuration file; and converting the OEM information and the original manufacturer information mutually. By using the scheme of the invention, a plurality of OEM edition packages can be simultaneously constructed under the condition of one set of codes and integrated into the system ISO mirror image of the corresponding OEM edition, thereby avoiding the conditions of modifying the codes for many times, maintaining a plurality of code branches and constructing CIM interfaces for many times, greatly improving the development efficiency, saving the code maintenance cost, ensuring the information safety and the software stable operation of the OEM manufacturer because the CIM interfaces of the OEM edition can only operate on the corresponding OEM product platform.

Description

A method and device for CIM interface customization compatible with multiple OEM products

technical field

The art relates to the computer field, and more particularly to a method and device for CIM interface customization compatible with various OEM products.

Background technique

The storage system provides a CIM (Common Information Model, common information model) interface externally, so that users can manage and monitor the storage system. Since the storage system will be customized by OEM (Original Equipment Manufacturer, OEM or original equipment manufacturer), the CIM interface also needs to be modified or developed by OEM. In the current development process, according to the needs of each OEM manufacturer, it is necessary to establish a separate code branch, modify the manufacturer information in the existing source code, and develop OEM customization functions on this basis. After completing the function development, you need to compile and build the installation package separately and install it on the corresponding OEM platform. As the number of OEM manufacturers increases, the amount of code to be maintained increases gradually. If the code version is updated, it is necessary to update the code for each OEM code branch, and build the software installation package separately, which increases the workload of code maintenance and software version construction.

SUMMARY OF THE INVENTION

In view of this, the purpose of the embodiments of the present invention is to propose a method and device for CIM interface customization compatible with multiple OEM products. By using the method of the present invention, multiple OEM version packages can be simultaneously constructed under a set of codes, And integrated into the system ISO image of the corresponding OEM version, avoiding the need to modify the code multiple times, maintain multiple code branches, and build the CIM interface multiple times, which greatly improves the development efficiency and saves the cost of code maintenance. The OEM version of the CIM interface is only It can run on the corresponding OEM product platform, which ensures the information security of the OEM manufacturer and the stable operation of the software.

Based on the above object, an aspect of the embodiments of the present invention provides a method for customizing a CIM interface compatible with multiple OEM products, including the following steps:

Define the compilation configuration file;

Perform macro control on the OEM custom fields in each CIM interface, and compile the OEM custom fields according to the macro control;

Modify the OEM information of the static files in the CIM interface code base according to the compilation configuration file;

Convert OEM information and original manufacturer information to each other.

According to one embodiment of the present invention, the compilation configuration file contains OEM manufacturer information, a static file list, original manufacturer terms, and OEM terms.

According to an embodiment of the present invention, performing macro control on the OEM customized fields in each CIM interface, and compiling the OEM customized fields according to the macro control includes:

In the development stage of the CIM interface function, judge whether the code corresponding to the OEM custom field needs to be compiled through macro control;

In response to the need to compile the code corresponding to the OEM custom field, the macro compiles the above code, and enables the CIM interface function to support the compiled OEM custom field.

According to an embodiment of the present invention, modifying the OEM information of the static file in the CIM interface code base according to the compilation configuration file includes:

According to the compilation configuration file, modify and compile the static files for each configured OEM product in turn;

Package each OEM product into a CIM interface software package;

Decompress the CIM interface software package and integrate it into the system ISO image of the corresponding OEM version.

According to an embodiment of the present invention, the mutual conversion between the OEM information and the original manufacturer information includes:

When the CIM interface processes the request, replace the OEM information in the request with the original manufacturer information;

When the CIM interface returns the result, replace the original manufacturer information in the returned result with the corresponding OEM manufacturer information.

Another aspect of the embodiments of the present invention also provides a CIM interface customization device compatible with multiple OEM products, the device includes:

Define the module, define the module configuration to define the compilation configuration file;

The compilation module is configured to perform macro control on the OEM customized fields in each CIM interface, and compile the OEM customized fields according to the macro control;

Modify the module, modify the module configuration to modify the OEM information of the static file in the CIM interface code base according to the compilation configuration file;

The conversion module, the conversion module is configured to convert the OEM information and the original manufacturer information to each other.

According to one embodiment of the present invention, the compilation configuration file contains OEM manufacturer information, a static file list, original manufacturer terms, and OEM terms.

According to an embodiment of the present invention, the compilation module is further configured to:

In the development stage of the CIM interface function, judge whether the code corresponding to the OEM custom field needs to be compiled through macro control;

In response to the need to compile the code corresponding to the OEM custom field, the macro compiles the above code, and enables the CIM interface function to support the compiled OEM custom field.

According to an embodiment of the present invention, the modification module is further configured to:

According to the compilation configuration file, modify and compile the static files for each configured OEM product in turn;

Package each OEM product into a CIM interface software package;

Decompress the CIM interface software package and integrate it into the system ISO image of the corresponding OEM version.

According to an embodiment of the present invention, the conversion module is further configured to:

When the CIM interface processes the request, replace the OEM information in the request with the original manufacturer information;

When the CIM interface returns the result, replace the original manufacturer information in the returned result with the corresponding OEM manufacturer information.

The present invention has the following beneficial technical effects: the method for customizing a CIM interface compatible with multiple OEM products provided by the embodiment of the present invention compiles a configuration file by defining it; performs macro control on the OEM custom fields in each CIM interface, and controls the OEM customization fields according to the macro control. Compile the OEM custom field; modify the OEM information of the static file in the CIM interface code base according to the compilation configuration file; the technical scheme of converting the OEM information and the original manufacturer information to each other, can build multiple OEM versions at the same time under a set of codes package, and integrated into the system ISO image of the corresponding OEM version, avoiding the need to modify the code multiple times, maintain multiple code branches, and build the CIM interface multiple times, which greatly improves the development efficiency and saves the cost of code maintenance. The OEM version of CIM The interface can only run on the corresponding OEM product platform, which ensures the information security of the OEM manufacturer and the stable operation of the software.

Description of drawings

In order to explain the embodiments of the present invention or the technical solutions in the prior art more clearly, the following briefly introduces the accompanying drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only These are some embodiments of the present invention. For those of ordinary skill in the art, other embodiments can also be obtained according to these drawings without creative efforts.

FIG. 1 is a schematic flowchart of a CIM interface customization method compatible with multiple OEM products according to an embodiment of the present invention;

FIG. 2 is a schematic diagram of a CIM interface customization device compatible with multiple OEM products according to an embodiment of the present invention.

Detailed ways

In order to make the objectives, technical solutions and advantages of the present invention more clearly understood, the embodiments of the present invention will be further described in detail below with reference to the specific embodiments and the accompanying drawings.

Based on the above objective, in a first aspect of the embodiments of the present invention, an embodiment of a method for customizing a CIM interface compatible with multiple OEM products is provided. Figure 1 shows a schematic flow chart of the method.

As shown in Figure 1, the method may include the following steps:

S1 defines a compilation configuration file, which is used to quickly modify the OEM information in the source code;

S2 performs macro control on the OEM customized fields in each CIM interface, and compiles the OEM customized fields according to the macro control;

S3 modifies the OEM information of the static files in the CIM interface code base according to the compilation configuration file. The static files include the configuration files (namespace, request protocol and port, security level, log level, etc.) required for the operation of the CIM interface, and related to the operation of the CIM interface. Script files (start, stop, monitor), MOF files that constrain the CIM interface, and CIM interface source code files;

S4 converts OEM information and original manufacturer information to each other.

The invention firstly defines an OEM compilation configuration file, which is used to quickly modify the OEM information in the source code, so as to ensure that the CIM interface code of the OEM version is correctly compiled and run, and provides static OEM information. Then in the CIM interface development stage, through macro control of the OEM custom fields of each interface code, the control of whether the macro control code is compiled and packaged is realized, and the purpose of a set of codes providing different functions on different OEM platforms is achieved. By providing a transit agent service during the operation of the CIM interface, it can dynamically receive and return OEM information. In the CIM interface compilation and packaging stage, the corresponding OEM version code files and other files are generated according to the content of the OEM compilation configuration file, and then compiled and packaged into the corresponding OEM version CIM interface software package, and used for integration in the subsequent generation of the corresponding OEM version storage system ISO image . Through the above reasonable and effective method, the present invention realizes that a set of CIM interface codes is compiled and constructed at one time to generate CIM interfaces of multiple OEM versions, and the safe and reliable operation of the corresponding OEM products is ensured.

Through the technical scheme of the present invention, multiple OEM version packages can be simultaneously constructed under one set of codes, and integrated into the system ISO image of the corresponding OEM version, thereby avoiding multiple code modification, maintenance of multiple code branches, and multiple constructions. The case of the CIM interface greatly improves the development efficiency and saves the cost of code maintenance. The OEM version of the CIM interface can only be run on the corresponding OEM product platform, which ensures the information security of the OEM manufacturer and the stable operation of the software.

In a preferred embodiment of the present invention, the compilation configuration file contains OEM manufacturer information, a static file list, original manufacturer terms and OEM terms.

In a preferred embodiment of the present invention, performing macro control on the OEM customized fields in each CIM interface, and compiling the OEM customized fields according to the macro control includes:

In the development stage of the CIM interface function, judge whether the code corresponding to the OEM custom field needs to be compiled through macro control;

In response to the need to compile the code corresponding to the OEM custom field, the macro compiles the above code, and enables the CIM interface function to support the compiled OEM custom field. In the CIM interface function development stage, for the fields customized by the OEM, whether the code corresponding to the field is compiled is controlled by the compilation macro, and the compilation module transmits the compilation macros of the corresponding OEM version when compiling the CIM interface of each OEM version. If a compilation macro of an OEM version is passed in, the code segment controlled by the macro will be compiled, and the final CIM interface function will support this field; the code segment controlled by the compilation macro of other OEM versions will not be compiled. The final CIM interface function does not support these fields.

In a preferred embodiment of the present invention, modifying the OEM information of the static files in the CIM interface code base according to the compilation configuration file includes:

According to the compilation configuration file, modify and compile the static files for each configured OEM product in turn;

Package each OEM product into a CIM interface software package;

Decompress the CIM interface software package and integrate it into the system ISO image of the corresponding OEM version. In the software code compilation stage, according to the content of the compilation configuration file, modify and compile the OEM terminology of the static file for each configured OEM product in turn. The output content includes compiled files, script files, MOF files, configuration files, etc. suitable for each OEM platform type, and a CIM interface software package is packaged for each OEM version. These OEM version CIM interface software packages are decompressed and invoked by the higher-level system ISO image packaging module and integrated into the corresponding OEM version system ISO image. After these system ISO images are canned on the products of the corresponding OEM version, the CIM interface can normally provide services of the corresponding OEM version.

In a preferred embodiment of the present invention, the mutual conversion between the OEM information and the original manufacturer information includes:

When the CIM interface processes the request, replace the OEM information in the request with the original manufacturer information;

When the CIM interface returns the result, replace the original manufacturer information in the returned result with the corresponding OEM manufacturer information. In the running phase of the CIM interface, the original manufacturer information and the OEM manufacturer information in the request and response are converted by the dynamic OEM information agent module. Since the CIM interface processes requests and returns responses relying on the system command line (CLI), and the information returned by the system command line is not adapted to the OEM, it is necessary to dynamically convert these information in real time when the CIM interface is running. The details are as follows: when the CIM interface processes the request, the dynamic OEM information proxy module replaces the OEM information in the parameter information in the request with the original manufacturer information, and further processes the request according to the original manufacturer information; when the CIM interface returns a response, the dynamic OEM information The proxy module replaces the original manufacturer information in the returned result with the corresponding OEM manufacturer information.

Through the technical scheme of the present invention, multiple OEM version packages can be simultaneously constructed under one set of codes, and integrated into the system ISO image of the corresponding OEM version, thereby avoiding multiple code modification, maintenance of multiple code branches, and multiple constructions. The case of the CIM interface greatly improves the development efficiency and saves the cost of code maintenance. The OEM version of the CIM interface can only be run on the corresponding OEM product platform, which ensures the information security of the OEM manufacturer and the stable operation of the software.

It should be noted that those of ordinary skill in the art can understand that all or part of the processes in the methods of the above-mentioned embodiments can be implemented by instructing relevant hardware through a computer program. The above-mentioned programs can be stored in a computer-readable storage medium. When the program is executed, it may include the flow of the embodiments of the above-mentioned methods. The storage medium may be a magnetic disk, an optical disk, a read-only memory (Read-Only Memory, ROM), or a random access memory (Random Access Memory, RAM) or the like. The above computer program embodiments can achieve the same or similar effects as any of the foregoing method embodiments corresponding thereto.

In addition, the methods disclosed according to the embodiments of the present invention may also be implemented as a computer program executed by the CPU, and the computer program may be stored in a computer-readable storage medium. When the computer program is executed by the CPU, the above-mentioned functions defined in the methods disclosed in the embodiments of the present invention are executed.

Based on the above purpose, the second aspect of the embodiments of the present invention provides a CIM interface customization device compatible with multiple OEM products. As shown in FIG. 2 , the device 200 includes:

Define the module, define the module configuration to define the compilation configuration file;

The compilation module is configured to perform macro control on the OEM customized fields in each CIM interface, and compile the OEM customized fields according to the macro control;

Modify the module, modify the module configuration to modify the OEM information of the static file in the CIM interface code base according to the compilation configuration file;

The conversion module, the conversion module is configured to convert the OEM information and the original manufacturer information to each other.

In a preferred embodiment of the present invention, the compilation configuration file contains OEM manufacturer information, a static file list, original manufacturer terms and OEM terms.

In a preferred embodiment of the present invention, the compilation module is further configured to:

In the development stage of the CIM interface function, judge whether the code corresponding to the OEM custom field needs to be compiled through macro control;

In response to the need to compile the code corresponding to the OEM custom field, the macro compiles the above code, and enables the CIM interface function to support the compiled OEM custom field.

In a preferred embodiment of the present invention, the modification module is further configured to:

According to the compilation configuration file, modify and compile the static files for each configured OEM product in turn;

Package each OEM product into a CIM interface software package;

Decompress the CIM interface software package and integrate it into the system ISO image of the corresponding OEM version.

In a preferred embodiment of the present invention, the conversion module is further configured to:

When the CIM interface processes the request, replace the OEM information in the request with the original manufacturer information;

When the CIM interface returns the result, replace the original manufacturer information in the returned result with the corresponding OEM manufacturer information.

It should be particularly pointed out that the embodiments of the above system use the embodiments of the above method to specifically describe the working process of each module, and those skilled in the art can easily think of applying these modules to other embodiments of the above method.

In addition, the above-mentioned method steps and system units or modules can also be implemented by using a controller and a computer-readable storage medium for storing a computer program that enables the controller to implement the functions of the above-mentioned steps or units or modules.

Those skilled in the art will also appreciate that the various exemplary logical blocks, modules, circuits, and algorithm steps described in connection with the disclosure herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described generally in terms of their functionality. Whether such functionality is implemented as software or hardware depends on the specific application and design constraints imposed on the overall system. Those skilled in the art may implement the functions in various ways for each specific application, but such implementation decisions should not be interpreted as causing a departure from the scope of the disclosed embodiments of the present invention.

The above-described embodiments, particularly any "preferred" embodiments, are possible examples of implementations, and are presented merely for a clear understanding of the principles of the invention. Numerous changes and modifications may be made to the above-described embodiments without departing from the spirit and principles of the technology described herein. All modifications are intended to be included within the scope of this disclosure and protected by the appended claims.

Claims (10)

1. a method for customizing the CIM interface compatible with multiple OEM products, is characterized in that, comprises the following steps: Define the compilation configuration file; Perform macro control on the OEM customized fields in each of the CIM interfaces, and compile the OEM customized fields according to the macro control; Modify the OEM information of the static file in the CIM interface code base according to the compilation configuration file; The OEM information and the original manufacturer information are converted into each other. 2 . The method according to claim 1 , wherein the compilation configuration file contains OEM manufacturer information, a static file list, original manufacturer terms and OEM terms. 3 . 3. The method according to claim 1, wherein performing macro control on the OEM customized fields in each of the CIM interfaces, and compiling the OEM customized fields according to the macro control comprises: In the development stage of the CIM interface function, determine whether the code corresponding to the OEM custom field needs to be compiled through the macro control; In response to the need to compile the code corresponding to the OEM custom field, the macro compiles the above code, and enables the CIM interface function to support the compiled OEM custom field. 4. The method according to claim 1, wherein modifying the OEM information of the static file in the CIM interface code base according to the compilation configuration file comprises: According to the compiling configuration file, modify and compile the static file for each configured OEM product in turn; Package each OEM product into a CIM interface software package; The CIM interface software package is decompressed, invoked, and integrated into the system ISO image of the corresponding OEM version. 5. The method according to claim 1, wherein the mutual conversion of the OEM information and the original manufacturer information comprises: When the CIM interface processes the request, replace the OEM information in the request with the original manufacturer information; When the CIM interface returns a result, the original manufacturer information in the returned result is replaced with the corresponding OEM manufacturer information. 6. A CIM interface customized equipment compatible with multiple OEM products, wherein the equipment comprises: a definition module, the definition module is configured to define a compilation configuration file; a compiling module, the compiling module is configured to perform macro control on the OEM custom fields in each of the CIM interfaces, and compile the OEM custom fields according to the macro control; a modification module, the modification module is configured to modify the OEM information of the static file in the CIM interface code base according to the compilation configuration file; A conversion module, the conversion module is configured to convert the OEM information and the original manufacturer information to each other. 7 . The device according to claim 6 , wherein the compilation configuration file contains OEM manufacturer information, a static file list, original manufacturer terms and OEM terms. 8 . 8. The device according to claim 6, wherein the compiling module is further configured to: In the development stage of the CIM interface function, determine whether the code corresponding to the OEM custom field needs to be compiled through the macro control; In response to the need to compile the code corresponding to the OEM custom field, the macro compiles the above code, and enables the CIM interface function to support the compiled OEM custom field. 9. The device according to claim 6, wherein the modification module is further configured to: According to the compiling configuration file, modify and compile the static file for each configured OEM product in turn; Package each OEM product into a CIM interface software package; The CIM interface software package is decompressed, invoked, and integrated into the system ISO image of the corresponding OEM version. 10. The device according to claim 6, wherein the conversion module is further configured to: When the CIM interface processes the request, replace the OEM information in the request with the original manufacturer information; When the CIM interface returns a result, the original manufacturer information in the returned result is replaced with the corresponding OEM manufacturer information.

Images