Initial Import Scripts

This feature requires an additional license. Contact your account manager or sales representative for licensing details.

The Initial Import Scripts populate the Audit Addon with event data that reflects the current state of the CMS. Use these scripts to import historical data into existing projects. After you add the Audit Addon to your project, it will record all future events automatically.

These scripts use only the data currently available in the CMS. They do not use the hippo:log, as its history may be incomplete or unreliable. The scripts do not reconstruct historical events. Instead, they persist events as if the current CMS state is the only recorded state.

Available Scripts

• Populate Initial Channel Events
• Populate Initial Content Events
• Populate Initial Project Events
• Populate Initial Security Events

Running the Import Scripts

These scripts do not support a "dry run" mode. All events are persisted to the data store, regardless of any dry run flag. To prevent events from being persisted, comment out all calls to persistEvent(Event event) in the script.

The scripts are pre-configured for use with the Updater editor. Each script includes a pre-defined XPath query for execution.

Use the following XPath queries with each script. For the Security Events script, run it twice: once for users and once for groups, using the appropriate XPath query.

• Channel Events XPath:

  //*/hst:configurations//element(*, hst:channel)
  

• Content Events XPath:

  //content/documents//element(*, hippo:handle)
  

• Project Events XPath:

  //hippowpm:hippowpm/hippowpm:projects//element(*, hippowpm:project)
  

• User Security Events XPath:

  //hippo:configuration/hippo:groups//element(*, hipposys:group)
  

• Group Security Events XPath:

  //hippo:configuration/hippo:users//element(*, hipposys:user)