Deployment Weblogic Integration Application failure !

Hi,
I've a problem when I'm deploying my application on BEA Weblogic 9.2 !
If I'm deploying via the Administration console my application, I'm getting :
Unable to access the selected application.
Exception in AppMerge flows' progression
This is due to the weblogic-extension.xml file in my ear file (under META-INF). This is the content of this file :
<?xml version='1.0' encoding='utf-8'?>
<weblogic-extension xmlns="http://www.bea.com/ns/weblogic/90">
<module-provider>
<name>TaskPlanModule</name>
<module-factory-class-name>com.bea.wli.worklist.internal.taskplan.module.TaskPlanModuleFactory</module-factory-class-name>
<binding-jar-uri>task-plan-binding.jar</binding-jar-uri>
</module-provider>
<custom-module>
<uri>Loans/Loan Approval.task</uri>
<provider-name>TaskPlanModule</provider-name>
<configuration-support>
<base-root-element>task-plan</base-root-element>
<base-namespace>java:com.bea.wli.worklist.internal.taskplan.config</base-namespace>
<base-uri>Loans/Loan Approval.task</base-uri>
<base-package-name>com.bea.wli.worklist.internal.taskplan.config</base-package-name>
</configuration-support>
</custom-module>
</weblogic-extension>
When I'm packaging my application without this file, the console deployment works but I do not have access to my task plan !
If I deploy my application WITH weblogic-extension.xml, it works too...
But with the console... the error appears all the time !
To install my application at my customer, I need that the console deployment of my application works !
Thanks a lot in advance,
Best regards,
Mathieu Triquoit

If the application is worklist not sure you can deploy it through console. you can deploy using
weblogic.Deployer -adminurl t3://<HOST>:7001 -username weblogic -password weblogic -deploy -name WorklistTest -source WorklistTest.ear ?upload

Similar Messages

  • Weblogic Integration Application - Redeploy

    While using Weblogic Integration 7,is redeploy possible for the "Weblogic Integration"
    Application or of components within it. I have a war and a jar file inside this
    application, and running in Development mode iam able to redeploy the WAR, but
    while i redeploy the JAR i have the face the exception that say "bean already
    undeployed". But the deployment status for the JAR reads "Deployed" as true.
    Any information on this would be appreciated
    Thanks
    Raja

    If the application is worklist not sure you can deploy it through console. you can deploy using
    weblogic.Deployer -adminurl t3://<HOST>:7001 -username weblogic -password weblogic -deploy -name WorklistTest -source WorklistTest.ear ?upload

  • CgPool in WebLogic Integration 10.2

    Hi everyone.
    I'm working on Best Practice for WebLogic Integration 10.2 Link:[Document is here|http://download.oracle.com/docs/cd/E13214_01/wli/docs102/pdf/bestpract.pdf]
    In the WLI Application recovery topic, it says "cgDataSource is configured in cgPool.Best Practices for WebLogic® Integration Application Life Cycle"
    The problem is I can't find a cgPool in WLI 10.2 but it can be found in WLI 8.1. There's only cgDatasource and how can i know which pool it's in.
    However, my point is to test and preparing Application Recovery scenario but I think the information is too less and not enough. Could anyone help or advice me?
    Thank for advance.

    Hi,
    In WLI 8.1x the Concept of creating the DataSource was different...First we used to create the Connection Pool (Suppose: cgPool), then We Used to create the DataSource (Suppose: cgDataSource), While Creating the DataSource we used to add the Connection Pool to the DataSource.
    But from WLI9.x onwards, the dataSource Creation concept is changed...Now we Need not to Separately create the ConnectionPool, We Can directly Create a DataSource ... ConnectionPool will internally configured...
    Could you please explain a Bit about "Which kind of Application Recovery" you are talking about...?
    One Way is to Achieve Application Failover& recovery Using WebLogic clustering ...
    Thanks
    Jay SenSharma
    http://jaysensharma.wordpress.com (WebLogic At A Glance)

  • BEA-160197: Simple ADF application fails to deploy on integrated weblogic

    JDeveloper 11.1.1.6.0
    Simple JSF ADF application fails to test localy on integrated weblogic. I have never seen this and have no clue where to look for the problem. Anyone?
    [01:11:01 PM] Deploying Application...
    <23.05.2012. 13.11.01 CEST> <Error> <J2EE> <BEA-160197> <Unable to load descriptor C:\Documents and Settings\drtodor\Application Data\JDeveloper\system11.1.1.6.38.61.92\o.j2ee\drs\TrackingSystem11g/META-INF/weblogic-application.xml of module TrackingSystem11g. The error is weblogic.descriptor.DescriptorException: Unmarshaller failed
         at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:161)
         at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:323)
         at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
         at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)
         at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
         at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)
         at weblogic.application.ApplicationDescriptor.getWeblogicApplicationDescriptor(ApplicationDescriptor.java:324)
         at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:181)
         at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
         at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
         at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
         at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:89)
         at weblogic.management.deploy.internal.MBeanConverter.createApplicationForAppDeployment(MBeanConverter.java:67)
         at weblogic.management.deploy.internal.MBeanConverter.setupNew81MBean(MBeanConverter.java:315)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.compatibilityProcessor(ActivateOperation.java:81)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.setupPrepare(AbstractOperation.java:295)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:97)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
         at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused by: com.bea.xml.XmlException: weblogic.descriptor.BeanAlreadyExistsException: Bean already exists: "weblogic.j2ee.descriptor.wl.LibraryRefBeanImpl@86e4fd19(/LibraryRefs[[CompoundKey: adf.oracle.domain]])"
         at com.bea.staxb.runtime.internal.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:54)
         at com.bea.staxb.runtime.internal.RuntimeBindingType$BeanRuntimeProperty.setValue(RuntimeBindingType.java:539)
         at com.bea.staxb.runtime.internal.AttributeRuntimeBindingType$QNameRuntimeProperty.fillCollection(AttributeRuntimeBindingType.java:381)
         at com.bea.staxb.runtime.internal.MultiIntermediary.getFinalValue(MultiIntermediary.java:52)
         at com.bea.staxb.runtime.internal.AttributeRuntimeBindingType.getFinalObjectFromIntermediary(AttributeRuntimeBindingType.java:140)
         at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalBindingType(UnmarshalResult.java:200)
         at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:169)
         at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
         at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:150)
         ... 27 more
    Caused by: weblogic.descriptor.BeanAlreadyExistsException: Bean already exists: "weblogic.j2ee.descriptor.wl.LibraryRefBeanImpl@86e4fd19(/LibraryRefs[[CompoundKey: adf.oracle.domain]])"
         at weblogic.descriptor.internal.ReferenceManager.registerBean(ReferenceManager.java:231)
         at weblogic.j2ee.descriptor.wl.WeblogicApplicationBeanImpl.setLibraryRefs(WeblogicApplicationBeanImpl.java:1440)
         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 com.bea.staxb.runtime.internal.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:48)
         ... 35 more
    .>
    <23.05.2012. 13.11.01 CEST> <Error> <Deployer> <BEA-149605> <Failed to create App/Comp mbeans for AppDeploymentMBean TrackingSystem11g#V2.0. Error - weblogic.management.DeploymentException: Unmarshaller failed.
    weblogic.management.DeploymentException: Unmarshaller failed
         at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:193)
         at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
         at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
         at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
         at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:89)
         Truncated. see log file for complete stacktrace
    Caused By: weblogic.descriptor.BeanAlreadyExistsException: Bean already exists: "weblogic.j2ee.descriptor.wl.LibraryRefBeanImpl@86e4fd19(/LibraryRefs[[CompoundKey: adf.oracle.domain]])"
         at weblogic.descriptor.internal.ReferenceManager.registerBean(ReferenceManager.java:231)
         at weblogic.j2ee.descriptor.wl.WeblogicApplicationBeanImpl.setLibraryRefs(WeblogicApplicationBeanImpl.java:1440)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         Truncated. see log file for complete stacktrace
    >
    <23.05.2012. 13.11.01 CEST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1337771461093' for task '1'. Error is: 'weblogic.management.DeploymentException: Unmarshaller failed'
    weblogic.management.DeploymentException: Unmarshaller failed
         at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:193)
         at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
         at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
         at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
         at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:89)
         Truncated. see log file for complete stacktrace
    Caused By: weblogic.descriptor.BeanAlreadyExistsException: Bean already exists: "weblogic.j2ee.descriptor.wl.LibraryRefBeanImpl@86e4fd19(/LibraryRefs[[CompoundKey: adf.oracle.domain]])"
         at weblogic.descriptor.internal.ReferenceManager.registerBean(ReferenceManager.java:231)
         at weblogic.j2ee.descriptor.wl.WeblogicApplicationBeanImpl.setLibraryRefs(WeblogicApplicationBeanImpl.java:1440)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         Truncated. see log file for complete stacktrace
    >
    <23.05.2012. 13.11.01 CEST> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'TrackingSystem11g [Version=V2.0]'.>
    <23.05.2012. 13.11.01 CEST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
    weblogic.management.DeploymentException: Unmarshaller failed
         at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:193)
         at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
         at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
         at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
         at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:89)
         Truncated. see log file for complete stacktrace
    Caused By: weblogic.descriptor.BeanAlreadyExistsException: Bean already exists: "weblogic.j2ee.descriptor.wl.LibraryRefBeanImpl@86e4fd19(/LibraryRefs[[CompoundKey: adf.oracle.domain]])"
         at weblogic.descriptor.internal.ReferenceManager.registerBean(ReferenceManager.java:231)
         at weblogic.j2ee.descriptor.wl.WeblogicApplicationBeanImpl.setLibraryRefs(WeblogicApplicationBeanImpl.java:1440)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         Truncated. see log file for complete stacktrace
    >
    [01:11:01 PM] #### Deployment incomplete. ####
    [01:11:01 PM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)
    #### Cannot run application TrackingSystem11g due to error deploying to IntegratedWebLogicServer.
    [Application TrackingSystem11g stopped and undeployed from Server Instance IntegratedWebLogicServer]

    OK I found it and opened it. This is the content before I started the application:
    <?xml version = '1.0' encoding = 'windows-1250'?>
    <weblogic-application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                          xsi:schemaLocation="http://xmlns.oracle.com/weblogic/weblogic-application http://xmlns.oracle.com/weblogic/weblogic-application/1.1/weblogic-application.xsd"
                          xmlns="http://xmlns.oracle.com/weblogic/weblogic-application">
      <listener>
        <listener-class>oracle.adf.share.weblogic.listeners.ADFApplicationLifecycleListener</listener-class>
      </listener>
      <listener>
        <listener-class>oracle.mds.lcm.weblogic.WLLifecycleListener</listener-class>
      </listener>
      <library-ref>
        <library-name>adf.oracle.domain</library-name>
      </library-ref>
    </weblogic-application>I kept it open and ran the app. It got edited in front my eyes just like this:
    <?xml version = '1.0' encoding = 'windows-1250'?>
    <weblogic-application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                          xsi:schemaLocation="http://xmlns.oracle.com/weblogic/weblogic-application http://xmlns.oracle.com/weblogic/weblogic-application/1.1/weblogic-application.xsd"
                          xmlns="http://xmlns.oracle.com/weblogic/weblogic-application">
      <listener>
        <listener-class>oracle.adf.share.weblogic.listeners.ADFApplicationLifecycleListener</listener-class>
      </listener>
      <listener>
        <listener-class>oracle.mds.lcm.weblogic.WLLifecycleListener</listener-class>
      </listener>
      <listener>
        <listener-class>
          oracle.adf.share.weblogic.listeners.ADFApplicationLifecycleListener
        </listener-class>
      </listener>
      <listener>
        <listener-class>
          oracle.mds.lcm.weblogic.WLLifecycleListener
        </listener-class>
      </listener>
      <library-ref>
        <library-name>adf.oracle.domain</library-name>
      </library-ref>
      <library-ref>
        <library-name>
          adf.oracle.domain
        </library-name>
      </library-ref>
    </weblogic-application>

  • Packaging and Deploying the ADF Application From JDeveloper to weblogic

    Hi,
    I Have Created ADF Project in JDeveloper.
    I had created the EAR file from JDeveloper (from deployment tab) to deploy my project on weblogic server (Other Than Integrated Weblogic Server).
    i have already installed ApplicationDevelopment Runtime (ADR) on weblogic and also extend the domain with JRF.
    but when i try to deploy it on my weblogic it gives me the following exceptions :
    An error occurred during activation of changes, please see the log for details.
    Failed to load webapp: 'My-ViewController-context-root'
    org.apache.myfaces.trinidad.webapp.UIXComponentELTag
    Can anybody help what i am missing ?
    Please Help...

    Hi,
    i have installed the ADF Runtime 11.1.1.5.0_disk1_1of1.
    but when i try to deploy the ADF application it gives me some tags missing exception
    the exception gone when i insert the following jar files :
    trinidad-api-1.2.11.jar
    trinidad-impl-1.2.11.jar
    and application is get deployed successfully.
    but when i try to run the application it gives me following exception
    java.lang.ClassCastException: org.apache.myfaces.trinidadinternal.config.xmlHttp.XmlHttpConfigurator cannot be cast to org.apache.myfaces.trinidad.config.Configurator
         at org.apache.myfaces.trinidadinternal.config.GlobalConfiguratorImpl.init(GlobalConfiguratorImpl.java:366)
         at org.apache.myfaces.trinidadinternal.config.GlobalConfiguratorImpl.beginRequest(GlobalConfiguratorImpl.java:199)
         at org.apache.myfaces.trinidadinternal.config.GlobalConfiguratorImpl.getExternalContext(GlobalConfiguratorImpl.java:304)
         at org.apache.myfaces.trinidadinternal.context.FacesContextFactoryImpl$CacheRenderKit.(FacesContextFactoryImpl.java:86)
         at org.apache.myfaces.trinidadinternal.context.FacesContextFactoryImpl.getFacesContext(FacesContextFactoryImpl.java:64)
         at org.apache.myfaces.trinidadinternal.context.FacesContextFactoryImpl.getFacesContext(FacesContextFactoryImpl.java:64)
         at javax.faces.webapp.FacesServlet.service(FacesServlet.java:260)
         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:300)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:205)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
         at java.security.AccessController.doPrivileged(Native Method)
         at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
         at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
         at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
         at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161)
         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:136)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
         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:2277)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    what went wrong...
    i am stuck up here...
    please help.

  • Problem while deploying the ADF application in weblogic 10.3

    Hi,
    We did the application using ADF and EJB3.0 in JDeveloper11g relese and this application is working fine when i run in the JDeveloper release. When i try to deploy the same application in weblogic 10.3(Which I downloded and installed) i am getting following error.
    shared library "adf.oracle.domain" could not be found.
    Can any one tell me, what the problem is?
    Thanking you,
    NIRANJAN REDDY.

    person with many names,
    You need to configure the WLS domain for ADF.
    http://download.oracle.com/docs/cd/E12839_01/install.1111/e13666/toc.htm#wls_adf
    John

  • Steps to deploy an ejb application and running an ejb client in weblogic server6.1

    steps to deploy an ejb application and steps to run an ejb client in weblogic server6.1
    if the client is an simple java application and if the client is a servlet

    Hi.
    Check out the beanManaged example that ships with WLS and read the accompanying docs. This
    is a simple EJB with a servlet that invokes it.
    Michael
    shekhar sachdev wrote:
    steps to deploy an ejb application and steps to run an ejb client in weblogic server6.1
    if the client is an simple java application and if the client is a servlet--
    Michael Young
    Developer Relations Engineer
    BEA Support

  • Packaging and Deploying Weblogic Application

    Hi,
    I am having trouble in deploying a Weblogic application. I made a Web
    application in Weblogic6.1 on Windows2000. The directory structure of my
    JSPs, Images and Servlets are as follows:
    JSPs - DefaultWebApp
    JavaBeans(not EJB)(these JavaBeans are used by the JSPs as well as the
    Servlet)
    - DefaultWebApp\Web-Inf\Classes\Servletspkg\Loginpkg,
    - DefaultWebApp\Web-Inf\Classes\Servletspkg\Workpkg, etc.
    HTML - DefaultWebApp
    Images - DefaultWebApp\Images
    Servlets - DefaultWebApp\Web-Inf\Classes\Servletspkg
    web.xml and weblogic.xml - DefaultWebApp\Web-Inf
    The Web application runs fine. Now I want to package the above Web
    application and deploy it under Solaris8 (Weblogic 6.1)( in another
    machine.) I am not able to do that. I would be grateful if you could let me
    know the steps involved in packaging and deploying.
    Thanks in advance.
    -Jaya

    Hi Michael,
    I deployed the webapp to the default webapp on solaris and it worked.
    Thanks!
    -Jaya
    "Michael Young" <[email protected]> wrote in message
    news:[email protected]...
    Hi.
    Hmm, hard to say.
    I notice in your deployment on Windows 2000 you deployed in the defaultwebapp,
    but on solaris you deploy in 'test' webapp. I suspect this is the root ofthe
    problem. Since you are having problems calling J2.jsp I wonder how youare
    calling it. When calling from the default webapp you don't need tospecify a
    webapp context in the url, but from test webapp you do (depending on howyou are
    calling it - full url vs relative url).
    So in summary consider 2 things:
    1. how are you calling J2.jsp that might be different than how you callthe
    servlet from J1.jsp?
    2. what happens if you deploy your webapp to the default webapp onsolaris? my
    guess is that this will work.
    Hope this helps,
    Michael
    Vikor wrote:
    Hi,
    I could finally deploy the web application on the Solaris machine. But I
    am
    not sure if I did the right thing. I followed the steps below:
    1.I created a folder "test" under "config/mydomain/applications"folder.
    2.I extracted the .war file in this folder which was successful.
    3.Then I tried to run the application with the URL
    http://localhost:7001/test
    4. I got "J1.jsp" (located in "test" folder) as I excpected. This pagecalls
    a servlet "ControllerServlet" located in folder
    "test/WEB-INF/classes/servletspkg"
    5. The servlet in turn calls another jsp page J2.jsp located in "test"
    folder. This call is failing. I am getting 404 file not found error.
    Please suggest what I should do.
    Thanks in advance,
    Best regards,
    Jaya
    "Michael Young" <[email protected]> wrote in message
    news:[email protected]...
    Hi.
    I need more detail here. When you say you can't deploy to solaris,
    what
    does
    that mean? Do you get any errors/exceptions while deploying? If soplease
    post the errors here. Or does it deploy ok but you can't access it?
    Michael
    Vikor wrote:
    Hi,
    I am having trouble in deploying a Weblogic application. I made a
    Web
    application in Weblogic6.1 on Windows2000. The directory structureof my
    JSPs, Images and Servlets are as follows:
    JSPs - DefaultWebApp
    JavaBeans(not EJB)(these JavaBeans are used by the JSPs as well asthe
    Servlet)
    - DefaultWebApp\Web-Inf\Classes\Servletspkg\Loginpkg,
    - DefaultWebApp\Web-Inf\Classes\Servletspkg\Workpkg,etc.
    >>>>
    HTML - DefaultWebApp
    Images - DefaultWebApp\Images
    Servlets - DefaultWebApp\Web-Inf\Classes\Servletspkg
    web.xml and weblogic.xml - DefaultWebApp\Web-Inf
    The Web application runs fine. Now I want to package the above Web
    application and deploy it under Solaris8 (Weblogic 6.1)( in another
    machine.) I am not able to do that. I would be grateful if you couldlet
    me
    know the steps involved in packaging and deploying.
    Thanks in advance.
    -Jaya--
    Michael Young
    Developer Relations Engineer
    BEA Support
    Michael Young
    Developer Relations Engineer
    BEA Support

  • How to deploy a struts application on weblogic

    I tried to deploy the struts application on weblogic. It is not able to recognize the taglib files for jsp. I have included the .tld files.

    Hi,
    I have installed WebLogic 8.1.
    And Created a Basic WebLogic Server Domain.
    Started the server. Server is running.
    When I try http://localhost:7001.
    It is giving error as follows...
    Error 404--Not Found
    From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
    10.4.5 404 Not Found
    The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
    If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
    Can anybody assist me pls.
    Regards
    Siva

  • How to deploy DAC enterprise application on WebLogic Server

    hi,
    i have installed DAC server on Linux machine and DAC client on windows machine. I can able to log in to DAC by stand alone mode and
    Currently we are unable to login to the DAC 11g client by FMW(Web mode)
    To login into DAC client by FMW mode we need to deploy DAC enterprise application on WebLogic Server, could anybody help how to deploy DAC enterprise application on weblogic server ?
    Thanks in advance..
    Vinoth

    follow this doc http://docs.oracle.com/cd/E35287_01/fusionapps.7964/e14849.pdf
    mark if it helps

  • Console error while deploying a struts application..

    I am getting following exception while deploying a struts application:-
    javax.servlet.ServletException: org/apache/commons/logging/LogFactory
         at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:884)
         at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:848)
         at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:787)
         at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:3252)
         at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:3197)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:3174)
         at weblogic.servlet.internal.WebAppServletContext.setStarted(WebAppServletContext.java:5647)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:869)
         at weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer.java:2022)
         at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2063)
         at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2592)
         at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2515)
         at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2317)
         at weblogic.management.deploy.slave.SlaveDeployer$Task.checkAutoCommit(SlaveDeployer.java:2399)
         at weblogic.management.deploy.slave.SlaveDeployer$Task.prepare(SlaveDeployer.java:2311)
         at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2479)
         at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:798)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:507)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:465)
         at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    please help me out.

    The ServletException is just a wrapper exception which informs about an underlying failure. When interpreting stacktraces,the bottommost root cause parts is the most important part. I assume that it's just a java.lang.ClassNotFoundException on org/apache/commons/logging/LogFactory. In that case, the exception is self-explaining enough. The mentioned class is missing in the classpath. The solution is also obvious: add the mentioned class (or at least, the JAR file with the mentioned class) to the classpath and you're fine. As the package name already hints, you can download it at [http://commons.apache.org/logging].
    For future java.lang.* exceptions please consult 'New to Java' forum. This is unrelated to Java Servlet.

  • Upgrading a project from Weblogic Integration 8.1.3 to Weblogic Integration

    Can anyone offer any advice to assist me in upgrading a project from Weblogic Integration 8.1.3 to Weblogic Integration 9.2.1?
    Here are some nuances of the project:
    * The JNDI, JDBC, & JMS server resources are secured; access is controlled by Deployment Descriptor run-as/security-role/... tags and custom CSPs
    * The application is currently build for deployment using wlwBuild ant task (class in workshop.core.WlwBuildTask which is located in the 8.1.3 {weblogic.home}/workshop/wlw-ide.jar - so far I can't find this class/task in my 9.2.1 install)
    * The following are the application characteristics (and utilized WLI features): multiple web apps, EJBs, JMS, Page flow/netUI, web services, WLI controls (process, java, transformation), XMLBeans
    * One of the project goals is to not make any functional changes and modify as little code as necessary (the only expected justification for a modification is a) fallout out from the JVM 1.5 upgrade or b) something is no longer available in WLI 9.2)
    I know there is a edocs page with a tutorial for upgrading from 8.1.4 or 8.1.5 to 9.2, but I am interested in knowing if anyone has insight on upgrading directly from 8.1.3?
    Thanks in advance for any and all assistance.
    Regards,
    Andy Frank

    just as a followup to my original message.. regarding the 8.1.4 install log that had all the warnings with the msi it expected and the different one it found... at the bottom of the log..this is what I got;
    Property(S): SourcedirProduct = {AC76BA86-7AD7-1033-7B44-A81300000003}
    MSI (s) (6C:30) [11:11:23:828]: Product: Adobe Reader 8.1.4 - Update 'KB408682' installed successfully.
    MSI (s) (6C:30) [11:11:23:828]: Product: Adobe Reader 8.1.4 -- Installation operation completed successfully.
    when i go into adobe reader -> help -> about i stillget 8.1.3

  • Connection error in J dev 11g when deploying weblogic.

    We developer an ADF JSF 11g application. Deploy weblogic is OK
    for application module We use JDBC URL type connection.
    Our DB name is TESTDB. And url is jdbc:oracle:thin:@10.0.X.XXX:1521:TESTDB.
    We have configured web logic with the same connection information.
    conn is OK. Conn name is TESTDB. jndi name is TESTDB also.
    But when we run applicaion following error occurs.
    Messages for this page are listed below.
    Connection name vnot defined
    Unexpected exception caught: java.lang.NullPointerException, msg=null
    Unexpected exception caught: java.lang.NullPointerException, msg=null
    There seem a confilict with connection name ?
    How can we solve this problem.
    Thanks.

    yes we set the connection to JDBC data source in our application
    and then we have created jdbc data source in web logic server and we have written same jdbc data source name to jndi name
    but we get error "JNDI failure. Unable to lookup Data Source at context java:comp/env/jdbc/testdbDS"

  • Weblogic Integration failed to build Cluster ENV

    Dear buddies,
    I have used WL for months, WLS works pretty good with cluster support. but I failed to create WLI cluster.could you guys give me a hand and tell me how to create an WLI cluster?Thanks a lot!!!
    Here is the process how I created WLI cluster:
    ENV:RedHat9+ WL8.1_SP4
    Machine: 172.16.4.238(adminServer), 172.16.4.237/236(236/237 are in the same physical machine, one Network interface card listen to two ip address)
    BEA_HOME=/opt/bea/
    1.executed /opt/bea/weblogic81/common/bin/config.sh on 172.16.4.238 and create an admin server(cgServer,172.16.4.238:7001) and a cluster(TestCluster) inclued two managedServers(mServer1/172.16.4.236:7001,mServer2/172.16.4.237:7001)
    and I didn't create extra JDBC POOL except the standard one.
    2. I exectued same command on 172.16.4.236,create an admin Server(mServer1) and a cluster(TestCluster)with mServer2 included. and the other settings are just same as step1.
    Now I am having following problem.
    1.admin Server(cgServer) can startup without any problem
    2.mServers (mServer1 and mServer2)can't start up(detail output pasted later) it seems pointbase didn't start up correctly on port 9093
    3.so I start up point base on mServers machine with command "/opt/bea/weblogic81/common/eval/pointbase/tools/startPointBase.sh"
    but seems the pointbase only listen 9092!!
    4.I can't even startup adminserver and pointbase DB with Jrockit, but Sun's JVM seems works.
    below are detailed output when I startManagedServers:
    command:
    [root@localhost integration]# ./startManagedWebLogic.sh mServer1 http://172.16.4.238:7001
    ####<Dec 27, 2005 2:12:05 PM EST> <Notice> <Log Management> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-170019> <The server log file /opt/bea/user_projects/domains/integration/mServer1/mServer1.log is opened. All server side log events will be written to this file.>
    ####<Dec 27, 2005 2:12:05 PM EST> <Info> <Socket> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000415> <System has file descriptor limits of - soft: 1,024, hard: 1,024>
    ####<Dec 27, 2005 2:12:05 PM EST> <Info> <Socket> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000416> <Using effective file descriptor limit of: 1,024 open sockets/files.>
    ####<Dec 27, 2005 2:12:05 PM EST> <Info> <Socket> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000406> <PosixSocketMuxer was built on May 22 2003 15:43:24>
    ####<Dec 27, 2005 2:12:06 PM EST> <Info> <Socket> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000436> <Allocating 3 reader threads.>
    ####<Dec 27, 2005 2:12:06 PM EST> <Info> <Socket> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000440> <NativeIO Enabled>
    ####<Dec 27, 2005 2:12:14 PM EST> <Info> <Security> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-090093> <No pre-WLS 8.1 Keystore providers are configured for server mServer1 for security realm myrealm.>
    ####<Dec 27, 2005 2:12:14 PM EST> <Notice> <Security> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-090082> <Security initializing using security realm myrealm.>
    ####<Dec 27, 2005 2:12:14 PM EST> <Notice> <WebLogicServer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000328> <Starting WebLogic Managed Server "mServer1" for domain "integration">
    ####<Dec 27, 2005 2:12:14 PM EST> <Info> <WebLogicServer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000214> <WebLogic Server "mServer1" version:
    WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
    WebLogic XMLX Module 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
    WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
    WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
    WebLogic Integration 8.1 SP4 Tue Nov 30 10:34:16 PST 2004 471877 (c) 1995, 1996, 1997, 1998 WebLogic, Inc.
    (c) 1999, 2000, 2001 BEA Systems, Inc.>
    ####<Dec 27, 2005 2:12:14 PM EST> <Info> <WebLogicServer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000215> <Loaded License : /opt/bea/license.bea>
    ####<Dec 27, 2005 2:12:14 PM EST> <Info> <RJVM> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000570> <Network Configuration for Channel "mServer1"
    Listen Address          172.16.4.236:7001
    Public Address          N/A
    Http Enabled          true
    Tunneling Enabled     false
    Outbound Enabled     false
    Admin Traffic Enabled     true>
    ####<Dec 27, 2005 2:12:14 PM EST> <Debug> <RJVM> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000571> <Network Configuration Detail for Channel "mServer1"
    Channel Weight          50
    Accept Backlog          50
    Login Timeout          5000ms
    Max Message Size     10000000
    Message Timeout     60s
    Idle Timeout          65s
    Tunneling Timeout     40s
    Tunneling Ping          45s>
    ####<Dec 27, 2005 2:12:17 PM EST> <Info> <XML> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-130036> <Initializing XMLRegistry.>
    ####<Dec 27, 2005 2:12:17 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001135> <Initializing the JDBC service.>
    ####<Dec 27, 2005 2:12:18 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001137> <Initialization complete.>
    ####<Dec 27, 2005 2:12:18 PM EST> <Info> <Connector> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-190000> <Initializing J2EE Connector Service>
    ####<Dec 27, 2005 2:12:18 PM EST> <Info> <Connector> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-190001> <J2EE Connector Service initialized successfully>
    ####<Dec 27, 2005 2:12:18 PM EST> <Info> <IIOP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-002014> <IIOP subsystem enabled.>
    ####<Dec 27, 2005 2:12:19 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040090> <Deployed 5 default connection factories.>
    ####<Dec 27, 2005 2:12:19 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040305> <JMS service is initialized and in standby mode.>
    ####<Dec 27, 2005 2:12:19 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101128> <Initializing HTTP services.>
    ####<Dec 27, 2005 2:12:19 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101133> <Initializing Web server mServer1.>
    ####<Dec 27, 2005 2:12:19 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101052> <[HTTP mServer1] Initialized>
    ####<Dec 27, 2005 2:12:19 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101135> <mServer1 is the default Web server.>
    ####<Dec 27, 2005 2:12:21 PM EST> <Info> <J2EE> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-160037> <J2EE service initializing.>
    ####<Dec 27, 2005 2:12:21 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149207> <Initializing.>
    ####<Dec 27, 2005 2:12:23 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149059> <Module uddi of application uddi is transitioning from unprepared to prepared on server mServer1.>
    ####<Dec 27, 2005 2:12:24 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149060> <Module uddi of application uddi successfully transitioned from unprepared to prepared on server mServer1.>
    ####<Dec 27, 2005 2:12:24 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149059> <Module uddiexplorer of application uddiexplorer is transitioning from unprepared to prepared on server mServer1.>
    ####<Dec 27, 2005 2:12:24 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149060> <Module uddiexplorer of application uddiexplorer successfully transitioned from unprepared to prepared on server mServer1.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149059> <Module wl_management_internal1 of application wl_management_internal1 is transitioning from unprepared to prepared on server mServer1.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149060> <Module wl_management_internal1 of application wl_management_internal1 successfully transitioned from unprepared to prepared on server mServer1.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149059> <Module uddi of application uddi is transitioning from prepared to active on server mServer1.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149060> <Module uddi of application uddi successfully transitioned from prepared to active on server mServer1.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<anonymous>> <> <BEA-101047> <[ServletContext(id=20975280,name=uddi,context-path=/uddi)] WebServiceServlet: init>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149059> <Module uddiexplorer of application uddiexplorer is transitioning from prepared to active on server mServer1.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149060> <Module uddiexplorer of application uddiexplorer successfully transitioned from prepared to active on server mServer1.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<anonymous>> <> <BEA-101047> <[ServletContext(id=23108345,name=uddiexplorer,context-path=/uddiexplorer)] WebServiceServlet: init>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149059> <Module wl_management_internal1 of application wl_management_internal1 is transitioning from prepared to active on server mServer1.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149060> <Module wl_management_internal1 of application wl_management_internal1 successfully transitioned from prepared to active on server mServer1.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<anonymous>> <> <BEA-101047> <[ServletContext(id=13608238,name=wl_management_internal1,context-path=/wl_management_internal1)] WebServiceServlet: init>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149208> <Initialization Complete.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Notice> <Cluster> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000138> <Listening for announcements from cluster TestCluster on 237.0.0.1:7001.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Notice> <Cluster> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000133> <Waiting to synchronize with other running members of TestCluster.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JTA> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-110441> <Opening transaction log with driver version "j1.0" and synchronous write policy "Cache-Flush". For information on synchronous write policies, refer to the weblogic.management.configuration.ServerMBean javadoc or console online help.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001138> <Resuming the JDBC service.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001140> <Resume complete.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040108> <User connection factory "DefaultXAConnectionFactory" is started.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040108> <User connection factory "QueueConnectionFactory" is started.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040108> <User connection factory "MessageDrivenBeanConnectionFactory" is started.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040108> <User connection factory "DefaultConnectionFactory" is started.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040108> <User connection factory "TopicConnectionFactory" is started.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040306> <JMS service is active now.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101129> <Initializing the Web application container.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101238> <HTTP log rotation is size based for the Web server: mServer1.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101051> <[HTTP mServer1] started>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <WebService> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-220031> <The server does not support reliable SOAP messaging.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <WebService> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-220027> <Web Service reliable agents are started on the server.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149209> <Resuming.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001177> <Creating Connection Pool named bpmArchPool, URL = jdbc:pointbase:server://localhost:9093/workshop, Properties = {user=weblogic}.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <Common> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000625> <The application has disabled periodic testing of free resources in pool "bpmArchPool".>
    ####<Dec 27, 2005 2:12:57 PM EST> <Warning> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001129> <Received exception while creating connection for pool "bpmArchPool": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>
    ####<Dec 27, 2005 2:12:57 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001156> <Stack trace associated with message 001129 follows:
    java.sql.SQLException: SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.
         at com.pointbase.dbexcp.dbexcpException.getSQLException(Unknown Source)
         at com.pointbase.net.netJDBCConnection.<init>(Unknown Source)
         at com.pointbase.net.netJDBCDriver.getConnection(Unknown Source)
         at com.pointbase.net.netJDBCDriver.connect(Unknown Source)
         at com.pointbase.jdbc.jdbcUniversalDriver.getConnection(Unknown Source)
         at com.pointbase.jdbc.jdbcUniversalDriver.connect(Unknown Source)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:189)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:124)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1145)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1079)
         at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:171)
         at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1018)
         at weblogic.jdbc.common.internal.ConnectionPool.start(ConnectionPool.java:142)
         at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:306)
         at weblogic.jdbc.common.internal.JDBCService.addDeployment(JDBCService.java:180)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
         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:324)
         at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:754)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:733)
         at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:509)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1560)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1528)
         at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:988)
         at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:946)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:954)
         at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
         at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7691)
         at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1304)
         at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:347)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
         at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
         at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
         at weblogic.Server.main(Server.java:32)
    >
    ####<Dec 27, 2005 2:12:58 PM EST> <Warning> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001129> <Received exception while creating connection for pool "bpmArchPool": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>
    ####<Dec 27, 2005 2:12:58 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001156> <Stack trace associated with message 001129 follows:
    java.sql.SQLException: SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.
         at com.pointbase.dbexcp.dbexcpException.getSQLException(Unknown Source)
         at com.pointbase.net.netJDBCConnection.<init>(Unknown Source)
         at com.pointbase.net.netJDBCDriver.getConnection(Unknown Source)
         at com.pointbase.net.netJDBCDriver.connect(Unknown Source)
         at com.pointbase.jdbc.jdbcUniversalDriver.getConnection(Unknown Source)
         at com.pointbase.jdbc.jdbcUniversalDriver.connect(Unknown Source)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:189)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:124)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1145)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1079)
         at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:171)
         at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1018)
         at weblogic.jdbc.common.internal.ConnectionPool.start(ConnectionPool.java:142)
         at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:306)
         at weblogic.jdbc.common.internal.JDBCService.addDeployment(JDBCService.java:180)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
         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:324)
         at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:754)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:733)
         at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:509)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1560)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1528)
         at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:988)
         at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:946)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:954)
         at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
         at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7691)
         at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1304)
         at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:347)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
         at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
         at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
         at weblogic.Server.main(Server.java:32)
    >
    ####<Dec 27, 2005 2:12:59 PM EST> <Warning> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001129> <Received exception while creating connection for pool "bpmArchPool": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>
    ####<Dec 27, 2005 2:12:59 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001156> <Stack trace associated with message 001129 follows:
    java.sql.SQLException: SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.
         at com.pointbase.dbexcp.dbexcpException.getSQLException(Unknown Source)
         at com.pointbase.net.netJDBCConnection.<init>(Unknown Source)
         at com.pointbase.net.netJDBCDriver.getConnection(Unknown Source)
         at com.pointbase.net.netJDBCDriver.connect(Unknown Source)
         at com.pointbase.jdbc.jdbcUniversalDriver.getConnection(Unknown Source)
         at com.pointbase.jdbc.jdbcUniversalDriver.connect(Unknown Source)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:189)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:124)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1145)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1079)
         at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:171)
         at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1018)
         at weblogic.jdbc.common.internal.ConnectionPool.start(ConnectionPool.java:142)
         at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:306)
         at weblogic.jdbc.common.internal.JDBCService.addDeployment(JDBCService.java:180)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
         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:324)
         at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:754)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:733)
         at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:509)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1560)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1528)
         at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:988)
         at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:946)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:954)
         at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
         at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7691)
         at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1304)
         at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:347)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
         at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
         at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
         at weblogic.Server.main(Server.java:32)
    >
    ####<Dec 27, 2005 2:13:00 PM EST> <Warning> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001129> <Received exception while creating connection for pool "bpmArchPool": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>
    ####<Dec 27, 2005 2:13:00 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001156> <Stack trace associated with message 001129 follows:
    java.sql.SQLException: SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.
         at com.pointbase.dbexcp.dbexcpException.getSQLException(Unknown Source)
         at com.pointbase.net.netJDBCConnection.<init>(Unknown Source)
         at com.pointbase.net.netJDBCDriver.getConnection(Unknown Source)
         at com.pointbase.net.netJDBCDriver.connect(Unknown Source)
         at com.pointbase.jdbc.jdbcUniversalDriver.getConnection(Unknown Source)
         at com.pointbase.jdbc.jdbcUniversalDriver.connect(Unknown Source)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:189)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:124)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1145)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1079)
         at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:171)
         at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1018)
         at weblogic.jdbc.common.internal.ConnectionPool.start(ConnectionPool.java:142)
         at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:306)
         at weblogic.jdbc.common.internal.JDBCService.addDeployment(JDBCService.java:180)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
         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:324)
         at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:754)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:733)
         at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:509)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1560)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1528)
         at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:988)
         at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:946)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:954)
         at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
         at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7691)
         at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1304)
         at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:347)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
         at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)

    Since a couple of days we see the same in our project. Same release. It started when we added versioning to our ~140 processes. A hint would be great. We too didn't find anything helpful on the web.

  • Weblogic Integration WLI adapters for Siebel

    To integrate with Siebel and Oracle EBS, earlier version of WLI (8.2 & 9) had adapters available with it, but the latest version of WLI 10.2 does not have the adapters.
    Can we know what should be the recommended and supported mechanism of integration with Siebel and Oracle EBS for synchronous request response scenarios?

    Krish,
    You can build a JMS/TIBCO adapter and deploy it on any J2EE CA compliant container.
    Pros:
    Your adapter can be deployed on any compliant application server (including WLS).
    Cons:
    The J2EE CA 1.0 specification is very limited when it comes to EAI. It does not
    address bi-directional communication (EIS events), asynchronous service invocation
    and implementing javax.resource.cci interfaces is not mandatory (these are what come
    to mind first, there are others). So, if you don't use WLI, you can't take
    advantage of our value added features. TIBCO may have extended JCA as well, I don't
    know.
    Summary:
    If your adapter just sticks to what is specified in the JCA spec, you have total
    autonomy, however, you have limited EAI capabilities. If you use the proprietary
    extensions provided by a particular vendor (BEA WLI, TIBCO, etc...) then you are
    tied the their environment. Until the J2EE Connector Architecture addresses these
    EAI issues, you will run into proprietary EAI solutions.
    Cheers,
    Chris
    Krish Khambadkone wrote:
    Can one implement an EAI solution with only the weblogic server. There is a need
    to interface with TIBCO. Is it mandatory that one use Weblogic Integration for
    integration or can we build a JMS/TIBCO adapter and deploy it on just weblogic.
    What are the Pros and Cons.
    --Krish.

Maybe you are looking for