Chatee ahora con Soporte
Chat con el soporte

Identity Manager 9.2 - Configuration Guide

About this guide One Identity Manager software architecture Customizing the One Identity Manager default configuration Customizing the One Identity Manager base configuration One Identity Manager schema basics Editing the user interface
Object definitions for the user interface User interface navigation Forms for the user interface Statistics in One Identity Manager Extending the Launchpad Task definitions for the user interface Applications for configuring the user interface Icons and images for configuring the user interface Using predefined database queries
Localization in One Identity Manager Process orchestration in One Identity Manager
Mapping processes in One Identity Manager Setting up Job servers
The One Identity Manager Service functionality Tracking changes with process monitoring Conditional compilation using preprocessor conditions Scripts in One Identity Manager
Visual Basic .NET scripts usage Notes on message output Notes on using date values Tips for using Windows PowerShell scripts Using dollar ($) notation Using base objects Calling functions Pre-scripts for use in processes and process steps Using session services Using #LD notation Script library Support for processing scripts in the Script Editor Creating and editing scripts in the Script Editor Copying scripts in the Script Editor Testing scripts in the Script Editor Testing script compilation in the Script Editor Overriding scripts Permissions for running scripts Editing and testing script code with the System Debugger Extended debugging in the Object Browser
One Identity Manager query language Reports in One Identity Manager Adding custom tables or columns to the One Identity Manager schema Web service integration One Identity Manager as SCIM 2.0 service provider Processing DBQueue tasks One Identity Manager Service configuration files

Querying configuration parameters

The full path for the configuration parameter always has to entered when configuration parameter are queried.

Syntax

Session.Config().GetConfigParm("<full path>")

When a configuration parameter is tested in a generating condition in VB.Net syntax, the function returns a string. In order to compare this value to a numerical value, the configuration parameter has to be set and contain a numerical value. This depends on the implicit value type conversion from VB.Net. If the configuration parameter is not enabled, the function returns an empty string ("") that cannot be compared to a numerical value. This results in a VB.Net runtime error. Configuration parameter values are therefore always compared to strings.

Do not use:

Session.Config().GetConfigParm("QER\Person\User\DeleteOptions\Homedir")=1

Use instead:

Session.Config().GetConfigParm("QER\Person\User\DeleteOptions\Homedir")="1"

In order to ensure that a logical value is always returned, the VID_IsTrue function should be used.

Example

If VID_IsTrue(Session.Config().GetConfigParm("QER\Person\User\DeleteOptions\Homedir")) Then ...

Related topics

Testing for the existence of certain database entries

NOTE: The test should take place without taking access permissions into account.

Syntax

Session.Source().Exists("<Tablename>","<WhereClause>")

Example

Session.Source().Exists("Person", "CentralAccount = '" & accnt & "' and uid_person <> '" & uid_person & "'")

Related topics

Querying session object global variables

Global variables are allocated by the set up program. In addition to the predefined variables, all environment variable and custom variables defined on the session object can be used. Custom session variables can be defined, for example, using scripts, methods, or customizers.

NOTE: If you define a custom session variable, you must remove it again afterward. Otherwise it remains for the rest of the session and, in certain circumstances, the wrong processes can be generated.

Syntax

Variables("<Variable name>")

Example of use in process step parameters

Value = Variables("GENPROCID")

Value = CBool(Session.Variables("FULLSYNC"))

Table 134: Permitted predefined global variables
Variable Meaning

EnvUserName

 

Name of user to be authenticated in the environment, for example, Domain\User in Active Directory

FullSync

 

The variable is set by all synchronizers. The values are True and False.

GenProcID

Unique Process ID number

LogonUser

DialogUser.Username of the currently logged in user.

DialogUserUID

DialogUser.UID_DialogUser of the logged in user.

UserName

Name displayed in XUserInserted or XUserUpdated.

UserUID

Logged in user’s UID_Person, if user related authentication is being used.

ShowCommonData

Specifies whether system data is shown (value = 1) or not shown (value = 0). The variable is evaluated in the Designer by the Show system data program setting.

SessionType

Specifies whether a direct database connection or a connection over an application server is supported.

Direct database connection only: '%SessionType%' = 'Direct'

Connect with the application server only: '%SessionType%' = 'AppServer'

Feature_<Featurename>

Queries additional program functions (DialogFeature) that are available for the user. The value is 1 when the program function is available, otherwise the variable is not set.

ManageOutstandingOperation

This variable is used to differentiate between running operations during post-processing of outstanding objects in target system synchronization. Permitted values are Delete, DeleteState, and Publish.

Related topics

Using #LD notation

#LD notation is used for displaying language-dependent information. #LD notation is mainly used in process tracking and processing notification, but it can also be used in scripts that are stored in the script library.

Syntax

Value=#LD[<language>|<language code>](<key>,{<Parameter>}*)#

where:

<language>|<language code>

(Optional) Language or language code for the output.

<Key>

Basis string with place holder. The place holder syntax corresponds to a format place holder in VB.Net ({0} to {9})

<Parameter>

Parameter for replacing the place holder (comma delimited)

Table 135: Using #LD notation
Context Table.column

Remarks

Process tracking

Job.ProcessDisplay

Mapped to DialogProcessStep.DisplayName

JobChain.ProcessDisplay

Mapped to DialogProcessChain.DisplayName

JobEventgen.ProcessDisplay

Mapped to DialogProcess.DisplayName

Process handling notification

Job.NotifyAddress

 

Job.NotifyAddressSuccess

 

Job.NotifyBody

 

Job.NotifyBodySuccess

 

Job.NotifySender

 

Job.NotifySenderSuccess

 

Job.NotifySubject

 

Job.NotifySubjectSuccess

 

JobRunParameter.ValueTemplate

On in the MailComponent process component

Templates

 

DialogColumn.Template

 

DialogColumn.CustomTemplate

 

Formats

 

DialogColumn.FormatScript

 

DialogColumn.CustomFormatScript

 

Task definitions

DialogMethod.MethodScript

 

Insert values

 

 

 

DialogObject.InsertValues

 

DialogTable.InsertValues

 

DialogTree.ListInsertValues

 

DialogSheet.InsertValues

 

Selection scripts

 

DialogTable.SelectScript

 

DialogObject.SelectScript

 

Process generating scripts

Job.GenCondition

 

Job.PreCode

 

Job.ServerDetectScript

 

JobChain.GenCondition

 

JobChain.PreCode

 

Related topics
Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación