Issue Descriprion:
The ADF code when deployed on an remote ADF server fails with below exception.
Error Log:
#### <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.ke rnel.Default (self-tuning)'> <> <> <402a65ad9b43fa5a:69fd5e4b:12cff20c642:-8000-00000000000002f4> <1293010450094>
in the execution of deployment request with ID '1293010438085' for task '0'. Error is: 'weblogic.management.DeploymentException: [J2EE:160149]Error while pro
cessing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: adf.oracle.domain, Implementatio
n-Version: 11.1.1.1.0, exact-match: false], [Extension-Name: oracle.jsp.next, exact-match: false].'
weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblog
ic-application.xml: [Extension-Name: adf.oracle.domain, Implementation-Version: 11.1.1.1.0, exact-match: false], [Extension-Name: oracle.jsp.next, exact-matc
h: false].
Cause:
The remote ADF server managed server on which you are trying to deploy your ADF code doesn't have the ADF run time libraries deployed on it. Ask your server admin to deploy it.
Solution:
There are primarily two ways to deploy the ADF run time libraries on a Weblogic managed server(ADF Runtime libraties are supported/installed in the WLS domain).
Method 1: Through EM Console
Method 2: WLST scripts
Method 3: While creating a domain the ADF libraries can be deployed on the managed server.
I will be describing Method 2 here:
You use the custom WLST command applyJRF to configure the Managed Servers or cluster with JRF. To use the custom WLST commands, you must invoke the WLST script from an Oracle home in which the Oracle Fusion Middleware component has been installed
The format of the applyJRF command is:
applyJRF(target={server_name | cluster_name | *}, domainDir=domain_path,
[shouldUpdateDomain= {true | false}])
You can use the applyJRF command online or offline:
In online mode, the JRF changes are implicitly activated if you use the shouldUpdateDomain option with the value true (which is the default.) In online mode, this option calls the online WLST save() and activate() commands.
In offline mode, you must restart the Administration Server and the Managed Servers or cluster. (In offline mode, if you specify the shouldUpdateDomain option with the value true, this option calls the WLST updateDomain() command.)
To configure a Managed Server with JRF, use the following command:
applyJRF(target='server1', domainDir='/scratch/Oracle/Middleware/user_projects/domains/domain1')
To configure all Managed servers in the domain with JRF, specify an asterisk (*) as the value of the target option.
To configure a cluster with JRF, use the following command:
cd $FMW_HOME/oracle_common/common/bin (eg /orionsap_u01/app_ADF/oracle/product/fmw/oracle_common/common/bin)
applyJRF(target='cluster', domainDir='/scratch/Oracle/Middleware/user_projects/domains/domain1')
An Example:
cd $FMW_HOME/oracle_common/common/bin
sh wlst.sh
wls:/offline/test_domain>connect('weblogic','!Welc0me!','adf1.mycompany.com:8100')
Connecting to t3://adf1.mycompany.com:8100 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain 'test_domain'.
Warning: An insecure protocol was used to connect to the
server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.
wls:/mmi_domain/serverConfig> applyJRF('test_enc_ms_1','/u01/app_ADF/oracle/admin/test_domain/aserver/test_domain')
Location changed to serverRuntime tree. This is a read-only tree with DomainMBean as the root.
For more help, use help(domainConfig)
Location changed to domainRuntime tree. This is a read-only tree with DomainMBean as the root.
For more help, use help(domainRuntime)
Location changed to edit tree. This is a writable tree with
DomainMBean as the root. To make changes you will need to start
an edit session via startEdit().
For more help, use help(edit)
Starting an edit session ...
Started edit session, please be sure to save and activate your
changes once you are done.
Saving all your changes ...
Saved all your changes successfully.
Activating all your changes, this may take a while ...
The edit lock associated with this edit session is released
once the activation is completed.
Activation completed
Already in Edit Tree
After this is done,restart the managed server and redeploy your code.
Soumya....
The ADF code when deployed on an remote ADF server fails with below exception.
Error Log:
####
in the execution of deployment request with ID '1293010438085' for task '0'. Error is: 'weblogic.management.DeploymentException: [J2EE:160149]Error while pro
cessing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: adf.oracle.domain, Implementatio
n-Version: 11.1.1.1.0, exact-match: false], [Extension-Name: oracle.jsp.next, exact-match: false].'
weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblog
ic-application.xml: [Extension-Name: adf.oracle.domain, Implementation-Version: 11.1.1.1.0, exact-match: false], [Extension-Name: oracle.jsp.next, exact-matc
h: false].
Cause:
The remote ADF server managed server on which you are trying to deploy your ADF code doesn't have the ADF run time libraries deployed on it. Ask your server admin to deploy it.
Solution:
There are primarily two ways to deploy the ADF run time libraries on a Weblogic managed server(ADF Runtime libraties are supported/installed in the WLS domain).
Method 1: Through EM Console
Method 2: WLST scripts
Method 3: While creating a domain the ADF libraries can be deployed on the managed server.
I will be describing Method 2 here:
You use the custom WLST command applyJRF to configure the Managed Servers or cluster with JRF. To use the custom WLST commands, you must invoke the WLST script from an Oracle home in which the Oracle Fusion Middleware component has been installed
The format of the applyJRF command is:
applyJRF(target={server_name | cluster_name | *}, domainDir=domain_path,
[shouldUpdateDomain= {true | false}])
You can use the applyJRF command online or offline:
In online mode, the JRF changes are implicitly activated if you use the shouldUpdateDomain option with the value true (which is the default.) In online mode, this option calls the online WLST save() and activate() commands.
In offline mode, you must restart the Administration Server and the Managed Servers or cluster. (In offline mode, if you specify the shouldUpdateDomain option with the value true, this option calls the WLST updateDomain() command.)
To configure a Managed Server with JRF, use the following command:
applyJRF(target='server1', domainDir='/scratch/Oracle/Middleware/user_projects/domains/domain1')
To configure all Managed servers in the domain with JRF, specify an asterisk (*) as the value of the target option.
To configure a cluster with JRF, use the following command:
cd $FMW_HOME/oracle_common/common/bin (eg /orionsap_u01/app_ADF/oracle/product/fmw/oracle_common/common/bin)
applyJRF(target='cluster', domainDir='/scratch/Oracle/Middleware/user_projects/domains/domain1')
An Example:
cd $FMW_HOME/oracle_common/common/bin
sh wlst.sh
wls:/offline/test_domain>connect('weblogic','!Welc0me!','adf1.mycompany.com:8100')
Connecting to t3://adf1.mycompany.com:8100 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain 'test_domain'.
Warning: An insecure protocol was used to connect to the
server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.
wls:/mmi_domain/serverConfig> applyJRF('test_enc_ms_1','/u01/app_ADF/oracle/admin/test_domain/aserver/test_domain')
Location changed to serverRuntime tree. This is a read-only tree with DomainMBean as the root.
For more help, use help(domainConfig)
Location changed to domainRuntime tree. This is a read-only tree with DomainMBean as the root.
For more help, use help(domainRuntime)
Location changed to edit tree. This is a writable tree with
DomainMBean as the root. To make changes you will need to start
an edit session via startEdit().
For more help, use help(edit)
Starting an edit session ...
Started edit session, please be sure to save and activate your
changes once you are done.
Saving all your changes ...
Saved all your changes successfully.
Activating all your changes, this may take a while ...
The edit lock associated with this edit session is released
once the activation is completed.
Activation completed
Already in Edit Tree
After this is done,restart the managed server and redeploy your code.
Soumya....
Hi
ReplyDeletePlease let me know how to do this activity through WLST Script .
Thanks
Anil
Samrat already mentioned the same in the post...
Delete