Adding ConApp Containers

Summary:

This document provides a guide for managing and adding additional containers within a ConApp environment through a SmartBuy requisition process. Jim Hebert seeks information on how to add more connectors or containers in their ConApp setup but learns that only pre-defined containers are available, with no support for local container additions. The author explains the correct method of automatically adding containers when importing software connectors and managing them remotely via a ConApp appliance. It emphasizes maintaining consecutive port numbers across all connectors by setting `remote.management.enabled=true` and `remote.management.listener.port=9001` in the `agent.properties` file, along with utilizing the "scan host" feature for efficient management of multiple connectors under a single host without exceeding the limit per scan host.

Details:

Emrah Alpa introduces a new blog post titled "Adding ConApp containers" by Jim Hebert, discussing how to manage and add additional containers in a ConApp environment. The author explores the process of creating a SmartBuy requisition for TippingPoint TP10 desktop units and shares knowledge on various topics such as ConnAppBootcampQuiz.docx by Darla Sadler, Strange ESX/VM Installation Error (GUI) by Randal Rioux, and Check Point SmartConnector – Unsure of opsec_sic_name opsec_sslca_file by Jan Stodola. The post also includes a discussion thread with Jim Hebert asking about adding containers to an existing ConApp, with Madhura Chopda providing information on the "scan host" feature for SW type hosts. The text discusses interactions related to container management within a ConApp appliance. Jim Hebert initially queries about adding an additional container for more connectors but learns that this functionality is not supported; only pre-defined containers are available. Chuck Grochowski clarifies that local containers cannot be added, while Dave Sheyman confirms the correct process of automatically adding containers when importing software connectors, even remotely managing them through a ConApp appliance. The summary provided outlines the process for adding connectors to a remote management system in a specific scenario, where connectors are installed on a host and managed remotely using SW connector running along with JVMs within containers. It emphasizes the importance of maintaining consecutive port numbers across all connectors when adding the two lines `remote.management.enabled=true` and `remote.management.listener.port=9001` to the `agent.properties` file, as well as the correct usage of the "scan host" feature to manage multiple connectors under a single host without exceeding the limit per scan host. The process involves installing connectors on the remote host first and then adding them using 'scan host' in the management tool. It is important not to skip any port numbers while assigning consecutive ports to each connector, as this ensures proper functionality of the remote management setup.

Disclaimer:

The content in this post is for informational and educational purposes only. It may reference technologies, configurations, or products that are outdated or no longer supported. If there are any comments or feedback, kindly leave a message and will be responded.