Weblogic : Unresolved application library references - ASCP deployment

I was trying to deploy ASCP application ear file (PlanningUI.ear) in weblogic.

It deployed fine, but while activating the changes, it fails with the below error:

Message icon - Error An error occurred during activation of changes, please see the log for details.

Message icon - Error [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: adf.oracle.domain, exact-match: false], [Extension-Name: oracle.jsp.next, exact-match: false], [Extension-Name: oracle.adf.desktopintegration.model, exact-match: false].

 

Just to check if I can ignore the above errors, I tried to start the deployment to service all requests

and as expected it failed with below error

 

 Message icon - Error weblogic.management.DeploymentException: [Deployer:149003]Unable to access application source information in '/u01/install/ascp/FMW_Home/user_projects/domains/ascp_domain/servers/ASCPManagedServer/stage/PlanningUI/PlanningUI.ear' for application 'PlanningUI'. The specific error is: [Deployer:149158]No application files exist at '/u01/install/ascp/FMW_Home/user_projects/domains/ascp_domain/servers/ASCPManagedServer/stage/PlanningUI/PlanningUI.ear'..

Upon looking further , it seems to be complaining about the following libraries :

adf.oracle.domain

oracle.jsp.next

oracle.adf.desktopintegration.model

I verified, if these libraries are available at all and find those libraries available . To check that you can search for the above libraries in the deployments tab.

However, if I click on each of the library and check the targets for the library, the library is only deployed for the admin server and not for the managed server.

Since I was trying to deploy the planning ear file on the managed server and since the libraries are only deployed on the admin server, I faced this issue.

I clicked on each of the library and deployed them to both admin and managed server. I did that not only the above libraries , but for all the libraries available.

Then retried the deployment and it went successful.

Also , i had to set StartScriptEnabled to true, in the node manager properties file earlier, to get this to working.

/u01/install/ascp/FMW_Home/wlserver_10.3/common/nodemanager

Hope this helps some one.