Intel® AMT Developers: Please stop using SOAP!

Of course by that I mean that moving forward with developing applications for Intel® Active Management Technology you should no longer be including Simple Object Access Protocol as a basis for your software implementation.  Instead, you should use the WS-MAN interface that is provided in the Intel AMT Software Development Kit.

A little history and the reason why we must talk about this is simple.  Years ago, I wrote a blog warning the world of the imminent end to the relationship between Intel® AMT and SOAP.  Of course, I was vague on when this would actually happen.  Well the light is now at the end of the tunnel and the train is coming in very fast. So with this blog, I would like to provide some coaching on how to handle your Intel AMT development moving forward: (Note: Starting with Intel AMT Release 3.2, the WS-Management API is used to manage all Intel AMT features. The deprecated SOAP API should not be used in new applications, as it does not support newer Intel AMT capabilities.)

Scenario 1:

“We have been writing Management Console Applications for Intel AMT for many years and we have never used the WS-Man interface.  We are all about SOAP, baby.”

 Advice:  You may notice that in the SDK, it is becoming more and more difficult to find the documentation pertaining to the SOAP APIs.  Many of the APIs have been deprecated (the API is no longer accessible, but the firmware still supports it) and many APIs have been obsoleted (meaning, no more API; firmware no longer supports it.)  You may also have noticed that APIs for the new features being released are no longer offered via the SOAP interface.  Over time, as new Intel AMT platforms are released, you may find that your code no longer works due to the obsoleted SOAP APIs.  You will want to start moving your code over to support the WS-Man interface in order  to keep your application working over time and new Intel AMT releases.

Scenario 2:

“We are brand new to Intel AMT and we just use WS-Man – no SOAP for us. 

Advice: This is good too, however, you may run into a situation where someone wants to run your software on a pre-AMT 3.2 platform and your software will not work (because of the SOAP requirement for older platforms.)  In this case, you would continue writing your software using the WS-Man interface but you will want to run it against the WS-Man Translator when it must run on those older systems.  This tool will convert your WS-Man code back to SOAP for use with those older platforms.  You may want to take a look at Ajith’s Blog which describes the translator in more detail.

Scenario 3:

“We just started writing software supporting Intel AMT.  Code for older (pre-AMT 3.2) platforms is written using the SOAP APIs but all newer development was shifted over to the WS-Man interface.”

Advice:  This is great – your app will not require many changes!  Platforms older than Intel AMT 3.2 do not use the WS-Man interface so using the SOAP interface for them is OK.

Well I hope that ending your relationship with SOAP doesn’t stink too badly.  Let us know if you have any further questions regarding this topic.

Einzelheiten zur Compiler-Optimierung finden Sie in unserem Optimierungshinweis.
Kategorien: