Home › Discussions › Questions & Answers › Enabling External Access to ECC Core Solr Application

Enabling External Access to ECC Core Solr Application

Avatar photoCustomer Questions & Answers 7 replies

Our security team needs to monitor the ECC Solr application status from a separate monitoring server (IP 192.0.1.1). However, when they try to access the core Solr URL directly, access is denied. How can I grant this specific external IP access?

7 replies

  • Support Enginatics

    To allow external hosts to access the core Solr application, you must configure the Weblogic Connection Filter rules . You need to log into the ECC Weblogic admin console . Navigate to Domain Structure -> `ecc_domain`, then choose Security -> Filter . Here, you must add an explicit allow rule for the monitoring server’s IP address .

  • What is the specific syntax for adding an allow rule for IP 192.0.1.1, covering HTTP and HTTPS traffic on the managed server port?

  • Support Enginatics

    The allow rule format specifies the host, target, port, and protocols . For IP 192.0.1.1 on the managed server port (default 7776), the rule should be entered as: `192.0.1.1 * 7776 allow t3 t3s http https` . After adding the rule, ensure you click ‘Save’ and ‘Activate Changes’ in the Weblogic console .

  • Once the rule is applied, how can the team verify access to the core Solr application?

  • Support Enginatics

    They can verify successful login to the core Solr application by navigating to the URL: `[ECC_HOST_PROTOCOL]://[ECC_HOST_NAME]:[ECC_PORT]/core_ecc` . For a non-SSL setup, this would look like `http://ecc.enginatics.com:7776/core_ecc` . Successful access indicates the connection filter is correctly permitting the traffic from the monitoring server’s IP .

  • If I am experiencing a connectivity error related to the connection filter (e.g., `weblogic.security.net.FilterException`), what temporary workaround is sometimes effective?

  • Support Enginatics

    In troubleshooting scenarios where the connection filter causes a failure (e.g., blocking the EBS host), a temporary workaround that has proven effective is removing the specific denial rule in the Weblogic Admin console . An example of such a problematic denial rule is: `* * 7776 deny` . Removing this rule allows traffic, but exercise caution as this reduces security; it should only be a temporary measure .

  • You must be logged in to reply to this post.