I'm making some tests in the integration Composer x RequisitePro.

The project connection synchronization is enable to both sides (Push requirement changes to RequisitePro and Pull requirement changes from RequisitePro). But when I change an attribute in ReqWeb, this change isn't reflected in Composer. The oposite works ok. Other thing is that when I associate a requirement with other requirement in Composer and synchronize them to ReqPro, the traceability doesn't appear.

' s


Daniel Squires

Please ensure the following:

Rational Requirements Composer
Server and Client both running at 2.0.0.1
Rational RequisitePro
ReqWEB component installed
7.1.1 iFix01
New DB Schema
Requires an enterprise database (SQL Server, Oracle, DB2)
Run TLogSchemaUpdate.sql script in order to update the schema

A setting was added in the 2.0 fronting.properties that disabled the sync for the whole repository. The setting should have been removed in 2.0.0.1. Make sure this value is not present for the sync to work:
com.ibm.rdm.fronting.server.synchronizing=false


synchronization limitations

No way to unmanage a requirement. (Same as 1.0)
Each Composer project at most can be mapped to one ReqPro project. (Same as 1.0)
Requirement Type duplicates are not allowed by either name or prefix.
Can't use apostrophe in list items
Sync does not support ReqPro multi-select lists and timestamp attribute types.
Sync does not support RRC URI or Boolean attribute types


troubleshooting

Sync interval in the fronting.properties can be adjusted. Default is 1 minute
<install>\IBM\RRCS20\server\conf\rdm\fronting.properties
com.ibm.rdm.fronting.server.PollingDuration=1
If sync not responding
stop/restart RRC server
disable/reenable the sync option in the connection dialog
Public URI Root property in RDM setup must be populated
May cause the sync not to work
This is documented in the RRC server install guide - look on the jazz.net RRC download page for the "Getting Started" it references the Installation Roadmap

https://publib.boulder.ibm.com/infocenter/rpcmpose/v2r0/index.jsp?topic=/com.ibm.rational.rrc.install_upgrade.doc/topics/t_install_rpc.html

We also find that attribute changes (single word added to a text field) from the ReqPro desktop client (patched to 7.1.1 ifix001) is also fails to sync in RRC (v2.0.0.1) but works in the opposite direction.
The rdm log occasionally reports:
2010-02-17 12:46:29,218 ERROR er.services.servicedocument.ProjectResourceService - HTTP/1.1 409 CRJZS5054E If-Match () was not equal to the resource ETag ("_D6s2MRu6Ed-5UMewy9_PUA") and was not a wildcard.
com.ibm.rdm.fronting.server.exception.UnexpectedResponseException: HTTP/1.1 409 CRJZS5054E If-Match () was not equal to the resource ETag ("_D6s2MRu6Ed-5UMewy9_PUA") and was not a wildcard.
at com.ibm.rdm.fronting.server.core.internal.InternalDomainServiceBase.doPutInternal(InternalDomainServiceBase.java:307)
at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.runInternalMethod(RRSRestServiceBase.java:219)
at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.handleMethod(RRSRestServiceBase.java:171)
at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.doPut(RRSRestServiceBase.java:80)
at com.ibm.team.jfs.app.servlet.AppContainerServlet.dispatchRequest(AppContainerServlet.java:109)
at com.ibm.team.jfs.app.servlet.AppContainerServlet.service(AppContainerServlet.java:181)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:75)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:121)
at com.ibm.team.repository.server.servletbridge.JazzServlet.service(JazzServlet.java:54)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:870)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685)
at java.lang.Thread.run(Thread.java:811)
2010-02-17 12:46:29,218 ERROR er.services.servicedocument.ProjectResourceService - Response: 409 CRJZS5054E If-Match () was not equal to the resource ETag ("_D6s2MRu6Ed-5UMewy9_PUA") and was not a wildcard. - for request: PUT https://adcw-rmg-rat1:9443/rdm/project-resources/_a5K54Ru2Ed-Zx7Bg83jvfg HTTP/1.1

Mike

In addition to the tips noted below, make sure that the user for the requirement changes in ReqPro/ReqWeb is not the same user appearing in the Edit Connection wizard in Composer.

If this is not the issue, then do one of the following...

1. stop, then restart the Composer server
2. turn off the Pull from RequisitePro option in the Edit Connection wizard and Save. Then turn it back on and save again.

Make a requirement change in RequisitePro (to a managed or imported requirement) and then check for synchronization after a minute or so.

BTW, trace relationships are not synchronized between RequisitePro and Composer.