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

Similar Messages

  • 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

  • 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 WebLogic vs OAS/OC4J: application redeployment

    Hi gang
    I'm currently researching solutions to JEE application redeployment, or more specifically when you want to update an existing deployed application on a JEE app server, how can you do so with minimal interruption to the users?
    From my research on the internet I've found two approaches, one with the Oracle OAS camp, and another in the BEA Weblogic camp.
    Deepek Arora in this Redeploy Web App to Application Server points to an Oracle whitepaper that states the OAS approach is to use clusters. However this article is somewhat old so may not be the most recent recommended approach.
    I note that in the BEA documentation for the WebLogic Server here, the documentation details a feature called Production Redeployment (documented here). This feature allows both versions of the application to be deployed, and gracefully moves new user connections to the new application version, while maintaining existing user connections on the old version, eventually shutting down the older application version once the users have disconnected.
    What I'd like to know and I hope you can help me with is:
    a) Is clusters still the recommended OAS approach to this problem?
    b) Does OAS support the similar WebLogic facilities, or are there plans in the future (maybe 11g?) to include this feature?
    Very much thanks for your assistance in advance. This question has been bugging me for awhile, so it'd be great to hear your thoughts and recommendations. Alternatively any pointers to any Oracle documentation, whitepapers etc would be appreciated as there is a lot to digest.
    Thanks & regards,
    Chris Muir.

    Hey Chris --
    OC4J doesn't implement the same side-by-side versioning approach that WLS does -- it's a nice facility from what I have seen of it. We should buy them if we ever get the chance .. :-) Their staged/admin-only deployment model is also very useful for deploy/test/publish scenarios.
    In OracleAS 10.1.3.1+ we have the ability to execute a redeployment operation to a "group" of OC4J instances in a serial form.
    When a sequential redeployment operation is executed, the cluster deployment handler:
    1. Picks the first OC4J instance in the group.
    1.1 The container STOPS the application
    1.1.1 Signals to mod_oc4j to take it out of the route table so it doesn't get any new requests -- this happens dynamically with no restart required with OHS/mod_oc4j 10.1.3.
    1.1.2 Allows all current inflight requests to finish, flushes any session state updates
    1.2 The current version of the application is then undeployed
    1.3 The new version of the application is deployed
    1.4 The application is started
    1.4.1 Signals to mod_oc4j that is available for service, dynamically added back into the routing mix.
    1.5 Starts receiving and servicing requests
    2. Group deployment mechanism waits for the specified timeout period.
    3. Repeats the process for the remaining OC4J instances.
    4. Finishes.
    Since we have session affinity with OHS/mod_oc4j routing, any existing client requests will continue to go to their current instance unless it is stopped. So for customers on V1 of an application, they'll stay on it until it is upgraded. Any requests that get serviced by V2 of an application will continue to be serviced by that server/application, unless it is taken down for some reason.
    For those applications that are maintaining client "state" within the server, if the application has configured state-replication, then any session state will be maintained on other nodes as the redeployment of a specific node occurs.
    In earlier releases, this was documented in a far more manual fashion as something called a "cluster dance" -- where due to the automated synchronization when operating in a cluster, you needed to take instances out of one cluster into another to do the upgrade, then join them back together.
    http://www.oracle.com/technology/products/ias/hi_av/OracleApplicationServer10gR2StatefulRollingUpgrades-WP.pdf
    The sequential group deployment mechanism, IMHO offers a much simpler path to do a multiple instance redeployment while maintaining availability.
    There's a general doc about this from the same author above here:
    http://www.oracle.com/technology/products/ias/hi_av/OracleApplicationServer10gR3HA-WP.pdf
    There's a screen cam/viewlet somewhere on OTN I believe that demos this as well.
    And a fairly simple form of how-to here which walks you through an example:
    http://www.oracle.com/technology/products/ias/hi_av/Dynamic%20Routing.htm
    -steve-

  • Weblogic Application redeployment  not working

    Hi guys
    I am running on WL10.0 (WLP10.2). I was trying to implement application-redeployment. I gave version name to app, and update it. But application just keeps on waiting (deploy Running status). Where as it should come to Active state and the older version should be retired state.
    Is it working for anyone?
    Thanks

    I have seen this many times wls 9 and 10. I usually follow these steps to get it in active state.
    1. Shutdown all the JVMs.
    2. Start Admin server and undo any unactivated changes
    3. delete the cache directory on all the jvms. (check also permission for all the files)
    4. bring up the managed servers
    5. update the application again.
    It works for me most of the time. Hope this helps.
    regards,
    Harsha

  • Process instances terminate upon application redeployment

    Hello all,
    I have been trying to find an answer for this question in the forums, but to no result.
    I have created a proof-of-concept process and deployed it on the server. The process works just fine, containing Client Request controls, creating Tasks etc.
    The problem is when, during development, I make some change in some helper class or the procees itself and redeploy the application. Even when I just rebuild/redeploy w/o any changes.
    Then, any running process instances (e.g. blocked, waiting for a Client Response or a Task onComplete) are terminated w/o any message, at least not a message that I can see.
    Is this a "feature" or have I forgotten to setup something correctly?
    If this is a feature, why aren't the open Task Controls also terminated, like the process instances that created them are?
    How can I prevent the process instances from being auto-terminated upon application redeployment?
    My process' properties:
    - freeze on failure: true
    - persistent: always
    - on sync failure: rethrow
    - retry count: 1
    - retry delay: <empty>
    - stateless: false
    - binding: webservice
    - version strategy: loosely coupled
    My configuration:
    - Weblogic Integration 8.5 SP6
    - Weblogic Server 8.1 SP6
    - Back-end DB: the default DB server, that comes with the BEA installation
    I would greatly appreciate any help/suggestions/links, as I find this feature/error very frustrating.
    My apologies if this has already been answered before.
    Thank you for your time,
    S.

    OK, to answer my own question.
    It was not a "problem", but a "feature".
    I had the server starting in development mode, so by default process instances are terminated upon redeployment.
    Editing the setDomainEnv.cmd and setting
    set PRODUCTION_MODE=true
    solved my "problem".
    Hope this helps s/o in the future.

  • 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

  • Understanding Weblogic Integration 9.2

    Hi All,
    I am very new to Weblogic Integration and we were asked to make our application use WLI. Our application has many source feeds and we also interface with SAP with Web Services calls. I am totally new to Weblogic Integration and I would appreciate if anyone can point me to the starting point. I want to learn how WLI works and how to write controls etc.
    I downloaded Weblogic platform and tried to follow through the tutorial that Bea provides, but could not find any help. Tried to search for books online but could not find any. Any help regarding resources i.e. books or online "free" tutorials/courses is greatly appreciated.
    Thank you,
    S

    Sarin,
    I have worked on an WLI project,where integration was with SAP.We used iWay adapter to integrate with SAP system.With respect to WLI, you need to learn JPD(Java Process Definition),Data Transformation,XQuery,Event generators,Channel file,need a very good understanding of XSD(Schema Definition).Also you need to work with WLI console(http://localhost:7001/wliconsole),where you can create your business calendars,event generators.The weblogic workshop help would be a good starting point.Again you can find lots of documents at http://www.edocs.bea.com.
    Let me know if you have any specific question.
    Regards
    Bishnu
    Edited by bishnu_kumar at 05/21/2007 1:29 AM

  • 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.

  • WebLogic Integrated Commons Logging - Necessary?

    When using Workshop 10.1 to develop applications, dynamic web projects pull in the Weblogic Integrated Commons Logging facet in the recommended set. It is possible to deselect the facet at that time. I would like to know what is the benefit of including that facet, especially when migrating existing code to Workshop 10.1 that already includes application level logging using log4j.
    1.Is it mandatory to have the Weblogic Integrated Commons Logging facet for Beehive controls or other common Weblogic facets?
    2.The Workshop UI allows me to remove the facet from the Dynamic Web project, but once it is targeted to an Enterprise Application project, I cannot remove it without editing the weblogic-application.xml by hand. What are the correct steps to remove Weblogic Integrated Commons Logging from various types of projects?
    3.If Integrated Commons Logging is left in place, and filters are used to stop application logging, what overhead does it cause? Must each message be evaluated before deciding not to process it?
    4.I found a ton of information on the site on how to configure Integrated Commons Logging, but nothing on benefits of using it or the costs of enabling it.
    Thanks
    -Russ

    After further investigation, WebLogic Integrated Commons Logging is not required for any standard Workshop 10.1 project type, but is included in the recommended facet sets for dynamic web and utility projects. It may be removed from those projects at any time.
    Also, when a project that includes WebLogic Integrated Commons Logging is targeted to an enterprise application project, WebLogic Integrated Commons Logging is automatically included in the weblogic-application.xml and it's configuraiton properties is added to APP-INF/classes. If you delete the web/utility project from the EAR, WebLogic Integrated Commons Logging is not removed from it. I suggest either
    1) Remove WebLogic Integrated Commons Logging from the web/utility project before removing the targeting to the EAR project
    or after the web/utility is no longer targeted and no other targeted project depends on it:
    1) Delete the wls-commonslogging-bridge library ref from weblogic-application.xml
    2) Delete commons-logging.properties from EarContent/APP-INF/classes
    WebLogic Integrated Commons Logging is an interesting tool with some great benifits. It's a good option if you don't already have a solid logging and notification framework integrated into your environment.
    -Russ

  • Weblogic Integration and Format Builder

    I use Format Builder to create MFL file to translate dat file to xml. How can i restrict a length to some like 6.
    I used like this.
    <FieldFormat name='PoolNumber' type='Numeric' length='6' codepage='Default'/>
    I Tested with Formatbuilder its not transforming.
    but when i send it in Weblogic workshop there is no errors.
    This is sample mfl file i have.
    <MessageFormat name='ClosedPool' version='2.01'>
    <StructFormat name='Pool' repeat='*'>
    <FieldFormat name='PoolNumber' type='Numeric' length='6' codepage='Default'/>
    <FieldFormat name='CUSIPNumber' type='String' delim='!' codepage='Default'/>
    </MessageFormat>
    In the first element i need to add delimeter also .
    The flat file looks like this.
    102111!CUSIP1802! CL!D03973!000000!09/02/2005!09/01/2005!01/01/2001!01/01/2001!01/01/2001!
    I need to validate the first numeric as 6 didgits and should be 6 digit number and also delimeter value will be !.
    Thanks if anybody can give me suggestion.
    Thanks

    From that perspective, WebLogic Integration is simply a set of applications, tools, and APIs that are deployed into WebLogic server instances. A WebLogic Integration Java Process Definition is compiled into EJB components and deployed to the server instance. The following provides a good overview: [http://edocs.bea.com/wli/docs102/overview/index.html]

  • WebLogic Integration help me?

    Hi,
    We are planning to use WLS as our new portal
    site platform. We already have an e-commerce
    server and want to integrate it with WL server.
    (The components of the e-commerce server are
    written in Perl and communicate to each other in
    their own protocol.) We want to use this server
    as our shopping engine in our site.
    I am just wondering how WL Ingegration can help me.
    Can any body give me some suggestions?
    What additional components that our original
    server should provide?
    Please let me know if I describe the scenario unclearly.
    Thanks.
    David Lin

    David,
    WebLogic Integration could provide a platform for easier integration of
    other applications and businesses for your portal. You would have to
    look at your Portal and Backend Application architecture. Chances are,
    it will not always be one type of architecture/technologies or
    applications. But you will need to share information between all of
    them.
    WLI provides several parts that help you do the end to end integration,
    all built using the J2EE based WebLogic Server Platform:
    1 - Business Process Management - this is a Process Engine that gives
    you flexiblity on how your components are used in your application. Your
    applications no longer need to be hardcoded at a source code level or
    script level. It provides the glue between your different components
    with a Visio like flowchart visual graphical interface. It also allows
    you to monitor your business process instances in a runtime environment.
    The business processes can be initiated either using Event Messages
    (normally XML, but don't have to be) or using a java API.
    2 - Application Integration - this is a integration framework built on
    the J2EE Connection Architecture standard, that allows you to integrate
    with backend applications at a business level (referred to as Enterprise
    Information Systems, or EIS in the spec).
    This framework allows you to integration with the EIS at a business
    level (using XML msgs). The framework accesses the EIS using a resource
    adapter (defined as part of the specification). Since the J2EE
    Connection Architecture is a java standard (part of J2EE 1.3 spec),
    resource adapters will be available for main EIS systems (applications
    like SAP, ...). The business level services can be called from a
    Business Process or they can be used to start a Business Process as
    well.
    3 - Data Integration - provides data translation (XML<->non-XML) and
    data transformation (XML<->XML). These can be called from a Business
    Process.
    4 - B2B Integration - allows you to extend your Business Processes
    across the internet with secure, reliable messaging to other companies
    you do business with. These can be suppliers, distributors, logistic
    companies ...
    Since your current components are based on Perl, there would be some
    initial work needed to access these from WLI. This could be done by
    writing a java wrapper (either as a java class or an EJB) that would
    call your perl scripts. This would allow you to call your perl scripts
    from Business Processes.
    The Business Process provides the flexiblity to change the process
    without having to change source code. The process engine also allows you
    to view active Business Process Instances, to see what point it is at in
    the Process. You could then use the WLI Application Integration to share
    information with your back end applications at a business level
    interface.
    There is a lot more information about each part of WebLogic Integration,
    so I would suggest you contact a local BEA person for more information.
    Online documentation on WLI is available at edocs.bea.com.
    Hope this information is helpful.
    Bill
    David Lin wrote:
    Hi,
    We are planning to use WLS as our new portal
    site platform. We already have an e-commerce
    server and want to integrate it with WL server.
    (The components of the e-commerce server are
    written in Perl and communicate to each other in
    their own protocol.) We want to use this server
    as our shopping engine in our site.
    I am just wondering how WL Ingegration can help me.
    Can any body give me some suggestions?
    What additional components that our original
    server should provide?
    Please let me know if I describe the scenario unclearly.
    Thanks.
    David Lin

  • Weblogic Integration and Taglibs

    Has anyone thought about having a taglib for using Weblogic Integration, (specifically
    the BPM) for simplification of accessing workflow information.
    I think this would be a very useful taglib.
    any comments?

    From that perspective, WebLogic Integration is simply a set of applications, tools, and APIs that are deployed into WebLogic server instances. A WebLogic Integration Java Process Definition is compiled into EJB components and deployed to the server instance. The following provides a good overview: [http://edocs.bea.com/wli/docs102/overview/index.html]

  • Announcement : Monitor Bea WebLogic - ManageEngine Applications Manager

    AdventNet introduces ManageEngine Applications Manager 6 - an affordable and integrated Application, Server, and System Monitoring Tool for Enterprise IT.
    This release also includes a Free Edition, with which you can manage up to 10 WebLogic Servers.
    In addition to WebLogic (6.x, 7.x, 8.x), it supports the following applications :
    Application Servers : Tomcat, JBoss, WebSphere
    Databases : Oracle, MS SQL, MySQL
    Systems : Linux, Windows, Solaris
    Services : TCP Ports, Mail Servers, Web Servers, HTTP URLs (Web Pages)
    Custom Applications : JMX and SNMP Consoles
    Other Features : Root Cause Analysis, Alerts, Reports, Web Client
    Live Demo [ http://demo.appmanager.com ]
    WebLogic Monitoring Capabilities :
    http://manageengine.adventnet.com/products/applications_manager/weblogic-management.html
    To learn more about the product, please visit:
    http://manageengine.adventnet.com/products/applications_manager/
    Free Download :
    http://manageengine.adventnet.com/products/applications_manager/download.html
    For support queries and feedback, kindly mail us to [email protected]

    MAke sure you have not set ANY environment variable related to Oracle / BEA / Java / LD_library path. Use the following script to unset / set the initial settings:
    #!/bin/sh
    unset ORACLE_BASE ORACLE_HOME ORACLE_SID ORACLE_TERM
    unset LD_LIBRARY_PATH LD_LIBRARY_PATH_64
    unset CLASSPATH JAVA_HOME
    export PATH=.:/usr/sbin:/usr/bin:/usr/local/bin:/opt/VRTS/bin
    export BEA_HOME=/appl/oracle/products/9.2/weblogic
    Marc
    http://orasoa.blogspot.com

Maybe you are looking for

  • Scrollfunction from the touchpad on a Satellite A100-812 does not work

    The scrollfunction of the touchpad (A100-812) does not work anymore. Device should work perfectly says hardware check.

  • How to edit file sent in Read-only ?

    I want to add a stamp to a document that was sent to me in a read-only format to prevent modification, is this possible?

  • What is used in place of skeleton interface?

    So in Java 2 SDK, Standard Edition, v 1.2 the skeleton interface was deprecated - i.e. should not be used since it will eventually be removed. So what on the server side allows for the marshalling and unmarshalling of objects? Is it RemoteObject or R

  • Screen light burned out

    My screen light seems to have burned out. My computer is probably about 6 years old, so I was wondering if this can be fixed?

  • Sound distortion after downloading artworks

    I am using the latest version of itunes 7.0.1.8 It has seemed ok, until yesterday i decided to click on get album artwork. The artwork was downloaded fine but the noice quality immediately after and since has been awful. I can only describe it as an