Endeca Extension HTTP-404 Page not found

Issue – HTTP-404 Page not found

User is trying to navigate to Endeca pages and receives http-404 page not found error. Below is the screenshot.

Fix:

Verify the  profile option FND_ENDECA_PORTAL_URL and make sure it is correctly set.

Endeca Extensions There was an error when trying to access the data source

Issue 1- Datasource Error

There was an error when trying to access the data source. Please confirm with your system administrator that the data source is available.

Below error is observed on Endeca Pages when a clone of EBS Instance is completed.

  Below are the few causes for the issue:

1)      The source EBS may not have Endeca application configured.

2)      Not executed Concurrent program “Populate Endeca Metadata for iProcurement” after any metadata changes performed on Endeca side <-- This is specific to iProcurment page

3)      Endeca data source ebsdb is not listing target managed servers

Launch Console of Endeca Server -> Datasources -> click on datasource ebsdb ->  Monitoring -> Testing. This screen should list the Studio Managed server.

Studio log file reported below errors: (/u01/Oracle/Middleware/user_projects/domains/endeca_domain/servers/StudioManagedServer/logs/StudioManagedServer.log)

####<Jun 8, 2015 10:18:46 PM CDT> <Error> <Deployer> <hpeidrd01.hpinc.com> <StudioManagedServer> <[ACTIVE] ExecuteThread: '17' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KrMKwR45yW^5xVWByW1LT_gK000000> <1433819926781> <BEA-149205> <Failed to initialize the application 'ebsdb' due to error weblogic.application.ModuleException: .

weblogic.application.ModuleException:

        at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:327)

Caused By: weblogic.common.resourcepool.ResourceSystemException:

 Could not connect to 'oracle.apps.fnd.ext.jdbc.datasource.AppsDataSource'.

 The returned message is: ORA-01017: invalid username/password; logon denied

 It is likely that the login or password is not valid.

 It is also possible that something else is invalid in

 the configuration or that the database is not available.

        at weblogic.jdbc.common.internal.JDBCUtil.parseException(JDBCUtil.java:301)

        at weblogic.jdbc.common.internal.PooledConnectionEnvFactory.makeConnection(PooledConnectionEnvFactory.java:317)

        at weblogic.jdbc.common.internal.PooledConnectionEnvFactory.createResource(PooledConnectionEnvFactory.java:97)

        at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1310)

Fix:

The password of EBS User ENDECADM in console is incorrect. Update the correct password for user ENDECADM in console to correct value and save it.

Console -> Lock & Edit in change center -> Datasource -> click on ebsdb -> configuration -> Connection Pool.

Update the password to correct value  and click on Save.

Activate Changes on control center

Once the changes are activated we should be able to see the Managed Server.

 

adop phase=prepare failed with ERROR: Script failed, exit code 255 while creating WLS domain

Issue: 
We are trying to run adop prepare phase on our EBS 12.2 Patch file system and it came out with below errors in FSCloneApplyAppsTier_08200431.log file.

START: Creating new WLS domain.
Running /u01/app/EBSDB/fs2/FMW_Home/oracle_common/bin/pasteConfig.sh -javaHome /u01/app/EBSDB/fs2/EBSapps/comn/util/jdk64 -al /u01/app/EBSDB/fs1/EBSapps/comn/adopclone_ebsdb01/FMW/WLS/EBSdomain.jar -tdl /u01/app/EBSDB/fs2/FMW_Home/user_projects/domains/EBS_domain_EBSDB -tmw /u01/app/EBSDB/fs2/FMW_Home -mpl /u01/app/EBSDB/fs1/EBSapps/comn/adopclone_ebsdb01/FMW/WLS/plan/moveplan.xml -ldl /u01/app/EBSDB/fs1/inst/apps/EBSDB_ebsdb01/admin/log/clone/wlsT2PApply -silent true -debug true -domainAdminPassword /u01/app/EBSDB/fs1/EBSapps/comn/adopclone_ebsdb01/FMW/tempinfo.txtScript Executed in 1602 milliseconds, returning status 255
ERROR: Script failed, exit code 255


The above information didn't give sufficient information and had to review CLONE2015-08-20_04-31-47AM.log &  CLONE2015-08-20_04-31-47AM.error logfiles under $ADOP_LOG_HOME/22/<prepare..>/<CONTEXT_NAME>/ directory.  These have provided below additional information which helped in resolving the issue.

CLONE2015-08-20_04-31-47AM.error:

SEVERE : Aug 20, 2015 4:31:49 AM - ERROR - CLONE-20372   Server port validation failed.
SEVERE : Aug 20, 2015 4:31:49 AM - CAUSE - CLONE-20372   Ports of following servers - AdminServer(7004) - are not available.  <-- This port is of Run filesystem instead it should look for 7005
SEVERE : Aug 20, 2015 4:31:49 AM - ACTION - CLONE-20372   Provide valid free ports.
oracle.as.t2p.exceptions.FMWT2PPasteConfigException: PasteConfig failed. Make sure that the move plan and the values specified in moveplan are correct.

CLONE2015-08-20_04-31-47AM.log:FINE : Aug 20, 2015 4:31:49 AM - [J2EEGenericValidationUtil:validateAndGetServerPort] Listen Port(7805) of server forms-c4ws_server1 is valid and free.FINE : Aug 20, 2015 4:31:49 AM - [J2EEGenericValidationUtil:validateServerConfig] Mapping of ports vs servers from moveplan = {AdminServer=[7004], forms-c4ws_server1=[7805], forms_server1=[7405], oacore_server1=[7205], oafm_server1=[7605]} FINE : Aug 20, 2015 4:31:49 AM - [J2EEGenericValidationUtil:validateServerConfig] Mapping of temporary ports assigned vs servers = {}
FINE : Aug 20, 2015 4:31:49 AM - [J2EEGenericValidationUtil:validateServerConfig] map_serverName_vs_actualPort_vs_TempPort = {}

Above highlighted area confirms that except AdminServer port all the other ports are properly picked up.

Additional info noticed in FSCloneApplyAppsTier_08200431.log
m_LstnAddrPrtsDBMap size = 6
Total no. of configGroup = 6
 configGroup Type name = SERVER_CONFIG
configProperty id = Server1
Count for NodeIterator nextNode = 3

Input for AdminServer Listen Address OR Port is NULL
Moveplan won't be updated for AdminServer Listen Address
Moveplan won't be updated for AdminServer Listen Port+++++++++++++++++++++++++
configProperty id = Server2
Count for NodeIterator nextNode = 3
Input for oacore_server1 Listen Address OR Port is NULL
 Updating oacore_server1 Listen Address to ushtc0app02.jacobs.com
 Updating oacore_server1 Listen Port to 7205

These highlighted details above confirmed that adop is unable to update AdminPort to correct value as part of its preparations.

Fix:
Upon further investigation, Listen Address value for AdminServer on Run Filesystem is removed manually.

1) Login to weblogic console of Run  Filesystem. Perform Lock & Edit. Then Navigate to Domain Structure -> Servers -> Select Adminserver.
2) Under Configuration screen -> Update Listen Address value to application server hostname(FQDN).
3) Bounce all the application services.
4) Run adop phase=prepare.

Workaround:
If you want the Listen address value to be Null. Run fs_clone for the EBS Apps. Then proceed with adop prepare phase.