Absent Member.
Absent Member.
608 views

Issue Manager JIRA Integration

We currently have Issue Manager integrated with JIRA but today have run into an issue where Silk Central as sent a high volume of requests to JIRA to update issue/status(s).

I am unclear on how the synchronization works between the 2 systems.

Is there a way to check what triggered this high volume sync? Or somewhere we can check the configuration of the scheduled sync?

Tags (2)
0 Likes
3 Replies
Micro Focus Expert
Micro Focus Expert

Hi ddang31,

Issue tracking integrations are updated either by schedule or manually.

 

1. Logs on scheduled updates can be found in the AppServer log files (accessible via Administration > Log Files > Application Server Log).

The schedule is configured in TMAppServerHomeConf.xml (e.g. C:\Program Files (x86)\Silk\Silk Central 19.5\instance_1_silk\Conf\AppServer\TMAppServerHomeConf.xml). The relevant configuration options can be found in Config > IssueStateUpdate

It is possible to configure the UpdateInterval in minutes, to turn on/off the issue statistics, to turn on/off issue statistics for baselines and to optionally schedule a timestamp when the update should start for the first time.

A description how to disable updating of external issue statistics can be found here: 

http://documentation.microfocus.com/help/topic/com.microfocus.sctm.doc/GUID-BB41264C-7466-4846-9185-08FC9201CB87.html

 

2. Manual updates can be triggered In Tests > Details View > Tab: Issues

If you press the button Update Issue States then immediately the update starts. Logs on this can be found in the FrontendServer log files.

In both cases most of the data is logged in log level DETAILED or higher.

 

Regards,

Hubert

Absent Member.
Absent Member.

Hi Hubert,

We've investigated the configuration of the scheduled Sync and have confirmed no manual syncs are being run frequently.

But we continue to see a high volume of Attempts from Silk Central authenticating to JIRA.

Any idea's on how we can narrow our search to find the root cause of this problem as it is creating performance issues with JIRA.

Thanks,
David
0 Likes
Micro Focus Expert
Micro Focus Expert

Hi David,

 

If you set the log level to DEBUG then more information will be visible in the logs.

Frontendserver (manual triggered updates), e.g.

C:\Program Files (x86)\Silk\Silk Central 19.0\instance_1_silk\Conf\FrontendServer\SccFrontendBootConf.xml

 

AppServer (scheduled updates), e.g.

C:\Program Files (x86)\Silk\Silk Central 19.0\instance_1_silk\Conf\AppServer\SccAppServerBootConf.xml

 

Config > Log > LogLevel

Set to 3 (= DEBUG)

It is not necessary to restart the services.

Information on the issue updates will be logged to FrontendServer.log and AppServer.log.

 

Regards,

Hubert

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.