RE: SystemName issue while Creating FIlter and Handler Instances
2005-06-01 21:54:29 GMT
Hi Carol
Thanks once again for very timely and detail response. I truly appreciate it. Out of the following option looks like option 1 will work for me.
Thanks once again
Urvish
-----Original Message-----
From: Graves, Carol Ann Krug
[mailto:carolann.graves <at> hp.com]
Sent: Wednesday, June
01, 2005 2:17 PM
To: Urvish Shah
Subject: RE: SystemName issue
while Creating FIlter and Handler Instances
Hi Urvish,
In this case, I assume that you no longer have the path returned from the Create Instance operation. In that case, it seems there would be a few possibilities:
1) Enumerate Filter/Handler instance names, select the desired one based on the Name property value, and use that instance name in the Get Instance operation.
2) Enumerate CIM_ComputerSystem instance names, and use the CreationClassName property value to set the Filter/Handler instance name SystemCreationClassName property value, and use that instance name in the Get Instance operation.
3) Try the Filter/Handler Create Instance operation, and check for an exception that the instance already exists.
Carol Ann
P.S. I belileve the Pegasus FAQ is accessible without a login at http://www.openpegasus.org/pf/.
Carol Ann Krug
Graves carolann.graves <at> hp.com
Hewlett-Packard Company 408-447-5208
-----Original Message-----
From: Urvish Shah [mailto:urvish.shah <at> promise.com]
Sent: Wednesday, June 01, 2005 1:48 PM
To: Graves, Carol Ann Krug
Subject: RE: SystemName issue while Creating FIlter and Handler InstancesHi Carol
Thanks for the prompt response. Actually I am checking if the oldInstance (of either Handler/Filter) does not exist then only create the new one. So to get the particular oldInstance I need to pass those Keys (SystemName, SystemCreation etc.) right? Or is there any solution for this.
--Urvish
Urvish Shah
Software Engineer
Advance Storage Group
Promise Technology Inc
580 Cottonwood Drive
Milpitas, CA95035
Tel: 408-228-1580
CONFIDENTIALITY NOTICE: The information contained in or attached to this email message is either proprietary and/or confidential information, or information intended solely for the use of the individual or entity named above. If the reader of this message is not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify us by email and delete the original message from your computer/server with confirmation to us that you have done so. Thank you.
-----Original Message-----
From: Graves, Carol Ann Krug [mailto:carolann.graves <at> hp.com]
Sent: Wednesday, June 01, 2005 1:13 PM
To: Urvish Shah
Subject: RE: SystemName issue while Creating FIlter and Handler Instances
Hi Urvish,
Sorry about that. I had thought that everyone could view the FAQ using the login they use to log in to the http://www.openpegasus.org website, but apparently that's not true. I've sent a message to Martin asking about making the FAQ public. In the meantime, the entry that I was pointing you to is as follows:
Topic:
IND
Question:
4. What are the recommended settings for the SystemCreationClassName, SystemName, or CreationClassName key property values when creating indication filter and listener destination instances?
Answer:
When an indication filter or listener destination instance is created, if the SystemCreationClassName, SystemName, or CreationClassName key property does not exist or has a NULL value, the Indication Service adds the property with the correct value or sets the property to the correct value. If the property does exist and has a non-NULL value, the Indication Service validates these property values, and rejects any instance with invalid key property values. (Note that a blank string or empty string is not a NULL value, and is an invalid value for a CIM class name or system name.) The SystemCreationClassName must match the value of the CreationClassName property of the ComputerSystem provider instance for the system on which the instance is being created (i.e. 'CIM_ComputerSystem' for HP-UX systems). The SystemName must match the value of the Name property of the ComputerSystem provider instance for the system on which the instance is being created (i.e. the fully qualified hostname, e.g. 'ahost.region.acme.com'). The CreationClassName must match the correct class name for the instance being created (e.g. 'CIM_IndicationFilter', 'CIM_ListenerDestinationCIMXML'). The recommended behavior for a client creating an indication filter or listener destination instance is to NOT include the SystemCreationClassName, SystemName, or CreationClassName key properties in the instance. The Indication Service will add each property to the instance with the correct value.
Visibility:
Public
Created by:
carolann.graves on 07-Feb-2005
Updated by:
carolann.graves on 08-Feb-2005
Archived:
No - archive ?
Cheers,
Carol Ann
Carol Ann Krug Graves carolann.graves <at> hp.com
Hewlett-Packard Company 408-447-5208-----Original Message-----
From: Urvish Shah [mailto:urvish.shah <at> promise.com]
Sent: Wednesday, June 01, 2005 12:41 PM
To: Graves, Carol Ann Krug
Subject: RE: SystemName issue while Creating FIlter and Handler InstancesHi Carol
Clicking on the link is asking for the username and password. I am not sure how to get it
Thanks
Urvish
Urvish Shah
Software Engineer
Advance Storage Group
Promise Technology Inc
580 Cottonwood Drive
Milpitas, CA95035
Tel: 408-228-1580
CONFIDENTIALITY NOTICE: The information contained in or attached to this email message is either proprietary and/or confidential information, or information intended solely for the use of the individual or entity named above. If the reader of this message is not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify us by email and delete the original message from your computer/server with confirmation to us that you have done so. Thank you.
-----Original Message-----
From: Graves, Carol Ann Krug [mailto:carolann.graves <at> hp.com]
Sent: Wednesday, June 01, 2005 12:37 PM
To: Urvish Shah; pegasus-l <at> openpegasus.org
Subject: RE: SystemName issue while Creating FIlter and Handler Instances
Hi Urvish,
Please see the Pegasus FAQ entry on this topic:
The recommended behavior for a client creating an indication filter or listener destination instance is to NOT include the SystemCreationClassName, SystemName, or CreationClassName key properties in the instance. The Indication Service will add each property to the instance with the correct value.
Carol Ann
Carol Ann Krug Graves carolann.graves <at> hp.com
Hewlett-Packard Company 408-447-5208-----Original Message-----
From: Urvish Shah [mailto:urvish.shah <at> promise.com]
Sent: Wednesday, June 01, 2005 11:51 AM
To: pegasus-l <at> openpegasus.org
Subject: SystemName issue while Creating FIlter and Handler Instances
Hi All
I have some issues regarding the Event subscription.
We create event subscription by creating instances of
1) Filter
2) Handler
3) Subscription
For Filter and Handler “SystemName” is part of a key. “SystemName” expects the full computer Name with DNS (for the host computer where CIMOM is running). I need to know dynamically the full computer name from the IP. I am using Java as CIMClient and JAVA’s InetAddress just returns hostName (e.g. computerName NOT computerName.company.com) from IP. So it is throwing”invalid parameter” Exception.
Is there any way to handle this?
Thanks In advance.
Urvish
Urvish Shah
Software Engineer
Advance Storage Group
Promise Technology Inc
580 Cottonwood Drive
Milpitas, CA95035
Tel: 408-228-1580
CONFIDENTIALITY NOTICE: The information contained in or attached to this email message is either proprietary and/or confidential information, or information intended solely for the use of the individual or entity named above. If the reader of this message is not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify us by email and delete the original message from your computer/server with confirmation to us that you have done so. Thank you.
RSS Feed