Environment

ControlPoint 5.x

Situation

How do we ingest content from JAMA using ControlPoint?

Resolution

No core connector is shipped with CP for ingesting from JAMA however it is possible to optionally obtain a JAMA connector as part of IDOL. You can then use the JAMA connector in conjunction with an XML repository created in ControlPoint to allow you to ingest and browse content from JAMA.

If you need to setup a new XML repository follow the instructions in guide available from support called 'How to add additional XML Connectors in ControlPoint.pdf' available from Support.

Ensure JAMA administrator assigns admin privileges to the correct account in JAMA you are wishing to use that has access to the data in JAMA.
Inside JAMA go to user profile for this account and click Set API Credentials.
Note the Client ID and client secret shown and use these to update oauth_tool.cfg.

Invoke Administrative command prompt.
Change directory to JAMA connector and type: oath_tool.exe
After it runs it will generate OAuth bin file as referenced by Oauth.cfg.

Stop JAMA connector
Delete logs, actions folder and the connector*.db file.

Updated JAMA connector.cfg so it automatically commences a scan of the named repository

e.g.

[Connector]
EnableScheduledTasks=TRUE
ScheduleStartTime=now
ScheduleCycles=1

[FetchTasks]
Number=1
0=TaskJAMARepo

Then start connector and check ingestion commences via inspection of  the synchronize.log

The JAMA connector supports:
- Projects
- Items (including test cyles, test plans, test runs, and attachments).
- Comments
- Tags
- Relationships

You can use the regular expression examples in the JAMA connector.cfg to fine tune exactly what you want to ingest or exclude etc.

Access support article here