RTC integration with Siebel, Remedy, etc.

In the Rational Change Management team area, we are investigating
providing a "bridge connector" (as opposed to a "synchronizer connector"
that is provided by the ClearCase Connector) betwen a "request" (i.e.
the kind of object you'd find in Siebel and Remedy), and a "task" (the
kind of object representing development work). We're working on
defining a simple API that you'd implement above your request repository
(in the "Common CM Service" team area).

If you'd like to describe the specific interactions (and repositories)
you'd like to see supported, please submit workitems against the "Change
Management" category.

Cheers,
Geoff (ClearCase Connector, Change Management team)

mkrash wrote:

Are there plans to integrate ticketing systems, such as Siebel and
Remedy, with RTC using connectors, or something more direct?

Mark

Note: The new work on a "bridge connector" that I describe below is in
addition to the "synchronizing connector" that is currently provided in
RTC. So you can decide whether you want to support a bridge connector
or a synchronizing connector (or both) for a given repository.

The difference between a "bridge" and a "synchronizer" is that a
"bridge" provides a link that lets you navigate from one repository to
the other, while a "synchronizer" causes data from one repository to be
replicated into the other repository (and periodically synchronized).

Cheers,
Geoff

Geoffrey Clemm wrote:

In the Rational Change Management team area, we are investigating
providing a "bridge connector" (as opposed to a "synchronizer connector"
that is provided by the ClearQuest Connector) betwen a "request" (i.e.
the kind of object you'd find in Siebel and Remedy), and a "task" (the
kind of object representing development work). We're working on
defining a simple API that you'd implement above your request repository
(in the "Common CM Service" team area).

If you'd like to describe the specific interactions (and repositories)
you'd like to see supported, please submit workitems against the "Change
Management" category.

Cheers,
Geoff (ClearCase Connector, Change Management team)

mkrash wrote:
Are there plans to integrate ticketing systems, such as Siebel and
Remedy, with RTC using connectors, or something more direct?

Mark

So does this mean the synchronizer already exists for RTC as well? If so, how do we get that?

There are two kinds synchronizers that currently ship with RTC: an "Item
Synchronizer" which synchronizes things like workitems, and an "SCM
Synchronizer" which synchronizers SCM streams.

Both synchronizers have a "generic component", so that you can extend
the synchronizer to your repository of choice).

There currently is a ClearQuest extension for the Item Synchronizer, and
a ClearCase extension for the SCM synchronizer.

Both synchronizers are available in the source code distribution for RTC
(the Interop component contains the code for the Item Synchronizer, and
the ClearCase Connector component contains the code for the SCM
Synchronizer.

Cheers,
Geoff


gandyb wrote:

So does this mean the synchronizer already exists for RTC as well? If
so, how do we get that?

Will this bridge be available in RTC 2.0?

The ClearQuest Bridge is planned for 2.0 (our goal is to have it
available in the Beta2 release), but the extension of this Bridge to
other repositories beyond CQ is not yet scheduled.

Cheers,
Geoff

mkrash wrote:

Will this bridge be available in RTC 2.0?

Hello RTC friends.

I've seen that this topic was discussed before, but that was in April, so I open this new topic. (Old discussion:
http://jazz.net/forums/viewtopic.php?t=2812&highlight=bmc+remedy)

I'm looking for an possibility to connect RTC 2.0 with BMC Remedy, since I've the order to build up an ticket system (Issue tracking system). We're looking for a connection to link the two systems together (don't ask me why, it isn't my decision and the customer wants it like this).

So my questions:

Does anyone have experience with BMC Remedy and RTC
Is it an Bridge Connector planned to connect RTC with other systems?

Thanks for your help!

In the Rational Change Management team area, we are investigating
providing a "bridge connector" (as opposed to a "synchronizer connector"
that is provided by the ClearCase Connector) betwen a "request" (i.e.
the kind of object you'd find in Siebel and Remedy), and a "task" (the
kind of object representing development work). We're working on
defining a simple API that you'd implement above your request repository
(in the "Common CM Service" team area).

If you'd like to describe the specific interactions (and repositories)
you'd like to see supported, please submit workitems against the "Change
Management" category.

Cheers,
Geoff (ClearCase Connector, Change Management team)

mkrash wrote:

Are there plans to integrate ticketing systems, such as Siebel and
Remedy, with RTC using connectors, or something more direct?

Mark

Is it an Bridge Connector planned to connect RTC with other systems?

well, this is a community effort.. the RTC team will not do all the work.

I am building a connector to SFDC Service Cloud.

And we may have to build bi-directional connectors, not just bridge, to misc defect mgmt systems as part of my company's expected transition to RTC.

Sam