Ear deployment issue.

Hi,
i am using jdev Studio Edition Version 11.1.1.4.0
I have created EAR of my application and trying to depoly it on Weblogic server.
I have following entry in weblogic-application.xml
<library-ref>
<library-name>adf.oracle.domain</library-name>
</library-ref>
[03:12:39 PM] ---- Deployment started. ----
[03:12:39 PM] Target platform is (Weblogic 10.3).
[03:13:07 PM] Retrieving existing application information
[03:13:07 PM] Running dependency analysis...
[03:13:07 PM] Building...
[03:13:28 PM] Deploying 3 profiles...
[03:13:29 PM] Moving WEB-INF/adfc-config.xml to META-INF/adfc-config.xml
[03:13:30 PM] Wrote Archive Module to /home/kpophale/CDMR/13June/frontend/ConsoleApps/AppsInventoryManagerUi/deploy/AppsInventoryManagerUi.jar
[03:13:38 PM] Wrote Web Application Module to /home/kpophale/CDMR/13June/frontend/ConsoleApps/AppsInventoryManagerUi/deploy/AppsInventory.war
*[03:13:38 PM] Removing the following prohibited entry from the EAR: lib/trinidad-api.jar*
*[03:13:38 PM] Removing the following prohibited entry from the EAR: lib/trinidad-impl.jar*
[03:13:38 PM] removed bundleresolver.jar from lib because it cannot be part of an EJB deployment
[03:13:54 PM] Wrote Enterprise Application Module to /home/kpophale/CDMR/13June/frontend/deploy/AppsInventoryManager.ear
[03:13:55 PM] Entering Oracle Deployment Plan Editor
[03:15:53 PM] Deploying Application...
[03:16:41 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application AppsInventoryManager on AdminServer.: [Deployer:149145]Unable to contact 'bam_server1'. Deployment is deferred until 'bam_server1' becomes available.; nested exception is:
     java.rmi.UnknownHostException: Could not discover administration URL for server 'bam_server1'.
[03:16:41 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application AppsInventoryManager on AdminServer.: [Deployer:149145]Unable to contact 'osb_server1'. Deployment is deferred until 'osb_server1' becomes available.; nested exception is:
     java.rmi.UnknownHostException: Could not discover administration URL for server 'osb_server1'.
[03:16:41 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application AppsInventoryManager on AdminServer.: [Deployer:149145]Unable to contact 'soa_server1'. Deployment is deferred until 'soa_server1' becomes available.; nested exception is:
     java.rmi.UnknownHostException: Could not discover administration URL for server 'soa_server1'.
[03:16:41 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application AppsInventoryManager on AdminServer.: [Deployer:149145]Unable to contact 'adf_server1'. Deployment is deferred until 'adf_server1' becomes available.; nested exception is:
     java.rmi.UnknownHostException: Could not discover administration URL for server 'adf_server1'.
[03:16:41 PM] [Deployer:149193]Operation 'deploy' on application 'AppsInventoryManager' has failed on 'AdminServer'
[03:16:41 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application AppsInventoryManager on AdminServer.: Failed to load webapp: 'trellis-AppsInventoryManagerUi-context-root'.
[03:16:41 PM] Weblogic Server Exception: weblogic.application.ModuleException: Failed to load webapp: 'trellis-AppsInventoryManagerUi-context-root'
*[03:16:41 PM] Caused by: java.lang.NoClassDefFoundError: org/apache/myfaces/trinidad/webapp/UIXComponentELTag*
[03:16:41 PM] See server logs or server console for more details.
[03:16:41 PM] weblogic.application.ModuleException: Failed to load webapp: 'trellis-AppsInventoryManagerUi-context-root'
[03:16:41 PM] #### Deployment incomplete. ####
[03:16:41 PM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)
I am getting above exception while i am trying to depoly the my ear. please see bold lines.
Please give me some guide line .
Regards,
Kiran.

Hi John,
Yes I have. I even tried on two seperate WebLogic installations. I noticed, even when I create just an ear file (not deploy to server), it gives me the same warnings about removing trinidad. Is there something i'm missing in JDeveloper?
For my installations:
On one Middleware home: I installed: WLS 10.3.5, ADF 11.1.1.5, then ADF 11.1.2 Patch 12611176. configured domain with all ADF/JRF libraries, followed by upgradeADF WLST command. I got same deployment issue.
On another middleware home: I even just installed JDeveloper 11.1.2, configured a new domain with all librearies. I got same deployment issue.
FYI: I also added the two Trinidad JSP Tag Libraries to my View Controller Project. I got same error.
Thank you,
Gavin
Edited by: GavinWoods on Feb 14, 2012 6:25 AM

Similar Messages

  • Adobe-livecycle-weblogic.ear deployment issue on weblogic 12c

    Hi All,
         I am trying to install livecycle 3 on weblogic 12c. but in configuration manager adobe-livecycle-weblogic.ear is not getting deployed when packaged JDBC is selected
    has anyone faced this isse before...

    Hi Ravi,
    WebLogic 12c is not a supported Application Server for LiveCycle ES3.
    You can visit http://help.adobe.com/en_US/livecycle/10.0/supported_platforms.html for a list of supported Application Servers for LiveCycle ES3.
    Thanks and Regards,
    Hina Rastogi

  • Application Deployment issue in Webdynpro project

    Hi,
    I have created an sample Webdynpro project which just displays the name. EAR file has been transformed to SCA file using NWPACKTOOL for deploying the application in JSPM.
    When i tried to deploy the SCA file i am getting an exception as,
    Deployment Items -
         1. Client path 'C:\usr\sap\WP1\SYS\EPS\in\test1.sca'
              Deploy status is 'Aborted'
              Description:'1. Item is skipped because of failed deployment of item 'test.com_test' and because the applied error strategy is OnErrorStop
              2. Contains Aborted deployment component:
    test.com_test'.
              SCA : name 'test', vendor 'test.com', location 'local', version '1000.1.0.1.0.20110810105342'
              Contained DCs:
                   1.1 : Relative path 'C:\usr\sap\WP1\SYS\EPS\in\test1.sca --> test.sca.ear'
                        Deploy status is 'Aborted'
                        Description:'1. ASJ.dpl_ds.006193 Error while deploying ear file C:\usr\sap\WP1\J00\j2ee\cluster\server0\.\temp\tcbldeploy_controller\archives\56\test1_sca1312954437078\DEPLOYARCHIVES\test.sca.ear; nested exception is:
         com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception while [validating application test.com/test.
         The test.com/test application was processed from [developmentserver] containers, but none of them returned information about deployed components.
         The registered containers in this moment were [BRMS_Content_Archive, z_com.sap.security.policy-configurations, utl_handler, developmentserver, Monitoring Configurator, component.info_handler, servlet_jsp, connector, classification_handler, CTCContainer, JDBCConnector, PortalRuntimeContainer, dbcontentcontainer, scheduler~container, Content Container, src.zip_handler, PCD Content Deployment Handler, ConfigurationsContainer, orpersistence, appclient, JMSConnector, Cluster File System, Cache Configuration Upload, com.sap.security.ume, SCA Composites Container, metamodelrepository, textcontainer, eden_handler, Galaxy_Content_Archive, uddi_handler, MigrationContainer, com.sap.security.login-modules, webservices_container, EJBContainer, dbschemacontainer, MDRContainer, com.sap.security.policy-configurations, app_libraries_container].
         Possible reasons :
         1.Empty or incorrect application, which is not recognized by registered containers.
         2.An AS Java service, which is providing a container, is stopped or not deployed.
         3.The containers, which processed it, are not implemented correctly, because the application was deployed or started initially, but containers didn't return information about deployed components in the application deployment info].'.
                        SDA : name 'test', vendor 'test.com', location 'local', version '2', software type ('J2EE', s
    Can some one help me in deploying the SCA file?
    Please let me know how to resolve this issue.
    Thanks in Advance!!
    Regards
    MG
    Edited by: madhanssmile on Aug 10, 2011 2:34 PM

    go to "DC Metadata" "used DC"  , and "Properties" in context menu
    for all you your components.
    problematic component reference probable has check box "deploy time" checked.
    remove that reference.
    usually only "Build time"  check box must be checked. try to do so.

  • Outbound BPEL Process deployment Issue in SOA (binding.jca-12600)

    Hi,
    I have Designed an Outbound BPEL Process for Siebel CRM Service Integration using Jdeveloper (11.1.1.3.0). After that I am facing the deployment issue of this application in SOA suite (11.1.1.6.0). Following is the deployment.log status in jdeveloper:-
    [10:57:54 AM] ---- Deployment started. ----
    [10:57:54 AM] Target platform is (Weblogic 10.3).
    [10:57:54 AM] Running dependency analysis...
    [10:57:54 AM] Building...
    [10:57:58 AM] Deploying profile...
    [10:57:58 AM] Wrote Archive Module to C:\JDeveloper\mywork\Siebel_Outbound_BPEL\QueryWithView_Invoke\deploy\sca_QueryWithView_Invoke_rev1.0.jar
    [10:57:58 AM] Deploying sca_QueryWithView_Invoke_rev1.0.jar to partition "default" on server AdminServer [10.10.22.81:7001]
    [10:57:58 AM] Processing sar=/C:/JDeveloper/mywork/Siebel_Outbound_BPEL/QueryWithView_Invoke/deploy/sca_QueryWithView_Invoke_rev1.0.jar
    [10:57:58 AM] Adding sar file - C:\JDeveloper\mywork\Siebel_Outbound_BPEL\QueryWithView_Invoke\deploy\sca_QueryWithView_Invoke_rev1.0.jar
    [10:57:58 AM] Preparing to send HTTP request for deployment
    [10:57:59 AM] Creating HTTP connection to host:10.10.22.81, port:7001
    [10:57:59 AM] Sending internal deployment descriptor
    [10:57:59 AM] Sending archive - sca_QueryWithView_Invoke_rev1.0.jar
    [10:58:00 AM] Received HTTP response from the server, response code=500
    [10:58:00 AM] Error deploying archive sca_QueryWithView_Invoke_rev1.0.jar to partition "default" on server AdminServer [10.10.22.81:7001]
    [10:58:00 AM] HTTP error code returned [500]
    [10:58:00 AM] Error message from server:
    #;There was an error deploying the composite on AdminServer: Deployment Failed: [JCABinding] [QueryWithView_Invoke.QueryWithView/1.0]Unable to complete load due to: Generic error.
    #;Generic error.
    #;Cause: Unable to find suitable outbound binding.
    #;Please create a Service Request with Oracle Support.
    #;: Generic error.
    #;Generic error.
    #;Cause: Unable to find suitable outbound binding.
    #;Please create a Service Request with Oracle Support.
    [10:58:00 AM] Check server log for more details.
    [10:58:00 AM] Error deploying archive sca_QueryWithView_Invoke_rev1.0.jar to partition "default" on server AdminServer [10.10.22.81:7001]
    [10:58:00 AM] #### Deployment incomplete. ####
    [10:58:00 AM] Error deploying archive file:/C:/JDeveloper/mywork/Siebel_Outbound_BPEL/QueryWithView_Invoke/deploy/sca_QueryWithView_Invoke_rev1.0.jar
    (oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)
    And the following is the SOA Server Side log file status:-
    ####<Jun 3, 2013 10:36:05 AM AST> <Info> <Health> <HOSADDAT02> <AdminServer> <weblogic.GCMonitor> <<anonymous>> <> <4be72ac3bdb5ebae:-a61256d:13f08d94c98:-8000-00000000000000f4> <1370244965280> <BEA-310002> <36% of the total memory in the server is free>
    ####<Jun 3, 2013 10:36:12 AM AST> <Error> <ServletContext-/soa-infra> <HOSADDAT02> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <4be72ac3bdb5ebae:-a61256d:13f08d94c98:-8000-000000000000182b> <1370244972343> <BEA-000000> <Error during deployment
    oracle.fabric.common.FabricException: Deployment Failed: [JCABinding] [QueryWithView_Invoke.QueryWithView/1.0]Unable to complete load due to: Generic error.
    Generic error.
    Cause: Unable to find suitable outbound binding.
    Please create a Service Request with Oracle Support.
    : Generic error.
    Generic error.
    Cause: Unable to find suitable outbound binding.
    Please create a Service Request with Oracle Support.
         at oracle.integration.platform.blocks.deploy.StandaloneCompositeDeploymentCoordinatorImpl.coordinateCompositeDeployment(StandaloneCompositeDeploymentCoordinatorImpl.java:64)
         at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deployNewComposite(BaseDeployProcessor.java:415)
         at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deploySARs(BaseDeployProcessor.java:250)
         at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:167)
         at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:112)
         at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeploy(DeployProcessor.java:99)
         at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.process(DeployProcessor.java:81)
         at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPostInsideLoggingSession(CompositeDeployerServlet.java:219)
         at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPost(CompositeDeployerServlet.java:130)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
         at java.security.AccessController.doPrivileged(Native Method)
         at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
         at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
         at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
         at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
         at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
         at java.security.AccessController.doPrivileged(Native Method)
         at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
         at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
         at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
         at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
         at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Caused By: oracle.fabric.common.FabricDeploymentException: [JCABinding] [QueryWithView_Invoke.QueryWithView/1.0]Unable to complete load due to: Generic error.
    Generic error.
    Cause: Unable to find suitable outbound binding.
    Please create a Service Request with Oracle Support.
    : Generic error.
    Generic error.
    Cause: Unable to find suitable outbound binding.
    Please create a Service Request with Oracle Support.
    {rootCauses=[]}
         at oracle.integration.platform.blocks.adapter.AdapterReference.load(AdapterReference.java:458)
         at oracle.integration.platform.blocks.adapter.AdapterReference.load(AdapterReference.java:82)
         at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnection.deployReferences(CompositeDeploymentConnection.java:201)
         at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnection.deploy(CompositeDeploymentConnection.java:93)
         at oracle.integration.platform.blocks.deploy.CompositeDeploymentManagerImpl.initDeployment(CompositeDeploymentManagerImpl.java:150)
         at oracle.integration.platform.blocks.deploy.CompositeDeploymentManagerImpl.load(CompositeDeploymentManagerImpl.java:63)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
         at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
         at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
         at oracle.integration.platform.blocks.deploy.DeploymentEventPublisher.invoke(DeploymentEventPublisher.java:77)
         at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
         at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
         at $Proxy314.load(Unknown Source)
         at oracle.integration.platform.blocks.deploy.StandaloneCompositeDeploymentCoordinatorImpl.coordinateCompositeDeployment(StandaloneCompositeDeploymentCoordinatorImpl.java:59)
         at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deployNewComposite(BaseDeployProcessor.java:415)
         at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deploySARs(BaseDeployProcessor.java:250)
         at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:167)
         at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:112)
         at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeploy(DeployProcessor.java:99)
         at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.process(DeployProcessor.java:81)
         at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPostInsideLoggingSession(CompositeDeployerServlet.java:219)
         at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPost(CompositeDeployerServlet.java:130)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
         at java.security.AccessController.doPrivileged(Native Method)
         at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
         at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
         at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
         at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
         at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
         at java.security.AccessController.doPrivileged(Native Method)
         at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
         at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
         at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
         at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
         at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Caused By: BINDING.JCA-12600
    Generic error.
    Generic error.
    Cause: Unable to find suitable outbound binding.
    Please create a Service Request with Oracle Support.
         at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterBindingConfig.addAdapterReference(AdapterBindingConfig.java:206)
         at oracle.integration.platform.blocks.adapter.AdapterReference.setupAdapterReference(AdapterReference.java:506)
         at oracle.integration.platform.blocks.adapter.AdapterReference.load(AdapterReference.java:425)
         at oracle.integration.platform.blocks.adapter.AdapterReference.load(AdapterReference.java:82)
         at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnection.deployReferences(CompositeDeploymentConnection.java:201)
         at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnection.deploy(CompositeDeploymentConnection.java:93)
         at oracle.integration.platform.blocks.deploy.CompositeDeploymentManagerImpl.initDeployment(CompositeDeploymentManagerImpl.java:150)
         at oracle.integration.platform.blocks.deploy.CompositeDeploymentManagerImpl.load(CompositeDeploymentManagerImpl.java:63)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
         at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
         at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
         at oracle.integration.platform.blocks.deploy.DeploymentEventPublisher.invoke(DeploymentEventPublisher.java:77)
         at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
         at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
         at $Proxy314.load(Unknown Source)
         at oracle.integration.platform.blocks.deploy.StandaloneCompositeDeploymentCoordinatorImpl.coordinateCompositeDeployment(StandaloneCompositeDeploymentCoordinatorImpl.java:59)
         at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deployNewComposite(BaseDeployProcessor.java:415)
         at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deploySARs(BaseDeployProcessor.java:250)
         at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:167)
         at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:112)
         at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeploy(DeployProcessor.java:99)
         at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.process(DeployProcessor.java:81)
         at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPostInsideLoggingSession(CompositeDeployerServlet.java:219)
         at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPost(CompositeDeployerServlet.java:130)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
         at java.security.AccessController.doPrivileged(Native Method)
         at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
         at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
         at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
         at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
         at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
         at java.security.AccessController.doPrivileged(Native Method)
         at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
         at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
         at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
         at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
         at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Kindly help me in this regard

    Solution:
    Workaround the issue immediately by removing the "ns1:" qualification on the operation for the binding.jca entry in the composite.xml and redeploying.
    For example:
    From:
    <binding.jca config="BAPI_COMPANYCODE_GETDETAIL_invoke_3P.jca"
    operation="ns1:BAPI_COMPANYCODE_GETDETAIL"/>
    To:
    <binding.jca config="BAPI_COMPANYCODE_GETDETAIL_invoke_3P.jca"
    operation="BAPI_COMPANYCODE_GETDETAIL"/>
    Regards,
    Shaheer Badar

  • Adobe Acrobat 9 Pro deployment issue

    Hello. I am having a deployment issue with Adobe Acrobat 9 using Altiris. I create the rip which is bassically an image of the install. My facility has pruchased 50 seats for this software so I know we are covered for the users that we have to use this software. The issue that I am having after I make the rip, and deploy it to a machine it asks for the CD key again in order to use. Am I having an issue with my installation or is Adobe put some kind of security into their software so that when you try to make a rip of the installation is asks for teh CD Key again after the install? Is this an issue that can be resolved?

    SOLUTION:
    The issue was somehow related to DPI (START > Settings > Control Pannel > Display > Settings Tab > Advanced button). Eventhough the DPI was set to normal, I switched it to LARGE, restarted the machine, logged in after the reboot, changed it back to normal size, restarted again, logged in once more, checked the Printer Preferences and PRESTO --- a properly displayed window.

  • Deploy issue from JDeveloper 10.1.3.5 to OAS 10.1.2

    I have written an application using ADF on JDeveloper 10.1.3.5 and need to deploy it to our OAS 10.1.2. I have run the adfinstaller on the linux server to upgrade the ADF libraries to the correct versions, updated the web.xml files to have the correct versions, changed to J2SE 1.4.2_19 for the application and have still got deployment issues.
    Error
    An error occurred while redeploying application "FormsSiebelIntegration". See base exception for details.
    Resolution:
    See base exception for details.
    Base Exception:
    java.lang.UnsupportedClassVersionError
    com/sun/faces/application/ApplicationAssociate (Unsupported major.minor version 49.0). com/sun/faces/application/ApplicationAssociate (Unsupported major.minor version 49.0)
    Removing the jsf-impl.jar file allows the application to deploy, but when running on the app server I get the following errors:
    OracleJSP: oracle.jsp.parse.JspParseException:
    /codename.jspx: Line # 6, <jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.0" xmlns:h="http://java.sun.com/jsf/html" xmlns:f="http://java.sun.com/jsf/core" xmlns:af="http://xmlns.oracle.com/adf/faces" xmlns:afh="http://xmlns.oracle.com/adf/faces/html">
    Help! I'm starting to have total mind block as to what to do next.
    Error: Unable to load taghandler class: http://java.sun.com/jsf/html

    I had already applied all of this before trying to deploy.
    The error seems to be a versioning error in the jsf-impl.jar file as the ApplicationAssociate class is found there. I have changed the JDK and J2EE to 1.4.2 and 1.3 respectively, rebuilt everything, updated all the settings to the right versions for 10.1.2 but it still keeps failing on the deploy.

  • WebLogic Server EAR Deployment Queries!

    Hi All,
    I have few queries with respect to EAR deployment in BEA WebLogic Server
    a) we have a requirement wherein we need to deploy the modified EAR file to one node in a cluster, whereas the other node will still continue to use the old EAR file. Is that possible in a production environment?
    b) we also have a requirement wherein we need to bring down the cluster and start the servers as independent servers instead of a clustered servers from command line without logging into the weblogic server console
    c) we have one more requirement wherein we have all the configuration xml files for each web application in a EAR File. We need a way to deploy the configuration xml file separately if there is a change only to the configuration xml file. Is that possible?
    Also, we need to deploy a specific web application in a EAR file instead of re-creating the EAR again. Like an emergency release of one or more web application in a EAR.
    d) Is that possible to update the JAR file and WAR file dynamically which are deployed as part of the EAR file.
    Any pointers to info source will be REALLY appreciated.
    Wiating for your reply.
    Many Thanks in Advance,
    C R Baradwaj

    Hi,
    Can anyone from BEA team help me in these queries?
    This is very urgent!
    have few queries with respect to EAR deployment in BEA WebLogic Server
    a) we have a requirement wherein we need to deploy the modified EAR file to one node in a cluster, whereas the other node will still continue to use the old EAR file. Is that possible in a production environment?
    b) we also have a requirement wherein we need to bring down the cluster and start the servers as independent servers instead of a clustered servers from command line without logging into the weblogic server console
    c) we have one more requirement wherein we have all the configuration xml files for each web application in a EAR File. We need a way to deploy the configuration xml file separately if there is a change only to the configuration xml file. Is that possible?
    Also, we need to deploy a specific web application in a EAR file instead of re-creating the EAR again. Like an emergency release of one or more web application in a EAR.
    d) Is that possible to update the JAR file and WAR file dynamically which are deployed as part of the EAR file.
    Thanks and Regards,
    C R Baradwaj

  • WLS 11 Policy migration during EAR deployment

    We are installing an ADF 11g EAR into our development instance of WLS 10.3.1 and are seeing some strange behavior with the ADF policy migration. During the EAR install from either the WLS console, or using WLST scripts, the ear deployment appears to create entries in our domains system-jazn-data.xml file in the .../config/fmwconfig directory. The policies work fine when testing the application. Users in the various application roles see expected security behavior. If we then start and stop a completely different managed server from the console, the entries that were in the system-jazn-data.xml file disappear, but the our application security continues to work as expected. If we then bounce the server our ear is deployed to, the entries show up again in system-jazn-data.xml.
    Can anyone explain this behavior and verify if this is expected?
    Additional Information: We have followed the enterprise deployment guide when setting up our middleware home directory. We have the following directory structure:
    /opt/oracle/admin/snidomain/aserver
    /opt/oracle/admin/snidomain/mserver
    The aserver directory contains the admin server and the mserver directory contains our managed servers. Each directory contains a config/fmwconfig subdirectory each containing a system-jazn-data.xml file. Each also contains a jps-config.xml file that specifies an XML policy provider pointing at "./system-jazn-data.xml". When we install an EAR that utilizes ADF security, the system-jazn-data.xml file in the mserver directory is updated during deployment, but the one in the aserver directory is not. Each recycle of a managed server appears to replace the contents of the system-jazn-data.xml file in the mserver directory.
    Also, when I bring up Fusion Middleware Control and view the roles/policies of the ear, none are displayed in the UI. If I add a role/policy using Fusion Middleware Control, the new role/policy is placed in the system-jazn-data.xml file in the aserver directory, and the contents of the one in the mserver directory is completely replaced with the same contents as the one in the asever directory, overwriting the ones added during the deployment.

    We are installing an ADF 11g EAR into our development instance of WLS 10.3.1 and are seeing some strange behavior with the ADF policy migration. During the EAR install from either the WLS console, or using WLST scripts, the ear deployment appears to create entries in our domains system-jazn-data.xml file in the .../config/fmwconfig directory. The policies work fine when testing the application. Users in the various application roles see expected security behavior. If we then start and stop a completely different managed server from the console, the entries that were in the system-jazn-data.xml file disappear, but the our application security continues to work as expected. If we then bounce the server our ear is deployed to, the entries show up again in system-jazn-data.xml.
    Can anyone explain this behavior and verify if this is expected?
    Additional Information: We have followed the enterprise deployment guide when setting up our middleware home directory. We have the following directory structure:
    /opt/oracle/admin/snidomain/aserver
    /opt/oracle/admin/snidomain/mserver
    The aserver directory contains the admin server and the mserver directory contains our managed servers. Each directory contains a config/fmwconfig subdirectory each containing a system-jazn-data.xml file. Each also contains a jps-config.xml file that specifies an XML policy provider pointing at "./system-jazn-data.xml". When we install an EAR that utilizes ADF security, the system-jazn-data.xml file in the mserver directory is updated during deployment, but the one in the aserver directory is not. Each recycle of a managed server appears to replace the contents of the system-jazn-data.xml file in the mserver directory.
    Also, when I bring up Fusion Middleware Control and view the roles/policies of the ear, none are displayed in the UI. If I add a role/policy using Fusion Middleware Control, the new role/policy is placed in the system-jazn-data.xml file in the aserver directory, and the contents of the one in the mserver directory is completely replaced with the same contents as the one in the asever directory, overwriting the ones added during the deployment.

  • How to reference sapjco from EAR deployment descriptors

    Hello techies,
    I´ve set up an EJB to use the JCo RFC Provider Service of the J2EE engine. Connection from R3 to EJB works but as soon as the EJB gets invoked, I get the error 'incompatible bean type - no processFunction found' from the RFCDefaultRequestHandler.invokeBean(..., JCO.Function) method.
    The reason is clear to me - the JCO.Function class is loaded by different class loaders and thus the method parameters don´t match.
    I´ve read in earlier postings that it is neccessary to reference the JCO in the module project and the ear deployment descriptor. That´s where my question begins.
    How do I reference the JCO in the module project (what´s that?)? I think it has to do with the EJB jar, doesn´t it?
    In the DeployTool I found a way how to set a reference to a library in the menu deploy-->libraries. But I am not sure what to specify here. I entered 'sapjco', since I saw an entry in the managers/library.txt file. Is that correct?
    Any hints are welcome!
    Regards,
    Jan

    Jan,
    you can set the reference to the EAR project using the reference.txt file that exists in the /managers folder.
    In the library.txt file set a path which is reference to sapjco.jar files..like
    library JCO sapjco.jar
    in the refernce.txt add the JCO referece to the EAR project...like
    reference Project library:JCO
    where Project here is the name of your EAR file..
    Ravi

  • A very urgent deployment issue about DBAdapter

    Hello All,
    I have a very urgent deployment issue about DBAdapter.
    That DBAdapter is connect to DB2 AS400 Database. I have a developing database (jdbc:as400://server01/TEST) and a production database (jdbc:as400://server01/PROD).
    During developing, I used DBAdapter wizard to create it, and import some tables, and set the Adapter to use jabc/DB2DS as connection information for easily deployment later.
    Then I deploy to Production. I configured Data-source.xml and oc4j-ra.xml rightly; I set DB connection point to production database. But the DBAdapter still write into developing Database.
    I checked the DBAdapter, the imported tables are something like this, TEST.table1, TEST.table2. And there are a lot "TEST" located in DB2Writer_toplink_mapping.xml, DB2Writer.xml, TEST.schema, DB2Writer.table1.ClassDescriptor.xml.
    This TEST is refrer to the TEST in connect String jdbc:as400://server01/TEST.
    I think this might be the reason cause the problem. As to production database, "TEST" should replaced by "PROD". If I changed it manually, I have to change every time when switch between TEST and PROD. And I also don't know if it is safe to do it? (I tried, and bring some toplink mapping problem)
    By the way, for Oracle Database, because we use 2 instances for testing and production with same schema name, and do not have this issue.
    Anyone could help and many thanks.
    Kerr
    Message was edited by:
    Kerr

    Hi Kerr,
    The idea is to set up all connections in the BPEL or ESB services with logical names, e.g. typically of the form eis/DB/MyFinancialSystem or eis/DB/MyLogisticsSystem. This way, you do not have to modify code when deploying it onto different environments that serve different purposes.
    When moving your services through their lifecyle, on every environment you deploy these to you will have the same logical connections configured on each instance, e.g. for DEV, QA, SIT, UAT and PROD. Only, in case of QA the actual physical connection is configured to point to the QA instance of the systems that your services interact with whereas in case of UAT it points to the UAT instance of the same system.
    Maybe your problem is caused by connecting as user "SomeUser" when running the DB Adapter wizard during development and actually selecting objects from a different schema than you used to connect with, e.g. "Test" in your case.
    Hth,
    Sjoerd

  • Webdynpro application deployment issue.

    Hi Laydies/Gentlements,
    When I try to deploy webdynpro application, it threw application deployment exception. Anyone can help me?
    The message like below:
    2010/11/11 下午 03:36:36 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
    [008]Deployment aborted
    Settings
    SDM host : PSTVHKDV12
    SDM port : 50018
    URL to deploy : file:/C:/DOCUME1/ericl/LOCALS1/Temp/temp51927phoenixtv.com~eform.ear
    Result
    => deployment aborted : file:/C:/DOCUME1/ericl/LOCALS1/Temp/temp51927phoenixtv.com~eform.ear
    Aborted: development component 'eform'/'phoenixtv.com'/'LOKAL'/'0.2010.11.11.15.36.16'/'0':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Cannot deploy application phoenixtv.com/eform.. Reason: Clusterwide exception: Failed to deploy application phoenixtv.com/eform. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is:      com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application phoenixtv.com/eform. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment exception : The deployment of at least one item aborted
    I copied the source from the other project to current new DC Project. But it's not deployed  successfully.
    Thank you
    Hope you can help me.
    Regards
    Eric

    Hello,
    There are two reasons for the Clusterwide exception:
    1) Firstly, check whether all the referenced components (any used DCs) are already deployed on the server. If not, then first deploy those components and then try deploying the eform.ear again
    2) If all the dependent components are already deployed, then the reason for this error is that there is already an .ear deployed on the J2EE server with the same application and/or component name. So, you must either:
    a) Undeploy the previous application (having the same application name as the eform.ear application)
    OR
    b) Create a new application in the eform.ear project and rename the component. Renaming the component would require changing the name of the component in the implementation as well, wherever the component has been referenced. The newly created application must be mapped to this new component.
    Then try re-deploying the eform.ear again.
    Hope this helps. Do let me know if you need further help.
    Regards,
    Divyata

  • Exploded EAR deployment supported?

    Hi,
    I am currently developing with the MyEclipse IDE. Does Sun Java Studio Enterprise 8.1 support exploded deployment of EARs, and can it 'hot deploy' changes into the running Application Server?
    Thank You

    Hi.
    SJSE 8.1 doesn't support exploded deployment of EAR projects. It currently supports exploded deployment of WAR projects.
    I know that folks have extended NetBeans to support exploded EAR deployment in NB 6.0...
    You can find out more about that in this blog entry and screencast:
    http://blogs.sun.com/vkraemer/entry/new_glassfish_integration_feature_directory
    http://serverplugins.netbeans.org/screencasts/pfsc1.html
    Can you clarify what you mean by 'hot deploy'? Different folks have different definitions of this phrase... I think SJSE 8.1 does 'hot deploy' as I understand it... but my understanding may not match your vision of this feature...
    vbk

  • NWDI - How to control EAR deployment order

    We are developing a custom application in NWDI. We have created a software component for the this and have created all required DCs under this software component.
    All the J2EE DCs are deployed through separate EAR DCs and there are references from one to another ear DC where ever required.
    Deployment of a EAR DC fails if the dependent EARs are missing at that time as it looks for some classes at the time of deployment. We could resolve this in development env as we have the control over individual EAR deployment.
    But for deployment in QA through NWDI, where the whole software component is deployed as one SCA file, deployment is failing due to wrong order of deployment for the EARs. We are not able to figure out how to control the order of EAR deployments contained in a single SCA.
    Please let me know for any further info.
    Points will be awarded for helpful answers
    Regards, Chandra

    Hi  Chandra,
    It defines runtime-reference. And should automatically add references to application-j2ee-engine.xml
    But as far as I remember it is done only in NW7.1
    Regards,
    Andrei.

  • Re: Deployment Issues

    Hi Dale;
    We have the similar situation. We wrote an application to be able to send
    alert message before we shut down the Forte application. When we upgrade our
    applications, we will send alert message to all users before we shut down the
    Forte application through ECONSOLE which forces all users to log out, and then
    overwrite the files.
    Our client files are sitting at one of our network servers instead of
    individual user's PC, so the user accesses the files through network. So we
    are facing the same issue that we have to shut all users down before we
    upgrade our applications. If you install those files on your individual user's
    PC, you may try to use "compatible level" to update your application.
    Hope this helps.
    Lu Wang
    Eli Lilly and Company
    [email protected]

    My problem lies more in the way that we update the Forte software. We are
    controlled enough with a new distribution from the application side that
    there are not problems there.
    My question is: how is everyone updating their client PC's from say Forte
    R2 to R3. This was not a problem before because we didn't have very many
    clients. Now we have quite a few and we can't just copy the proper files
    because of the registry updates that are required.
    Does anyone have any suggestions? Can I run the Forte client software off
    the Novell server?
    Thanks,
    Tony
    -----Original Message-----
    From: Lu Wang X1 <[email protected]>
    To: Dale V. Georg <[email protected]>
    Cc: Forte Users <[email protected]>; Gardner, Steve
    <[email protected]>
    Date: Wednesday, November 19, 1997 11:17 AM
    Subject: Re: Deployment Issues
    You are right. Through econsole, we can only shut down the serverpartitions,
    even though we can uninstall the application, as long as the clientpartition
    is running, we can't overwrite the files. We were probably lucky that nouser
    was running the application when we upgraded it.
    Since our applications can capture the system alert message, probably wecan
    make changes to our application to be able to shut itself down when it
    receives certain type of alert message. Just a thought. Don't know ifthere
    is any better way to handle it.
    Lu
    "Dale V. Georg" <[email protected]> on 11/19/97 03:02:27 AM
    Please respond to "Dale V. Georg" <[email protected]>
    To: Lu Wang X1/AM/LLY
    cc: Forte Users <[email protected]>, "Gardner, Steve"
    <[email protected]>
    Subject: Re: Deployment Issues
    On Tue, 18 Nov 1997 11:04:53 -0500, Lu Wang X1 wrote:
    Hi Dale;
    We have the similar situation. We wrote an application to be able to send
    alert message before we shut down the Forte application. When we upgradeour
    applications, we will send alert message to all users before we shut down
    the
    Forte application through ECONSOLE which forces all users to log out, andthen
    overwrite the files.If I remember correctly, econsole will only forcibly close down the
    server partitions, not the client partitions.
    Our client files are sitting at one of our network servers instead of
    individual user's PC, so the user accesses the files through network. So
    we
    are facing the same issue that we have to shut all users down before we
    upgrade our applications. If you install those files on your individualuser's
    PC, you may try to use "compatible level" to update your application.We did think about using the compatibility level at one point, but that
    introduces extra maintenence whenever a new version of the application
    is rolled out. On the other hand, if that's the cost of a smooth and
    reliable upgrade, then it may be worth paying.
    Dale
    ================================================
    Dale V. Georg
    Systems Analyst
    Indus Consultancy Services
    [email protected]
    ================================================

  • IBFBS failed to deploy in Embedde OC4J but works with EAR deploy.

    Hi
    When i try to deploy IBFBS sample project in JDevloper by Embedde OC4J : its giving
    an error saying "there is no EJB module to deploy".
    But when i deployed through EAR deployment method its working fine.
    PLease kindly help me.
    Sai.

    Hi,
    Can you pls post the Version of JDeveloper and OC4J that you are using?
    I tried to deploy IBFBS using JDeveloper 9.0.3.988 (JDK 1.3.1) on Standalone OC4J server (9.0.3) and it works fine.
    One constraint for not running the application from JDeveloper (by using embedded OC4J) is that, the OC4J where the FBS is deployed needs to have the -userThreads option enabled.
    This option is enabled by starting OC4J with -userThreads option.
    java -jar oc4j.jar -userThreadsRef : Connection to embedded OC4J per FBS Setup Tutorial-Problem.
    Let us know if your problem still persists.
    Thanks
    -- OTN@IDC Team

Maybe you are looking for

  • Dont work software

    i bought e75 before 3 month in icad uae.when i repair softwore dont work . It has no guarntee/warenty?

  • Client from 800 to 000 client to activate the TAX Procedures..

    Hi Guru's, In my practice server i am not able to get the tax procedures TAXINN and TAXINJ for this i went to institute they said that copying from 000 client to 800 client..then we can get in 800 client also.. but here is the problem how to do it..

  • Is now the time to buy FCP?

    I own the original Final Cut Studio. I just bought a new Mac Pro eight core. I'm considering the latest version but don't know if the timing is right. When was the last time FCP was updated? Buy now or wait? The upgrade from FCP Studio is $499 from A

  • How to change logo in sap provided smartform

    Hi gurus, How to change logo in sap provided smartform Regards Naveen

  • Capturing Outbound Interface (In UDF)

    Hi, I have designed a Outbound Interface: <?xml version="1.0" encoding="UTF-8"?> <MT_DMS_FINAL>    <Record>       <Row>          <FirstName/>       </Row>    </Record> </MT_DMS_FINAL> Now i write a Adapter Module to get the File name when the Sender