Importing data into new or existing Business Rules releases

When the DSU is used to import Business Rules configuration data into the FTM database, each import operation imports the data into a new Business Rules release by default. The releaseId property in the DSU properties file is used to specify which release the import operation uses.

The import operation allows data to be imported into either a new or an existing release.

Existing

To import data into or to update an existing Business Rules release, specify the release ID.

New

To create a new Business Rules release, comment out the releaseId property.

To ensure that all of the Business Rules configuration data is imported into the same Business Rules release, the releaseId property in the properties files that are used for the subsequent Business Rules configuration data import operations must be set to the ID of the new release.

The release ID of the newly generated Business Rules release is written to the log file. If the logToConsole runtime property is set to true, the ID is also displayed on the console.

The releaseID property can also be specified as an extra parameter when the data setup utility is run.

In addition, after a new release is created by using the DSU, users must be granted permissions to be able to view the release on the manage releases page. If the permissions associated with the release are not available to be assigned by using the groups page, restart the WebSphere® Application Server that has the Business Rules user interface.

Example using the reference implementation

The following steps provide an example of importing Business Rules configuration data into a single release that uses multiple import operations. The example uses the properties files that are used to import the data for the reference implementation.

Perform an import operation by using the BusinessRulesBaseXMLImport.properties file. A new release is created.
Find the ID of the release that was created. Search for the string DSU - Environment name is 'SAMPLE' and release ID is in the DSU log file that was created by the import operation. For example, after BusinessRulesBaseXMLImport.properties is imported, the entry in the DSU log file should look similar to DSU - Environment name is 'SAMPLE' and release ID is '1'.
Use the release ID for all subsequent import operations that need to import data into that same release. The release ID can be specified in the following ways:
1. Update the releaseId property in the property file associated with each of the import operations. For example, set the releaseID property to 1 in the BusinessRulesEdiImport.properties file.
2. Provide the releaseId property as a parameter when the DSU is run. For example, DSU import BusinessRulesEdiImport.properties "releaseId=1"

After the new SAMPLE release is created, use the groups page to add the following permissions for groups that need to work with the Business Rules releases. For the reference implementation, this group is the Business Rule Administrator group. Users in the group need to log off and log back on whenever the permissions for the group are changed.

Table 1. Permissions for the Business Rules SAMPLE release
Applications	Categories	Permission names to assign
BusinessRule	Dynamic Environments	SAMPLE
	Dynamic Tables	SAMPLE/* (Assign all of the table permissions for SAMPLE)
	BusinessRule > Environments > SAMPLE	View Environment SAMPLE
		Edit Environment SAMPLE
		Create Environment SAMPLE
		Delete Environment SAMPLE
	BusinessRule > Releases > SAMPLE	View Releases: SAMPLE
		Create Releases: SAMPLE
		Delete Releases: SAMPLE
		Lock Releases: SAMPLE
		Edit Releases: SAMPLE
		Copy Releases: SAMPLE
		Promote Releases: SAMPLE
		Activate Releases: SAMPLE
		Reactivate Releases: SAMPLE
		Import Releases: SAMPLE
		Export Releases: SAMPLE
		Close Releases: SAMPLE
		View Business Rules: SAMPLE
	BusinessRule > Distributors > SAMPLE	View BR XML Distributors: SAMPLE
		Edit BR XML Distributors: SAMPLE
		Create BR XML Distributors: SAMPLE
		Delete BR XML Distributors: SAMPLE