This documentation supports the 18.02 version of BMC Digital Workplace. To view the latest version, select the version from the Product version menu.

Archiving social data

Social data is stored in Mongo DB. You can archive or delete this data based on your organization's archiving policies or to manage the data size. For example, you can choose to archive all the data for closed incidents. You can perform the following tasks:

  • You can choose to store this archived data in a different location.
  • You can also choose to import the archived data whenever you need it. 
  • You can also choose to delete data.

Note

If you import the data twice you will not create duplicates.


To archive social data

  1. Update the config.js with archiving and data deletion related entries.

    By setting appropriate values of archiving and data deletion related flags, you can choose to archive and delete data, archive data without deleting, or delete data without archiving.  Following is an example snippet that shows how you can configure to data archiving without deleting it:

    archive_conf: {
            tenant_ids: [],//list of tenant ids data to archive if empty all tenant's data will be archive example: ["tentanid1", "tenantid2"]
            type:"CLOSED_ONLY",//ALL - everything or CLOSED_ONLY -> closed/resolved only tickets will be archived/deleted
            archive_flag: true,//set this to true/false if you want/don't want archive
            archive_freq : 180 ,// x days old will be archived
            delete_flag: false,//set this to true/false to delete/not to after archive
            delete_freq: 180,// y days old will be deleted
            archive_loc: "./data/archive", //all the archives will be placed here
            SECRET_KEY: "key",
            import_loc: "./data/import",
            to_db: false, //when set to true above config will be ignored and does a DB archive (delete from main Social DB and pushes to archive DB)
            db_name: "social_archive"
        },
  2. Go to <Installation directory>\SmartITMyIT\SmartITMyIT\Social

  3. Run the archive.js script. Run the following command:

    Run node scripts/archive.js

To import social data

  1. Update the config.js with archiving related entries. Following is an example snippet:

    archive_conf: {
            tenant_ids: [],//list of tenant ids data to archive if empty all tenant's data will be archive example: ["tentanid1", "tenantid2"]
            type:"CLOSED_ONLY",//ALL - everything or CLOSED_ONLY -> closed/resolved only tickets will be archived/deleted
            archive_flag: false,//set this to true/false if you want/don't want archive
            archive_freq : 180 ,// x days old will be archived
            delete_flag: false,//set this to true/false to delete/not to after archive
            delete_freq: 180,// y days old will be deleted
            archive_loc: "./data/archive", //all the archives will be placed here
            SECRET_KEY: "key",
            import_loc: "./data/import",
            to_db: false, //when set to true above config will be ignored and does a DB archive (delete from main Social DB and pushes to archive DB)
            db_name: "social_archive"
        },
  2. Go to <Installation directory>\SmartITMyIT\SmartITMyIT\Social

  3. Run the import.js script. Run the following command:

    Run node scripts/import.js
Was this page helpful? Yes No Submitting... Thank you

Comments