지금 지원 담당자와 채팅
지원 담당자와 채팅

Identity Manager 9.2 - Software Management Administration Guide

Extended main data of software

Enter the data for installing software.

NOTE: Permitted values are predefined. Use the Designer to define other permitted values.

Table 3: Extended main data of a software application
Property Description

Installation type

Type of installation. Permitted values are Local installation and Network installation.

Use state

The actual state of usage. Permitted values are Planned, Available, and Not available.

Use state changed on

Date on which the use state was changed.

Access type

How the software is accessed. Permitted values are Limited access and Public access.

Change cycle

Type of change cycle. Permitted values are Yearly, Monthly, Quarterly, and On demand.

Approval process

Approval process for the software. Permitted values are General approval, Approval by item, and Global approval.

Supported operating systems

Provides information about which operating systems are supported. Use the button to insert new operating systems.

Installation date

Installation date of the software.

Risk index

Value for evaluating the risk of assigning the software to identities. Set a value in the range 0 to 1. This field is only visible if the QER | CalculateRiskIndex configuration parameter is set. For more information, see the One Identity Manager Risk Assessment Administration Guide.

Software supervisors

Enter identities that are responsible for the software.

Table 4: Identities responsible for a software application

Property

Description

Expert and deputy Expert

Expert and deputy for the software.

If the software can be requested in the IT Shop, the experts are automatically members in the application role for product owners to which the service item is assigned.

Coordinator

Software coordinator

IT manager and deputy IT manager

IT manager and deputy for the software.

Software inventory data

Enter the required inventory information on the Inventory tab. This information can be included in the performance calculation if necessary.

Table 5: Software application inventory data
Property Description

Usage [months]

Period of use for the software in months.

Internal transfer price

Information about the price for invoicing the software internally.

Company software

Specifies whether the software is the company's own software.

Assigning software to workdesks and identities

You can assign software directly or indirectly to identities or workdesks. In the case of indirect assignment, identities (workdesks) and software applications are grouped into hierarchical roles. The number of software applications is calculated from the position in the hierarchy and the direction of inheritance assigned to an identity (or workdesk).

Software can also be assigned to identities through IT Shop requests. Add identities to a shop as customers so that software can be assigned through IT Shop requests. Any software that can be assigned to this shop can be requested by the customers. Requested software is assigned to the identities after approval is granted.

Using system roles, you can group together software and assign it to identities and workdesks as a package. You can create system roles that only contain software. You can also group any number of company resources into a system role.

Prerequisites for indirect assignment of software to identities

  • Assignment of identities and software is permitted for the role class (department, cost centers, location, or business role).

Prerequisites for indirect assignment of software to workdesks

  • Assignment of workdesks and software is permitted for the role class (department, cost center, location or business role).

ClosedAllow assignments to role classes of departments, cost centers, locations, or roles

NOTE: There are other configuration settings that play a role when company resources are inherited through departments, cost centers, locations, and business roles. For example, role inheritance might be blocked or inheritance of identities or workdesks not allowed. For more detailed information about the basic principles for assigning company resources, see the One Identity Manager Identity Management Base Module Administration Guide.

For more information see the following guides:

Topic

Guide

Basic principles for assigning and inheriting company resources

One Identity Manager Identity Management Base Module Administration Guide

One Identity Manager Business Roles Administration Guide

Assigning company resources through IT Shop requests

One Identity Manager IT Shop Administration Guide

System roles

One Identity Manager System Roles Administration Guide

Detailed information about this topic
관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택