Solved

IFS TEST Enviroment not working after clone from PROD

  • 2 October 2020
  • 3 replies
  • 811 views

Userlevel 1
Badge +4

Hi,

Last sunday we cloned the PROD database to our TEST enviroment. After that the TEST enviroment is not working anymore. When I start IFS test the following error pops up:

 

 

THE URI: https:"LINK_OF_IFS_TEST_AS”:58080/fndext/clientgateway/ cannot be found. Please contact your sys admin.

 

Error 404 - Not Found.

 

Does anyone recognized this problem or knows the solution?

 

Best regards,

Bram

icon

Best answer by Ruchira 2 October 2020, 10:10

View original

3 replies

Userlevel 5
Badge +12

Hi,

Didi you try a reconfiguration of the Application server after the database clone?

Userlevel 1
Badge +4

Hi,

Didi you try a reconfiguration of the Application server after the database clone?

Didn't think about but it worked! Thank you

Userlevel 2
Badge +6

Apps9. When we clone from live to test, we have a script to update the following: 

fnd_setting_tab (system parameters from explorer):

Parameter:

URL_HELP_BASE

REPDES_GRAPHICS

URL_EXT_SERVER

CR_VIRTUAL_DIRECTORY

 

The CONN_STR parameter on the PLSQLAP_ENVIRONMENT_TAB.

 

For data migrations:

update the intface_path on the intface_header_tab to change the path on all data migrations.

 

If you are using docman with ftp or file share you might want to check the edm repositories to ensure test and live are not referring to the same location.

 

A script to disable the email report rules to prevent statements/invoices getting email automatically.

 

We change the smtp host/port to an internal dummy smtp server on the test system.

You might need to check the ACL.

 

We don’t run the reconfiguration of the application server. I think you still need to take some of these changes into consideration though. After the configuration, you can compare live with test. Hope this is of some use.

 

 

Reply