Can We Avoid Hardcoding Hostnames in DISA config.properties File?

(Doc ID 2311893.1)

Last updated on OCTOBER 31, 2017

Applies to:

Siebel CRM - Version 16.8 [IP2016] and later
Information in this document applies to any platform.

Goal

Having DISA installed on different environments - DEV, TEST and PROD, while deploying DISA to agents' desktops for testing, the config.properties file would need to be customized to environment specific whitelisted domain URLs.

How to circumvent the whitlelist settings in DISA config.properties  file in order to avoid creation of multiple environment specific(DEV, TEST, PROD) DISA packages for deployment on users' machines ? 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms