LiquidData -- is it part of WLI?

What's the latest -- can LD be used on WebLogic Server 8.1 only or it
requires the costly Integrator?
Thanks

Hi
LiquidData requires WebLogic 7.0 SP1 or later version. It won't run on
WebLogic 7.0 with no service pack though. :)
Regards,
Tinnapat.
"Gleb Tulukin" <[email protected]> wrote in message
news:[email protected]..
What's the latest -- can LD be used on WebLogic Server 8.1 only or it
requires the costly Integrator?
Thanks

Similar Messages

  • Can I modify WLI system Bean's transaction attribute --turn on archiver resulting endless exception in log file

    hi,erveryone,
    one difficult question need help.
    Environment: WLS8.1sp2 + WLI8.1sp2 + ORACLE9i + solaris9
    when I started archiver manually,just for a while, wli system generated about 40,000 JMS messages in
    wli.internal.worklist.timer.queue,and consume the great mass of system resource of Database server,I had to stop these
    archive processes immediately to keep other applicaitons which using the same database running normal. I did so by
    following steps:
    (1) in WLI console, delete wli.internal.worklist.timer.queue;
    (2) in WLI console, reconstruct wli.internal.worklist.timer.queue;
    (3) restart wli server.
    after server was restarted, wli server output endless and repeatly exception to log file ,the typical exception was:
    ####<May 8, 2005 3:08:26 PM CST> <Info> <EJB> <app01> <jcwliserver> <ExecuteThread: '54' for queue:
    'weblogic.kernel.Default'> <<anonymous>> <BEA1-54B26B551CC1A8856F80> <BEA-010049> <EJB Exception in method: remove:
    java.sql.SQLException: Transaction rolled back: Unknown reason.
    java.sql.SQLException: Transaction rolled back: Unknown reason
         at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1299)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1250)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:385)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:343)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:305)
         at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.getConnection(RDBMSPersistenceManager.java:2247)
         at
    com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14__WebLogic_CMP_RDBMS.__WL_loadGroup0(ListenerBean_1nsp14__WebLogic_CMP_R
    DBMS.java:1055)
         at
    com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14__WebLogic_CMP_RDBMS.__WL_setTaskBean_listeners(ListenerBean_1nsp14__Web
    Logic_CMP_RDBMS.java:596)
         at
    com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14__WebLogic_CMP_RDBMS.__WL_setTaskBean_listeners(ListenerBean_1nsp14__Web
    Logic_CMP_RDBMS.java:584)
         at
    com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14__WebLogic_CMP_RDBMS.ejbRemove(ListenerBean_1nsp14__WebLogic_CMP_RDBMS.j
    ava:2423)
         at weblogic.ejb20.manager.DBManager.remove(DBManager.java:1318)
         at weblogic.ejb20.internal.EntityEJBLocalHome.remove(EntityEJBLocalHome.java:214)
         at
    com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14_LocalHomeImpl.remove(ListenerBean_1nsp14_LocalHomeImpl.java:131)
         at
    com.bea.wli.worklist.beans.session.RemoteWorklistManagerBean.removeTaskListeners(RemoteWorklistManagerBean.java:3001)
         at
    com.bea.wli.worklist.beans.session.RemoteWorklistManagerBean_us8t1c_EOImpl.removeTaskListeners(RemoteWorklistManagerBean_us8t
    1c_EOImpl.java:698)
         at com.bea.wli.worklist.timer.WorklistTimerMDB.processListenerToRemove(WorklistTimerMDB.java:102)
         at com.bea.wli.worklist.timer.WorklistTimerMDB.onMessage(WorklistTimerMDB.java:61)
         at weblogic.ejb20.internal.MDListener.execute(MDListener.java:382)
         at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:316)
         at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    >
    ####<May 8, 2005 3:08:26 PM CST> <Info> <EJB> <app01> <jcwliserver> <ExecuteThread: '96' for queue:
    'weblogic.kernel.Default'> <<anonymous>> <BEA1-54B96B551CC1A8856F80> <BEA-010049> <EJB Exception in method: remove:
    javax.ejb.NoSuchEntityException: [EJB:010140]Bean with primary key: '153.22.52.28-17343c7.10243c3c6ec.a51' not found..
    javax.ejb.NoSuchEntityException: [EJB:010140]Bean with primary key: '153.22.52.28-17343c7.10243c3c6ec.a51' not found.
         at
    com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14__WebLogic_CMP_RDBMS.__WL_loadGroup0(ListenerBean_1nsp14__WebLogic_CMP_R
    DBMS.java:1165)
         at
    com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14__WebLogic_CMP_RDBMS.__WL_setTaskBean_listeners(ListenerBean_1nsp14__Web
    Logic_CMP_RDBMS.java:596)
         at
    com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14__WebLogic_CMP_RDBMS.__WL_setTaskBean_listeners(ListenerBean_1nsp14__Web
    Logic_CMP_RDBMS.java:584)
         at
    com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14__WebLogic_CMP_RDBMS.ejbRemove(ListenerBean_1nsp14__WebLogic_CMP_RDBMS.j
    ava:2423)
         at weblogic.ejb20.manager.DBManager.remove(DBManager.java:1318)
         at weblogic.ejb20.internal.EntityEJBLocalHome.remove(EntityEJBLocalHome.java:214)
         at
    com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14_LocalHomeImpl.remove(ListenerBean_1nsp14_LocalHomeImpl.java:131)
         at
    com.bea.wli.worklist.beans.session.RemoteWorklistManagerBean.removeTaskListeners(RemoteWorklistManagerBean.java:3001)
         at
    com.bea.wli.worklist.beans.session.RemoteWorklistManagerBean_us8t1c_EOImpl.removeTaskListeners(RemoteWorklistManagerBean_us8t
    1c_EOImpl.java:698)
         at com.bea.wli.worklist.timer.WorklistTimerMDB.processListenerToRemove(WorklistTimerMDB.java:102)
         at com.bea.wli.worklist.timer.WorklistTimerMDB.onMessage(WorklistTimerMDB.java:61)
         at weblogic.ejb20.internal.MDListener.execute(MDListener.java:382)
         at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:316)
         at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    >
    The wli server generated log file very quickly ,:it can output 1M bytes log file per second,all logged information
    is similar to the <BEA-010049> excetpion metioned above. BEA support engineer suggested me to totally stop the
    archive ,I did so,but the server was still ouput the log file like crazy as before and the normal log information are
    completely override by <BEA-010049> excetpion.
    I checked the EntityEJBs in WLI console :Mywlidomain> Applications> WLI System EJBs> WLI Worklist Persistence$)A#,and
    found that in statistics table :
    ListenerBean : Pool miss ratio = 99.67%, transaction rollback ration = 99.90%,Destory Bean Ratio = 99.48%(see
    attachment)
    WorklistTimerMDB: transaction rollback ratio = 99.97%
    It seems ListenerBean worked incorrectly.I searched in support.bea.com and found one example which also about server
    output endless log file,the author solved this problem by changing Bean's transaction-attribute from 'Required'
    to 'RequiresNew' thought he didn't know why it works. I try this method by changing ListenerBean's
    transaction-attribute from 'Required' to 'RequiresNew'.
    $weblogic_home/integration/lib/wli-ejbs.ear/ejb-jar-generic.xml:
    <ejb-name>CommentBean</ejb-name>
    <method-name>*</method-name>
    </method>
    <trans-attribute>Required</trans-attribute>
    </container-transaction>
    <container-transaction>
    <method>
    <ejb-name>ListenerBean</ejb-name>
    <method-name>*</method-name>
    </method>
    <trans-attribute>RequiresNew</trans-attribute> -----------the default value is Required,I modified it to
    RequiresNew.
    </container-transaction>
    <container-transaction>
    really it works, the log file output resume normal. But there are still some problems:
    (1) this exception is still exist:
    javax.ejb.NoSuchEntityException: [EJB:010140]Bean with primary key: '153.22.52.28-17343c7.10243c3c6ec.a51' not found.
    (2) is this method safe ?(Does "Modify ListenBean's transaction-attribute" impat other parts of wli system?)
    (3) after changed the transaction attribute, if turn on archive again, the server output endless exception:
    ####<Jun 1, 2005 5:14:58 PM CST> <Info> <EJB> <app01> <jcwliserver> <ExecuteThread: '63' for queue:
    'weblogic.kernel.Default'> <<anonymous>> <BEA1-2F43890B86B0A8856F80> <BEA-010036> <Exception from ejbStore:
    java.sql.SQLException: XA error: XAER_RMERR : A resource manager error has occured in the transaction branch start()
    failed on resource 'weblogic.jdbc.jta.DataSource': XAER_RMERR : A resource manager error has occured in the transaction
    branch
    oracle.jdbc.xa.OracleXAException
         at oracle.jdbc.xa.OracleXAResource.checkError(OracleXAResource.java:1160)
         at oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:311)
         at weblogic.jdbc.wrapper.VendorXAResource.start(VendorXAResource.java:50)
         at weblogic.jdbc.jta.DataSource.start(DataSource.java:617)
         at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1075)
         at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1007)
         at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:218)
         at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:419)
         at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1287)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1250)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:385)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:343)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:305)
         at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.getConnection(RDBMSPersistenceManager.java:2247)
         at
    com.bea.wli.worklist.beans.entity.TaskBean_9fxazu__WebLogic_CMP_RDBMS.__WL_store(TaskBean_9fxazu__WebLogic_CMP_RDBMS.java:363
    6)
         at
    com.bea.wli.worklist.beans.entity.TaskBean_9fxazu__WebLogic_CMP_RDBMS.ejbStore(TaskBean_9fxazu__WebLogic_CMP_RDBMS.java:3548)
         at weblogic.ejb20.manager.DBManager.beforeCompletion(DBManager.java:927)
         at weblogic.ejb20.internal.TxManager$TxListener.beforeCompletion(TxManager.java:745)
         at weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(ServerSCInfo.java:1010)
         at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(ServerSCInfo.java:115)
         at weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAndChain(ServerTransactionImpl.java:1142)
         at weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(ServerTransactionImpl.java:1868)
         at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:250)
         at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:221)
         at weblogic.ejb20.internal.MDListener.execute(MDListener.java:412)
         at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:316)
         at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    java.sql.SQLException: XA error: XAER_RMERR : A resource manager error has occured in the transaction branch start()
    failed on resource 'weblogic.jdbc.jta.DataSource': XAER_RMERR : A resource manager error has occured in the transaction
    branch
    oracle.jdbc.xa.OracleXAException
         at oracle.jdbc.xa.OracleXAResource.checkError(OracleXAResource.java:1160)
         at oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:311)
         at weblogic.jdbc.wrapper.VendorXAResource.start(VendorXAResource.java:50)
         at weblogic.jdbc.jta.DataSource.start(DataSource.java:617)
         at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1075)
         at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1007)
         at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:218)
         at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:419)
         at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1287)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1250)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:385)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:343)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:305)
         at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.getConnection(RDBMSPersistenceManager.java:2247)
         at
    com.bea.wli.worklist.beans.entity.TaskBean_9fxazu__WebLogic_CMP_RDBMS.__WL_store(TaskBean_9fxazu__WebLogic_CMP_RDBMS.java:363
    6)
         at
    com.bea.wli.worklist.beans.entity.TaskBean_9fxazu__WebLogic_CMP_RDBMS.ejbStore(TaskBean_9fxazu__WebLogic_CMP_RDBMS.java:3548)
         at weblogic.ejb20.manager.DBManager.beforeCompletion(DBManager.java:927)
         at weblogic.ejb20.internal.TxManager$TxListener.beforeCompletion(TxManager.java:745)
         at weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(ServerSCInfo.java:1010)
         at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(ServerSCInfo.java:115)
         at weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAndChain(ServerTransactionImpl.java:1142)
         at weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(ServerTransactionImpl.java:1868)
         at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:250)
         at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:221)
         at weblogic.ejb20.internal.MDListener.execute(MDListener.java:412)
         at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:316)
         at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
         at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1292)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1250)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:385)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:343)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:305)
         at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.getConnection(RDBMSPersistenceManager.java:2247)
         at
    com.bea.wli.worklist.beans.entity.TaskBean_9fxazu__WebLogic_CMP_RDBMS.__WL_store(TaskBean_9fxazu__WebLogic_CMP_RDBMS.java:363
    6)
         at
    com.bea.wli.worklist.beans.entity.TaskBean_9fxazu__WebLogic_CMP_RDBMS.ejbStore(TaskBean_9fxazu__WebLogic_CMP_RDBMS.java:3548)
         at weblogic.ejb20.manager.DBManager.beforeCompletion(DBManager.java:927)
         at weblogic.ejb20.internal.TxManager$TxListener.beforeCompletion(TxManager.java:745)
         at weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(ServerSCInfo.java:1010)
         at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(ServerSCInfo.java:115)
         at weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAndChain(ServerTransactionImpl.java:1142)
         at weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(ServerTransactionImpl.java:1868)
         at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:250)
         at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:221)
         at weblogic.ejb20.internal.MDListener.execute(MDListener.java:412)
         at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:316)
         at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    >
    How can I solve these problem ? any suggestion is warm welcome.
    Thanks in advance.
    Great Lou

    Back up all data to at least two different storage devices, if you haven't already done so. The backups can be made with Time Machine or with a mirroring tool such as Carbon Copy Cloner. Preferably both.
    Boot into Recovery (command-R at startup), launch Disk Utility, and erase the startup volume with the default options.This operation will destroy all data on the volume, so you had be better be sure of your backups. Quit Disk Utility and install OS X. When you reboot, you'll be prompted to go through the initial setup process. That’s when you transfer the data from one of your backups. For details of how this works, see here:
    Using Setup Assistant
    Transfer only "Users" and "Settings" – not "Applications" or "Other files." Don't transfer the Guest account, if it was enabled on the old system. Test. If the problem is still there, you have a hardware fault. Take the machine to an Apple Store for diagnosis.
    If the problem is resolved, reinstall your third-party software cautiously. Self-contained applications that install into the Applications folder by drag-and-drop or download from the App Store are safe. Anything that comes packaged as an installer or that prompts for an administrator password is suspect, and you must test thoroughly after reinstalling each such item to make sure you haven't restored the problem.
    Note: You need an always-on Ethernet or Wi-Fi connection to the Internet to use Recovery. It won’t work with USB or PPPoE modems, or with proxy servers, or with networks that require a certificate for authentication.

  • Migration from WLI2.0 to WLI2.1 - problems and solutions

    We have experienced a number of issues when migrating from WLI2.0 (no service packs)
    to WLI2.1 - We are only using the WLPI (BPM) part of WLI. We decided to publish
    these issues in case they can be of help to others.
    Problems:
    1. The documentation (http://edocs.bea.com/wlintegration/v2_1/migrate/4zubemig.htm#998197)
    says the migration process works from WLPI 1.2.1 and from WLI 2.0 (SP2, 3, 4).
    What about WLI2.0 with no service packs - I don't see why BEA should have left
    out migration from that platform. We decided to follow the process and see what
    happened.
    2. There is no indication in the documentation of how to run the GUI based migration
    tools on Unix, only for Windows so we had to follow the manual route.
    3. The Manual process refers (http://edocs.bea.com/wlintegration/v2_1/migrate/4zubemig.htm#999969)
    to the DB variable setting scripts. It then says to run "migratedb.sh". None of
    these files have extensions ".sh" - the files that were installed have no extension.
    Obviously that did not stop us running them but the documentation needs correcting.
    4. The migratedb scripts calls "WLI_HOME/setenv.sh" - it is confusing that there
    is a second copy of this file in the bin folder called "setenv". Why are there
    2 copies. Also I note that the one in bin is executable and the other is not.
    All very confusing!!
    5. The migratedb script fails to run because we have not previously run setDomain.
    This is not documented.
    6. Running setDomain on a domain moved from a WLI2.0 installaion fails since it
    does not contain the expected folders. That basically means you cannot migrate
    such a domain. We carried on with the process using the bpmdomain so that we could
    at least migrate our database automatically.
    7. Having run setDomain, we tried migratedb again but it failed because we had
    not run switchdb. Again, this is not documented. We ran switchdb successfully.
    8. Now running migratedb creates a file called "migrate.sh". Unfortunately the
    script migratedb then attempts to run a file called "migrate". This is evidence
    that no-one has ever tested this script at BEA and we are very disconcerted by
    this fact!! We renamed the script and ran migratedb again - this time it ran the
    migrate script.
    9. This still fails with the following errors (when calling migrateCommonRep)
         -v (No such file or directory)
         null
         java.lang.NullPointerException
         at java.lang.Class.forName0(Native Method)
         at java.lang.Class.forName(Class.java:120)
         at com.bea.eci.migration.Migrate.getConnection(Migrate.java:207)
         at com.bea.eci.migration.Migrate.main(Migrate.java:73)
         java.lang.NullPointerException
         at com.bea.eci.migration.Migrate.main(Migrate.java:192)
    10. It also fails because it cannot find "sqlplus" - a fatal problem - we do not
    have sqlplus installed on the same machine as WLI and yet again this requirement
    is not documented. At this point we gave up trying to run the migrate script as
    there seemed to be no route forward.
    The process we took to move from WLI2.0 (WLPI only) was as follows:
    a. Since we had done no changes to filerealm.properties we simply copied the one
    fron bpmdomain into our own domain.
    b. We have been unable to run the step to migrate the common repository (see note
    9). If this is referring to the XML repository then that should not be a problem
    to us as we have not used it.
    c. We moved the "migrate/BPM_20SP3-21.sql" script to an NT machine and ran that
    script on our database. This seems to have successfully updated the database.
    Lastly, having completed the migration process we tried to run the server but
    it fails. This is because the startWeblogic script fails to call checkdomain properly.
    We modified the line to become:
         ". $WLI_HOME/bin/checkdomain"     # the '.' was missing
    Does anyone else have any experiences with this that would help us all?
    Pete

    Pete,
    Please post this to the weblogic.integration.interest and weblogic.integration.developer newsgroups?
    Pete Edwards wrote:
    We have experienced a number of issues when migrating from WLI2.0 (no service packs)
    to WLI2.1 - We are only using the WLPI (BPM) part of WLI. We decided to publish
    these issues in case they can be of help to others.
    Problems:
    1. The documentation (http://edocs.bea.com/wlintegration/v2_1/migrate/4zubemig.htm#998197)
    says the migration process works from WLPI 1.2.1 and from WLI 2.0 (SP2, 3, 4).
    What about WLI2.0 with no service packs - I don't see why BEA should have left
    out migration from that platform. We decided to follow the process and see what
    happened.
    2. There is no indication in the documentation of how to run the GUI based migration
    tools on Unix, only for Windows so we had to follow the manual route.
    3. The Manual process refers (http://edocs.bea.com/wlintegration/v2_1/migrate/4zubemig.htm#999969)
    to the DB variable setting scripts. It then says to run "migratedb.sh". None of
    these files have extensions ".sh" - the files that were installed have no extension.
    Obviously that did not stop us running them but the documentation needs correcting.
    4. The migratedb scripts calls "WLI_HOME/setenv.sh" - it is confusing that there
    is a second copy of this file in the bin folder called "setenv". Why are there
    2 copies. Also I note that the one in bin is executable and the other is not.
    All very confusing!!
    5. The migratedb script fails to run because we have not previously run setDomain.
    This is not documented.
    6. Running setDomain on a domain moved from a WLI2.0 installaion fails since it
    does not contain the expected folders. That basically means you cannot migrate
    such a domain. We carried on with the process using the bpmdomain so that we could
    at least migrate our database automatically.
    7. Having run setDomain, we tried migratedb again but it failed because we had
    not run switchdb. Again, this is not documented. We ran switchdb successfully.
    8. Now running migratedb creates a file called "migrate.sh". Unfortunately the
    script migratedb then attempts to run a file called "migrate". This is evidence
    that no-one has ever tested this script at BEA and we are very disconcerted by
    this fact!! We renamed the script and ran migratedb again - this time it ran the
    migrate script.
    9. This still fails with the following errors (when calling migrateCommonRep)
    -v (No such file or directory)
    null
    java.lang.NullPointerException
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:120)
    at com.bea.eci.migration.Migrate.getConnection(Migrate.java:207)
    at com.bea.eci.migration.Migrate.main(Migrate.java:73)
    java.lang.NullPointerException
    at com.bea.eci.migration.Migrate.main(Migrate.java:192)
    10. It also fails because it cannot find "sqlplus" - a fatal problem - we do not
    have sqlplus installed on the same machine as WLI and yet again this requirement
    is not documented. At this point we gave up trying to run the migrate script as
    there seemed to be no route forward.
    The process we took to move from WLI2.0 (WLPI only) was as follows:
    a. Since we had done no changes to filerealm.properties we simply copied the one
    fron bpmdomain into our own domain.
    b. We have been unable to run the step to migrate the common repository (see note
    9). If this is referring to the XML repository then that should not be a problem
    to us as we have not used it.
    c. We moved the "migrate/BPM_20SP3-21.sql" script to an NT machine and ran that
    script on our database. This seems to have successfully updated the database.
    Lastly, having completed the migration process we tried to run the server but
    it fails. This is because the startWeblogic script fails to call checkdomain properly.
    We modified the line to become:
    ". $WLI_HOME/bin/checkdomain" # the '.' was missing
    Does anyone else have any experiences with this that would help us all?
    Pete--
    Developer Relations Engineer
    BEA Support

  • Pending messages

    We are having a problem with some messages being stuck in the queue.
              They show as "pending" in the console and, in fact, get delivered to
              the listeners (MDBs) on server restart. The code of MDBs is beyond our
              control (the messages are actually sent to Weblogic Business Process
              Manager, part of WLI). The transaction attribute of the listeners is
              "Not Supported". Any ideas what's going on? It could be related to
              spikes in volume, but would not one expect the messages just sit in
              the queue and be picked up when the volume of incoming messages drops?
              Our biggest concern is finding a way to process these "lost" messages
              without having to restart the server. Any thoughts? Thanks!
              Igor
              

    version? there were some stalled listener problems fixed in 6.1 SP3.
              _sjz.
              "Igor Sidorin" <[email protected]> wrote in message
              news:[email protected]..
              > We are having a problem with some messages being stuck in the queue.
              > They show as "pending" in the console and, in fact, get delivered to
              > the listeners (MDBs) on server restart. The code of MDBs is beyond our
              > control (the messages are actually sent to Weblogic Business Process
              > Manager, part of WLI). The transaction attribute of the listeners is
              > "Not Supported". Any ideas what's going on? It could be related to
              > spikes in volume, but would not one expect the messages just sit in
              > the queue and be picked up when the volume of incoming messages drops?
              > Our biggest concern is finding a way to process these "lost" messages
              > without having to restart the server. Any thoughts? Thanks!
              >
              > Igor
              

  • XML document does not appear to contain a properly formed DOCTYPE header

    Hi,
    I've created an ejb which uses the studio API to start/execute etc the workflow
    tasks in a generic way. The same ejb contain certain method which I want to use
    as business operations in my workflows. However, when I deploy this ejb as a separate
    application by putting the required jar files in class path it works fine, but
    when I deploy it as a part of WLI application for accessing the business operations
    in workflow I'm getting the following error. I'm entering ejbcomponent entry under
    the wli application tag of config.xml and putting the jar file in the lib directory
    where other jar files are placed. I couldn't understand the reason why it is failing
    when I deploy it as a part of WLI application and not when I deploy it independently.
    Module Name: TestWLPI, Error: The XML parser encountered an error in your deployment
    descriptor. Please ensure that your DOCTYPE is correct. You may wish to compa
    re your deployment descriptors with the WebLogic Server examples to ensure the
    format is correct. The error was:
    weblogic.xml.process.ProcessorFactoryException: XML document does not appear to
    contain a properly formed DOCTYPE header
    at weblogic.xml.process.ProcessorFactory.getProcessor(ProcessorFactory.java:281)
    at weblogic.xml.process.ProcessorFactory.getProcessor(ProcessorFactory.java:224)
    at weblogic.ejb20.dd.xml.DDUtils.processXML(DDUtils.java:267)
    at weblogic.ejb20.dd.xml.DDUtils.processXML(DDUtils.java:242)
    at weblogic.ejb20.dd.xml.DDUtils.processAltDD(DDUtils.java:220)
    at weblogic.ejb20.dd.xml.DDUtils.createDescriptorFromJarFile(DDUtils.java:102)
    at weblogic.ejb20.deployer.EJBModule.loadEJBDescriptor(EJBModule.java:500)
    at weblogic.ejb20.deployer.EJBModule.loadDescriptor(EJBModule.java:207)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:714)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:458)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplications(SlaveDeployer.java:490)
    at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.java:253)
    at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initialize(DeploymentManagerServerLifeCycleImpl.java:150)
    at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
    at weblogic.Server.main(Server.java:32)

    javax.xml.stream.XMLStreamException: javax.xml.stream.XMLStreamException: Premature end of file encountered
    at weblogic.xml.stax.XMLStreamReaderBase.prime(XMLStreamReaderBase.java:80)
    at weblogic.xml.stax.XMLStreamReaderBase.setInput(XMLStreamReaderBase.java:99)
    at weblogic.xml.stax.XMLStreamInputFactory.createXMLStreamReader(XMLStreamInputFactory.java:316)
    at weblogic.xml.stax.XMLStreamInputFactory.createXMLStreamReader(XMLStreamInputFactory.java:49)
    at weblogic.application.descriptor.BasicMunger2.<init>(BasicMunger2.java:110)
    at weblogic.application.descriptor.BasicMunger2.<init>(BasicMunger2.java:128)
    at weblogic.application.descriptor.VersionMunger.<init>(VersionMunger.java:74)
    at weblogic.application.descriptor.VersionMunger.<init>(VersionMunger.java:63)
    at weblogic.servlet.internal.WlsWebAppReader2.<init>(WlsWebAppReader2.java:59)
    at weblogic.servlet.internal.WebAppDescriptor$MyWlsWebAppDescriptor.createXMLStreamReader(WebAppDescriptor.java:316)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:402)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
    Any Suggestions plz???
    Thanks

  • Updating sample plugin in samples domain

    I'm running WLI 2.1 SP1 and WLS 6.1 SP2.
    I've been trying to make some code changes to the sample plugin and deploy it
    to the samples domain.
    The sampleplugin-ejb.jar file is pre-deployed to this domain as part of the WLI
    deployment unit. The plugin is available after I first install the server.
    I made some changes to the plugin and recompiled using the supplied build.cmd.
    I then copied the Jar file to the c:\bea\wlintegration2.1\lib directory and updated
    the WLI deployment unit using
    java weblogic.deploy -port 7001 -host witless update security WLI c:\bea\wlintegration2.1\lib\sampleplugin-ejb.jar
    This creates a WLI.jar file in the .wlstaging directory that contains the files
    from my modified version of the sample plugin.
    When I start the studio and attempt to load the template definition I get an error
    telling me the plugin is not loaded.
    If I restart the server this error goes away and I can use the plugin actions
    etc. from the studio console. Unfortunately it's NOT my modified version of the
    plugin, its the version of the plugin that was deployed when the server was installed.
    Can anyone tell me the correct steps to follow to change the sample plugin and
    deploy the new version in the samples domain.
    Thanks !

    Tom,
    I have had similar problems using weblogic.Deploy for ejbs. Remove the
    WLI.jar in the .wlstaging directory. Make sure there isn't anything under
    the applications subdirectory related to this either. Since you've already
    copied the new jar file to the lib subdirectory just restart the server.
    Make sure the EJB deploys during startup.
    Generally speaking, stop the server, replaces the jar in the lib
    subdirectory and restart the server.
    Mike
    "Tom" <[email protected]> wrote in message
    news:3cbd5cbf$[email protected]..
    >
    I'm running WLI 2.1 SP1 and WLS 6.1 SP2.
    I've been trying to make some code changes to the sample plugin and deployit
    to the samples domain.
    The sampleplugin-ejb.jar file is pre-deployed to this domain as part ofthe WLI
    deployment unit. The plugin is available after I first install the server.
    I made some changes to the plugin and recompiled using the suppliedbuild.cmd.
    >
    I then copied the Jar file to the c:\bea\wlintegration2.1\lib directoryand updated
    the WLI deployment unit using
    java weblogic.deploy -port 7001 -host witless update security WLIc:\bea\wlintegration2.1\lib\sampleplugin-ejb.jar
    >
    This creates a WLI.jar file in the .wlstaging directory that contains thefiles
    from my modified version of the sample plugin.
    When I start the studio and attempt to load the template definition I getan error
    telling me the plugin is not loaded.
    If I restart the server this error goes away and I can use the pluginactions
    etc. from the studio console. Unfortunately it's NOT my modified versionof the
    plugin, its the version of the plugin that was deployed when the serverwas installed.
    >
    Can anyone tell me the correct steps to follow to change the sample pluginand
    deploy the new version in the samples domain.
    Thanks !

  • Re: Pending messages

    Those messages are not "lost" since they got delivered later (server
              restart).
              Since MDB is using async consumer so that there could have messages in the
              delivery pipeline and
              those messages are considered "pending" too. You can reduce the pipeline
              down to 1 so if the MDB doesn't
              consumer message fast enough some other consumer still can get those
              messages.
              "Igor Sidorin" <[email protected]> wrote in message
              news:[email protected]..
              > We are having a problem with some messages being stuck in the queue.
              > They show as "pending" in the console and, in fact, get delivered to
              > the listeners (MDBs) on server restart. The code of MDBs is beyond our
              > control (the messages are actually sent to Weblogic Business Process
              > Manager, part of WLI). The transaction attribute of the listeners is
              > "Not Supported". Any ideas what's going on? It could be related to
              > spikes in volume, but would not one expect the messages just sit in
              > the queue and be picked up when the volume of incoming messages drops?
              > Our biggest concern is finding a way to process these "lost" messages
              > without having to restart the server. Any thoughts? Thanks!
              >
              > Igor
              

    We are having the same problem, which messages stuck in the Pending mode even after restarting. Is there any way to retrieve those pending messages?
              Thanks,
              Jun Xiao
              Sogeti-USA
              

  • WebLogic 10.3.0 WLI Domain - Microsoft AD administrator user access issue.

    Hi SOA Experts,
    We are facing issue of getting noaccess exception on console (below) when doing datasource testing using Microsoft AD administrator user. The same works fine when testing using WLS embedded LDAP administrator user in WLI domain. In plain WLS 10.3.0 domain (without WLI) with same Microsoft AD configuration they do not see this issue, they are able to successfully test data source using both embedded WLS administrator and Microsoft AD administrator user.
    I enabled security ATN and ATZ debug flags and below is my observation.
    In plain WLS 10.3.0 domain I see that default weblogic administrator user in embedded LDAP is part of administrators group. Microsoft AD administrator user is part of Administrators group from MS AD.
    Whereas in WLI domain I see that default weblogic administrator user is part of Administrators & IntegrationAdministrators groups. In WLI domain Administrators group is again part of IntegrationAdministrators group (below is debug logs).
    Below is Plain WLS Domain Debug log
    ####<Dec 6, 2010 5:20:14 PM EST> <Debug> <SecurityAtz> <slsol10> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)
    '> <<WLS Kernel>> <> <> <1291674014123> <BEA-000000> < Subject: 2
    Principal = weblogic.security.principal.WLSUserImpl("weblogic")
    Principal = weblogic.security.principal.WLSGroupImpl("Administrators")
    Below is WLI Domain Debug Log
    <> <1291669863989> <BEA-000000> <XACML Authorization isAccessAllowed(): input arguments:>
    ####<Dec 6, 2010 4:11:03 PM EST> <Debug> <SecurityAtz> <slsol10> <AdminServer> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <>
    <> <1291669863989> <BEA-000000> < Subject: 3
    Principal = weblogic.security.principal.WLSUserImpl("weblogic")
    Principal = weblogic.security.principal.WLSGroupImpl("Administrators")
    Principal = weblogic.security.principal.WLSGroupImpl("IntegrationAdministrators")
    The issue of Microsoft AD administrator user not able to test datasource in WLI domain seems to be happening because of IntegrationAdministrators group which comes by default with WLI domain (in plain WLS domain we do not have this group). Looks like the datasource which is being created in WLI domain seems to be being treated as WLI resource and user accessing it is being checked if it part of IntegrationAdministrators group. In this case weblogic default administrator user is part of IntegrationAdministrators, for which we do not see issue where as Microsoft AD administrator user which is not part of IntegrationAdministrators seems to be having problem.
    Below is snipper of Microsoft AD administrator user in Debug logs
    ####<Dec 6, 2010 4:13:31 PM EST> <Debug> <SecurityAtz> <slsol10> <AdminServer> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <>
    <> <1291670011687> <BEA-000000> <XACML Authorization isAccessAllowed(): input arguments:>
    ####<Dec 6, 2010 4:13:31 PM EST> <Debug> <SecurityAtz> <slsol10> <AdminServer> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <>
    <> <1291670011687> <BEA-000000> < Subject: 2
    Principal = weblogic.security.principal.WLSUserImpl("MSADAdminUser")
    Principal = weblogic.security.principal.WLSGroupImpl("Administrators")
    Also one more observation about datasource which is created is in plain WLS & WLI domain created datasource resource type is shown as “jdbc” which is expected, but in addition in WLI domain I observe that created datasource resource type is marked as JMX and DS is being considered as application (below), not sure if this has something to do with the issue.
    Below is WLS domain debug log, below you can see that datasource is being treated as JDBC resource which is expected.
    ####<Dec 6, 2010 5:21:03 PM EST> <Debug> <SecurityAtz> <slsol10> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1291674063776> <BEA-000000> <com.bea.common.security.internal.service.AccessDecisionServiceImpl.isAccessAllowed Resource=type=<jdbc>, application=, module=, resourceType=ConnectionPool, resource=testDS, action=reserve>
    Below is WLI domain debug log, below you can see that datasource is being treated as application and it says resource type as JMX
    ####<Dec 6, 2010 4:12:17 PM EST> <Debug> <SecurityAtz> <slsol10> <AdminServer> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1291669937755> <BEA-000000> < Resource: type=<jmx>, operation=get, application=testDS, mbeanType=weblogic.j2ee.descriptor.wl.JDBCDataSourceBean, target=Name>
    I created user in embedded LDAP in WLI domain with same name as MS AD administrator user and assigned it to Administrators group, that obviously works but is not acceptable solution.
    Below is exception thrown on console when testing datasource using Microsoft AD administrator user.
    weblogic.management.NoAccessRuntimeException: Access not allowed for subject: principals=[MSADAdminUser, Administrators], on Resource weblogic.management.runtime.JDBCDataSourceRuntimeMBean Operation: invoke , Target: testPool at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:205) at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:222) at javax.management.remote.rmi.RMIConnectionImpl_1030_WLStub.invoke(Unknown Source) at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.invoke(RMIConnector.java:978) at weblogic.management.jmx.MBeanServerInvocationHandler.doInvoke(MBeanServerInvocationHandler.java:544) at weblogic.management.jmx.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:380) at $Proxy92.testPool(Unknown Source) at com.bea.console.actions.jdbc.datasources.testjdbcdatasource.TestJDBCDataSource.begin(TestJDBCDataSource.java:114) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.beehive.netui.pageflow.FlowController.invokeActionMethod(FlowController.java:870) at org.apache.beehive.netui.pageflow.FlowController.getActionMethodForward(FlowController.java:809) at org.apache.beehive.netui.pageflow.FlowController.internalExecute(FlowController.java:478) at org.apache.beehive.netui.pageflow.PageFlowController.internalExecute(PageFlowController.java:306) at
    - BoyelT

    This issue has been resolved.
    The problem of Microsoft active directory administrator user not able to test the datasource in WLI domain is caused because of IntegrationAdministrators group & IntegrationAdmin role which comes in WLI domain. Assigning the Microsoft Administrator group to IntegrationAdmin role from WebLogic console has resolved the issue.
    Below are steps for assigning the MS AD administrator group to IntegrationAdmin role from console in WLI domain.
    ======================================================
    - Login to console and click on "Security Realms" and "myrealm"
    - Go to "Roles and Policies" tab and expand "Global Roles" tree and "Roles" tree view under it.
    - Click on "View Role Conditions" link for "IntegrationAdmin" role.
    - Click on "Add Conditions" button select Group (default) for "Predicate List" drop down box and click Next button.
    - Specify MS AD admin group name for "Group Argument Name" text box and hit on Add button.
    ======================================================
    - BoyelT
    Edited by: BoyelT on Dec 20, 2010 1:36 PM

  • Disabling transactions from WLI Workshop Web Service application?

    I need to disable the transactions from a Workshop generated Web Service for WLI (Workshop 8.1.6).
    I can accomplish this by changing and repackaging the builded EAR-package by altering the ejb-jar.xml:s in the .workshop directory and setting the transactions from Required to NotSupported. It would be much more convenient, if I could do that change from the Workshop.
    Actual question: is there a way to disable transactions from a Web Service in Workshop? I have not found any place to change this property.

    Hi
    You have 2 options.
    As you mentioned you can modify the generated ejb descriptors. Unfortunately this attribute is not exposed as a property in the workshop, so you cannot change there.
    Other option is to suspend the transaction created by workshop so that your webservice functionality or any control called within that won't be part of the workshop transaction.
    More info at http://forums.bea.com/bea/message.jspa?messageID=600045134&tstart=0
    Thanks
    Vimala

  • EDI/XML translator in WLI 2.0

    are any translator for EDI to XML available in WLI 2.0, to allow
    developers to use EDI software as a service and/or integrate whole B2B solution
    based on WLI 2.0 with existing EDI systems ?
    thanx in advance ...

    In WLI 2.1 there will be full support for EDI including X12 and EDIFACT support. As
    part of the solution there is a mapping tool that you can use to create maps from
    EDI to XML.
    Sunil Raju
    Milan Krajnak wrote:
    are any translator for EDI to XML available in WLI 2.0, to allow
    developers to use EDI software as a service and/or integrate whole B2B solution
    based on WLI 2.0 with existing EDI systems ?
    thanx in advance ...

  • WLI 2.1 setting all workflows to Suspended Mode

    Hi,
    Twice now I have seen WLI set all instantiated workflows to a suspended state. Worse,
    I can continue to create workflows (via JMS Events), but they are also set to a suspended
    state. This normally occurs when a database exception has been raised on a WLI table
    or when someone was dynamically changing the active workflow template while one was
    being instantiated.
    Has anyone seen this happen? If so, what needs to be done to get WLI out of this
    mode of creating workflows in a suspended state?
    We are using WLI 2.1 SP1 and WLS 6.1 SP2.
    Thanks.
    --Todd

    BEA has provided a fix for this problem with WLI 2.1 SP1 rolling patch 3. You will
    need to contact BEA to get this patch.
    --Todd
    "Todd Dolan" <[email protected]> wrote:
    >
    After contacting BEA, they have confirmed that the suspended workflow problem
    is a
    bug and something that will be fixed with WLI 2.1 SP2. However, they did
    not have
    a date as to the release of that service pack.
    Louise -- Thanks for pointing me in the right direction.
    --Todd
    "Louise Scully" <[email protected]> wrote:
    Hi Todd,
    We were getting the suspended workflows problem a couple of months ago.
    We recieved
    a fix for this in a service patch, but we were running WLPI 2.0, so I would
    assume
    that the fix we received would be part of the service pack for 2.1
    To get WLPI out of this behaviour once it happens, try removing all the
    instances
    which are suspended by running this SQL:
    delete from eventwatch where instanceid in (select instanceid from instance
    where
    state=0);
    delete from instance where state=0;
    Hope this helps,
    Louise
    "Todd Dolan" <[email protected]> wrote:
    Hi,
    Twice now I have seen WLI set all instantiated workflows to a suspended
    state. Worse,
    I can continue to create workflows (via JMS Events), but they are alsoset
    to a suspended
    state. This normally occurs when a database exception has been raisedon
    a WLI table
    or when someone was dynamically changing the active workflow template
    while
    one was
    being instantiated.
    Has anyone seen this happen? If so, what needs to be done to get WLIout
    of this
    mode of creating workflows in a suspended state?
    We are using WLI 2.1 SP1 and WLS 6.1 SP2.
    Thanks.
    --Todd

  • WLI 7.0 samples database setup problem

    I have just installed WL Platform 7.0. I want to run the WLI samples and did the following:
    1. Started "Integration Database Wizard" for WLI samples and performed "SwitchDB"
    - provided valid database properties for oracle. Completed successfully - config.xml
    for samples is updated.
    2. Ran RunSamples script - Gives database connect problems and database is not created.
    The user/pwd/machine name/SID are all correct.
    I observed that as part of "RunSamples", it again invokes "SwitchDB" (command I see
    is "switchdb oracle"). This resets the database properties in config.xml to the defaults
    - so obviously this is causing the connection problem.
    Pls let me know what is going wrong here?
    Thanks

    Garf,
    You are correct in your analysis. When you run the 'RunSamples' script,
    it will call switchdb and this causes the 'defaults' to be set in
    config.xml. Running the wliconfig utility is the customer experience
    BEA would like to have with regard to setting up the database. However,
    the RunSamples script has not been updated to correctly reflect that the
    customer would have already performed this step. When RunSamples calls
    switchdb, it is getting the defaults from the following location:
    <USER_DEFINED_DOMAIN>/dbInfo/<DATABASE>/setDBVars and setDBVarsExt files
    So for example, if you accepted the default user directory and your
    BEA_HOME is C:/bea and you were using the EAI Domain template calling
    your domain eaidomain and your are using Oracle, you should update the
    following files:
    C:\bea\user_projects\eaidomain\dbInfo\oracle\setDBVars.cmd and
    setDBVarsExt.cmd
    Edit these files to reflect your DB connection properties.
    When RunSamples calls switchdb, these properties will be used to update
    the wliPool in config.xml. I hope this helps and sorry for the
    inconvenience.
    Cheers,
    Chris
    Garf wrote:
    I have just installed WL Platform 7.0. I want to run the WLI samples and did the following:
    1. Started "Integration Database Wizard" for WLI samples and performed "SwitchDB"
    - provided valid database properties for oracle. Completed successfully - config.xml
    for samples is updated.
    2. Ran RunSamples script - Gives database connect problems and database is not created.
    The user/pwd/machine name/SID are all correct.
    I observed that as part of "RunSamples", it again invokes "SwitchDB" (command I see
    is "switchdb oracle"). This resets the database properties in config.xml to the defaults
    - so obviously this is causing the connection problem.
    Pls let me know what is going wrong here?
    Thanks

  • Is Aqualogic BPM a replacement for WLI ?

    Hi all,
    Until now I have worked with Workshop 8.x to build my processes.
    Now I have downloaded Workshop 9.x and I cannot see anymore JPD in it. I wonder if Bea is dropping WLI for Aq BPM......
    As in the subject: is Aq BPM a replacement for WLI ?
    Thanks
    Francesco

    Hi Leonardo,
    Let me re-iterate the basic rule of programming: "We never program for exceptions". The scenario that you are describing is very much valid and applied/followed in any orchestration process i.e. in no way the orchestration layer (BPM/ WLI/ BPEL etc.) access the data directly, but it is done through a Data layer or data services; however, one must take a business process in totality and not confuse it with a specfic use case.
    Let me explain, there is a fundamental difference betwwen the process view as described for a traditional RUP or UML model (which has its origins in Object Oriented Analysis and Design- OOAD) and the BPM model. The UML model characterizes scenarios or use cases by primary actor(s) and all other systems are secondary. thus a flow in UML is the perspective of a single actor. In contrast, if one looks at a business process in totality, it might have diffenert actors altogether, and all might be primary. For example, consider a simplest business process for order processing in retail domain. Though the process is initiated by the Customer, the entire activity of order processing (taking order, checking inventory, shipping, collaborationg etc) might have the intervention of several actors (Say sales dept, sales manager, delivery manager, sales rep etc). To represent such a scenario in WLI, one may have to develop several JPD's or work-flows, each workflow concentrating on the part of a specific actor. The coupling or ordering between these workflows might or might not be apparant to the business user on a top level. As compared to this, the entire scenario can be represented in one single model of BPM. The individual activities/ responsibilities of each actor can be detailed out in subsequent sections.
    Coming to you specific question, for that particular scenario, one might not want to go for BPM. Having said that, I will also specify that when looking at the entire business flow/ process, such processes are concidered as exceptions. The primary focus of any BPM solution is to automate the unavoidable human interventions that occur in any business process, and not plain orchestartion. Also, the worklist solution might help in a very limited user base, but is not able to handle the complex scenarios of user groups, multiple assignments, multiple roles for a user, which can easily be implemented in BPM (ALBPM organization chart)
    Your point about BAM in WLI is also valid, but tell me , as a programmer, or an architect, would you like to re-invennt the wheel for doing something for which BPM is providing an out-of-the-box solution,or would you life to invest your effort in doing something else like process enhancement and modification. The point being, one can also write POJOs for maintaining BAM databases and generate reports, but as a developer commisioned to architect/ build a business process, why would one invest his/her energies in developing BAM like features?
    Thanks and Regards
    Vivek Nandey
    BEA Certified Developer for Integration Solutions

  • Problem building WLI 10.2 applications with exported ant build files

    Hello,
    I'm trying to build a WLI application without the workshop IDE. To accomplish this I exported ant build files, workspace.xml and the workspace libraries.
    When I run the build, I get the following (part of the) stacktrace:
    [apt] Compiling 8 source files to C:\development\BuildOFOP\workspace\ContractAccountService-Web\build\classes
    [apt] warning: Annotation types without processors: [com.bea.wli.transform.XQueryTransform.SchemaValidate]
    [apt] java.io.FileNotFoundException: File not found
    [apt] at java.util.zip.ZipFile.open(Native Method)
    [apt] at java.util.zip.ZipFile.<init>(ZipFile.java:117)
    [apt] at java.util.zip.ZipFile.<init>(ZipFile.java:76)
    [apt] at com.bea.wli.bpm.bean.codegen.JarHelper.unJar(JarHelper.java:31)
    [apt] at com.bea.wli.bpm.bean.codegen.ResourceConfig.configureEjbJars(ResourceConfig.java:749)
    [apt] at com.bea.wli.bpm.bean.codegen.ResourceConfig.configureEjbJars(ResourceConfig.java:704)
    [apt] at com.bea.wli.bpm.compiler.JpdAnnotationProcessor.generateBeans(JpdAnnotationProcessor.java:343)
    [apt] at com.bea.wli.bpm.compiler.JpdAnnotationProcessor.generate(JpdAnnotationProcessor.java:56)
    [apt] at com.bea.wli.knex.ap.TwoPhaseAnnotationProcessor.process(TwoPhaseAnnotationProcessor.java:103)
    [apt] at com.sun.mirror.apt.AnnotationProcessors$CompositeAnnotationProcessor.process(AnnotationProcessors.java:60)
    [apt] at com.sun.tools.apt.comp.Apt.main(Apt.java:454)
    [apt] at com.sun.tools.apt.main.JavaCompiler.compile(JavaCompiler.java:448)
    [apt] at com.sun.tools.apt.main.Main.compile(Main.java:1075)
    [apt] at com.sun.tools.apt.main.Main.compile(Main.java:938)
    [apt] at com.sun.tools.apt.Main.processing(Main.java:95)
    [apt] at com.sun.tools.apt.Main.process(Main.java:43)
    [apt] at com.sun.tools.apt.Main.main(Main.java:34)
         [apt] Problem encountered during annotation processing;
    [apt] see stacktrace below for more information.
    [apt] java.lang.IllegalStateException: Error customizing project beans; could not locate weblogic home null
    [apt] at com.bea.wli.bpm.bean.codegen.ResourceConfig.configureEjbJars(ResourceConfig.java:769)
    [apt] at com.bea.wli.bpm.bean.codegen.ResourceConfig.configureEjbJars(ResourceConfig.java:704)
    [apt] at com.bea.wli.bpm.compiler.JpdAnnotationProcessor.generateBeans(JpdAnnotationProcessor.java:343)
    [apt] at com.bea.wli.bpm.compiler.JpdAnnotationProcessor.generate(JpdAnnotationProcessor.java:56)
    [apt] at com.bea.wli.knex.ap.TwoPhaseAnnotationProcessor.process(TwoPhaseAnnotationProcessor.java:103)
    [apt] at com.sun.mirror.apt.AnnotationProcessors$CompositeAnnotationProcessor.process(AnnotationProcessors.java:60)
    [apt] at com.sun.tools.apt.comp.Apt.main(Apt.java:454)
    [apt] at com.sun.tools.apt.main.JavaCompiler.compile(JavaCompiler.java:448)
    [apt] at com.sun.tools.apt.main.Main.compile(Main.java:1075)
    [apt] at com.sun.tools.apt.main.Main.compile(Main.java:938)
    [apt] at com.sun.tools.apt.Main.processing(Main.java:95)
    [apt] at com.sun.tools.apt.Main.process(Main.java:43)
    [apt] at com.sun.tools.apt.Main.main(Main.java:34)
    [apt] Caused by: java.io.FileNotFoundException: File not found
    [apt] at java.util.zip.ZipFile.open(Native Method)
    [apt] at java.util.zip.ZipFile.<init>(ZipFile.java:117)
    [apt] at java.util.zip.ZipFile.<init>(ZipFile.java:76)
    [apt] at com.bea.wli.bpm.bean.codegen.JarHelper.unJar(JarHelper.java:31)
    [apt] at com.bea.wli.bpm.bean.codegen.ResourceConfig.configureEjbJars(ResourceConfig.java:749)
    [apt] ... 12 more
    Anyone got any idea what might be the problem here? I did followed the BEA instructions for exporting the ant build files.
    Grtz, Jaco

    Hi
    This is a known issue addressed by CR205204
    As you said, IBM actually does not have rt.jar in its JDK - they have moved contents of rt.jar into various jars.
    IBM is not using org/apache/crimson/tree/ in their JDK at all.So the error shows up in the end of build even if it succeeds
    You may need to add crimson.jar to wlwBuild classpath, since it is not part of IBMs JDK.
    Note: the build will work even w/o crimson.jar giving a non build related IDE exception in the very end.
    Thanks
    Vimala

  • Accessing the MBean for ProcessRuntime(WLI) through WLST

    Since the cmo is not available for Custom MBeans and WLI MBeans are custom, how can I access or execute the methods for the MBean from WLST. I guess I can probably do it with the invoke command but the sytax foroperation invocation is not that intuitive. Is there another way i can access the ProcessRuntime Bean and invoke the methods directly.
    Thanks.

    Marc,
    This is just a guess(have'nt done this), but I think the settings are not an exception, and you should be able to find the MBean here:
    http://docs.oracle.com/cd/E17904_01/webcenter.1111/e12405/wcadm_intro.htm#BHCCJJED
    This section of the doc seems to walk through an example setting properties in adf-config.xml
    I would interpret those instructions in the official doc to mean :
    1. If you don't mind changing this at deploy time and re-deploying(like we do when we're in deep development), you can change this and redeploy.
    2. If you have a deployed application, you can make changes through WLST. But keep in mind that the changes you make through WLST will not be overwritten later when you change the adf-config in Jdev and redeploy.
    (This lets you fine tune the timeouts for specific environments. ex: bigger timeouts for dev envs hosted with smaller resources/unstable un-optimized code, rather than guess a timeout that works for all environments )
    Now comes the conflicting parts :
    "If you must modify these properties, post deployment, you must edit adf-config.xml manually."
    I think,they mean "manually using WLST". This can probabaly be done with both WLST commands and the MBeans.
    Now once you make these changes to a deployed application, the changes you made are stored in MDS. This means that this "tuning" will survive a re-deployment.
    So if we :
    set the timeout to 1 minute initially at design time,
    then change that to 5 minutes through WLST,
    and then edit adf-config again in Jdev to a 10 minute value and redeploy,
    the MDS still has the 5 minute value, and it will overwrite the 10 minute value we set later at design time and redeployed.
    MDS documents are always applied on top of the deployed stuff.
    The doc you refered to : http://docs.oracle.com/cd/E17904_01/webcenter.1111/e12405/wcadm_app_config_files.htm#CHDGEDGJ
    does make a good explanation of how the changes persisted in MDS affects the final configuration.
    Hop that helps !

Maybe you are looking for