Mapping Configuration

Map the fields between Micro Focus ALM and the other system to be integrated to ensure that the data between both the systems synchronizes correctly.

Click Mapping Configuration to learn the step-by-step process to configure mapping between the systems.

Mapping Checkpoints for Micro Focus Quality Center as the target system
  • Req Full Path field needs to be mapped for requirement entity to synchronize requirement under specific requirement folder. When this field is mapped and incoming requirement path that is mapped with the target Micro Focus ALM field does not exist in Micro Focus ALM, then you can create same hierarchy in Micro Focus ALM as a requirement folder tree by mapping one more extra boolean field. This field is ‘Req Folder Auto Create’ with default value ‘true’.


Integration Configuration

Set a time to synchronize data between Micro Focus ALM and the other system to be integrated. Also, define parameters and conditions, if any, for integration.

Click Integration Configuration to learn the step-by-step process to configure integration between two systems.

Criteria Configuration

If you want to specify conditions for synchronizing an entity between Micro Focus ALM and the other system to be integrated, you can use the Criteria Configuration feature.

Go to Criteria Configuration section on Integration Configuration page to learn in detail about Criteria Configuration.

Configure

To configure criteria in Micro Focus ALM, integration needs to be created with Micro Focus ALM as the source system.

Query

Query in Micro Focus ALM is the valid SQL (version 10.0)/Rest (version 11.x,12.x) query that can contain any column property name (internal name of fields) available in Micro Focus ALM.

Sample Queries
  • Micro Focus Quality Center 10: BG_PRIORITY=’1-Low’ (Steps given above are applicable for version 10.0 only)
  • Micro Focus Quality Center 11.X/12.x:
    • priority[1-Low];status[Open] [Rest based queries does not allow to use ‘or’ condition]
    • creation-time[>2017-11-02]
    • Search for custom field User_02 with value 80. The front-end name of User_02 is Remote Id:user-02[=80]

Criteria with value containing ” is not supported in Integration Configuration.

Learn how How to find out internal name/key in version.

Known behavior
  • Micro Focus ALM 11 allows creating entity even when mandatory fields are not specified.
  • Micro Focus ALM 10 truncates data of custom fields if the data size is greater than field length.

The usage of Micro Focus ALM comments is based on certain assumptions. Click Micro Focus ALM comments to learn more.


Appendix

How to find out internal name/key in version 10.0

To know the internal field name, refer to Tools->Customize->Project Entities and here:

  • Expand entity type that is selected in integration, for example ‘Defect’.
  • Select attribute for which internal name needs to be found.
  • On the right pane, it will appear labelled as ‘Name’.
  • If it is an enumerated attribute, set of values can be found by clicking the Go to List button.

Micro Focus ALM

How to find out internal name/key in version 11.x/12.x
Note: For Microfocus ALM/QC version 11 or higher, you might need to keep the value in ” ” , if it contains space (It is recommended to use the values as shown in Micro Focus ALM/QC UI filter). For example, user-01[“OpsHub & Inc”]
Note: To find the internal name/key, when Microfocus ALM is running on the HTTPS, go to: https://hostname:port/qcbin/rest/domains/[DOMAIN]/projects/[PROJECT]/[requirements/defects/tests]/{Existing requirement/defect/test id}?login-form-required=y. (The port number can be skipped if the port for Microfocus ALM (running on HTTPS) is 443)

Proxy Configuration steps
  • Before performing the following steps, please make sure the server on which you are configuring proxy satisfies the prerequisites for proxy configuration
  • Navigate to <OpsHub_Installation_Directory>\Other_Resources\Resources directory.
  • Extract OpsHub_ALMQC_WebService.zip from the above-mentioned directory to IIS directory (C:\Inetpub\wwwroot\). This will create the HPQCWebService directory inside the IIS directory (e.g. C:\Inetpub\wwwroot\HPQCWebService).
    prerequisites
  • Set Physical path to the extracted directory (C:\Inetpub\wwwroot\HPQCWebService). Set Site name. Set port on which this proxy will serve requests. For example, if you want to create the website with the name HPQCWebservice, which will be bound with the 8844 port of IP address 10.13.28.178, then refer to the configuration shown in the image below.
    prerequisites
    Note: If you will not bind the website with an IP address (E.g. if you select All Unassigned in the IP address field), then the website will be bound to the localhost.
  • This will create an Application Pool with the same name given as Site name. In the Connections pane, expand the server name, and then click Application Pools. Navigate to the application pool that is used for OpsHub ALM/QC Web Service application. In the Actions pane, click Advanced Settings. In the Advanced Settings dialog box, set the following values for properties in given sections:
    GeneralCPUProcess ModelRapid-Fail Protection
    .NET framework Version: v2.0

    Enable 32-Bit Applications: True

    Managed Pipeline Mode: Classic

    Processor Affinity Enabled: True

    Processor Affinity Mask: 1

    Maximum Worker Processes: 1Enabled = Fast
    Note: Enable 32-Bit Applications is required only when the Proxy Host machine is 64-Bit.
  • For the reference, please refer below screenshot of Advanced Settings.
    prerequisites
  • Open %systemroot%\Microsoft.NET\Framework\v2.0.50727\CONFIG\machine.config file in notepad. Replace processModel section under <system.web> with the following :
    <processModel enable=”true” autoConfig=”false” maxWorkerThreads=”1″ minWorkerThreads=”1″ />
  • Open web.config from OpsHub ALM/QC Web Service application in a notepad and change following properties: Set the value of “value” attribute of <param name=”File”> element under <configuration> <log4net><appender> with the valid path to logger file that has appropriate write permission for logging. For example, when we save logs to the C:\logs\ folder, the setting will look like this: <configuration> <log4net> <appender name=”LogFileAppender” type=”log4net.Appender.FileAppender”> <param name=”File” value=”C:\logs\OpsHubProxyLog.txt” />.
  • Set following date formats in Region and Language:
    • Short date: M/d/yyyy
    • Long date: dddd, MMMM dd, yyyy
    • Short time: h:mm tt
    • Long time: h:mm:ss tt
  • Restart IIS.
  • With the above configuration, the OpsHub ALM/QC web service will be deployed successfully. To check whether the web service is deployed properly or not, click Browse Website from the Actions pane in the IIS Manager.
    prerequisites
  • Please make sure that the Directory Browsing is enabled for the added website. For example, when you have added the website HPQCWebservice, then to enable Directory Browsing for the website HPQCWebservice, go to Sites -> HPQCWebservice -> Feature View -> Directory Browsing -> enable
    Feature View
  • To refer to the deployed web service, use http://<Host name\IP address>:<Port Number>/HPQCService.asmx link (IP address and the port number will have the same value as mentioned for the website configuration in the IIS Manager). For example, http://10.13.28.178:8844/HPQCService.asmx
    Note: The proxy can be deployed with the default application pool .NET v4.5 Classic. To deploy proxy with the default application pool, above-mentioned changes must be done in this application pool. For example, after you have added the website HPQCWebservice, then to change the application pool for the website HPQCWebservice, go to: Sites -> HPQCWebservice -> Basic Settings -> Select ->Application Pool -> .NET v4.5 Classic
    Feature View


Micro Focus ALM comments

Micro Focus Quality Center (QC) comments work on the following underlying assumptions:

  • Comment once added will not be deleted and can only be accumulated. However, if you delete the previously added comment, the poller won’t fail but it will synchronize other comments of all the revisions on the target system.
  • Comment once added will not be modified. Updating the previously added comment will result into synchronization of comment value of all the revisions on the target system.
  • The reason behind above assumptions being the manner in which comments in Micro Focus ALM are compared between successive revisions. Comments in Micro Focus ALM are compared based on the assumption that the new value of comment starts with the old value of comment, this being the only way by which difference in content of successive comments can be ascertained, above best practices should be followed to avoid duplicity.