Methodology on ADF and non-ADF apps

108 views

Skip to first unread message

jayaram nagarajan

unread,

Jun 17, 2015, 2:51:41 PM6/17/15

to adf-met...@googlegroups.com

Hello,

Checking with you all on which is the best approach.

Here s the scenario

Step1: Weblogic 12c - basic domain D1 - a non-ADF app deployed to a managed serverM1 - works ok.

Step2: D1 domain extended for JRF option, RCU utility used and created db schemas and datasources - another managed server created M2 - ADF app deployed .

Step2 - breaks library dependencies like common-beanutils for non-ADF app - overcome by specifying in weblogic.xml in the non-adf app.

but non-ADF managed server M1 now throws a different error "says OPSSdatasource not found ".

This datasource is part of JRF/ADF option and target for this is only M2 server and is not needed in M1 but since JRF option is applied at the domain level, Weblogic keeps looking for opssdatasource in all managed servers and throws errors accordingly.

In this case, we suggest the best approach is to keep ADF apps/JRF extended in one domain and non-ADF apps in another domain on the same physical/logical server.