Call for topics!


Well, we are coming to the end of the first itinerary through ILM “2” extensibility.  Keeping this blog to the schedule has been a fun learning experience for me, and I appreciate the feedback.  I hope it is clear from this and the other ILM “2” blogs that we are shipping a quality product which provides real customer value.  I especially am grateful to see some of the experiments people tried after reading this blog.  Two shout outs to Bahram Rushenas at Microsoft and Thomas Thomsen Skovsende at Omada.  ILM “2” is fortunate to have fantastic partners.

As you see from the initial schedule in Topic 1, we do not have topics planned past the first week in January.  To ensure we provide thorough content, we would like to plan ahead which topics we cover in the new year.  What would you like to see?  What about ILM “2” extensibility would you like to learn more about?

Send me your comments either at my work email address or leave a comment below.  There is no deadline, per se, but sooner is always better.  We will pick up the blog again the first week of February.


Comments (8)
  1. Donatas Vyzas says:

    In the client there is ILMSchema.xsd file. Is there posibility to update this file automatically, after I have updated the schema?

  2. Colin Gormley says:

    How to put objects into the system like a new object type for example.

  3. Tomek says:

    How to utilize ILM2 web services for reporting purposes. How to construct XPath queries to get different kind of information related to changes in objects from web service.

  4. Joe Schulman says:

    # Donatas Vyzas said on December 16, 2008 8:36 AM:

    > In the client there is ILMSchema.xsd file. Is there posibility to update this file automatically, after I have updated the schema?

    Great question: the ILMSchema.xsd is there to bridge functionality between RC and RTM.  In RC the client must tell the server what data types it is sending in requests.  The server checks that the client is correct about the data types before processing the request.  We originally thought this was a security feature, but we decided to remove the requirement for RTM since it only complicates building a client.

    Rather than implement a full-blown schema management class which auto-updates schema, etc., we added the static copy of ILM schema in RC.  The client reads the schema from the file when making requests.  This file will not be needed in RTM.

    To update the file, I recommend adapting Topic 14 (http://blogs.msdn.com/imex/archive/2008/12/14/sample-scenario-get-ilm-schema.aspx) to output XSD.

  5. Joe Schulman says:

    # Colin Gormley said on December 16, 2008 11:23 AM:

    > How to put objects into the system like a new object type for example.

    Adding object type descriptions to ILM “2” — the way you add new object types — is conceptually similar to Topic 15 (http://blogs.msdn.com/imex/archive/2008/12/19/sample-scenario-create-a-new-group.aspx).  However, I think this is a good topic worth covering on its own.

  6. Joe Schulman says:

    # Tomek said on December 19, 2008 6:08 AM:

    > How to utilize ILM2 web services for reporting purposes. How to construct XPath queries to get different kind of information related to changes in objects from web service.

    Great idea.  I have added this to the list of topics we will cover.

    I recommend watching out for posts by Nima Ganjeh (http://blogs.technet.com/doittoit/) who knows a lot about PowerShell and everything about querying in ILM "2".

  7. Nima Ganjeh says:

    # Colin Gormley said on December 16, 2008 11:23 AM:

    > How to put objects into the system like a new object type for example.

    If you are interested specifically in extending the schema, for a detailed walkthrough on how to do this I would recommend reading the step-by-step on this blog post:  http://blogs.technet.com/doittoit/archive/2008/06/25/extending-ilm-2-to-manage-and-provision-computer-objects.aspx

Comments are closed.

Skip to main content