Mark,

If the goal is: "to robotically create incidents when required" then
why not use WebServices as the interface
or use the ARS API as the interface?

I think the "BackChannel" is internal to the Mid-Tier and as such is
not only "not supported" (by itself) but also undocumented.

-- 
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 Tue, Jul 21, 2009 at 12:07 PM, John
Sundberg<[email protected]> wrote:
> You might want to consider
> http://www.kineticdata.com/Products/KineticLink.html.
> Free/opensource -- similar concept to backchannel.
>
> -John
>
> On Jul 20, 2009, at 8:21 PM, grenadaguy wrote:
>
> Greetings all,
>
> I'm trying to write a couple of scripts which use wget (from a Linux box) to
> robotically create incidents when required. I feel this could be useful in
> my environment to ease the transition from my internal-only customers
> currently sending requests by e-mail, also to facilitate the creation of
> regular maintenance tasks. While these may be features supported in some
> Remedy configurations I am not in full administrative control of the system
> we use and such features are not likely to be enabled for my use.
>
> So far I am able to duplicate a case having captured the backchannel
> messages from doing it manually, i.e. sent by the browser when accessing
> http://<server ip>/arsys/BackChannel/. Logging in and maintaining session
> cookies using wget seem to work fine for this - the real work seems to be
> done by the backchannel access. The only modification to the original POSTed
> message as sent by the browser is a new incident number and a related Id.
>
> When I try and adjust the obvious parameters in the backchannel SetEntryList
> message to actually generate a new incident (user, title, notes) I'm getting
> the response "Message not found". I have no idea what this error means nor
> what the implied problem is with my POST data for it not to be accepted. I'd
> be happy to post my script in full if anyone is inclined to look at it in
> detail.
>
> I've not been able to find any documentation on backchannel, only vague
> references, but then I don't have a support id with access to the full
> documentation (presumably someone in the company where I work does). I just
> need to know enough to adjust any other parameters which need adjusting for
> backchannel to accept my POST data. Reference is made to backchannel in the
> documentation for the Borland SilkPerformer product so presumably what I'm
> trying to do is one of the things backchannel was designed for (i.e. to
> bypass the user interface).
>
> Anyone with backchannel experience, please help.
>
> Thanks
>
> Mark
>
> --
> John David Sundberg
> 235 East 6th Street, Suite 400B
> St. Paul, MN 55101
> (651) 556-0930-work
> (651) 247-6766-cell
> (651) 695-8577-fax
> [email protected]

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

Reply via email to