This is part 2 of HP ALM and SAP Solution Manager integration blog series. Part 1 is available in the below link
1. Prepare System
1.1 Schedule background jobs
Go to step 4.1 Schedule Background Jobs under Partner test management guided procedure
Schedule the background jobs by clicking on Execute All button
Note: This is not required if you don’t want to sync Solution documentation and Test Results automatically.
1.2 Activate ICF Services
Go to step 4.2 Activate SICF Services under Partner test management guided procedure
Click Execute All button to activate the required ICF services automatically
1.3 Define Partner connections
In this step, you define the partner connections by creating a partner and configuring the Web services with the SOA Manager.
Choose Create Partner. In the Partner System Connection screen enter the below details and choose Create Connection.
Adapter Alias Name: HPEI_<SolMan SID>
External Tool Type: HP ALM
Select the partner connection and click on launch logical port for blueprint api
Create –> WSDL based configuration
Provide the logical port name and click on next
Enter the ALM DEV WSDL URL
https://<<HP ALM Host name>>:<port>/qcbin/EIServer/services/AGS_SM_BLUEPRINT_API?wsdl
Click on Next until Step 6 and click on Finish.
No need to change any values from Step 3 onwards
Click on Launch binding under Service Definition
Enter the service name and binding name
Select SSL and Sigle Sign on using SAML. Click on Next and Finish
Go to Service Desk Tab (only required if you want to integrate defects)
Create Logical ports and Binding using the above steps
WSDL for CO_AGS_SD_ADAPTER_API
https:<<HP ALM Hostname>:<port>/qcbin/EIServer/services/ICT_SERVICE_DESK_API
WSDL for CO_PCICT_SERVICE_DESK_API
https:<<HP ALM Hostname>:<port>/qcbin/EIServer/services/AGS_SD_ADAPTER_API
Select the Partner Connection –> click on Reload –> Assign the logical ports and binding to the partner using drop down
Note: This needs to be performed for all logical ports and binding that you have created above.
2. Setup Service Desk Related Configuration
2.1 Register External Service Desk
Go to transaction ICTCONF, Click on Add and Provide the below details
Note: The logical port name may vary based on the logical name used in partner connection definition
Activate the connection
2.2 Define Transaction Type
2.2.1 Define Target Transaction Type
If you use several transaction types and receive messages from external service desks, you can use BADI_DET_PROC_TYPE_FOR_EXT_SD BAdI implementation to specify in which target transaction type the message is created.
Go to transaction SE18
BAdI BADI_DET_PROC_TYPE_FOR_EXT_SD –> Change
Right click Implementation and Create BAdI implementation
Provide enhancement implementation name and Short Text
Double click on Implementation Name. Provide BAdI implementation name, description and Implementing Class name
Enter the below code in the implementation
CV_PROC_TYPE = ‘ZMIN’
Note: Make sure the Z* transaction name you provide here exists already. Else copy the S* transaction to the Z* namespace using transaction copy tool.
Activate the BAdI implementation
2.2.2 Adjust Status Schema for Transaction Type
Open view CRMV_PROCESS_MA in transaction SM34
Double click on your Z* transaction
Assign SMINHPQC to the status profile
2.2.3 Define Extended Interface Mapping
Go to transaction SE38 and execute report AGS_ADAPTER_ICTCUSTOM_AUTOCONF
Select the third party GUID which you have created in transaction ICTCONF and enter the Z* transaction type
Click on execute to register to map the interface
2.3 Synchronize Application components, Systems, Client
Go to step 6.3 in Partner test management guided procedure
Click on Execute All to schedule the background job for automatic synchronization of Application components, systems, clients into HP ALM
2.4 Defect Field Mapping in HP ALM
Login to ALM Desktop client
Go to Tools –> SAP tools –> Defect Mapping
In the Application box, select the appropriate Solution Manager system.
In the Required Fields section, map a required ALM field to a required Incident Management field.
Note: Field mapping should be performed for Detected by and Severity fields. Other fields are optional
Select a non-mapped ALM field in the left grid that you want to map. Possible SAP fields for
mapping is displayed in the right grid. Select a corresponding field in the right grid, and click
the Map Field button.
Similarly map HP-ALM Severity field with SolMan Priority field.
Also, perform value mapping for Severity field by clicking on Value Mapping button
2.5 Update Defect status in ALM automatically when incident status is set to proposed solution
Go to transaction CRMC_ACTION_DEF –> Select ZMIN_STD and Double click on Action Definition
Click on New entries and enter the below details
Double click on Processing types and click on New entries
Select method call using value help under Permitted processing type of action
Select PASS_ICT_PROPOSE_SOL_TO_THIRD using value help in Method
Save your changes.
Go to transaction CRMC_ACTION_CONF, enable technical names and change to Edit Mode
Double click on ZMIN_STD
Click on Create and Select the action which you have create above
Make sure the same action is selected and go to Start Condition –> Click on Edit condition
Provide name for the schedule condition and click under condition definition to create a start condition
Provide the start condition as below
Save your changes.
2.6 Create Project association
Go to Partner test management application in SOLMAN_WORKCENTER –> Test Suite –> Click on Partner Test Management Tile
Click on New Association button
Map the Production branch with Production Project
Note: It is mandatory to associate the Production branch first
Similarly create association for Development and Maintenance branches
You can filter the type of document/execute transferred to HP ALM using Add Test Objects button under Test object filters tab.
You can map SAP Solution Manager attribute with HP ALM attribute for value transfer. This can be performed using Map attribute button under Attribute Mapping tab
3. BPCA Integration
3.1 Create Endpoint for BPCA Web service
Go to transaction SOAMANAGER –> Web Service Configuration –> Search for AGS_BPCA_WS_API –> Click on Service Definition
Click on Create Service
Enter the below data and click on Next
Note: Provide the binding name in small letters (Not B in caps). BPCA URL is not getting updated in ALM if it is in caps
Select SSL transport level security and SAML message authentication
Leave other fields unchanged, click Next and Finish
3.2 Create Logical Ports in SAP Solution Manager
Go to transaction SOAMANAGER –> Web Service Configuration –> Search for CO_AGS_BPCA_3PTM_API –> Click on the consumer proxy
Click on Create –> WSDL based configuration
Enter the logical port name and description. Click on Next
Enter the WSDL URL and click on Next
https://<HP ALM Host name>:<port>/qcbin/EIServer/services/AGS_BPCA_3PTM_API_72?wsdl
Click on Next
Click on Next and Finish. No need to change any values
3.3 Register Partner Test Tool in SolMan
Go to transaction SM34
Maintain and click on New Entry
Create the below entry
Click on Ping. The tool should be registered and you will get the below output
Save, go back to SM34 and Reopen the View cluster
Select the newly created entry and double click on “Partner Test Management Test Case Types”
All the test case types in HP-ALM should be visible
This will also create the entry in HP-ALM under Tools –> SAP Tools –> BPCA Integration
4.1 Missing authorization error in ALM
The below error will be raised when triggering import from HP-ALM
Check the authorization logs of SM_HPCOM user
Provide the below authorization
This will trigger SolDoc sync from ALM. Still you may find the requirements not updated in ALM. This due to missing authorization for SOLDOC and LMDB. Keep on checking SU53 logs of SM_HPCOM user and provide all the required authorizations until the sync is successful.
4.2 Number of required defect fields in ALM is different from Solution Manager
Make sure connectivity between ALM and SolMan is established properly using SSL and SAML certificates. check the authorization logs for SM_HPCOM user in SU53. Provide the missing authorization.