CQ connector setup error

Hi Gary,

There is an updated version of the setup doc which explains what to do; it will be included in the beta2 release build. In short, you need to add the missing packages to your schema repository. From the updated doc:

use CQ Designer to open the repository, sample_schema_repo. Select Defect Tracking Interop, then Package on the toolbar. Select the Package Wizard, and select the packages that are not installed. If they are not listed, select More Packages and click OK.

You can find the latest version of the doc at

https://jazz.net/learn/LearnItem.jsp?href=content/docs/cq-interop-install/index.html

Hope this helps,
John

I am getting this error when trying to run the cqimport step in the CQ connector readme doc (readmeCQConnect.html). I am stuck. Please help.

C:\rtcm4\jazz\connectors\jazz\connectors\gateway>cqload importschema -dbset sample_schema_repo admin "" C:\rtcm4\jazz\connectors\jazz\connectors\gateway\DefectTrackingInteropSchema.txt
*********************************************************
Starting importschema
*********************************************************

The import file "C:\rtcm4\jazz\connectors\jazz\connectors\gateway\DefectTracking
InteropSchema.txt" is invalid:
The schema requires the following package(s), which is(are) not currently instal
led in the database...
revision '7.1' of package 'Email'
revision '5.0' of package 'Notes'.

*********************************************************
ERROR: importschema FAILED!
*********************************************************

C:\rtcm4\jazz\connectors\jazz\connectors\gateway>cqload importschema -dbset samp
le_schema_repo admin "" C:\rtcm4\jazz\connectors\jazz\connectors\gateway\DefectT
rackingInteropSchema.txt

John, I followed the link to the new doc and that step works now. thanks

C:\rtcm4\jazz\connectors\jazz\connectors\gateway>cqload importschema -dbset sample_schema_repo admin "" C:\rtcm4\jazz\connectors\jazz\connectors\gateway\DefectTrackingInteropSchema.txt
*********************************************************
Starting importschema
*********************************************************


*********************************************************
Successfully completed importschema
*********************************************************

C:\rtcm4\jazz\connectors\jazz\connectors\gateway>

I am able to get the incoming sync (CQ to Jazz) to work ok. Creating/updating in CQ triggers create/update in Jazz. However, attachment doesn't seem to come over to Jazz though.

Outgoing sync (Jazz to CQ) is currently not working and I am not sure why but I am going back to the outgoing sync steps to see what I might have missed. The current behavior is that when the workitem is created in RTC client, no new record is created in CQ. I noticed that the links tab of the workitem record does not show the external links node like the workitem created when CQ record is created. I am sure it is a user error somewhere in my environment regarding outgoing sync. If there are things I should checked, let me know.


I also tried these as well -

https://jazz.net/learn/LearnItem.jsp?href=content/docs/cq-interop-install/index.html#Enable_Outgoing_Synchronization

I defined the in the project process spec that new work items should result in new CQ records being created (as opposed to only synchronizing work items that are already connected to CQ records). I did that by adding "enableCreation" elements to your project area's process specification as described in

https://jazz.net/learn/LearnItem.jsp?href=content/docs/cq-interop-install/index.html#Customize_Team_Process

Outgoing synchronization is a periodic background task that (by default) runs every 5 minutes, so there could be up to a 5 minute delay after creating a work item before it results in the creation of a CQ record. So if you checked right away, check again. If you waited awhile and still don't see it, then would you paste in the entire contents of the configuration-data element for synchronization preferences that you added to your process spec? The opening tag of the element should look like this:

<configuration-data xmlns="http://com.ibm.team.interop/syncPreferences" id="com.ibm.team.interop.configuration.syncPreferences">

John

I am able to get the incoming sync (CQ to Jazz) to work ok. Creating/updating in CQ triggers create/update in Jazz. However, attachment doesn't seem to come over to Jazz though.

Outgoing sync (Jazz to CQ) is currently not working and I am not sure why but I am going back to the outgoing sync steps to see what I might have missed. The current behavior is that when the workitem is created in RTC client, no new record is created in CQ. I noticed that the links tab of the workitem record does not show the external links node like the workitem created when CQ record is created. I am sure it is a user error somewhere in my environment regarding outgoing sync. If there are things I should checked, let me know.


I also tried these as well -

https://jazz.net/learn/LearnItem.jsp?href=content/docs/cq-interop-install/index.html#Enable_Outgoing_Synchronization

I defined the in the project process spec that new work items should result in new CQ records being created (as opposed to only synchronizing work items that are already connected to CQ records). I did that by adding "enableCreation" elements to your project area's process specification as described in

https://jazz.net/learn/LearnItem.jsp?href=content/docs/cq-interop-install/index.html#Customize_Team_Process

Waited a long time. still not seeing the CQ record created when work item is created in RTC client. Here is the

<configuration-data id="com.ibm.team.interop.configuration.syncPreferences" xmlns="http://com.ibm.team.interop/syncPreferences">
<outgoingSync>
<enableCreation syncRuleName="com.ibm.rational.clearquest.sample_schema_repo.Defect"/>
<enableCreation syncRuleName="com.ibm.rational.clearquest.sample_schema_repo.Project"/>

</outgoingSync>
<managerPreferences id="com.ibm.team.interop.service.managers.kernel.ContributorManager" incomingCaseInsensitive="true">
</managerPreferences>
<managerPreferences id="com.ibm.team.interop.service.managers.clearquest.CQExternalManager,com.ibm.team.interop.service.managers.clearquest.CQExternalManagerForUser">

<cqGateway uri="http://localhost:8081/InteropGateway/InteropServlet">
<connection_info>
<cq_connection dbSet="sample_schema_repo" db="SAMPL"/>
<login_info user_id="jazz" password="jazz"/>
</connection_info>
</cqGateway>

</managerPreferences>

Try turning on debug logging for at least the Jazz server as described in my post to the topic

https://jazz.net/forums/viewtopic.php?t=537

In this case, be sure to set

log4j.logger.com.ibm.team.interop.service.outgoingSyncJob=DEBUG

And before doing that, scan your server log for any message with text like "Outgoing external synchronization is disabled"; if you see that, then you haven't successfully enabled outgoing synchronization. If it is enabled, then the debug logging should display messages every 5 minutes about searching for items needing synchronization - report what you see. (Create or modify a work item that should be synchronized.)

John

Waited a long time. still not seeing the CQ record created when work item is created in RTC client. Here is the

<configuration-data id="com.ibm.team.interop.configuration.syncPreferences" xmlns="http://com.ibm.team.interop/syncPreferences">
<outgoingSync>
<enableCreation syncRuleName="com.ibm.rational.clearquest.sample_schema_repo.Defect"/>
<enableCreation syncRuleName="com.ibm.rational.clearquest.sample_schema_repo.Project"/>

</outgoingSync>
<managerPreferences id="com.ibm.team.interop.service.managers.kernel.ContributorManager" incomingCaseInsensitive="true">
</managerPreferences>
<managerPreferences id="com.ibm.team.interop.service.managers.clearquest.CQExternalManager,com.ibm.team.interop.service.managers.clearquest.CQExternalManagerForUser">

<cqGateway uri="http://localhost:8081/InteropGateway/InteropServlet">
<connection_info>
<cq_connection dbSet="sample_schema_repo" db="SAMPL"/>
<login_info user_id="jazz" password="jazz"/>
</connection_info>
</cqGateway>

</managerPreferences>