Unless stated otherwise, find these settings in the \Data Management\IBM Content Manager Integration subfolder of the machine policy.
This setting is mandatory. Find it in the \Data Management\ subfolder of the machine policy. Set it to ‘IBM DB2 Content Manager’.
This setting controls where captured data files (Binary Large Objects) are stored. By default, the blob file is written to disk and saved in the \Data folder specified when the CMS was installed.
Note: You can use this setting to configure the concurrent use of multiple object stores.
This mandatory setting must be set to the name of the IBM Content Manager database, for example, icmnlsdb.
This mandatory setting must be set to the user name of the IBM Content Manager user permitted to read and write Resource Items.
This mandatory setting must be set to the password of the Content Manager user permitted to read and write Resource Items.
This setting controls additional Content Manager connection options and should not normally be necessary. Refer to your IBM DB2 Content Manager documentation for more information.
Defaults to rmdb. This sets the name of the resource manager used to store the CA DataMinder resource items. The default resource manager is automatically set up when Content Manager 8.3 is installed. Resources are stored as items of type S_wgnblob, which is set up by the CA DataMinder Content Manager Integration when it starts for the first time.
This is the TCP connection information used to locate the service provided by WgnIBMCM.exe (that is, the CA DataMinder IBM Content Manager Interface Service). The setting may be left at the default of 127.0.0.1 on port number 56200 if the WgnIBMCM.exe service is installed on the CMS. If the service needs to be installed on another machine, set that machine’s name or IP address here.
Note: The IBM DB2 Information Integrator for Content component must be installed on the machine which hosts WgnIBMCM.exe.
This setting along with the Content Manager Interface Service Host Address is the TCP connection information used to locate the CA DataMinder Content Manager Interface Service.
Defaults to 10. This setting controls the number of resource items that can be stored to the Content Manager simultaneously. Storing more items at the same time may result in a faster storage rate.
Defaults to 1. This setting defines how many CA DataMinder blob files are stored within one IBM Content Manager blob file.
The default value is set to 1 as a precautionary measure. It ensures that data belonging to an event cannot be deleted early if a custom purge script is used to purge events based on criteria other than event expiry date. If you implement such a purge script and need to set this value to more than 1, contact Technical Support for further information. If using the standard purge script, we recommend that this value is set to 100.
Note: CA DataMinder blobs with different retention periods will not be stored in the same IBM Content Manager blob file.
Defaults to 1,048,576 KB (1 GB). This setting limits the number of CA DataMinder blob files stored in an IBM Content Manager blob by ensuring that the total number of bytes stored in the blob does not exceed the value set here.
Defaults to 60. This specifies how long CA DataMinder waits before storing a resource item if there are insufficient blob files to fill it. Resource item capacity is defined by the Maximum Number of BLOBs per Resource Item and Maximum Number of KB per Resource Item settings. If there are not enough blobs to fill the resource item according to these settings, CA DataMinder waits for the flush interval to elapse then stores the resource item anyway.
|
Copyright © 2014 CA.
All rights reserved.
|
|