Re: embedded CIM Instance

Marek is correct.  You are not the only one 
having issues with differences between the way 
Pegasus handles embedded Instances and SFCB 
does.  Talking right not to a couple of 
other  users that see the difference but I have 
not looked at trace from SFCB  server - client 
yet to see what it actually sends.

Background, at least for CIM/XML

The CIM/XML protocol helps the receiver by 
providing a set of attributes for the String 
properties that represent embedded 
instances/objects (See DSP0201) so that the 
receiver will know that the Strings are actually 
embedded instances/qualifiers without having the 
Class itself.  Pegasus does send these attributes 
(EMBEDDED OBJECT ...) and Pegasus also converts 
the String back to the Pegasus extensions to the 
CIMData types (CIMInstance or CIMObject).

We are in the proces of extending the command 
line tool cimcli to be able to create and display 
these embedded entities (see PEP 361 and bug 9007) and it does work in Pegasus.

In fact recursive embedding works (embedded 
object properties within embedded object properties).

Karl
Thanks for your message at 07:22 AM 8/22/2011. Your message was:
>What you describe sounds a lot like Sfcb does 
>not handle embedded instances very well. To 
>determine if that's actually the case you could 
>track the CIM-Xml exchanged between your client and the CIMOM.
>If it proves true that SFCB does not write the 
>EmbeddedInstance qualifier, you should open a Bug against SFCB.
>
>
>
>Mit freundlichen Grüßen / Kind regards
>Marek Szermutzky
>
>Software Engineer / OpenPegasus Maintainer (PMC) and z/OS PlatformRep.
>IBM Systems &Technology Group, Systems Software 
>Development / z/OS Capacity Management and Support
>-------------------------------------------------------------------------------------------------------------------------------------------
>IBM Deutschland
>Schoenaicher Str. 220
>71032 Boeblingen
>Phone: +49-7031-16-5182
>E-Mail: [email protected]
>-------------------------------------------------------------------------------------------------------------------------------------------
>IBM Deutschland Research & Development GmbH / 
>Vorsitzender des Aufsichtsrats: Martin Jetter
>Geschäftsführung: Dirk Wittkopp
>Sitz der Gesellschaft: Böblingen / 
>Registergericht: Amtsgericht Stuttgart, HRB 243294
>
>
>
>From:        Karl Schopmeyer <[email protected]>
>To:        <[email protected]>, <[email protected]>
>Date:        19.08.2011 17:18
>Subject:        Re: embedded CIM Instance
>
>
>
>
>What to the strings look like and what does the 
>cim/xml look like?  If the cim/xml does not 
>contain the embeddedobject attribute for the 
>property, the client could not determine if the 
>strings received are actually embedded 
>objects.  Remember that in cim/xml today.
>
>1. EmbeddedInstance and object properties are 
>defined in mof as a string type with a qualifier 
>to identify them as embedded objects or instances.
>2. The embedded instance is normally encoded in 
>the cim/xml protocol/encoding as xml with the 
>xml special characters escaped and the embedded 
>Object attribute in the cimx/ml to tell the 
>receiver that this is an embedded object.
>
>3. In pegasus, we actually added an 
>embeddedinstance DataType and attempt in the 
>client infrastructure to decode your object if the attribute is attached.
>
>Note that we are finishing some extensions to 
>our command line client tool cimcli that adds 
>capabilities for embedded instance/object 
>creation, display, etc. and that will shortly be 
>in Pegasus head of tree  It can be seen now as 
>bug 9007 (preliminary) and PEP 361.
>
>Karl
>Thanks for your message at 11:53 PM 8/18/2011. Your message was:
>Hi all,
>   We need to return an array of CIM Instances 
> in a vendor extension method in our CMPI 
> Provider. we have defined the method as follows:
>
>uint32 xxx(
>
>[IN (false), OUT, Description ("xxx"), EmbeddedInstance( "Our_Class")]
>
>string instances[]);
>
> From provider code we are adding out argument of type CMPI_instanceA.
>Our client uses SBLIM 2.0.9.3 to get CIM 
>Instances. When we are using OpenPegasus as a 
>CIMOM, client receives the data as an array of 
>CIM Instances properly. But when we use SFCB in 
>Vmware ESX as CIMOM . Client is receiving it as 
>array of strings only, not as CIM Instances.
>
>Any help?
>
>
>Thanks and regards,<?xml:namespace prefix = o ns 
>= "urn:schemas-microsoft-com:office:office" />
>
>Souvik Roy
>
>Wipro Technologies
>
>Block - DM, Sector -V Salt Lake. Kolkata- 
>700091. <?xml:namespace prefix = st1 ns = 
>"urn:schemas-microsoft-com:office:smarttags" />India
>
>VOIP: 8584750
>
>Direct: +91 33 30954750
>
>
>
>Only when the last tree has died and the last 
>river been poisoned and the last fish been 
>caught will we realise we cannot eat money
>
>
>Please do not print this email unless it is absolutely necessary.
>
>The information contained in this electronic 
>message and any attachments to this message are 
>intended for the exclusive use of the 
>addressee(s) and may contain proprietary, 
>confidential or privileged information. If you 
>are not the intended recipient, you should not 
>disseminate, distribute or copy this e-mail. 
>Please notify the sender immediately and destroy 
>all copies of this message and any attachments.
>
>WARNING: Computer viruses can be transmitted via 
>email. The recipient should check this email and 
>any attachments for the presence of viruses. The 
>company accepts no liability for any damage 
>caused by any virus transmitted by this email.
>
><http://www.wipro.com/>www.wipro.com
>
>Karl Schopmeyer                   Inova Development Inc.
>305 Spring Creek Village, Suite 475 -  Dallas TX, 75248 USA
>EMAIL: [email protected]       FAX: 1-972-239-0326
>Phone 1-972-814-5581
>Skype: kschopmeyer         Skype Phone: (214) 556-5971

Karl Schopmeyer                   Inova Development Inc.
305 Spring Creek Village, Suite 475 -  Dallas TX, 75248 USA
EMAIL: [email protected]       FAX: 1-972-239-0326
Phone 1-972-814-5581
Skype: kschopmeyer         Skype Phone: (214) 556-5971