Idea ID: 2873742

The maintenance of configuration data for the application integrations

Status : New Idea

Delete all configuration data, when the last backup definition for the integration is deleted or ask for deletion.

Tags:

Labels:

Exchange
Oracle
Other Integrations
PostGRESQL
SAP - SAP HANA
SharePoint
SQL-MySQL
  • No, that's not the desired result. The main issue is, that unused configuration data remains in the directories. A cleanup job or a workflow (recognizes that it is the last link to the configuration data) is desirable. For Oracle I'm using the following script e.g. to create a cleanup job:

    grep CLIENT /etc/opt/omni/server/barlists/oracle8/* |cut -d":" -f2 | awk '{print $2 " " $3}' | tr -d "\"" | while read DB HOST
    do
    DBID=`cat /etc/opt/omni/server/integ/config/Oracle8/${HOST}%${DB} | grep ORACLE_DBID | cut -d"=" -f2 | tr -d "\'" | tr -d ";"`
    echo "$HOST;$DB;$DBID"
    done > /tmp/configs_with_barlists.lst

    echo "Barlists with configuration entries: /tmp/configs_with_barlists.lst"

    # Look for DBID without Barlist
    for file in `ls -1 /etc/opt/omni/server/integ/config/Oracle8/[0-9]*`
    do
    ID=`basename $file`
    grep "${ID}$" /tmp/configs_with_barlists.lst > /dev/null
    if [ $? -ne 0 ]
    then
    echo "rm $ID"
    fi
    done > /tmp/remove_ora_integ.sh

    # Host without Barlist
    for file in `ls -1 /etc/opt/omni/server/integ/config/Oracle8/*%_OB2_GLOBAL`
    do
    HOST=`basename $file | cut -d "%" -f 1`
    grep "${HOST};" /tmp/configs_with_barlists.lst > /dev/null
    if [ $? -ne 0 ]
    then
    DBINST=`cat /etc/opt/omni/server/integ/config/Oracle8/${HOST}%_OB2_GLOBAL | grep INSTANCE_LIST | cut -d"=" -f2 | tr -d "\'" | tr -d ";" | tr -d "\(" | tr -d "\)" | sed -e "s/,/ /g"`
    for db in $DBINST
    do
    echo "rm ${HOST}%${db}"
    done
    echo "rm ${HOST}%_OB2_GLOBAL"
    fi
    done >> /tmp/remove_ora_integ.sh

    echo "Remove script /tmp/remove_ora_integ.sh was created"
    echo "Please, check before use!!!"

  • If this is implemented then any future integration would depend on generating configuration data from scratch (without any past basis). This would also prevent re-engaging with the same system without recreating the integration.

    Is this the desired result?