Integrate > Micro Focus UCMDB > Using the ServiceManagerAdapter9.41 Adapter > Tailoring the Integration > Integration Tailoring Options > How to Update the Integration Adapter Configuration File (sm.properties)

How to Update the Integration Adapter Configuration File (sm.properties)

The integration uses a properties file (sm.properties) 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 sm.properties file:

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

    Parameter

    Default value

    Comment

    timeout.minutes

    10

    The integration connection timeout value (in minutes).

    number.of.concurent.sending.threads

    6

    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.

    min.objects.for.concurent.sending

    50

    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.

    number.of.chunks.per.thread

    3

    The number of chunks per thread used for the push feature.

    number.of.cis.per.request

    1000

    The maximum number of objects retrieved from Service Manager by ID.

    Note 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.

    use.global.id

    true

    If set to true, globalId is used in the integration.

    If set to false, ucmdbId is used in the integration.

    For more information about the differences between UcmdbID and GlobalID, see the UCMDB documentation.

    type.of.expand.enum

    2

    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.

    use.type.label

    true

    It configures whether the generated source XML uses the real CI/Relationship type directly or uses the label that is defined in the query.

    If set to false, the real type is used directly instead of the label.

    op.pagination.switch

    on

    It indicates if pagination (client driven) is enabled.

    • on: Enabled.
    • off: Disabled.

    Note It is used for the population feature.

    pop.pagination.recordcount

    1000

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

    Note It is used for the population feature.

    pop.createci.key

    sm_id

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

    Note It is used for the population feature.

    ucmdbid.pushback.request

    UpdateucmdbID
    PushBackRequest

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

    Note It is used for the population feature.

    ucmdbid.pushback.xslt

    ucmdbid_pushback.xslt

    The xslt configuration file for pushing the UCMDB ID back to Service Manager.

    Note It is used for the population feature.

    check.sm.connections

    false

    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.