Configuring the Silk Central Location in Issue Manager

Describes how to configure the location of your Silk Central installation in Issue Manager. This enables the traceability from issues in Issue Manager to related tests in Silk Central. For additional information on using the traceability feature, refer to the Issue Manager documentation.

To configure the Silk Central location in Issue Manager:

On the Instance Administration page, stop the front-end server of the instance that you want to modify.
Open the SRFrontendBootConf.xml file with a text editor. The default path for this file is C:\Program Files (x86)\Silk\Silk Central 20.0\instance_<instance number>_<instance name>\Conf\FontendServer on the front-end server.
Locate the Alm\ElementServiceEndpoint and Alm\LinkServiceEndpoint XML tags.
Replace the default values localhost:19120 with the host and port information of your Silk Central installation in both tags. If your Silk Central installation uses the same front-end server as your Issue Manager installation, and you use Tomcat Web server with the default port, then you can leave the default values.
Save and close the XML file.

If you do not use the default port, edit the file configuration.xml, located in \instance_<instance number>_<instance name>\wwwroot\AlmServices1.0. Locate the connectString XML tag and set the correct ports. Example:

<properties>
   <name>connectString</name>
   <!-- value>com.borland.tm.system.endpoint=http://gershwin:19120/services/sccsystem;
      com.borland.tm.spi.endpoint=http://gershwin:19120/services/SpiService</value  -->
   <value>com.borland.tm.system.endpoint=http://MyHost:8555/services/sccsystem;
      com.borland.tm.spi.endpoint=http://MyHost:8555/services/SpiService</value>
</properties>

Re-start the front-end server.