CIM Event Unified Automated Testing Framework

The Public Information model (Common information MODEL,CIM) provides an event (indication) notification mechanism in which clients notify the CIM subscription event, and when the subscription event occurs, all clients subscribing to the event receive the appropriate message. The current test mode is: Event subscription and event triggering are performed by different applications, requiring testers to subscribe, trigger, and verify notification mechanisms, and different CIM products need to build their own test procedures. Code reusability is poor and automation of testing is not possible.

Introduction to CIM indication mechanism

The Public Information Model CIM (Common information Model) is a conceptual one that is independent of implementation and describes management information. The CIM provides an event notification (indication) mechanism through which clients can understand what is happening on the server. The implementation steps are:

Indication Subscriptions: A message that the client subscribes to the server for a specific event type.

Indication BUILD: When an event occurs, the server generates a corresponding message.

Indication distribution: The server sends messages to all clients that subscribe to the event type.

Indication receive: The client will receive the appropriate message.

Indication provides 11 types of events: CIM class generation, deletion, modification, CIM Instance generation, deletion, modification, CIM Instance method invocation, CIM Instance read operation, CIM Warning, Java EE notification, SNMP Trap 。 The CIM uses the following class names to represent these 11 event types:

Cim_classcreation

Cim_classdeletion

Cim_classmodification

Cim_instcreation

Cim_instdeletion

Cim_instmethodcall

Cim_instmodification

Cim_instread

Cim_alertindication

Cim_j2eenotification

Cim_snmptrapindication

The present indication test mode introduction and its drawbacks

After understanding the CIM indication mechanism, let's take a look at the current test pattern. The current test mode uses dual-client, manual subscription messages, triggering events, and analysis results.

Subscription message: Open a client to subscribe to a specific type of message.

Trigger event: Open another client to trigger the CIM event.

Close subscription: Closes the subscription client.