Application or Server Specific Overrides
The Flex framework is used by several NMS applications. Application or server specific overrides allow you to tailor the configuration for those applications.
Override specific sections of the Flex configuration for different applications or servers by adding an appOverrides section to a Flex configuration file. Each entry is evaluated against an application context object containing the URL, flags, and information about the connected WebLogic server. To inspect this object, enter the following in the browser development tools:
window.appConfigContext
The key fields are:
• isWws: Whether Flex is running within Java Web Workspace; commonly used to identify the Java Common Network Viewer.
• app: The application that is running, such as nmsDerms for the DERMS application.
• serverInfo / mobileInfo: Details from the connected WebLogic server.
• URL: The URL of the WebLogic server from which the application is running.
• isMobile: Whether Flex is running on a mobile device, such as an iPad.
The overrides are tested against this object using standard Flex expression syntax. Matching override content is applied in the same way as other Flex configuration overrides, on top of the default Flex configuration overrides.
For example, use IDCS authentication for users connecting through one WebLogic server and NMS authentication for users connecting through another:
{
"config": {
"client": {
"login": {
"appOverrides": {
// Enable IDCS login on the server matching example-wls-url
"$matches(URL, 'example-wls-url')": {
"idcs": true
}
}
}
}
}
}