Exporting Decision Center data

Use this tool to export the contents of the Decision Center database. The files can be used in migration and diagnostics.

Before you begin

Follow these steps to set up the database dumping tool:

  1. Download this file: decisioncenter-dbdump.war_.zip External link opens a new window or tab.
  2. Decompress decisioncenter-dbdump.war_.zip and extract decisioncenter-dbdump.war.
  3. Deploy decisioncenter-dbdump.war.

    For example, on Liberty, copy the WAR file to the apps directory: <InstallDir>\wlp\usr\servers\<ODMVersion>\apps

  4. Map the rtsAdministrator role to users and groups.

    For example, on Liberty, add the following in the server.xml: 

    <!-- DB dump -->
	<application type="war" id="decisioncenter-dbdump" name="decisioncenter-dbdump"
		location="${server.config.dir}/apps/decisioncenter-dbdump.war">
		<classloader delegation="parentLast" />
		<application-bnd>
		<security-role name="rtsAdministrator">
		<group name="AdminGroup" />
		</security-role>
		</application-bnd>
	</application>
Note: The web application uses basic authentication, so be sure to map the rtsAdministrator role during deployment. If necessary, you can disable security by commenting out the bottom section of the WEB-INF/web.xml file, for example, <security-constraint> ....</security-role>.

About this task

This web application creates a compressed (.zip) file that contains the contents of a Decision Center repository. Optionally, the application can exclude the rule definitions to address privacy concerns while still reproducing most repository issues. The application must be deployed on the server that contains Decision Center data source. It can typically be deployed alongside Decision Center.

Note: This application does not communicate with or depend on Decision Center. It uses the data source directly, and can therefore be used to export the database from any version of Decision Center.

Procedure

Use one of the following options to use the database dumping tool:
Web page
  1. Browse to http://<hostname or IP>:<port>/decisioncenter-dbdump.
  2. Provide the JNDI name for the data source. The suggested default value is jdbc/ilogDataSource.
  3. Optionally, click the Lookup button to get information about the data source.
  4. Provide the schema name for the Decision Center schema.

    The option Use data source default means that the same schema name as computed by the Decision Center application that is used to retrieve the tables.

  5. Select the check box Exclude definitions if you want to exclude rule definitions.
  6. Generate the compressed (.zip) file by using one of the following options:
    1. Click Direct download and a compressed file download starts shortly. No file is saved on the server.
    2. Click Save on server and the export is generated on the server. When the export is complete, a link is shown.
Direct URL

A URL can be used to initiate the download. It should match the following form:

http://<hostname or IP>:<port>/decisioncenter-dbdump
External link opens a new window or tab/services/download?<parameters...>

The parameters:

  • ds: The JNDI name of the data source, for example, ds=jdbc/ilogDataSource
  • schemaName: The name of the schema, for example, schemaName=ODMDB
  • excludeDefinitions: Request to exclude definitions by using excludeDefinitions=true
  • useDefaultSchemaName: Request to use the default schema name by using useDefaultSchemaName=true
In this example, the curl on Windows assumes the host is a local host and the HTTP port is 9080:
curl -u rtsAdmin:rtsAdmin -o dbdumpWithCurl.zip http://localhost:9080/decisioncenter-dbdump
External link opens a new window or tab
      /services/download?useDefaultSchemaName=true&ds=jdbc/ilogDataSource
If you have a problem with this tool and an exception is thrown, it should be shown in the same web page that was used to initiate the export. You might have to refresh your browser.
http://<host>:<port> /decisioncenter-dbdump
External link opens a new window or tab
If the export does not complete and no error message is shown in the user interface, check the application server log. Whenever possible, if an exception occurred during the export, a file error.txt is saved in the generated compressed archive. It can be useful when initiating the export from the command line. With the direct URL, if an error occurred but a compressed file can still be retrieved, checking for error.txt can help troubleshoot the issue.
If another diagnostic trace is needed, the JDK logging of the JVM application server should be configured with the finer level trace for the package:
:ilog.rules.teamserver.dbdump.*