If you modify Angular library code, you must create and deploy custom versions of all Angular applications that will use the modified Angular library.
For example, if you modify the qer Angular library, you must also compile the qer-app-portal, qer-app-operationsupport, and qer-app-pwdportal Angular applications, because all of these applications contain the qer Angular library.
If you modify Angular plug-in library code, you must create and deploy a separate version of the Angular plug-in library itself and all Angular plug-in libraries that depend on it.
For example, if you modify the tsb Angular plug-in library, you must also compile the aad and o3t Angular plug-in libraries because these Angular plug-in libraries contain the tsb Angular plug-in library.
Plug-ins are Angular libraries that are dynamically loaded at runtime. The plug-ins are managed by the API Server. Plug-ins are automatically detected by the API Server by searching the program directory for files named imx-plugin-config.json.
The following sample file specifies that the Angular plug-in library ccc should be loaded into the qer-app-portal application. The name of the Angular module to be instantiated is CustomConfigModule.
{ |
"qer-app-portal":[ |
{ |
"Container":"ccc", |
"Name":"CustomConfigModule" |
} |
] |
} |
To add a plug-in
-
On the API Server, create the file imxweb\<Angular plug-in library name>\imx-plugin-config.json with the following content:
{ |
"<Name of the HTML application>":[ |
{ |
"Container":"<Name of the Angular plugin library>", |
"Name":"<Name of the Angular module>" |
} |
] |
} |
-
Import the file into your One Identity Manager database using the Software Loader and assign it to the API Server machine role. For more information on importing files using the Software Loader, see the One Identity Manager Operational Guide.
-
(Optional) To check if the HTML application loads the plug-in correctly, open the <API Server URL>/imx/applications URL and check that the corresponding plug-in appears at the HTML application position in the list.
You can check HTML applications for missing user interface translations using the ImxClient command line program. For more information about the ImxClient command line program, see the One Identity Manager API Development Guide.
TIP: Translatable text is marked in the source code with the #LDS# prefix.
To check an HTML application for missing translations
-
Start the ImxClient command line program.
-
In the folder you want to check for missing translations, run the check-translations command.
This creates a report. The report shows you any files containing texts that have not yet been translated or have not been translated in full.
-
(Optional) To add translation keys and translations, use the Designer program. For more information about translations, see the One Identity Manager Configuration Guide.
To deploy new HTML applications for use and display them on the API Server's home page, you must add the HTML applications to the database.
To add an HTML application to the database
-
Start the Designer program.
-
Connect to the relevant database.
-
In the navigation, click the Base data > Security settings > HTML applications category.
-
On the menu bar, click 
(Create a new object).
-
Click the new entry in the list.
-
In the Properties view, enter the HTML application data in the respective fields. Enter at least the following information:
-
Display name: Enter a name for the HTML application.
-
HTML application: Enter the path CCC/<name of your HTML application>.
-
Precompiled: Set the value to True.
