User Privileges

  • Create one user for Micro Focus ALM, dedicated to OpsHub Integration Manager. This user should not do any other operations from the Micro Focus ALM’s user interface. For creating user, please refer https://admhelp.microfocus.com/alm/en/12.60/online_help/Content/Admin/cust_users_add_to_proj.htm.
  • Micro Focus ALM/QC user must be an Active site user in Micro Focus ALM/QC. If the user is de-active user in Micro Focus ALM/QC, then activate the user. For help on how to activate the user, please refer Activate the User in Appendix.
  • To use a particular project in Micro Focus ALM/QC, the user must be present as a Project User for that project. For help on how to add a project user in the project, please refer Add project user in project in Appendix.
  • Micro Focus ALM user must have Project Administrator rights on the Project that is to be synchronized. For help on how to set the access rights on project, please refer Add Permissions To Project in Appendix.
Note: In case your Micro Focus ALM/QC is configured with SSO, then the above mentioned user privileges and permissions are sufficient.


Database Prerequisites

  • For Micro Focus ALM Quality Center 10 and 11, supported database types are: MS SQL Server and Oracle.


Proxy Configuration

For certain Micro Focus ALM versions, proxy configuration is required only for specific types of data synchronization, such as:

  • For version 10.0, 11.0, and 11.5: Required only when design steps or requirement traceability need to be synchronized.
  • For version 12.0: Required only when design steps need to be synchronized.
  • For any other version: Required only when test set execution need to be synchronized.
CPUCore duo 1.6 Ghz (or higher) or equivalent compatible processor
Memory (RAM)4 GB (recommended)
Operating system (Tested On)Windows 7, Windows 10, Windows Server 2008, Windows Server 2012, Windows Server 2016
Software–  Visual C++ 2005 SP1 ATL Security Update Redistributable

–  Microsoft .NET Framework 3.5 (SP1)

–  IIS 7.0 with ASP.NET configured in it

–  Micro Focus ALM Connectivity Add-in

Download from: http://<hpqchost>:<port>/qcbin/addins.html

Note: For Test Set Execution Request integration, the Micro Focus ALM/QC Proxy must be configured on a machine on which UFT has been installed. Click here for Proxy Configuration steps.
This proxy-configuration is also required for synchronizing QTP script.


Configurations Required to Copy QTP Script

    Following additional configurations are required to copy QTP script:

  • Quick Test Professional and appropriate QuickTest Professional Add-In must be installed on the machine on which Micro Focus ALM proxy is configured. To download QuickTest Professional Add-In, please follow the link https://hpln.hp.com/page/quicktest-professional-add.


Enable History of Fields to be Mapped

  • It is recommended to enable history at least on those fields that are going to be mapped in the integration for OpsHub Integration Manager and on ‘Modified’ field to ascertain whether any modifications are made on a particular field. Click Enable history of fields to be mapped to learn the steps to enable history of fields to be mapped.
  • If Micro Focus ALM/QC is the target system, then integration recovery will not work if the history has not been enabled. The integration recovery can, in fact, create duplicate entities in Micro Focus ALM/QC. Integration will throw error before performing create/update if history has not been enabled on any mapped field.
  • If Micro Focus ALM/QC is the source system and history has not been enabled, then integration needs to be configured in Current State Sync mode only.


Associate a custom field with the Requirement

  • For the Requirement entity, if user wants to use a custom field in mapping, then the custom field must be associated with all the Requirement Types that will be used in the mapping.
  • Click How to associate a custom field with the Requirement to know the steps for associating any custom field that is being used in integration.




Appendix


Activate the User as a Site User
  • Log in into Micro Focus ALM/QC Site Administration.
  • Click Site Users.
  • Expand the domain and click the User to whom you want to make an Active Site User.
  • Click User Details.
  • Click Activate.
  • Micro Focus ALM/QC


Add project user in project
  • Log in into Micro Focus ALM/QC Site Administration.
  • Click Site Projects.
  • Expand the domain and click the Project for which you need to add user.
  • Click Project Users.
  • Click Add.
  • Click Add from the Users list
  • Site Projects

  • Select the user that you want to add.
  • Click Add selected User
  • Site Projects


Add Permissions to Project
  • Log in into Micro Focus ALM Site Administration.
  • Click Site Projects.
  • Expand the domain and click the Project for which you need to set permission.
  • Click Project users.
  • Mark Project Administrator to the user for which permission required to set.
  • Micro Focus ALM Site Administration


How to associate a custom field with Requirement

To associate a custom field with Requirement type, follow the steps given below:

  • Log in to Micro Focus ALM/QC for the project specified in the integration.
  • Go to Tools->Customize->Requirement Types.
  • Select the specific requirement type that you have mapped in the integration. If one has not selected a specific type of requirement in the mapping, then for all requirement type below steps needs to be followed.
  • Click User Defined Fields.
  • Select the user defined field that you have used in the mapping.
  • Mark enable InType for that particular custom field.
  • For example, if a user has configured an integration between the Functional Type of Requirement of Micro Focus ALM/QC and any entity of the target system, and in the mapping, a user has used custom field Link to Remote Entity. Then to associate the custom field Link to Remote Entity with the Functional Type of requirement. Please refer below image.
  • Micro Focus ALM Site Administration

  • For example, if a user has configured an integration between any type of Requirement type of Micro Focus ALM/QC and any entity of the target system, and in the mapping, user has used custom field Link to Remote Entity. Then the user needs to associate the custom field Link to Remote Entity with all the type of requirement type.


How to Enable History of Fields to be Mapped

To enable/disable history on the field, follow the steps given below:

  • Log in to Micro Focus ALM.
  • Go to Tools->Customize->Project Entities.
  • Expand entity type for which the integration is configured, for example ‘Defect’.
  • Expand System Fields and Custom Fields folders.
  • Search for the attribute that is mapped for the integration.
  • On clicking the attribute, a checkbox labelled History will appear on the right pane.
  • Here you can enable/disable History for the selected attribute based on your requirement.
  • Micro Focus ALM Site Administration

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).
    Note: After extracting the service, The ‘HPQCWebService’ directory must contain the content of the extracted zip file (i.e. The ‘bin’ directory, ‘HPQCService.asmx’ file and ‘Web.config’ file) as its immediate children.
    IIS directory
  • Open Internet Information Service (IIS) Manager, expand server, and right click ”’Sites”’ and then select ”’Add Web Site”’. This opens ”’Add Web Site”’ dialog.
  • Open Internet Information Service (IIS)
  • 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.
    Open Internet Information Service (IIS)
    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.
    Advanced Settings
  • Open %systemroot%\Microsoft.NET\Framework\v4.0.30319\CONFIG\machine.config file in notepad. Replace processModel section under with the following :
    <processModel enable=”true” autoConfig=”false” maxWorkerThreads=”1″ minWorkerThreads=”1″ />
  • Note: In the path mentioned above the v4.0.30319 part may differ depending on the version of .NET framework installed.
  • 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.
    OpsHub ALM/QC web service
  • 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
    OpsHub ALM/QC web service
  • 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 as well. 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
    OpsHub ALM/QC web service