ECC Application Import Fails with HTTP Status 404

Customer July 26, 2019 at 11:04 pm

When running `./patchEccFiles.pl` to import applications, the process fails with `java.lang.Exception: http://:8001/ecc/user/import/applications?gfmString= failed with HTTP status: 404`. The error log says ‘404 Not Found’ for the ECC Web Entry URL. What does a 404 status indicate in this context?

Viewing 6 reply threads

Author
Replies
- Support July 27, 2019 at 6:56 pm
  An HTTP Status 404 (Not Found) means that the server (in this case, the ECC server’s Weblogic component) successfully received the request but could not find anything matching the Request-URI (the path `/ecc/user/import/applications…`) . This often points to an incorrect URL or a failure in the routing or context path configuration . However, in ECC integration, it frequently indicates an issue with host or port resolution between the EBS server (where the script runs) and the ECC managed server .
- Customer July 28, 2019 at 5:07 pm
  We are using a RAC environment with SCAN listeners. Could this contribute to the 404 error during import?
- Support July 28, 2019 at 9:07 pm
  Yes, RAC environments using SCAN listeners have been implicated in connection issues during ECC setup . It is highly recommended to manually replace the SCAN entry with the Virtual IP (VIP) address in both the `EccConfig.properties` file and the generated `connection.dbc` file . This step ensures proper resolution and may resolve routing confusion that leads to the 404 error .
- Customer July 31, 2019 at 10:53 am
  The error description suggests using a 403 (Forbidden) code if the server doesn’t want to make information available. What does the use of the 404 code confirm about the status?
- Support August 1, 2019 at 12:14 am
  The use of the 404 code confirms that the server could not find the resource associated with the Request-URI . If security restrictions were blocking access, the server *should* use a 403 code instead . Therefore, the 404 status points more definitively toward a problem with network configuration, host resolution, or an internal Weblogic routing issue preventing the script from finding the necessary import application context .
- Customer August 3, 2019 at 1:37 am
  If I verify that the EBS and ECC servers are mutually resolvable via ping/telnet, what is the next logical step?
- Support August 3, 2019 at 12:24 pm
  If network connectivity is confirmed, the next logical step is internal Weblogic configuration validation. You should check the `AdminServer.log` on the ECC side for detailed internal server failures . If the application URL (e.g., `/ecc/user/import`) is correct, the 404 suggests the managed server hosting the ECC application context may be incorrectly deployed or registered within the Weblogic domain .
Author
Replies

Viewing 6 reply threads

You must be logged in to reply to this post.