| CA Technologies |
2.0 Enable Backward Compatibility with CA Catalyst r3.2 Connectors
2.1 CA Catalyst Installation Considerations
2.2 Event Management Considerations
2.3 Install the IFW Proxy
2.4 Verify Connector Data in CA SOI
2.5 Connector Data Considerations
2.6 IFW Proxy Using CA Catalyst Connector Controls
3.0 Interacting with CA Catalyst r3.2 Connectors
3.1 Connector Configuration
3.2 Configure Connector Administration Settings
3.3 Change Encrypted Connector Property Values from CA SOI Administration Tab
3.4 Change the CA SOI Password on a CA Catalyst Connector System
3.5 Remove the Connector and Connector Data from CA SOI
4.0 Install the CA Catalyst Container
This file contains information about the IFW Proxy component, which provides backward compatibility with CA Catalyst r3.2 connectors.
CA Service Operations Insight (CA SOI) r3.2 provides native support for connectors developed for its embedded version of the CA Catalyst platform (r2.5). These connectors are accessible from the CA Service Operations Insight product page on CA Support Online using the CA Spectrum Service Assurance/Service Operations Insight - Connectors, Solutions, & Patches link under Recommended Reading.
Other connectors are available for the CA Catalyst r3.0 platform (and subsequent releases). CA Catalyst controls the administration and management of these connectors independent of CA SOI, and current releases of CA SOI do not embed or support this CA Catalyst version. CA SOI administrators require the IFW Proxy backward compatibility module to use these connectors with CA SOI. The IFW Proxy runs in a CA Catalyst node, collects the connector data, and transmits it to the CA SOI IFW for visualization and management in CA SOI. These connectors are accessible from their specific individual connector packages.
The following versions of CA SOI support viewing CA Catalyst r3.2 connector data using the IFW Proxy:
Note: For information about support for the latest version of the CA Catalyst r3.0 platform in future CA SOI releases, see the documentation for that release.
Do the following to enable backward compatibility with CA Catalyst r3.2 connectors:
Note: The phrase "CA Catalyst r3.2 connectors" denotes connectors developed specifically for all releases of the CA Catalyst r3.0 platform, starting with r3.1.
Consider the following before installing the IFW Proxy when installing the prerequisite CA Catalyst components:
CA SOI r3.0 introduced a new Event Management component. CA Catalyst r3.2 does not contain this Event Management functionality by default. The CA Catalyst Container provided with the IFW Proxy enables event collection and exposure in CA Catalyst r3.2 connectors for CA SOI Event Management searches and policies.
The IFW Proxy enables CA SOI to visualize and manage data provided by CA Catalyst r3.2 connectors. Install the IFW Proxy on each CA Catalyst Container system that hosts connectors that you want to manage in CA SOI. A CA Catalyst Container is required on the system on which you install the IFW Proxy. If you have multiple CA Catalyst Containers hosting connectors on a single system, install a separate IFW Proxy to communicate with each Container.
We recommend that all connectors are installed on the CA Catalyst Container system before you install the IFW Proxy. However, you can install a connector on a Container system after installing the IFW Proxy.
Follow these steps:
Note: If multiple CA Catalyst Containers are available on the system, the IFW Proxy installer prompts you to select the appropriate Container.
The IFW Proxy installer opens to the Introduction page.
Note: Refer to your Installation Worksheet in the SA Manager section for these values.
Defines the administrator user name created during CA SOI installation.
Default: samuser
Defines the password for the administrator user.
Defines the host name where the SA Manager is installed.
Defines the ActiveMQ Server port through which connector communication occurs.
Default: 61616
Defines a valid port for the UCF Broker to send information created or updated in CA SOI to the CA Catalyst r3.2 connector.
Default: 8020
The IFW Proxy does not use this value.
Defines the name displayed for all connectors from this source. If you are implementing a high availability solution, change this value to the virtual host name.
The IFW Proxy installs, and the Install Complete page opens. If errors display, check the CA_IFWProxy_InstallLog.log file installed to CATALYST_HOME\containerName\logs for details.
Note: CATALYST_HOME denotes the root CA Catalyst installation directory, which is C:\Program Files\CA\Catalyst by default.
(Optional) Repeat Steps 1-4 for all local or remote CA Catalyst Containers that host connectors that you want to manage in CA SOI.
After IFW Proxy installation, the CA Catalyst connector data appears in the CA SOI instance that you provided during the IFW Proxy installation.
Follow these steps:
The details of the integrated CA Catalyst connector appear on the right pane. The Connector Description clarifies that the connector is a "Connector_Name running in Catalyst node Node_Name." If the Connector Status displays as Online, the integration was successful.
This page also contains connector configuration information.
Data from CA Catalyst r3.2 connectors differs from traditional CA SOI connectors as follows:
CA Catalyst adds various connector controls (that correspond to the connector controls in the IFW) to the connector configurations. The IFW Proxy uses these new CA Catalyst parameters to set the connector controls and determine how to use the connector. These CA Catalyst connector controls are available in the connector configuration files. For example, the dns_resolution property is available under the InterceptorChainConfig, Interceptor, Config section of the connector configuration file.
The new CA Catalyst connector controls that the IFW Proxy uses are mentioned in the following table. The table also includes the corresponding IFW connector controls:
| New CA Catalyst Connector Controls | Old IFW Connector Controls |
|---|---|
| DisableGetRelationshipsAtStartup | getRelationshipsAtStartup |
| DisableGetItemsAtStartup | getCIsAtStartUp |
| DisableDelta | performDeltaProcessing |
| dns_resolution | dns_resolution |
Specifies whether to rediscover relationships every time the connector starts.
Specifies whether to rediscover CIs every time the connector starts.
Specifies whether to process and publish deltas on CIs between the time the connector or SA Manager was last stopped or restarted.
Specifies whether to use DNS resolution to resolve device names.
The IFW Proxy includes default values for all the IFW connector controls in its configuration file (CATALYST_HOME\registry\topology\physical\nodename\ifw\ifw.properties). If a CA Catalyst connector configuration contains one of those CA Catalyst connector controls, the IFW Proxy uses it when interacting with that connector. Otherwise, the IFW Proxy uses its default value. If the connector configuration is changed using the CA SOI Administration UI, all the connector controls for that connector are saved into the CA Catalyst connector configuration.
Changes are saved as follows:
For the other IFW connector controls that do not have CA Catalyst equivalents (the ones not in the table), the IFW Proxy uses the IFW defaults, until the connector configuration is changed from the Administration UI. In that case, they are written to the CA Catalyst connector configuration.
This section lists methods of interaction with CA Catalyst r3.2 connectors that are different than those for traditional connectors.
You can perform the following CA Catalyst r3.2 connector configuration from the CA SOI Administration UI:
Note: For descriptions of each control, see the CA SOI Connector Guide.
By default, you can start or stop a CA Catalyst r3.2 connector from the CA SOI Administration UI using the Start and Stop buttons. You can configure whether these buttons actually start or stop the connector or simply stop the flow of connector data into CA SOI.
Follow these steps:
Note: If your CA Catalyst deployment includes a CA Catalyst Server, log in to the Registry Administration UI to access and modify this file.
Lets you actually start and stop the connectors in the CA SOI Administration UI. The Start and Stop buttons in the Administration UI start or stop the connector in CA Catalyst.
Lets you start or stop the data flow from connectors in the CA SOI Administration UI. The Start and Stop buttons do not actually control the connector status in CA Catalyst, only whether connector data makes it into CA SOI. If you set this value, you can start and stop connectors only from the CA Catalyst Registry files.
The CA SOI Administration tab supports modifying CA Catalyst connector properties. However, if you change the value of an encrypted property, use CA Catalyst encryption so that CA Catalyst can process the new encrypted value.
Follow these steps:
encrypter password
Defines the new value of the encrypted property.
An encrypted string appears.
The encrypted value change takes effect.
If you change the CA SOI administrator password using the instructions in the CA SOI Implementation Guide, also change the password in the IFW Proxy on the CA Catalyst Container. Keep this password synchronized in CA SOI and the IFW Proxy to avoid connection issues.
Follow these steps:
EncryptSAMCreds newpassword
Defines the new password for the administrator user.
The command generates an encrypted password.
Note: If your CA Catalyst deployment includes a CA Catalyst Server, log in to the Registry Administration UI to access and modify this file.
The password change takes effect.
Removing CA Catalyst r3.2 connectors and their data from CA SOI does not require uninstalling the connector. Uninstalling the IFW Proxy deletes the connection between CA SOI and CA Catalyst, and you can remove existing connector data from CA SOI.
Follow these steps:
Uninstalling the IFW Proxy removes the connection between CA SOI and the CA Catalyst connector.
The connector data is deleted from the SA Store database, and the entry disappears from the tree when the operation is complete.
If you need to maintain a connection between CA SOI and other connectors on the same system, retain the IFW Proxy. Clicking Remove Connector on the CA SOI Administration UI still removes the CA Catalyst r3.2 connector data and updates the connector configuration to prevent subsequent use of the connector in CA SOI.
To enable a disabled connector, set the SOIState property to Enabled or remove the property altogether in the connectorname.conf file located at CATALYST_HOME\containerName\registry\topology\physical\nodename\modules\configuration.
Note: If your CA Catalyst deployment includes a CA Catalyst Server, log in to the Registry Administration UI to access and modify this file.
Install a CA Catalyst Container (r3.2 Build 535 or higher) on the systems where you plan to install CA Catalyst r3.2 connectors. You can install multiple CA Catalyst r3.2 connectors on the same system into the same CA Catalyst Container.
For an IFW Proxy implementation, we recommend a Container-only CA Catalyst deployment. This procedure reflects the recommended selections to make in a Container-only environment. The CA Catalyst Server is not required.
Follow these steps:
The CA Catalyst Container installation wizard opens.
Note: For all installation pages not mentioned in this procedure, leave the default selections unless the default port numbers are in use. For the simplest deployment experience, complete the Installation Worksheet for the CA Catalyst Container for CA SOI with the values that you enter during installation.
Leave the default selection of Default Connector Container (CatalystConnector) unless you are installing multiple Containers on the same system.
Retain the default installation location.
(Optional) Select Configure for High Availability and enter the necessary information if you are deploying the CA Catalyst Container in a cluster environment.
Enter information about the Embedded Entitlements Manager server to use for CA Catalyst security. This can be the same Embedded Entitlements Manager server that you use for CA SOI. Use the default application name for CA Catalyst; all other values can be the same.
Enter CA Catalyst administrator credentials.
Select File Registry for a Container-only implementation.
Accept the default values unless the ports are already in use.
Retain the default port. If this is the second Container on the same system, the defaults automatically change to avoid conflicts. If this is anything past the second Container on the same system, you must manually change to unused ports.
Default: 8080, or 8180 on a multiple Container system
Retain the default port. If this is the second Container on the same system, the defaults automatically change to avoid conflicts. If this is anything past the second Container on the same system, you must manually change to unused ports.
Default: 7000, or 7100 on a multiple Container system
Retain the default port. If this is the second Container on the same system, the defaults automatically change to avoid conflicts. If this is anything past the second Container on the same system, you must manually change to unused ports.
Default: 7443, or 7543 on a multiple Container system
Verify that the check box is selected to start the services.
If you are installing on a 64-bit system, select Use 64 Bit JRE to install as a 64-bit application.
The CA Catalyst Container installs. The Install Complete page displays the results of the installation. To troubleshoot installation errors, see the CATALYST_HOME\containerName\logs\CA_Container_InstallLog.log file, or see the CA Catalyst Installation Guide.
Repeat this process on all systems where CA Catalyst Container installation is required for hosting CA Catalyst r3.2 connectors.
Contact CA Support
For your convenience, CA Technologies provides one site where you can access the information that you need for your Home Office, Small Business, and Enterprise CA Technologies products. At http://ca.com/support, you can access the following resources:
Providing Feedback About Product Documentation
If you have comments or questions about CA Technologies product documentation, you can send a message to techpubs@ca.com.
To provide feedback about CA Technologies product documentation, complete our short customer survey which is available on the CA Support website at http://ca.com/docs.
Copyright © 2013 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.