Re: Issue while parsing the WSDL file with the Filter set field action.
Abhishek, you will need to make following changes to your webservice 1. Have one part element per message. See how I have created a different message element for header element. So in WSDL it will look like below – CREATE-SERVICE request message. CREATE-SERVICE Response message. 2. Change operation definition in element like below for CREATE-SERVICE operation. Regards, Abhijeet From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Abhishek Anand Sent: 09 July 2017 13:53 To: arslist@ARSLIST.ORG Subject: Issue while parsing the WSDL file with the Filter set field action. ** Hi Experts, We are facing issue while trying to consume a WSDL file via the Filter set field action. Attached is the sample WSDL with three operations. Filter is able to parse the operations but not able to read the parameters within the operations:- Early response is highly appreciated. Cheers, AA _ARSlist: "Where the Answers Are" and have been for 20 years_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
Re: Issue while parsing the WSDL file with the Filter set field action.
Thanks for your kind response. Let me check it out and will revert back shortly. Cheers, AA On 10-Jul-2017 3:47 PM, "Gadgil, Abhijeet" wrote: > ** > > Abhishek, you will need to make following changes to your webservice > > > > 1. Have one part element per message. See how I have created a > different message element for header element. So in WSDL it will look like > below – > > > > <*wsdl:message* name="HEADER"> > > <*wsdl:part* name="osHeader" element="osXSD:OS_Header"/> > > > > > > <*wsdl:message* name="CREATE-SERVICE"> > > <*wsdl:documentation*>CREATE-SERVICE request message. *wsdl:documentation*> > > <*wsdl:part* name="osBody" element="osXSD:CREATE-SERVICE"/> > > > > > > <*wsdl:message* name="CREATE-SERVICEResponse"> > > <*wsdl:documentation*>CREATE-SERVICE Response message. *wsdl:documentation*> > > <*wsdl:part* name="osBody" element="osXSD:CREATE-SERVICEResponse"/> > > > > > > 2. Change operation definition in element like below > for CREATE-SERVICE operation. > > <*wsdl:input*> > > <*soap:header* message="osWS: HEADER" part="osHeader" use > ="literal"/> > > <*soap:body* parts="osBody" namespace="os.ws.v1" use > ="literal"/> > > > > <*wsdl:output*> > > <*soap:body* parts="osBody" namespace="os.ws.v1" use > ="literal"/> > > > > > > Regards, > > Abhijeet > > > > *From:* Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] *On Behalf Of *Abhishek Anand > *Sent:* 09 July 2017 13:53 > *To:* arslist@ARSLIST.ORG > *Subject:* Issue while parsing the WSDL file with the Filter set field > action. > > > > ** Hi Experts, We are facing issue while trying to consume a WSDL file via > the Filter set field action. Attached is the sample WSDL with three > operations. Filter is able to parse the operations but not able to read the > parameters within the operations:- Early response is highly appreciated. > Cheers, AA _ARSlist: "Where the Answers Are" and have been for 20 years_ > _ARSlist: "Where the Answers Are" and have been for 20 years_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
Re: Issue while parsing the WSDL file with the Filter set field action.
Hi Abhijeet, Thanks for your kind response. I am uploading the updated file again. Please could you elaborate in detail so as to amend the WSDL file to be consumed by filter & can parse the operations as well as its parameters. Cheers, AA ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years" http://www.w3.org/2001/XMLSchema"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";> Indicates the ORDERID Indicates the PONPortAlias Indicates the ONTSN Indicates the ORDERID Indicates the PONPortAlias Indicates the ONTSN FDN Account FDN CustomerName ServiceType Account SIPUSERNAME SIPUSERPWD WANPPPOEUSERNAME WANPPPOEUSERPWD The type of exception returned by failed invokation of an message request. The exception type based on the enumeration A string indicating further details about the exception. It is a free format string filled by the OS. None objects Parameters. The generic exception message. CREATE-SERVICE
DMT - Did not find Remedy Application Service password Question
We have been using DMT for years until this week. We now get an error when trying to import an XLS "Did not find Remedy Application Service password for server Bozo in UDM:RAppPassword Form on server Bozo" The weird thing is the servername Bozo that is referenced in the error log is not a server we have in our environment. I have no idea where this name came from or why DMT is now looking for this server. Our UDM:Config and UDM:RapPassword have no reference to this form. Does anyone know what form the DMT might be looking at to pull this info. Thanks ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
Re: DMT - Did not find Remedy Application Service password Question
Hi Kevin, Just a quick guess, check if said job was imported from somewhere and it may have references to this bozo server. Mostly this reference should be there in UDM:Permission form.(not exact name but search for permission form). Thanks, Vinod Gaidhani Ph# 346-907-1599 > On 10-Jul-2017, at 4:43 PM, Kevin Shaffer wrote: > > ** > We have been using DMT for years until this week. We now get an error when > trying to import an XLS "Did not find Remedy Application Service password for > server Bozo in UDM:RAppPassword Form on server Bozo" > > > > The weird thing is the servername Bozo that is referenced in the error log is > not a server we have in our environment. I have no idea where this name > came from or why DMT is now looking for this server. > > > > Our UDM:Config and UDM:RapPassword have no reference to this form. > > > > Does anyone know what form the DMT might be looking at to pull this info. > > > > Thanks > > > _ARSlist: "Where the Answers Are" and have been for 20 years_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
Re: DMT - Did not find Remedy Application Service password Question
So it appears a transformation was migrated from a sandbox to this dev box. When it was done the DB connection information was changed across all transformations, not sure why. So I found the record in the UDM:Repository Database form that had the wrong information. I exported the record from a working environment and now I get error impersonating user. When I open the transformations in Spoon I can see the Authentication field is populating in with an incorrect value on the DB connection. So there must be one more form that has this information. From: Action Request System discussion list(ARSList) on behalf of Vinod Gaidhani Sent: Monday, July 10, 2017 4:57:16 PM To: arslist@ARSLIST.ORG Subject: Re: DMT - Did not find Remedy Application Service password Question ** Hi Kevin, Just a quick guess, check if said job was imported from somewhere and it may have references to this bozo server. Mostly this reference should be there in UDM:Permission form.(not exact name but search for permission form). Thanks, Vinod Gaidhani Ph# 346-907-1599 On 10-Jul-2017, at 4:43 PM, Kevin Shaffer mailto:kshaf...@partneritsm.com>> wrote: ** We have been using DMT for years until this week. We now get an error when trying to import an XLS "Did not find Remedy Application Service password for server Bozo in UDM:RAppPassword Form on server Bozo" The weird thing is the servername Bozo that is referenced in the error log is not a server we have in our environment. I have no idea where this name came from or why DMT is now looking for this server. Our UDM:Config and UDM:RapPassword have no reference to this form. Does anyone know what form the DMT might be looking at to pull this info. Thanks _ARSlist: "Where the Answers Are" and have been for 20 years_ _ARSlist: "Where the Answers Are" and have been for 20 years_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
