Associate an application service to hardware model
Track your equipment assets such as computers and servers using hardware models.
Vorbereitungen
Starting with the Xanadu release, the legacy Technology Portfolio Management module has been deprecated from Enterprise Architecture (formerly Application Portfolio Management). However, if you’re an existing user of Enterprise Architecture (formerly Application Portfolio Management), you can still use the legacy Technology Portfolio Management module. If you’re a new activation user, the legacy Technology Portfolio Management module isn’t available.
You can leverage the same functionality by using the Technology Portfolio Management store application within the Enterprise Architecture Workspace. To learn more, see Manage the Technology Portfolio Management (TPM) in Enterprise Architecture Workspace.
Role required: sn_apm.apm_user
Warum und wann dieser Vorgang ausgeführt wird
Your business applications may run on multiple application services, which in turn can be installed on different types of hardware. Therefore associating application services with hardware models helps to know the risk on the Application Service due to underlying hardware.
When you run the Fetch Product Models job, the application service is automatically associated with a hardware model. The application service and the hardware product model are mapped and a record is created in the Application Service Hardware Models [sn_apm_tpm_app_service_hardware_model] table. However, you can also manually associate an application service to all hardware models, including the hardware.
After the Load TPM Risk Parameters and compute Application Service Risks scheduled job is executed, the technology risk data of the hardware model are generated and stored in Hardware Model Risks [sn_apm_tpm_hardware_model_risk] table.