VMWARE SRM API 5.0 HAS SOME CHANGES TO IT!

Okay to begin with, SRM API 5.0 also works with SRM 5.1! SRM is all good and great. But has anyone had a look at what the SRM API has to offer. With SRM 5.1, the API still is the 5.0 API with some minor changes. SRM 5.0 API does support both array based and vSphere replication as well.

Below are some of the important pieces of information that one needs to make sure they are aware of.

Lets begin with some terminology. Although I can write it up – I thought it was better to actually pick some excerpts from the API itself!

• Web service operations – Client interfaces that perform server‐side management and monitoring tasks. Standardized asWeb Services Interoperability Organization (WS‐I) Basic Profile
• WSDL – TheWeb services APIis defined in aWSDL file, which is used by client‐side Web services to create proxy code (stubs)that client applications use to interact with the server. Standardized as Web Services Description Language (WSDL) 1.1.
• SOAP–Client applications invoke operations by sending SOAP formatted messages.When passing data objects between client and server you need to build or parse a SOAP message that contains the data object properties asXML elements corresponding to the message structures described in the WSDL. Standardized byW3C as Simple Object Access Protocol(SOAP) 1.1.
• XML – A textrepresentation scheme similarto HTML but with more stringentregularized syntax. Standardized byW3C as Extensible Markup Language (XML) 1.0.

The SRM API has a wide range of API operations that you can use to call on to SRM. Some are listed below,

ListProtectionGroups

ListReplicatedDatastores

GetProtectionState

ProtectVms

GetProtectionStatus

ListPlans

GetRecoveryResult

Accessing the SRM server has changed a tad bit – with the port groups. The location of the API is in the <installdir>/www and the API uses the following listener port of 9007.  Remember that it talks over HTTPS!

The WSDL information can be obtained from the SRM API by requesting the file /srm.wsdl on the port 9085. This is a non HTTPS port. SRM API talks to two different ports to serve both internal and external requests. For internal it talks oer 8095 port while externally it talks over 9007. That means to talk to SRM API you have to connect to it over 9007 port while internally SRM talks to the other SRM server over 8095 port that is proxied by the vcenter servers over http port 80 or https port of 8095.

Hope this helps 🙂 Please comment