As an administrator, you can change the configuration settings, navigate to the Connector Configuration page on the Administration tab in the CA SOI Dashboard. Connectors are initially configured when you install them.
Follow these steps:
The Connector Configuration page opens and displays the Connector Status table.
The connector details page opens and displays a number of tables with additional details about the connector and the server where it is installed. Many connectors also have a read-only Connector Type Data table that displays information such as the supported CI types.
Note: If your connector supports Scheduler Configuration and has the scheduler property enabled, then the button is available. For more information about Scheduler Configuration availability, see the connector documentation provided with your connector.
Important! The CA:00056_service-discovery@servername entry on the SA Manager server represents the Service Discovery component. This entry always has blank Connection Details. Do not edit any of the connector controls for this entry.
Specifies whether to use DNS resolution to resolve device names. If a reliable DNS mechanism is not in place (for example, no DNS server on the network, or configuration items (CIs) not defined to the DNS), disable DNS lookups to prevent CI resolution and normalization failure.
Default: on
Specifies whether to filter alerts based on their existence in a managed service in CA SOI. If the control is turned on, the connector only sends domain manager alerts that are associated with a CI that is part of an existing managed service in CA SOI. If the control is turned off, the connector forwards all alerts from the domain manager, regardless of whether they relate to a service.
Default: on
Note: For CA SOI r3.1 and later, the IFW no longer requires or uses EVENT_FILTER requests. The IFW now sends the alerts (managed or unmanaged) that the connectors report to the SA Manager. CA SOI ignores the global setting sendAllAlerts (in the IFW configuration file) and the connector-specific setting useAlertFilter (on the Administration tab Connector Configuration page). CA SOI now behaves as if sendAllAlerts=1 and useAlertFilter=0, regardless of the actual settings.
Specifies whether to rediscover CIs every time the connector starts. This control is enabled by default so that connectors always provide a current record of all CIs from their domain managers. You can turn this control off if the connector does not support collecting CIs at startup, such as the Universal or SNMP connector.
Default: on
Specifies whether to allow the connector framework to access the connector remotely for create, update, and delete operations on the source domain manager.
Default: on
Specifies whether to send all relationships to CA SOI or only the ones associated with modeled services. Set the control to true to run relationships through a service filter and receive only the relationships associated with modeled services.
Default: on
Specifies whether to rediscover relationships every time the connector starts. This control is turned off by default so that relationships are only obtained and imported as a part of service model imports. You should only enable this control if you require relationship CIs outside of imported service models, for example, if you define an Unmanaged Relationship Service Discovery rule.
Default: off
Specifies whether to process and publish deltas on CIs between the time the connector or SA Manager was last stopped or restarted. When enabled, this setting also performs delta processing on relationships if the getRelationshipsAtStartup property is enabled.
Default: on
The changes are saved. Verify that any changes you make the connection settings do not break the connection. For example, if you modify a Host field in the Connection Details, first confirm that the domain manager is installed and configured on the new host.
Note: For information about the connector parameters for each connector, see the CA Catalyst Connector Guide provided with the specific connector package.
The connector is restarted. Depending on the type of connector, it can take a few minutes before the connector Status displays Online.
Important! Do not perform rapid start and stop operations on the connector. Each stop and start sends the corresponding command to the connector. Rapid start and stop operations from the interface can cause these commands to queue on the connector and cause the connector to start and stop repeatedly until all commands in the queue are processed.
|
Copyright © 2013 CA.
All rights reserved.
|
|