ECC Integration Fails: Connection Filter Hostname Resolution Error

Customer February 12, 2023 at 8:43 am

During step 5, ‘Integrate ECC with EBS’, the process fails when applying the Connection Filter with a `WLSTException` and the underlying error mentions `[Management:141190] The commit phase of the configuration update failed with an exception. Connection Filters cannot be applied.. Done.` What is causing this failure?

Viewing 6 reply threads

Author
Replies
- Support February 12, 2023 at 12:33 pm
  This specific failure during the commit phase of applying the Connection Filter rules suggests a configuration error in the rules themselves, often related to hostname resolution. You must check the `AdminServer.log` file in the Weblogic domain directory for more detail, as the error often manifests there as a `java.text.ParseException` with a message like ‘demo: Name or service not known’. This means that while the fully qualified domain name (FQDN) might resolve via DNS, the ECC installer is trying to resolve the hostname *separately* and failing, preventing the filter from being applied.
- Customer February 14, 2023 at 1:15 am
  The hostname is resolvable via DNS. If the installer is failing on the short hostname (‘demo’), how can I fix this before rerunning the integration step?
- Support February 14, 2023 at 11:36 pm
  To correct the resolution issue for the short hostname, you need to manually edit the `/etc/hosts` file on the ECC server. You should add an entry mapping the IP address of your EBS server to both the FQDN (e.g., `demo.enginatics.com`) and the short hostname (e.g., `demo`). Once this static entry is in place, the installer should be able to apply the Connection Filter successfully during integration.
- Customer February 15, 2023 at 4:24 am
  After successfully integrating, AutoConfig was run on the EBS side. Where should I verify that the necessary rewrite rules for ECC integration were added to OHS?
- Support February 16, 2023 at 5:20 am
  After running AutoConfig (`adautocfg.sh`) on the EBS application tier, you need to check the OHS configuration files, specifically looking for `ecc.conf`. The contents of this file should include a `RewriteEngine on` directive and a `RewriteRule` directing the `/ecc` path to the ECC managed server URL, usually including parameters like `?system=EBS`. If you struggle to locate `ecc.conf`, you can try navigating to `$FMW_HOME/webtier/instances` on the EBS node and running `find . -name ecc.conf`.
- Customer February 18, 2023 at 5:02 am
  What is the final action performed during the successful ‘Integrate ECC with EBS’ step (Option 5)?
- Support February 18, 2023 at 4:16 pm
  The final integration step performs several critical actions. First, it updates the `ECC_SOURCE_SYSTEM` table in the database, setting the `SECURITY_MANAGER` field to `oracle.ecc.security.extensions.EbsEccSecurityManager`. Then, it restarts the ECC managed server and applies the Connection Filter successfully. Finally, it updates the Source System connection string to point back to the EBS middleware host and port (e.g., `http://demo.enginatics.com:80`), completing the handshake between the two systems.
Author
Replies

Viewing 6 reply threads

You must be logged in to reply to this post.