Population from Atrium Adapter
This section contains details about the adapter.
Input CIT
The input CIT for this adapter is discoveryprobegateway. The job uses an instance of the Discovery Probe Gateway which has access to connect to the remote BMC Atrium server.
Used Scripts
The adapter uses the following scripts:
| Script | Description |
|---|---|
| atrium_query.py | Used to query BMC Atrium for data. |
| atrium_map.py | Used to map the queried data into data UCMDB can use. |
| atrium_to_ucmdb.py | Used to push imported data into UCMDB. |
Discovered CITs
This integration can discover any CIT or relationship which is (a) mapped in the integration and (b) can be queried and converted to its UCMDB equivalent.
Parameters
| Parameter | Detail |
|---|---|
| ARS_Port | The port for connecting to the ARS server. If portmapper is being used, this should be left as 0. Otherwise, specify the TCP port. |
| ARS_Server | The hostname or IP address of the BMC ARS server. |
| BMC_NameSpace | The BMC NameSpace to use. (For example: BMC.CORE.) |
| ChunkSize | The chunk size in which data should be retrieved from the remote server. |
| DateParsePattern | Set the date pattern to parse Atrium date strings. |
| DebugMode |
Set to true to run the integration in the debug mode; this does not send data to UCMDB. Default: false |
| DryRunMode |
Set to true to run the integration in the dryrun mode; this does not query any data from Atrium. Default: false |
| MaxCIs |
The maximum number of CI synchronized from a remote server. Default: 100000 |
| credentialsId | The credentials ID to use for Atrium integration. |
| remoteJVMArgs | JVM parameters that should be passed to the remote process. |
| remoteJVMClasspath | The external JVM class path. |
| runInSeparateProcess |
Whether to run the adapter in an external JVM. Default: true. |