Inactive deployments in OSB domain
See original GitHub issueI am installing an OSB domain using WDT 1.9.14 and it is provisioned with 168 deployments, but some of them are in status Installed. How to make them Active? Here is the list - they are mostly in Scope of “OSBBothTemplate template” but some are “Global”:
Aggregator Singleton Marker Application beehive-controls-1.0.1-10.0-war (1.0,1.0.2.2) beehive-netui-1.0.1-10.0 (1.0,1.0.2.2) beehive-netui-resources-1.0.1-10.0 (1.0,1.0.2.2) CoherenceAdapter com.bea.wlp.lwpf.console.app (10.3.0,10.3.0) com.bea.wlp.lwpf.console.web (10.3.0,10.3.0) JCAFrameworkImpl (12.1.2.0,12.1.2.0) JDEWorldAdapter jstl (1.2,1.2.0.1) LdapAdapter MQSeriesAdapter MSMQAdapter oracle.soa.commonconsole.dependencies (12.1.2,12.1.2) oracle.soa.sb.em.adf.mgmt (1.0,12.1.2.0.0) oracle.soa.webmapper (12.1.3,12.1.3) OracleAppsAdapter OracleBamAdapter resource-mq-connection (12.1.3,12.1.3) resource-mq-jms-connector (12.1.3,12.1.3) SAPAdapter SiebelAdapter SocketAdapter stage-logging (12.1.3,12.1.3) stage-publish (12.1.3,12.1.3) stage-routing (12.1.3,12.1.3) stage-transform (12.1.3,12.1.3) stage-utils (12.1.3,12.1.3) struts-1.2 (1.2,1.2.9) transport-dsp (12.1.3,12.1.3) transport-ejb (12.1.3,12.1.3) transport-email (12.1.3,12.1.3) transport-file (12.1.3,12.1.3) transport-ftp (12.1.3,12.1.3) transport-jca (12.1.3,12.1.3) transport-jejb (12.1.3,12.1.3) transport-mq (12.1.3,12.1.3) transport-pollersdk (12.1.3,12.1.3) transport-sftp (12.1.3,12.1.3) transport-soa (12.1.3,12.1.3) transport-tuxedo (12.1.3,12.1.3) UMSAdapter weblogic-controls-10.0-war (10.0,10.2) wlp-framework-common-web-lib (10.3.0,10.3.0) wlp-framework-struts-1.2-web-lib (10.3.0,10.3.0) wlp-light-web-lib (10.3.0,10.3.0) wlp-lookandfeel-web-lib (10.3.0,10.3.0) wls-commonslogging-bridge-war (1.0,1.1)
I tried defining some of those by explicitly putting into WDT model file, like this:
appDeployments:
Library:
'transport-mq#12.1.3@12.1.3':
CompatibilityName: 'transport-mq#12.1.3@12.1.3'
SourcePath: '@@ORACLE_HOME@@/osb/lib/transports/mq-transport.jar'
DeploymentOrder: 44
StagingMode: nostage
Target: 'OsbCluster,AdminServer'
but it didn’t work - deployment stays in Installed state, target is not getting set. Not to mention that this seems to be redundant to define it, if it is already deployed.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:9 (4 by maintainers)
OSB provided a fix ARU 24175240 for this issue.
Applying the patch 32343813 “DEPLOYMENT SCOPE IN WLS CONSOLE IS WRONG” fixed the problem. Thanks!