Re: [lyo-dev] Lyo OSLC Client for Rational DOORS

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

Re: [lyo-dev] Lyo OSLC Client for Rational DOORS

From: "Marcus Engelhardt" <FDSProject@xxxxxx>
Date: Fri, 24 Jan 2014 11:14:15 +0100 (CET)
Delivered-to: lyo-dev@xxxxxxxxxxx
Importance: normal
List-archive: <https://dev.eclipse.org/mailman/private/lyo-dev>
List-help: <mailto:lyo-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/lyo-dev>, <mailto:lyo-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/lyo-dev>, <mailto:lyo-dev-request@eclipse.org?subject=unsubscribe>
Sensitivity: Normal

Hi Maeve,

I think the dbadmin setup at least for those parameters is ok. I have checked the module properties within the Doors client. The module has a URL that starts as excepted. I can also ask for the resource of a given requirement. I got the URL from the requirement's properties in the Doors client, too. The response looks like this:

<?xml version="1.0"?>
<rdf:RDF
    xmlns:dcterms="http://purl.org/dc/terms/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:rm="http://jazz.net/ns/rm#"
    xmlns:rm_property="http://%HOSTNAME%:8080/dwa/rm/urn:rational::1-52d92f3f16611ecc-M-00000020/types/"
    xmlns:acp="http://jazz.net/ns/acp#"
    xmlns:oslc="http://open-services.net/ns/core#"
    xmlns:foaf="http://xmlns.com/foaf/0.1/"
    xmlns:oslc_rm="http://open-services.net/ns/rm#">
<oslc_rm:Requirement rdf:about="http://%HOSTNAME%:8080/dwa/rm/urn:rational::1-52d92f3f16611ecc-O-8447-00000020">
    <rm_property:attrDef-7 rdf:datatype="http://www.w3.org/2001/XMLSchema#dateTime"
    >2013-11-04</rm_property:attrDef-7>
    <rm_property:attrDef-9 rdf:datatype="http://www.w3.org/2001/XMLSchema#integer"
    >8447</rm_property:attrDef-9>
    <rm_property:attrDef-1025 rdf:parseType="Literal"></rm_property:attrDef-1025>
    <rm_property:attrDef-1020 rdf:parseType="Literal"></rm_property:attrDef-1020>
    <rm_property:attrDef-1024 rdf:resource="http://%HOSTNAME%:8080/dwa/rm/urn:rational::1-52d92f3f16611ecc-M-00000020/types/attrDef-1024#3"/>
    <rm_property:attrDef-1019 rdf:parseType="Literal"></rm_property:attrDef-1019>
    <dcterms:created rdf:datatype="http://www.w3.org/2001/XMLSchema#dateTime"
    >2013-11-04</dcterms:created>
    <rm_property:attrDef-5 rdf:datatype="http://www.w3.org/2001/XMLSchema#dateTime"
    >2013-11-04</rm_property:attrDef-5>
    <dcterms:contributor>
      <foaf:Person>
        <foaf:name>Alireza</foaf:name>
      </foaf:Person>
    </dcterms:contributor>
    <rm_property:attrDef-4 rdf:parseType="Literal">Alireza</rm_property:attrDef-4>
    <dcterms:title rdf:parseType="Literal">VZE_8447: DISPLAY,SPEAKER</dcterms:title>
    <oslc:shortTitle rdf:parseType="Literal">VZE_8447: DISPLAY,SPEAKER</oslc:shortTitle>
    <oslc:serviceProvider rdf:resource="http://%HOSTNAME%:8080/dwa/rm/discovery/service/urn:rational::1-52d92f3f16611ecc-M-00000020"/>
    <rm:primaryText rdf:parseType="Literal">DISPLAY,SPEAKER</rm:primaryText>
    <acp:accessControl rdf:resource="http://%HOSTNAME%:8080/dwa/rm/acp/urn:rational::1-52d92f3f16611ecc-F-00000000/gFgcK1req0%252BQ5gE6yE5YsEZZcDI%253D%250A"/>
    <rm_property:attrDef-12 rdf:parseType="Literal"></rm_property:attrDef-12>
    <oslc:instanceShape rdf:resource="http://%HOSTNAME%:8080/dwa/rm/oslc/shape/requirement/urn:rational::1-52d92f3f16611ecc-M-00000020"/>
    <rm_property:attrDef-10 rdf:resource="http://%HOSTNAME%:8080/dwa/rm/urn:rational::1-52d92f3f16611ecc-M-00000020/types/attrDef-10#1"/>
    <dcterms:description rdf:parseType="Literal">Sub-Blocks HMI</dcterms:description>
    <rm_property:attrDef-13 rdf:parseType="Literal">Sub-Blocks HMI</rm_property:attrDef-13>
    <dcterms:creator>
      <foaf:Person>
        <foaf:name>Alireza</foaf:name>
      </foaf:Person>
    </dcterms:creator>
    <rm_property:attrDef-1026 rdf:parseType="Literal"></rm_property:attrDef-1026>
    <dcterms:modified rdf:datatype="http://www.w3.org/2001/XMLSchema#dateTime"
    >2013-11-04T15:32:37Z</dcterms:modified>
    <dcterms:identifier rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >8447</dcterms:identifier>
    <rm_property:attrDef-6 rdf:parseType="Literal">Alireza</rm_property:attrDef-6>
    <rm_property:attrDef-8 rdf:datatype="http://www.w3.org/2001/XMLSchema#dateTime"
    >2013-11-04T15:32:37Z</rm_property:attrDef-8>
</oslc_rm:Requirement>
</rdf:RDF>

However, I can't query for a requirement using the query capability. Even if I query for the requirement whose RDF is printed above I receive an empty result:

<?xml version="1.0"?>
<rdf:RDF
    xmlns:dcterms="http://purl.org/dc/terms/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:rm="http://jazz.net/ns/rm#"
    xmlns:acp="http://jazz.net/ns/acp#"
    xmlns:oslc="http://open-services.net/ns/core#"
    xmlns:foaf="http://xmlns.com/foaf/0.1/"
    xmlns:oslc_rm="http://open-services.net/ns/rm#">
<oslc_rm:ResponseInfo rdf:about="http://%HOSTNAME%:8080/dwa/rm/oslc/query/requirement?oslc.paging=true&oslc.pageSize=10&oslc.where=dcterms:identifier=8447&oslc.prefix=dcterms=%3Chttp://purl.org/dc/terms/%3E">
    <dcterms:title>DOORS ERS Repository</dcterms:title>
</oslc_rm:ResponseInfo>
</rdf:RDF>

The lyo query code for this is:

OslcQueryParameters queryParams;
queryParams = new OslcQueryParameters();
queryParams.setPrefix("dcterms=<http://purl.org/dc/terms/>");
queryParams.setWhere("dcterms:identifier=8447");
OslcQuery query = new OslcQuery(client, queryCapability, 10, queryParams);
OslcQueryResult result = query.submit();

It's the same when I just query for the dcterms:identifier property:

<?xml version="1.0"?>
<rdf:RDF
    xmlns:dcterms="http://purl.org/dc/terms/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:rm="http://jazz.net/ns/rm#"
    xmlns:acp="http://jazz.net/ns/acp#"
    xmlns:oslc="http://open-services.net/ns/core#"
    xmlns:foaf="http://xmlns.com/foaf/0.1/"
    xmlns:oslc_rm="http://open-services.net/ns/rm#">
<oslc_rm:ResponseInfo rdf:about="http://%HOSTNAME%:8080/dwa/rm/oslc/query/requirement?oslc.paging=true&oslc.pageSize=10&oslc.where=dcterms:identifier=8447&oslc.select=dcterms:identifier&oslc.prefix=dcterms=%3Chttp://purl.org/dc/terms/%3E">
    <dcterms:title>DOORS ERS Repository</dcterms:title>
</oslc_rm:ResponseInfo>
</rdf:RDF>

The query code for this looks like:

OslcQueryParameters queryParams;
queryParams = new OslcQueryParameters();
queryParams.setSelect("dcterms:identifier");
queryParams.setPrefix("dcterms=<http://purl.org/dc/terms/>");
queryParams.setWhere("dcterms:identifier=8447");
OslcQuery query = new OslcQuery(client, queryCapability, 10, queryParams);
OslcQueryResult result = query.submit();

So querying for a single requirement does not work for me.

What I actually need is the possibility to query for the full requirements collection available. That's why I am also trying to query for a requirements collection. However, the result is empty here, too. I have tried to query for identifier, date created, title, etc. It's all the same.

He is the result for querying a requirements collection based on the identifier (which should give me the requirement shown above. The result is empty even when dropping the select parameter.

<?xml version="1.0"?>
<rdf:RDF
    xmlns:dcterms="http://purl.org/dc/terms/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:rm="http://jazz.net/ns/rm#"
    xmlns:acp="http://jazz.net/ns/acp#"
    xmlns:oslc="http://open-services.net/ns/core#"
    xmlns:foaf="http://xmlns.com/foaf/0.1/"
    xmlns:oslc_rm="http://open-services.net/ns/rm#">
<oslc_rm:ResponseInfo rdf:about="http://fokus-pc:8080/dwa/rm/oslc/query/requirementCollection?oslc.paging=true&oslc.pageSize=10&oslc.where=dcterms:identifier=8447&oslc.select=dcterms:identifier&oslc.prefix=dcterms=%3Chttp://purl.org/dc/terms/%3E">
    <dcterms:title>DOORS ERS Repository</dcterms:title>
</oslc_rm:ResponseInfo>
</rdf:RDF>

It's the same when querying by the creation date.

<?xml version="1.0"?>
<rdf:RDF
    xmlns:dcterms="http://purl.org/dc/terms/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:rm="http://jazz.net/ns/rm#"
    xmlns:acp="http://jazz.net/ns/acp#"
    xmlns:oslc="http://open-services.net/ns/core#"
    xmlns:foaf="http://xmlns.com/foaf/0.1/"
    xmlns:oslc_rm="http://open-services.net/ns/rm#">
<oslc_rm:ResponseInfo rdf:about="http://fokus-pc:8080/dwa/rm/oslc/query/requirementCollection?oslc.paging=true&oslc.pageSize=10&oslc.where=dcterms:created=%222013-11-04%22&oslc.select=dcterms:created&oslc.prefix=dcterms=%3Chttp://purl.org/dc/terms/%3E">
    <dcterms:title>DOORS ERS Repository</dcterms:title>
</oslc_rm:ResponseInfo>
</rdf:RDF>

I still can see any URL for a requirement in the attribute listing in DWA. Is there something wrong in my setup?

Thanks for your efforts.

Best,
Marcus

Gesendet: Donnerstag, 23. Januar 2014 um 18:24 Uhr
Von: "Maeve O Reilly" <maevedevine@xxxxxxxxx>
An: "Marcus Engelhardt" <FDSProject@xxxxxx>
Betreff: Re: Aw: Re: [lyo-dev] Lyo OSLC Client for Rational DOORS

Hi Marcus,

I doubt this is related to DCNs. But cut-n-paste of that dbadmin command can fail to run it properly in DOS - tab characters. If you just run dbadmin - data 36677@HOSTNAME -dwaHost HOSTNAME -dwaPort 8080 -dwaProtocol http

you should get a response 3 times - stating each parameter is set.

Then open a DOORS client and bring up the properties of a module. Does it have a URL with http://hostname etc? That is then what you GET.

Maeve

On Thursday, 23 January 2014, 17:06, Marcus Engelhardt <FDSProject@xxxxxx> wrote:

Hi Maeve,

I have checked the configuration a couple of times. I have configured DW using the following command (host name replaced)

dbadmin -dcnEnable -data 36677@HOSTNAME -dcnBrokerUri "tcp://HOSTNAME:61616" -dcnChannelName "dcn" -dwaHost HOSTNAME -dwaPort 8080 -dwaProtocol http

Everything is running locally. DWA is accessible via http://HOSTNAME:8080/dwa.

When I apply these settings above with the dbadmin tool and restart the doors server only (i.e. the service from the windows panel), the dbadmin tool diagnotistics says

"C:\DOORS\Server\bin>dbadmin -dcnInfo -data 36677@HOSTNAME
-I- DBADMIN: Data Change Notifications are currently enabled (Broker URI = 'tcp:

//HOSTNAME:61616', Channel Name = 'dcn')."

When restarting the whole machine and checking the configuration again, it says:

"C:\DOORS\Server\bin>dbadmin -dcnInfo -data 36677@HOSTNAME
-I- DBADMIN: Data Change Notifications are currently enabled but not sending (Br
oker URI = 'tcp://HOSTNAME:61616', Channel Name = 'dcn')."

Is this a hint? I am pretty sure, that the dbadmin tool said "Data Change Notifications are currently enabled" before applying the changes again. But maybe I am wrong ;(

Thanks,

Marcus

Gesendet: Donnerstag, 23. Januar 2014 um 16:53 Uhr
Von: "Maeve O Reilly" <maevedevine@xxxxxxxxx>
An: "lyo-dev@xxxxxxxxxxx" <lyo-dev@xxxxxxxxxxx>
Betreff: Re: [lyo-dev] Lyo OSLC Client for Rational DOORS

Hi Marcus,

if you are not seeing a URL to get, double check the dbadmin -dwaHost/dwaProtocol/dwaPort settings when you configured DWA.

This is what a RDF looks like for me, but I don't know how to query for that foaf stuff seen for creator. I assume you need some extra clauses.

Maeve

https://sse-doors.rcsnl.ams.nl.ibm.com:8443/dwa/rm/urn:rational::1-51929a740f221131-O-21-0000002a

<?xml version="1.0"?>

<rdf:RDF

xmlns:dcterms="http://purl.org/dc/terms/"

xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"

xmlns:doorsAttribute="http://jazz.net/ns/rm/doors/attribute#"

xmlns:rm="http://jazz.net/ns/rm#"

xmlns:rm_property="https://sse-doors.rcsnl.ams.nl.ibm.com:8443/dwa/rm/urn:rational::1-51929a740f221131-M-0000002a/types/"

xmlns:acp="http://jazz.net/ns/acp#"

xmlns:oslc="http://open-services.net/ns/core#"

xmlns:foaf="http://xmlns.com/foaf/0.1/"

xmlns:oslc_rm="http://open-services.net/ns/rm#">

<oslc_rm:Requirement rdf:about="https://sse-doors.rcsnl.ams.nl.ibm.com:8443/dwa/rm/urn:rational::1-51929a740f221131-O-21-0000002a">

<dcterms:contributor>

<foaf:Person>

<foaf:name>Administrator</foaf:name>

</foaf:Person>

</dcterms:contributor>

<oslc_rm:implementedBy rdf:resource="http://google.com"/>

<doorsAttribute:modifiedBy rdf:parseType="Literal">Administrator</doorsAttribute:modifiedBy>

<doorsAttribute:createdBy rdf:parseType="Literal">Administrator</doorsAttribute:createdBy>

<doorsAttribute:createdOn rdf:datatype="http://www.w3.org/2001/XMLSchema#dateTime"

>2013-10-14</doorsAttribute:createdOn>

<rm:primaryText rdf:parseType="Literal">My Eclipse Lyo CREATED Primary Text</rm:primaryText>

<doorsAttribute:absoluteNumber rdf:datatype="http://www.w3.org/2001/XMLSchema#integer"

>21</doorsAttribute:absoluteNumber>

<dcterms:modified rdf:datatype="http://www.w3.org/2001/XMLSchema#dateTime"

>2013-10-14T14:22:46Z</dcterms:modified>

<dcterms:title rdf:parseType="Literal">21: My Eclipse Lyo CREATED Primary Text</dcterms:title>

<dcterms:creator>

<foaf:Person>

<foaf:name>Administrator</foaf:name>

</foaf:Person>

</dcterms:creator>

<doorsAttribute:objectShortText rdf:parseType="Literal"></doorsAttribute:objectShortText>

<rm_property:attrDef-8 rdf:datatype="http://www.w3.org/2001/XMLSchema#dateTime"

>2013-10-14T14:22:46Z</rm_property:attrDef-8>

<oslc:serviceProvider rdf:resource="https://sse-doors.rcsnl.ams.nl.ibm.com:8443/dwa/rm/discovery/service/urn:rational::1-51929a740f221131-M-0000002a"/>

<doorsAttribute:objectHeading rdf:parseType="Literal"></doorsAttribute:objectHeading>

<oslc:shortTitle rdf:parseType="Literal">21: My Eclipse Lyo CREATED Primary Text</oslc:shortTitle>

<doorsAttribute:modifiedOn rdf:datatype="http://www.w3.org/2001/XMLSchema#dateTime"

>2013-10-14</doorsAttribute:modifiedOn>

<oslc:instanceShape rdf:resource="https://sse-doors.rcsnl.ams.nl.ibm.com:8443/dwa/rm/oslc/shape/requirement/urn:rational::1-51929a740f221131-M-0000002a"/>

<doorsAttribute:createdThru rdf:resource="https://sse-doors.rcsnl.ams.nl.ibm.com:8443/dwa/rm/urn:rational::1-51929a740f221131-M-0000002a/types/attrDef-10#1"/>

<dcterms:description rdf:parseType="Literal"></dcterms:description>

<dcterms:identifier rdf:datatype="http://www.w3.org/2001/XMLSchema#string"

>21</dcterms:identifier>

<dcterms:created rdf:datatype="http://www.w3.org/2001/XMLSchema#dateTime"

>2013-10-14</dcterms:created>

<acp:accessControl rdf:resource="https://sse-doors.rcsnl.ams.nl.ibm.com:8443/dwa/rm/acp/urn:rational::1-51929a740f221131-F-00000000/gFgcK1req0%252BQ5gE6yE5YsEZZcDI%253D%250A"/>

</oslc_rm:Requirement>

</rdf:RDF>

Hi Clyde,

thanks for the clue, but unfortunately I can't find any attribute that indicates a URL. How is the attribute usually called?

I have a set of "custom" properties and some "system" properties that are "absolute number", "created by", "created on", "last modified by" and "last modified on". In the set of the custom properties there is one called "requirements reference" but this a no value in case of all requirements.

Best,

Marcus

Gesendet: Mittwoch, 22. Januar 2014 um 16:57 Uhr
Von: "Clyde D Icuspit" <cdicuspi@xxxxxxxxxx>
An: "Lyo project developer discussions" <lyo-dev@xxxxxxxxxxx>
Cc: lyo-dev-bounces@xxxxxxxxxxx
Betreff: Re: [lyo-dev] Lyo OSLC Client for Rational DOORS

Hi Marcus,

In the DWA GUI, lower right-hand corner under Attributes, the URL property value is usually displayed. You can copy the URL of the selected requirement from there and temporarily hard-code it in a GET request to get the RDF representation of that requirement.

Sincerely,

Clyde Icuspit

____________________________________________________________

Business Partner ISV Technical Enablement

IBM Certified I/T Specialist L2

IBM Rational Software

tel: 617.693.7417

email: cdicuspi@xxxxxxxxxx

Ready for IBM Rational Software Partner Program

Ready for IBM Rational partner plug-ins

_______________________________________________ lyo-dev mailing list lyo-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/lyo-dev

Follow-Ups:
- Re: [lyo-dev] Lyo OSLC Client for Rational DOORS
  - From: Clyde D Icuspit

References:
- Re: [lyo-dev] Lyo OSLC Client for Rational DOORS
  - From: Maeve O Reilly

Prev by Date: Re: [lyo-dev] Challenge Adding Affected By Links to Requirements
Next by Date: Re: [lyo-dev] Lyo OSLC Client for Rational DOORS
Previous by thread: Re: [lyo-dev] Lyo OSLC Client for Rational DOORS
Next by thread: Re: [lyo-dev] Lyo OSLC Client for Rational DOORS
Index(es):
- Date
- Thread

Breadcrumbs