REST Driver with IBM Connections REST API

Hello guys,

I need to implement the connection between the REST Driver and the corresponding REST API from IBM Connections.

I read the REST Driver documentation understanding the behaviour and how it should work, but I have some doubts.

Firstly, I configured the connection data with the authentication to the API. Then, I filled up the Resources paragraph in the Subscriber configuration with the necessary URL's that are indicated in the IBM Connections REST API. Specifically I put those which I need, exactly www-10.lotus.com/.../xpAPIViewer.xsp Reference#action=openDocument
  • rcano <rcano@no-mx.forums.microfocus.com> wrote:
    >

    Hello guys,
    >
    > I need to implement the connection between the REST Driver and the

    corresponding REST API from IBM Connections.
    >
    > I read the 'REST Driver'

    (https://www.netiq.com/documentation/idm45drivers/generic_rest/data/bv5810b.html)
    documentation understanding the behaviour and how it should work, but I
    have some doubts.
    >
    > Firstly, I configured the connection data with the authentication to the

    API. Then, I filled up the Resources paragraph in the Subscriber
    configuration with the necessary URL's that are indicated in the IBM
    Connections REST API. Specifically I put those which I need, exactly
    'these'
    (www-10.lotus.com/.../xpAPIViewer.xsp Reference#action=openDocument
  • On 7/18/2016 7:18 AM, Alex Mchugh wrote:
    > rcano <rcano@no-mx.forums.microfocus.com> wrote:
    >>

    > Hello guys,
    >>
    >> I need to implement the connection between the REST Driver and the

    > corresponding REST API from IBM Connections.
    >>
    >> I read the 'REST Driver'

    > (https://www.netiq.com/documentation/idm45drivers/generic_rest/data/bv5810b.html)
    > documentation understanding the behaviour and how it should work, but I
    > have some doubts.
    >>
    >> Firstly, I configured the connection data with the authentication to the

    > API. Then, I filled up the Resources paragraph in the Subscriber
    > configuration with the necessary URL's that are indicated in the IBM
    > Connections REST API. Specifically I put those which I need, exactly
    > 'these'
    > (www-10.lotus.com/.../xpAPIViewer.xsp Reference#action=openDocument
  • geoffc;2434692 wrote:
    On 7/18/2016 7:18 AM, Alex Mchugh wrote:
    > rcano <rcano@no-mx.forums.microfocus.com> wrote:
    >>

    > Hello guys,
    >>
    >> I need to implement the connection between the REST Driver and the

    > corresponding REST API from IBM Connections.
    >>
    >> I read the 'REST Driver'

    > (https://www.netiq.com/documentation/idm45drivers/generic_rest/data/bv5810b.html)
    > documentation understanding the behaviour and how it should work, but I
    > have some doubts.
    >>
    >> Firstly, I configured the connection data with the authentication to the

    > API. Then, I filled up the Resources paragraph in the Subscriber
    > configuration with the necessary URL's that are indicated in the IBM
    > Connections REST API. Specifically I put those which I need, exactly
    > 'these'
    > (www-10.lotus.com/.../xpAPIViewer.xsp Reference#action=openDocument
  • On 7/18/2016 3:46 PM, rcano wrote:
    >
    > geoffc;2434692 Wrote:
    >> On 7/18/2016 7:18 AM, Alex Mchugh wrote:
    >>> rcano <rcano@no-mx.forums.microfocus.com> wrote:
    >>>>
    >>> Hello guys,
    >>>>
    >>>> I need to implement the connection between the REST Driver and the
    >>> corresponding REST API from IBM Connections.
    >>>>
    >>>> I read the 'REST Driver'
    >>>

    >> (https://www.netiq.com/documentation/idm45drivers/generic_rest/data/bv5810b.html)
    >>> documentation understanding the behaviour and how it should work, but

    >> I
    >>> have some doubts.
    >>>>
    >>>> Firstly, I configured the connection data with the authentication to

    >> the
    >>> API. Then, I filled up the Resources paragraph in the Subscriber
    >>> configuration with the necessary URL's that are indicated in the IBM
    >>> Connections REST API. Specifically I put those which I need, exactly
    >>> 'these'
    >>>

    >> (www-10.lotus.com/.../xpAPIViewer.xsp Reference#action=openDocument
  • geoffc;2434714 wrote:
    On 7/18/2016 3:46 PM, rcano wrote:
    >
    > geoffc;2434692 Wrote:
    >> On 7/18/2016 7:18 AM, Alex Mchugh wrote:
    >>> rcano <rcano@no-mx.forums.microfocus.com> wrote:
    >>>>
    >>> Hello guys,
    >>>>
    >>>> I need to implement the connection between the REST Driver and the
    >>> corresponding REST API from IBM Connections.
    >>>>
    >>>> I read the 'REST Driver'
    >>>

    >> (https://www.netiq.com/documentation/idm45drivers/generic_rest/data/bv5810b.html)
    >>> documentation understanding the behaviour and how it should work, but

    >> I
    >>> have some doubts.
    >>>>
    >>>> Firstly, I configured the connection data with the authentication to

    >> the
    >>> API. Then, I filled up the Resources paragraph in the Subscriber
    >>> configuration with the necessary URL's that are indicated in the IBM
    >>> Connections REST API. Specifically I put those which I need, exactly
    >>> 'these'
    >>>

    >> (www-10.lotus.com/.../xpAPIViewer.xsp Reference#action=openDocument
  • I think you should think more carefully about your model and how it can map
    to XDS in the way the driver shim wants.

    For example subscriber and subscription might make more sense as two
    different object classes, which might simplify your implementation
    somewhat.

    --
    If you find this post helpful and are logged into the web interface, show
    your appreciation and click on the star below...

  • alexmchugh;2435113 wrote:
    I think you should think more carefully about your model and how it can map
    to XDS in the way the driver shim wants.

    For example subscriber and subscription might make more sense as two
    different object classes, which might simplify your implementation
    somewhat.

    --
    If you find this post helpful and are logged into the web interface, show
    your appreciation and click on the star below...


    Indeed, subscriber and subscription are two different object classes. Only I need the subscription_id for this REST call. In fact, all the subscription_id codes will be populated via a driver variable, because them are unique and doesn't change.