Running initial registration

To complete initial registration of TADDM configuration items (CIs) in the Context Menu Service and Data Integration Service database, you must manually run the run_cms_dis_registration script. The CMSDISAgent topology builder agent does not automatically update CI registration until after this initial registration is complete.

If you are using a streaming server deployment, run the registration script on the primary storage server. If you are using a synchronization server deployment, run the registration script on the synchronization server.

To complete initial registration of TADDM CIs:

At a command prompt, navigate to the $COLLATION_HOME/bin directory.
Run the run_cms_dis_registration script for your operating system:
- Linux® and UNIX systems:
```
./run_cms_dis_registration.sh [ register [guid] | 
                                clean [guid [classtype]] |
                                re-register-all | register-menu |
                                help ]
```
- Windows systems:
```
run_cms_dis_registration.bat [ register [guid] | 
                                clean [guid [classtype]] |
                                re-register-all | register-menu |
                                help ]
```
Where:

register [guid]

Registers TADDM data in the Context Menu Service and Data Integration Service database. You can optionally specify the globally unique identifier (GUID) of a model object you want to register.

The first time you run the script with the register option and no GUID specified, all TADDM data is registered in the database, and all launch points are registered with the Context Menu Service. Subsequent runs with this option register only changes to TADDM data that have occurred since the previous run. This option is the default option.

If you specify a GUID, only the model object with the specified GUID is registered.

Note: Initial registration of all TADDM data can take a long time.

clean [guid [classtype]]

Unregisters TADDM data currently in the database.

If you do not specify a GUID, all TADDM data is unregistered. If you specify a GUID, only the model object with the specified GUID is unregistered. If the model object with the specified GUID is no longer available in TADDM, you must also specify the model object type.

re-register-all

Unregisters all TADDM data and launch points and then repeats the initial registration. This option is equivalent to running the script with the clean option and then with the register option.

register-menu

Updates the menu definitions only that are registered in the Context Menu Service database. Use this option when the TADDM data is registered but you want to update the menu definitions only.

help

Shows help information for the script.

This example registers all TADDM data with the Context Menu Service and Data Integration Service when run for the first time; on subsequent runs, it registers all changes since the last run:
```
./run_cms_dis_registration.sh
```

This example registers only the model object with the specified GUID.

./run_cms_dis_registration.sh register 3950DF835FA0337A829D864415CC1384

This example removes all registered TADDM data:
```
./run_cms_dis_registration.sh clean
```

This example removes the object with the specified GUID and model object type:

./run_cms_dis_registration.sh clean 3950DF835FA0337A829D864415CC1384
  LinuxUnitaryComputerSystem

This example removes all registered TADDM data and then repeats the registration:
```
./run_cms_dis_registration.sh re-register-all
```

If you want to run the registration script again at a later time, first disable the CMSDISAgent topology builder agent to stop incremental updates. To disable the agent, edit the $COLLATION_HOME/etc/collation.properties file and set the following property:

com.ibm.cdb.DisCmsIntegration.enabled=false

After the script finishes, you must then re-enable the agent by setting the property to true.