Presentation of the BDNA Connector
Use Case in HOPEX ITPM
In the ITPM solution, the BDNA Connector is available to the Functional Administrator. He/she is in charge of importing data from BDNA. He/she can initialize a new repository by importing software technologies from BDNA and use the Functional Administration Desktop to manage automatic update workflows and alert tools.
The Technology Portfolio Manager (TPM) is responsible for software technologies and their life cycle. He can include his software technologies in the scope of the automatic update in order to be notified automatically of any changes. He/she can also send the Functional Administrator a request to prepare the import of new software technologies using BDNA.
The Application Portfolio Manager should subscribe to the standard notification on sensitive software technologies that are used by his applications. Thus, when these software technologies are updated by automatic or manual import from BDNA properties, he will receive a notification of the change. He will analyze the impact and decide how to proceed (keep the software technology, use a new version or change it).
Prerequisite Conditions
The BDNA Connector is available with HOPEX IT Portfolio Management and requires the BDNA license that you will specify in the authentication settings.
To be able to connect to BDNA, you must set the Data Exchange options related to exchanges between HOPEX and third party tools.
To define the required options:
1. Start HOPEX Administration.
2. In the navigation tree, right-click the HOPEX site name and select Options > Modify.
The site options window opens.
3. Expand the Data Exchange > Import folder.
4. Click the BDNA folder.
5. In the right pane of the window, enter information to access BDNA APIs (provided by BDNA). These are the options visible under Activate BDNA:
• URL address of the BDNA API: this is the URL of the BDNA public catalog The HTTP protocol is used by default but to secure the exchanges you can use the HTTPS protocol by entering it directly in the option.
• Authentication user for the BDNA API; BDNA user
• Authentication key for the BDNA API: password
6. Activate SMTP proxy if necessary (provided by your IT service):
• Check Activate Proxy for BDNA API.
• Enter the address of the proxy.
• Enter the port.
7. Check the Authentication for the proxy option if required.
Scope of BDNA Connector
Within the context of the technology management in ITPM, the BDNA Connector enables import of the following concepts:
• Technology types: categorizes software products by the function they perform.
• vendors. Example: Microsoft
• Software technologies. Example: MS Office
Mappings with HOPEX concepts are detailed below.
Object correspondence
|
BDNA
|
HOPEX
|
|---|---|
|
Manufacturer (vendor)
|
Org Unit
|
|
Taxonomy (technology type)
|
_Type
|
|
Software Product
|
Technology
|
|
Software Edition
|
Variation of Software Technology
|
|
Software Standard Major/Minor Release
|
Variation of Software Technology
|
In BDNA, software technologies are divided into:
• Products (for example: Microsoft Office)
• Editions (for example: Family, Professional)
• Versions (for example: 2013, 2016)
• Releases (major, minor)
Only versions and releases have information on the life cycle (publication date, end support, end of extended support).
Software Products imported from BDNA BDNA™ into HOPEX are saved as Software Technologies. Editions and versions of a software are represented by variations of the Software Technology in MEGA.
