Jarl, I've read the relevant parts of:

White Paper
September 27, 2006
BMC ® Remedy® IT Service Management 7.0 Integrations

and

BMC® Remedy® Action Request System® 7.0
Integrating with Plug-ins and Third-Party Products

As well as browsing through a large number of others looking in vain for any
details of BackChannel (the latter is sort of documented in the performance
testing document).

Is there any other document which would be relevant to what I'm trying to
achieve? 

And would further examination of the documentation help me without your
other pre-requsite being satisfied?


If you trying to create and integration into AR System be sure to have
access to a person who got admin privilegies.

Reading the documentation is also a good start.

--
Jarl




2009/7/23 grenadaguy <[email protected]>:
> It almost certainly would help if I had any administrative access to the
> server, or indeed any access other than with a basic brower and user
> privileges only to open and resolve incidents, however sadly this is not
> the
> case.
>
> It seems like the diagnostics provided by Web Services out of the box are
> just as cryptic as those with BackChannel? At least with BackChannel I was
> able to get an incident number separately from the request that actually
> failed. Also that's a clue that getting an INC# isn't any indication of
> successful incident creation.
>
> Any suggestions where to go from here appreciated, I'm just about ready to
> give up. The chances of altering the configuration of the server to
> improve
> the diagnostics are next to nil (politics and beaurocracy).
>
>
> Mark,
>
> You can turn on WebService's logs on the Mid-Tier level to see some
> more details about the Web Services interactions. However, if you are
> in fact getting an Incident number back, then I would start with
> watching Server side Filter logs first. After all in order for the
> number to exist the data had to hit the DB. So it sounds like it is
> all getting there.
>
> Maybe you have a permissions problem with the incident? ( Did you try
> to find that incident as an admin user? )
>
> Maybe there is some workflow that is also deleting the record after it
> is created?
>
> Hope that helps.
>
> --
> Carey Matthew Black
> BMC Remedy AR System Skilled Professional (RSP)
> ARS = Action Request System(Remedy)
>
> Love, then teach
> Solution = People + Process + Tools
> Fast, Accurate, Cheap.... Pick two.
>
> On Wed, Jul 22, 2009 at 4:09 PM, grenadaguy<[email protected]>
> wrote:
>> Thanks, I got the tip to use WebServices from another source as well
>> (coincidentally including a perl script written you your good self).
>>
>> I have set up a request in soapUI and am getting a response back with an
>> incident number (below), but no ticket is created and there is no error
>> to
>> say what the problem might be (not much better than BackChannel??)
>>
>> I'm attaching the request as well.
>>
>> <soapenv:Envelope
>> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
>> xmlns:xsd="http://www.w3.org/2001/XMLSchema";
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
>>   <soapenv:Body>
>>      <ns1:HelpDesk_Submit_ServiceResponse
>> xmlns="urn:HPD_IncidentInterface_Create_WS"
>> xmlns:ns1="urn:HPD_IncidentInterface_Create_WS">
>>         <ns1:Incident_Number>INC000000127815</ns1:Incident_Number>
>>      </ns1:HelpDesk_Submit_ServiceResponse>
>>   </soapenv:Body>
>> </soapenv:Envelope>
>
> --
> View this message in context:
> http://www.nabble.com/Trying-to-use-BackChannel-%28AR-Mid-Tier-v7.0%29-tp24579862p24623675.html
> Sent from the ARS (Action Request System) mailing list archive at
> Nabble.com.

-- 
View this message in context: 
http://www.nabble.com/Trying-to-use-BackChannel-%28AR-Mid-Tier-v7.0%29-tp24579862p24628281.html
Sent from the ARS (Action Request System) mailing list archive at Nabble.com.

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"

Reply via email to