Integrate > Micro Focus UCMDB > Using the ServiceManagerEnhancedAdapter9.41 Adapter > Tailoring the Integration > Integration Tailoring Options > How to Update the Integration Adapter Configuration File (

How to Update the Integration Adapter Configuration File (

The integration uses a properties file ( as a configuration file of the adapter. Out-of-the-box, this file has been set up based on best practices, so usually you can keep the default parameter values. Optionally, you can update the parameter values to better suit your needs.

To update the file:

  1. Log in to UCMDB as an administrator.
  2. Navigate to Data Flow Management > Adapter Management > ServiceManagerEnhancedAdapter9.41 > Configuration Files.
  3. Click the properties configuration file:
  4. Update the parameter values as needed. For a list of the parameters, see the following table.

  5. Parameters in the file


    Default value




    The integration connection timeout value (in minutes)



    The number of concurrent threads used for the data push feature

    • 1: Disabled
    • 2 or higher: Enabled

    Note If you are connecting to multiple Service Manager instances to improve the CI data push performance (see the URL Override configuration in How to Create an Integration Point in UCMDB), you are recommended to increase this value for optimized performance. For example, set it to 12 if you are connecting to two Service Manager instances.



    The minimum number of Service Manager objects that is required to use concurrent sending instead of single thread sending

    Note It is used for the push feature.



    The number of chunks per thread used for the push feature

    Total of number of chunks = number.of.chunks.per.thread * number.of.concurrent.sending.threads

    recommended.min.cis.per.chunk 50

    The minimum allowed number of CIs per CI data chunk. This value is used to mitigate the risk of making your data chunks too small.

    For example, suppose your system uses the following settings:

    • number.of.chunks.per.thread=3
    • number.of.concurrent.sending.threads=3
    • recommended.min.cis.per.chunk=50

    When pushing 1000 CIs, the number of CIs in each chunk is calculated as 1000/3/3. The calculated value is greater than the recommended.min.cis.per.chunk value, so the calculated value is used. However, when pushing 270 CIs, the calculated value is less than the recommended.min.cis.per.chunk value, so the calculated value is used.

    max.running.hours.for.multi.threaded 20 The maximum number of hours before a push request times out in a multi-threaded environment.



    The maximum number of objects retrieved from Service Manager by ID

    Caution It is used for the population and federation features. Do not set it to a number greater than 1000 in case the request has a 64K limit.

    federation.request.pagination.switch on  
    federation.request.max.size 2000 size of query conditions for federation


    500 size of isin{} size true This parameter is obsolete for the generic adapter starting with SM9.41.



    It configures the value mapping rule for the UCMDB enum type

    • 0: The feature will be disabled
    • 1: The enum type will expand to “{value}”
    • 2: The enum type will expand to “{index}-{value}”

    Note It is used for the push feature.



    It indicates if pagination (client driven) is enabled

    • on: Enabled.
    • off: Disabled.

    Note It is used for the population feature.



    The maximum number of records displayed on each page when pagination is enabled.

    Note It is used for the population feature.



    The UCMDB field of a CI record that stores the Service Manager CI ID.

    Note It is used for UCMDB ID Push Back by the population feature.



    The web service request for pushing the UCMDB ID back to Service Manager.

    Note It is used for the population feature.


    It indicates whehter to check the SOAP connections to Service Manager instances before running a job.

    You can enable it under any of the following circumstances:

    • Your Service Manager is running in High Availability mode (with load balancing), and you want to connect UCMDB to multiple Service Manager instances.
    • You want UCMDB to not run a job when no integration connections are available, rather than run the job and then report a failure.