Prior to the merge of the contents of startODL.sh and startODL.oom.sh, executing startODL.sh in standalone mode (using docker-compose from sdnc/oam) triggered SDNC DB initialization, Installation of SDNC Keystore , Installing A1-adapter trust store and Installation of Directed Graphs. Post the merge, these tasks were triggered only if OOM_ENABLED flag is set to "true". However setting this flag to "true" has an impact when run in cluster mode as it expects some parameters which are available only in K8s based deployment. Also the variable name OOM_ENABLED is misleading in standalone environments. The proposed solution is as follows -

1. Remove OOM_ENABLED variable
2. No checks required for triggering Installation of SDNC Keystore and Installing A1-adapter trust store
3. A new variable named SDNC_DB_INIT with default value of "false" will be introduced. This value will be set to"true" via docker-compose so as to initialize SDNC DB in standalone environment. No impact on OOM environment as initialization happens via a separate job.
4. SERVICE_NAME and NAMESPACE values (for cluster mode installation) will be checked for non-empty values. If both are non-empty then the installation is considered as triggered via OOM else standalone environment is assumed