It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×3,954

question asked: Feb 17 '11, 10:51 p.m.
question was seen: 5,103 times
last updated: Jan 15 '13, 4:36 p.m.

Related questions

Is it possible to publish RRC process diagram with RPE

0
1
Michael Richardson (11●2●1) | asked Feb 17 '11, 10:51 p.m.
From https://www.ibm.com/developerworks/forums/thread.jspa?messageID=14584572&#14584572

Hello, Can someone share their approach for publishing RRC business process diagrams. I did try the pearl script and updated the data source schema per http://www-01.ibm.com/support/docview.wss?uid=swg21455926 and using the Dec 10, 2010 09:14:00 AM dc2inline.pl from https://www.ibm.com/developerworks/forums/thread.jspa?threadID=353871. That did not result in a rendering node that I could find.

The return from https://site:9443/rdm/publish/processes?resourceURI=rrcNNNN contains:

<ds>
<process>
<bpmn20:definitions xmlns:Definitions__EtKkECAoEeCycp9sCh_bHw="http://...

If this can be referenced, is this the business process diagram? If so, how should I reference this?

What about that <process> vs. <ds> ?

Should there be a <dc> ?

Thanks,Michael

One answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Edgar Ignacio Velazquez Mar (722●5) | answered Apr 28 '11, 5:09 p.m.
JAZZ DEVELOPER
Hi Michael,

The response from https://site:9443/rdm/publish/processes?resourceURI=rrcNNNN should contain something like: 
ds:artifact>

	dc:title>Classics CD Web Shopping/dc:title>

	dc:description>This is a business to business process diagram showing

		the interactions between the shopper and the cd classics web shopping

		system/dc:description>

	dc:identifier>rrc64/dc:identifier>

	ds:about>https://server:port/rdm/resources/rrc64/ds:about>

	dc:format>application/x-com.ibm.rdm.ba.process+xml/dc:format>

	ds:collaboration>.../ds:collaboration>

	ds:location>.../ds:location>

	ds:content>

		process:process

			rendering="https://server:port/converter/htmlgen?resourceURL=https://server:port/rdm/resources/rrc64.png

			&contentType=application/x-com.ibm.rdm.ba.process%2Bxml&revision=_OZoh8WVLEeC9QOpBfemhdw&doSuppressHtmlCreation=true&oauthToken=e93155fcd95a48818564b257a7d3f301&requestTokenSecret=uDduUaCPGWy4wK4eJfQJQul5HwTbbKQ7jlPNazf9Gb0%3D"

			revision="_OZoh8WVLEeC9QOpBfemhdw">

			process:attribute group="Origin" id="Type_ID_string"

				key="http://com.ibm.rdm.attribute.group.ORIGIN" name="Type" value="Enhancement" />

			bpmn20:definitions

				xmlns:Definitions__TKZwkJCmEd2HA......


What about that <process> vs. <ds> ?
Process contains the information for the Business Process Diagram

Should there be a <dc> ?
No, it is ok as it created

What is it then?
The problem is on the process schema, it's incorrectly defined and you are not able to obtain the rendering url since it is not exposed by the schema.

How to fix it?
Replace the content of process.xsd located on the folder <installation>/server\conf\rdm\reporting\initialization\xmlschema

with the following schema: 
?xml version="1.0" encoding="utf-8" ?>

xs:schema xmlns:tns="http://jazz.net/xmlns/alm/rm/process/v0.1" xmlns:h="http://www.w3.org/1999/xhtml" attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://jazz.net/xmlns/alm/rm/process/v0.1" xmlns:xs="http://www.w3.org/2001/XMLSchema">

	xs:import schemaLocation="__FRONTSIDE_SERVER_URL__/schema/xhtml" namespace="http://www.w3.org/1999/xhtml" />

	xs:element name="process">

		xs:complexType>

			xs:sequence minOccurs="0">

				xs:element maxOccurs="unbounded" minOccurs="0" name="attribute">

					xs:complexType>

						xs:attribute name="key" type="xs:string" use="optional" />

						xs:attribute name="group" type="xs:string" use="optional" />

						xs:attribute name="name" type="xs:string" use="optional" />

						xs:attribute name="value" type="xs:string" use="optional" />

					/xs:complexType>

				/xs:element>

			/xs:sequence>

			xs:attribute name="rendering" type="xs:string" use="optional" />

			xs:attribute name="revision" type="xs:string" use="optional" />

		/xs:complexType>

	/xs:element>

/xs:schema>

Note: you will need to add "<" at the beginning of each line since it didn't display the XML correctly here.

Then reinitialize the publishing service by going to the following url:
https://server:port/rdm/publish/initialize

Then you will need to update the schema on your report template with:
https://server:port/rdm/publish/processes?metada=schema

That should give you an attribute called rendering which is the url you need to use to get the image

Hope this helps!
Comments
Ian Kerins commented Jan 03 '13, 5:00 p.m.

Do you have a similar approach for RRC V4.0.1?  I am trying to migrate a Business process report from v2.0.0.4 (that has this fix) to RRC V4.0.1 however the process:attributes are no longer present in the response to https://site:9443/rdm/publish/processes?resourceURI=rrcNNNN

I can render the image just not extract the task names and the descriptions behind them

Any help you can give would be greatly appreciated.

Thanks

Edgar Ignacio Velazquez Mar commented Jan 14 '13, 4:09 p.m.
JAZZ DEVELOPER

Hi Ian,
 This workaround is to include the rendering element to the schema, this is not an issue in 4.0.1.
 The attributes are now just located under /rrm:collaboration/rrm:attributes this should be the same attributes that you used to access under process:attributes.

Task names have never been available on the schema, which is probably an enhancement

Edgar Ignacio Velazquez Mar commented Jan 15 '13, 4:36 p.m.
JAZZ DEVELOPER

For Task elements you can edit the template to add the bpmn schema elements

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.