ADDI Batch Server

Note:

Before you start to back up on Windows, make sure that the IBMApplicationDiscoveryBatchService, IBMApplicationDiscoveryGraphDBService, and IBMApplicationDiscoveryWebService services are stopped.
Before you start to back up on Linux®, make sure that the server.sh (corresponding to GraphDB), startServer.sh (corresponding to ADDI Batch Server), and startWBServer.sh (corresponding to ADDI Web Services) files are not running.

Generally, the data and conf folders that are distributed by the ADDI Batch Server installation must be included in the backing up procedure. See the following detailed description for the folders.

## path to the directory where configuration files are placed
## default: ${install.dir}/conf
conf.dir=<path>\conf

## path to the directory where data files are placed
## default: ${install.dir}/data
data.dir=<path>\data

## path to the directory where temporary data is placed
## default: ${data.dir}/tmp
tmp.dir=<path>\tmp

If the default paths for the data, conf, and tmp folders are changed in the server.properties configuration file, back up accordingly.

Procedure

Back up configurations.
1. Back up the <Batch Server Installation Path>\Conf configuration folder.
2. Back up the following configuration folders from the tmp folder:
  - <Batch Server Installation Path>\data\tmp\mfp
  - <Batch Server Installation Path>\data\tmp\ver
Back up OrientDB databases (graph databases).
Back up the default folder <Batch Server Installation Path>\data\tmp\gdb. The size of this folder might be large, depending on the number and size of IBM ADDI Build Client projects.

Back up the index folders as defined in the project.properties configuration file. The indexes that are generated by IBM® ADDI Batch Server and used for Search In Files analysis in IBM ADDI Analyze Client are stored in these folders. If indexes for specific projects are defined, back up the corresponding index folders as well.

## index global settings
## output folder where indexes are stored. (project name will be added by default)
## this setting does not override database entry!
## Note that index folder should be a shared folder in order for all Analyze client to be able to use it
index.indexFolder=\\9.20.128.211\\IBM AD\\Batch Server\\Indexes

### index project settings
## output folder where index for this project is stored. must be unique per project
## this setting does not override database entry!
project.
project.<projectName>.index.indexFolder==\\9.20.128.211\\IBM AD\\Batch Server\\Indexes\\<projectName>

Back up the <Batch Server Installation Path>\data\tmp\wsmetrics folder. The Web Services data is stored in this folder.
If the Rule Based component is used, back up Rule Based reports and queries.
1. Back up Rule Based reports.
  By default, the rule-based data is generated and stored in the data folder, which is already included in the backing up procedure. For more information about the data folder, see the preceding Note.
  If the default folders that are related to the Rule Based component are changed in the project.properties file, back up the folders as configured. If folders for specific projects are defined, back up the corresponding folders as well.
```
## output folder for rule based reports generated by source based rules. Default, data folder
ruleBased.reportsFolder=

## output folder for csv files generated by data based rules. Default, data folder
#ruleBased.csvFolder=

## output folder for controlTotals files generated by source based rules. Default, data folder
## used only if generateTotals is true
#ruleBased.totalsFolder=

## output folder for rule based reports generated by source based rules. Default, data folder
#project.<projectName>.ruleBased.reportsFolder=

## output folder for csv files generated by data based rules. Default, data folder
#project.<projectName>.ruleBased.csvFolder=

## output folder for controlTotals files generated by source based rules. Default, data folder
## used only if generateTotals is true
#project.<projectName>.ruleBased.totalsFolder=
```
2. Back up Rule Based queries.
  If you use Rule Based global settings, check the paths where input and queries are stored in the ruleBasedConfig.properties file.
  
  If you use Rule Based project settings, check the paths where input and queries are stored in the rule properties file of each project. Also, if the rule properties files are not stored in the conf folder, back up the folders where they are stored.
Back up the annotation database.
In earlier versions of IBM ADDI, IBM ADDI Batch Server creates a database that is called EZ#Annotations in Microsoft SQL Server. This database is created on the SQL Server as defined in the server.properties configuration file.
Figure 1. EZ#Annotations database

Starting with IBM AD V5.1.0, IBM ADDI Batch Server reads the configurations that are made in IBM AD Configuration Sever, under Annotations Database and create the annotations database in the relational database server that is specified there, by using the database name and the schema set by the user.

You can still add EZ#Annotations in database name field, together with dbo schema and associate the relational database server in which the annotation database was created, the one defined in the server.properties configuration file.

Using the configurations set in Annotations Database configurations area you can find out the name of your annotations database, the schema and the associated relational database server in order to know what database to back up.