WLI Client

Need a java client which can access the WLI workflow. Tried using the WLPI class but I am unable to login using the GUI. I am alos unable to look up the EJBs as the JNDI names are not bound. Any pointers on how to lookup the EJBs and access the workflow ?
Thanks,
Prasad

below is some code to use WLI from a client. this is on version 7.
make sure to use the right user name and password. depending on the
configuration, a different user might be configured for the weblogic
server (wls) admin, and the weblogic integration (wli) admin. in the
integration samples server, the admin user is both the wls and wli admin
user and defaults to admin, security.
you should be able to lookup the beans described in
http://e-docs.bea.com/wli/docs70/devclient/import.htm#1025696
note that the jndi names are not the class names...i think i had to look
at the deployment descriptors to find them.
if you post your error it might help.
Properties p = new Properties();
p.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory");
p.put(Context.PROVIDER_URL, "t3://appserver:7001");
p.put(Context.SECURITY_PRINCIPAL, "admin");
p.put(Context.SECURITY_CREDENTIALS, "security");
Context ctx = null;
Admin admin = null;
WLPIPrincipal wlpiPrincipal = null;
try {
ctx = new InitialContext(p);
AdminHome adminHome = (AdminHome)ctx.lookup("com.bea.wlpi.Admin");
admin = adminHome.create();
WLPIPrincipalHome wlpiPrincipalHome =
(WLPIPrincipalHome)ctx.lookup("com.bea.wlpi.WLPIPrincipal");
wlpiPrincipal = wlpiPrincipalHome.create();
} catch(Exception ex){
ex.printStackTrace();
} finally {
// remember to remove them when done
try{ admin.remove(); } catch(Exception ex){}
try{ wlpiPrincipal.remove(); } catch(Exception ex){}
try{ ctx.close(); }catch(Exception ex){}
Prasad wrote:
Need a java client which can access the WLI workflow. Tried using the WLPI class but I am unable to login using the GUI. I am alos unable to look up the EJBs as the JNDI names are not bound. Any pointers on how to lookup the EJBs and access the workflow ?
Thanks,
Prasad

Similar Messages

  • WLI/JMS Message problem

    I have written a WLI client program that has JMS listeners for assigned, update,
    and remove WLI Notify messages. The basic format for each selector is simple:
    orgId = 'ORG1' and action = 'assigned'
    I've noticed an inconsistency when it comes to the JMS messages sent to my application.
    Say Task A is configured to be assigned to Joe when it's activated. When the
    task is actually activated, my client program receives an update message followed
    by an assign message (both for that task).
    Okay, here's where it gets tricky. Say the workflow returns to Task A later on
    in the same instance of the workflow. This time my client only gets an update
    JMS message. I have to account for this inconsistency in my code, which is not
    good.
    Is this a bug, or is there a reason that this is behaving like this?

    David
    Please open a case or provide your demo code to me, I will take a look
    when I get some free time
    Tony
    "David Mrozek" <[email protected]> wrote in message
    news:3b852200$[email protected]..
    >
    I have written a WLI client program that has JMS listeners for assigned,update,
    and remove WLI Notify messages. The basic format for each selector issimple:
    >
    orgId = 'ORG1' and action = 'assigned'
    I've noticed an inconsistency when it comes to the JMS messages sent to myapplication.
    >
    Say Task A is configured to be assigned to Joe when it's activated. Whenthe
    task is actually activated, my client program receives an update messagefollowed
    by an assign message (both for that task).
    Okay, here's where it gets tricky. Say the workflow returns to Task Alater on
    in the same instance of the workflow. This time my client only gets anupdate
    JMS message. I have to account for this inconsistency in my code, whichis not
    good.
    Is this a bug, or is there a reason that this is behaving like this?

  • What is the format for a Client Request JMS message.

    I am trying to send directly to the JMS queue to start a WLI process. From the Workshop browser, the message is received. However, when sending my own JMS message, WebLogic complains with an "Unexpected message format" onMessageException.
    What is the correct format for a WLI Client Request node? A text message? Please help. Thanks - Frank.

    Kai,
    Thanks for the info. I have created a MB channel and a JMS event generator. But now it seems that my problem has simply been moved further out. Case in point: If I send a simple XML text message to the JMS event queue, the WebLogic JPD throws a MBConnectorException ("Could not determine channel type").
    So I am wondering if this is still not the best practice to accomplish what I want. Should I be using a MDB which then simply calls a JCX control that knows how to talk to the WLI start node? The whole idea is that I want to start the workflow with a simple JMS message.
    Thanks in advance,
    Frank

  • JMS Listener

    Hi,
    I have written a WLI client program that has three listeners for assigned, update,
    and remove WLI Notify messages.
    The format for each selector is simple:
    orgId = 'ORG1' and action = 'assigned'
    orgId = 'ORG1' and action = 'update'
    orgId = 'ORG1' and action = 'remove'
    I notice that whenever a task is assigned to a user, the assign JMS message is
    preceded by an update JMS message. This is annoying and I would like to eliminate
    it. Any ideas?
    Thanks,
    Dave

    You could double-check in the JMS newsgroup, but I'm pretty sure that a statically configured listener like this would have to be in the classpath.
    If possible, I'd encourage you to consider using a MDB instead. That could be in your EAR file instead.
    -- Rob

  • Application view creation in WLI SERVER

              Hi folks,
              w,r.to my previous mail,Iam getting the following errors while i try to login
              to the Application view console in WLI
              Server.pl. anyone try to help me to sort this problem.Iam new to WLI Server.
              <Cannot startup connection pool "wliPool" java.sql.SQLException: No suitable driver>
              <Jun 13, 2003 5:02:45 PM IST> <Error> <JDBC> <001059> <Error during Data Source
              creation: weblogic.common.ResourceException: DataSource(WLAI_DataSource) can't
              be created with non-existent Pool (connection or multi) (wliPool)
              at weblogic.jdbc.common.internal.JdbcInfo.validateConnectionPool(JdbcInfo.java:127)
              at weblogic.jdbc.common.internal.JdbcInfo.startDataSource(JdbcInfo.java:260)
              at weblogic.jdbc.common.internal.JDBCService.addDeploymentx(JDBCService.java:293)
              at weblogic.jdbc.common.internal.JDBCService.addDeployment(JDBCService.java:270)
              <Jun 13, 2003 5:02:49 PM IST> <Alert> <JMS> <040052> <JMSServer "WLIJMSServer",
              store failed to open, java.io.IOException: JMS JDBC store, connection pool = <wliPool>,
              prefix = <myserver___PBPUBLIC>: connection pool does not exist.
              java.io.IOException: JMS JDBC store, connection pool = <wliPool>, prefix = <myserver___PBPUBLIC>:
              connection pool does not exist
              >
              <Jun 13, 2003 5:02:52 PM IST> <Error> <Connector> <190024> << Calumma LDAP JCA
              Resource Adapter_LdapConnector > Error making initial connections for pool. Reason:
              CreateManagedConnection Error: 192.168.66.144:389>
              <Jun 13, 2003 5:03:04 PM IST> <Error> <AI> <000000> <Failed to initialize the
              WLI-Application Integration enterprise application due to an exception while initializing
              JMS resources.
              com.bea.wlai.JMSResourceException: Failed to initialize the WLAI asynchronous
              service request JMS Queue 'WLAI_ASYNC_REQUEST_QUEUE' bound at JNDI context 'com.bea.wlai.ASYNC_REQUEST_QUEUE'.
              Root Cause: javax.naming.NameNotFoundException: Unable to resolve 'com.bea.wlai.ASYNC_REQUEST_QUEUE'
              Resolved: 'com.bea.wlai' Unresolved:'ASYNC_REQUEST_QUEUE' ; remaining name 'ASYNC_REQUEST_QUEUE'
              at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:174)
              at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:263)
              at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:230)
              at weblogic.jndi.internal.ServerNamingNode_WLStub.lookup(Unknown Source)
              at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:337)
              at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:332)
              at javax.naming.InitialContext.lookup(InitialContext.java:347)
              at com.bea.wlai.JMSHelper.initQueue(Unknown Source)
              <Jun 13, 2003 5:03:05 PM IST> <Critical> <WebLogicServer> <000286> <Failed to
              invoke startup class "LwcStartup", java.lang.ClassNotFoundException: com.bea.lwclient.Startup>
              <Jun 13, 2003 5:03:07 PM IST> <Notice> <Management> <141052> <Application Poller
              started for development server.>
              <Jun 13, 2003 5:03:11 PM IST> <Error> <HTTP> <101165> <Could not load user defined
              filter: com.bea.b2b.transport.http.TransportServletFilter
              java.lang.ClassNotFoundException: com.bea.b2b.transport.http.TransportServletFilter
              at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:179)
              at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:62)
              at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
              at java.lang.ClassLoader.loadClass(ClassLoader.java:262)
              at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:41)
              at weblogic.servlet.internal.WebAppServletContext.loadClass(WebAppServletContext.java:4714)
              at weblogic.servlet.internal.WebAppServletContext.registerFilter(WebAppServletContext.java:2446)
              at weblogic.servlet.internal.WebAppServletContext.initFilters(WebAppServletContext.java:2433)
              at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:2703)
              at weblogic.servlet.internal.HttpServer.preloadResources(HttpServer.java:563)
              at weblogic.servlet.internal.WebService.preloadResources(WebService.java:476)
              at weblogic.t3.srvr.ServletInitRunner$1.run(ServletInitRunner.java:50)
              at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:780)
              at weblogic.t3.srvr.ServletInitRunner.run(ServletInitRunner.java:46)
              at java.lang.Thread.run(Thread.java:536)
              >
              <Jun 13, 2003 5:03:11 PM IST> <Error> <socket> <000433> <Unable to load performance
              pack, using Java I/O instead.
              Please ensure that libmuxer library is in :'/home/tsuresh/j2sdk1.4.0/jre/lib/i386/client:/home/tsuresh/j2sdk1.4.0/jre/lib/i386:/home/tsuresh/j2sdk1.4.0/jre/../lib/i386'
              java.lang.UnsatisfiedLinkError: no muxer in java.library.path
              java.lang.UnsatisfiedLinkError: no muxer in java.library.path
              at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1410)
              at java.lang.Runtime.loadLibrary0(Runtime.java:772)
              at java.lang.System.loadLibrary(System.java:832)
              at weblogic.socket.PosixSocketMuxer.<init>(PosixSocketMuxer.java:180)
              at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
              at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
              at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
              at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
              at java.lang.Class.newInstance0(Class.java:296)
              at java.lang.Class.newInstance(Class.java:249)
              at weblogic.socket.SocketMuxer.makeTheMuxer(SocketMuxer.java:54)
              at weblogic.socket.SocketMuxer.getMuxer(SocketMuxer.java:37)
              at weblogic.t3.srvr.ListenThread.run(ListenThread.java:205)
              >
              <Jun 13, 2003 5:03:12 PM IST> <Notice> <Management> <141030> <Starting discovery
              of Managed Server... This feature is on by default, you may turn this off by passing
              -Dweblogic.management.discover=false>
              <Jun 13, 2003 5:03:12 PM IST> <Notice> <WebLogicServer> <000354> <Thread "ListenThread.Default"
              listening on port 7010>
              <Jun 13, 2003 5:03:12 PM IST> <Notice> <WebLogicServer> <000331> <Started WebLogic
              Admin Server "myserver" for domain "ldap_adapterdomain" running in Development
              Mode>
              <Jun 13, 2003 5:03:15 PM IST> <Notice> <WebLogicServer> <000365> <Server state
              changed to RUNNING>
              <Jun 13, 2003 5:03:15 PM IST> <Notice> <WebLogicServer> <000360> <Server started
              in RUNNING mode>
              <Jun 13, 2003 5:04:18 PM IST> <Error> <AI> <000000> <Could not create NamespacePersistence
              Object.
              -------- Begin level 0 Exception Stack Trace --------
              com.bea.wlai.repository.PersistenceException: Failed to initialize WLI repository
              access layer for the Application Integration subcomponent because the JDBC data
              source was not found at JNDI name WLAI_DataSource due to Unable to resolve 'WLAI_DataSource'
              Resolved: '' Unresolved:'WLAI_DataSource'
              at com.bea.wlai.repository.NamespacePersistence.initDataSource(Unknown
              Source)
              at com.bea.wlai.repository.NamespacePersistence.<init>(Unknown Source)
              at com.bea.wlai.NamespaceManagerImpl.<init>(Unknown Source)
              at com.bea.wlai.NamespaceManagerImpl.getInstance(Unknown Source)
              at com.bea.wlai.client.bean.NamespaceManagerBean.establishImpl(Unknown
              Source)
              at com.bea.wlai.client.bean.NamespaceManagerBean.ejbCreate(Unknown Source)
              at com.bea.wlai.client.bean.NamespaceManagerBean_k6j0cj_Impl.ejbCreate(NamespaceManagerBean_k6j0cj_Impl.java:122)
              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.ejb20.pool.StatelessSessionPool.createBean(StatelessSessionPool.java:151)
              at weblogic.ejb20.pool.StatelessSessionPool.getBean(StatelessSessionPool.java:101)
              at weblogic.ejb20.manager.StatelessManager.preInvoke(StatelessManager.java:142)
              at weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:127)
              at weblogic.ejb20.internal.StatelessEJBObject.preInvoke(StatelessEJBObject.java:61)
              at com.bea.wlai.client.bean.NamespaceManagerBean_k6j0cj_EOImpl.getRootNamespace(NamespaceManagerBean_k6j0cj_EOImpl.java:83)
              at jsp_servlet.__nshierarchy._jspService(__nshierarchy.java:115)
              at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
              at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1058)
              at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:401)
              at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
              at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:543)
              at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:369)
              at weblogic.servlet.jsp.PageContextImpl.include(PageContextImpl.java:136)
              at jsp_servlet.__display._jspService(__display.java:511)
              at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
              at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1058)
              rgds
              Suresh.K
              

    1) http://commerce.bea.com/showproduct.jsp?family=WLP&major=8.1&minor=4
              2)Make sure you add your JDBC drivers to the beginning of CLASSPATH in either setDomainenv.cmd or setEnv.cmd
              3)What really helped was BEA support and playing with BEA's JDBC example that shows how to create and deploy and use a data source.
              http://dev2dev.bea.com/codelibrary/code/examples_jdbc.jsp

  • Using WS-Security with Web Service Controls in WLI 8.1 SP3

    We have a process that calls a web service hosted on a .NET environment. The technique we have used is to generate a service control from the web service WSDL and call that control from a process. The web service is protected using a WS-Security usernameToken policy. The problem is that the .NET environment requires the wsse:Nonce and wsu:Created elements to be provided along with the token and I cannot see how I can specify this using a wsse policy file in WebLogic workshop. Does anyone have any advice for the best way to add this information to the security element in the SOAP header from within a WLI process? I've seen some example code for a java web service client, but that would not really fit with the control-based approach normally adopted in a WLI environment.

    You won't be able to do this using the WSSE file.
    An easy way to get around this is to use an XML Bean built from the WS-Security XML Schema. You'll have to read the WS-Security spec to determine how to create the nonce, but you'll be able to convert this XML Bean into the Element[] that the setOutputHeaders() method, which is on the service control you call the .NET Web Service with.
    Regards,
    Mike Wooten

  • URGENT*** Test Client testpoint not generated in WebLogic 10.3.0.0

    Hi,
    I have created very basic "Java EE 1.5 with support for jax-ws Annotations" web service and deploying in to web logic server 10.3.0.0. I am using Jdeveloper 11g for convert my java file to web service and deploying the same in to WLS directly from Jdev IDE.
    Problem is, I cant able to see "Test Client" testPoint in order to test my webservice. When I access my web service via WLS admin console can able to see only "?WSDL" test point at TESTING tab and WSDL is accessible. But Test client is not getting generated.
    Please help me, what am I missing here, why the WLServer not generating the test client. Am I missing any setting at server side. Please help me. Below is my web service code.
    package edu.ws;
    import javax.jws.WebService;
    *@WebService(serviceName = "demoWS", portName = "demoWSSoapHttpPort")*
    public class demoWS
    public demoWS()
    public String fullName(String fn, String ln)
    String fullName = fn + ln;
    return fullName;
    WSDL file:
    *<!--*
    Published by JAX-WS RI at http://jax-ws.dev.java.net. RI's version is Oracle JAX-WS 2.1.3-07/10/2008 08:41 PM(bt).
    -->
    *<!--*
    Generated by JAX-WS RI at http://jax-ws.dev.java.net. RI's version is Oracle JAX-WS 2.1.3-07/10/2008 08:41 PM(bt).
    -->
    *<definitions targetNamespace="http://ws.syu.edu/" name="demoWS">*
    *<types>*
    *<xsd:schema>*
    *<xsd:import namespace="http://ws.syu.edu/" schemaLocation="http://192.168.88.131:7001/DemoWebService-DemoWS-context-root/demoWSSoapHttpPort?xsd=1"/>*
    *</xsd:schema>*
    *</types>*
    *<message name="fullName">*
    *<part name="parameters" element="tns:fullName"/>*
    *</message>*
    *<message name="fullNameResponse">*
    *<part name="parameters" element="tns:fullNameResponse"/>*
    *</message>*
    *<portType name="demoWS">*
    *<operation name="fullName">*
    *<input message="tns:fullName"/>*
    *<output message="tns:fullNameResponse"/>*
    *</operation>*
    *</portType>*
    *<binding name="demoWSSoapHttpPortBinding" type="tns:demoWS">*
    *<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>*
    *<operation name="fullName">*
    *<soap:operation soapAction=""/>*
    *<input>*
    *<soap:body use="literal"/>*
    *</input>*
    *<output>*
    *<soap:body use="literal"/>*
    *</output>*
    *</operation>*
    *</binding>*
    *<service name="demoWS">*
    *<port name="demoWSSoapHttpPort" binding="tns:demoWSSoapHttpPortBinding">*
    *<soap:address location="http://192.168.88.131:7001/DemoWebService-DemoWS-context-root/demoWSSoapHttpPort"/>*
    *</port>*
    *</service>*
    *</definitions>*
    Thanks
    klogube

    Hi LJ,
    I did the same. I configured my WLS for development mode by making production_mode = false. But still I cant able to open http://localhost:7001/wls_utc window and so far cant able to test my WS :(
    Please check my config file and let me know where else I suppose to make the production mode false!!
    #!/bin/sh
    # WARNING: This file is created by the Configuration Wizard.
    # Any changes to this script may be lost when adding extensions to this configuration.
    # --- Start Functions ---
    BP=100
    SP=$BP
    pushd()
         if [ -z "$1" ]
         then
              return
         fi
         SP=`expr $SP - 1`
         eval _stack$SP=`pwd`
         cd $1
         return
    popd()
         if [ $SP -eq $BP ]
         then
              return
         fi
         eval cd \${_stack$SP}
         SP=`expr $SP + 1`
         return
    # --- End Functions ---
    # This script is used to setup the needed environment to be able to start Weblogic Server in this domain.
    # This script initializes the following variables before calling commEnv to set other variables:
    # WL_HOME - The BEA home directory of your WebLogic installation.
    # JAVA_VM - The desired Java VM to use. You can set this environment variable before calling
    # this script to switch between Sun or BEA or just have the default be set.
    # JAVA_HOME - Location of the version of Java used to start WebLogic
    # Server. Depends directly on which JAVA_VM value is set by default or by the environment.
    # USER_MEM_ARGS - The variable to override the standard memory arguments
    # passed to java.
    # PRODUCTION_MODE - The variable that determines whether Weblogic Server is started in production mode.
    # DOMAIN_PRODUCTION_MODE
    # - The variable that determines whether the workshop related settings like the debugger,
    # testconsole or iterativedev should be enabled. ONLY settable using the
    # command-line parameter named production
    # NOTE: Specifying the production command-line param will force
    # the server to start in production mode.
    # Other variables used in this script include:
    # SERVER_NAME - Name of the weblogic server.
    # JAVA_OPTIONS - Java command-line options for running the server. (These
    # will be tagged on to the end of the JAVA_VM and
    # MEM_ARGS)
    # For additional information, refer to the WebLogic Server Administration
    # Console Online Help(http://e-docs.bea.com/wls/docs103/ConsoleHelp/startstop.html).
    ORACLE_HOME="/opt/oracle/middleware/jdeveloper"
    export ORACLE_HOME
    WL_HOME="/opt/oracle/middleware/wlserver_10.3"
    export WL_HOME
    BEA_JAVA_HOME="/opt/oracle/middleware/jrockit_160_05"
    export BEA_JAVA_HOME
    SUN_JAVA_HOME=""
    export SUN_JAVA_HOME
    if [ "${JAVA_VENDOR}" = "BEA" ] ; then
         JAVA_HOME="${BEA_JAVA_HOME}"
         export JAVA_HOME
    else
         if [ "${JAVA_VENDOR}" = "Sun" ] ; then
              JAVA_HOME="${SUN_JAVA_HOME}"
              export JAVA_HOME
         else
              JAVA_VENDOR="BEA"
              export JAVA_VENDOR
              JAVA_HOME="/opt/oracle/middleware/jrockit_160_05"
              export JAVA_HOME
         fi
    fi
    # We need to reset the value of JAVA_HOME to get it shortened AND
    # we can not shorten it above because immediate variable expansion will blank it
    JAVA_HOME="${JAVA_HOME}"
    export JAVA_HOME
    SAMPLES_HOME="${WL_HOME}/samples"
    export SAMPLES_HOME
    DOMAIN_HOME="/opt/oracle/middleware/user_projects/domains/base_domain"
    export DOMAIN_HOME
    LONG_DOMAIN_HOME="/opt/oracle/middleware/user_projects/domains/base_domain"
    export LONG_DOMAIN_HOME
    if [ "${DEBUG_PORT}" = "" ] ; then
         DEBUG_PORT="8453"
         export DEBUG_PORT
    fi
    if [ "${SERVER_NAME}" = "" ] ; then
         SERVER_NAME="AdminServer"
         export SERVER_NAME
    fi
    POINTBASE_FLAG="false"
    export POINTBASE_FLAG
    enableHotswapFlag=""
    export enableHotswapFlag
    PRODUCTION_MODE="false"
    export PRODUCTION_MODE
    doExitFlag="false"
    export doExitFlag
    verboseLoggingFlag="false"
    export verboseLoggingFlag
    while [ $# -gt 0 ]
    do
         case $1 in
         nodebug)
              debugFlag="false"
              export debugFlag
         production)
              DOMAIN_PRODUCTION_MODE="true"
              export DOMAIN_PRODUCTION_MODE
         notestconsole)
              testConsoleFlag="false"
              export testConsoleFlag
         noiterativedev)
              iterativeDevFlag="false"
              export iterativeDevFlag
         noLogErrorsToConsole)
              logErrorsToConsoleFlag="false"
              export logErrorsToConsoleFlag
         nopointbase)
              POINTBASE_FLAG="false"
              export POINTBASE_FLAG
         doExit)
              doExitFlag="true"
              export doExitFlag
         noExit)
              doExitFlag="false"
              export doExitFlag
         verbose)
              verboseLoggingFlag="true"
              export verboseLoggingFlag
         enableHotswap)
              enableHotswapFlag="-javaagent:${WL_HOME}/server/lib/diagnostics-agent.jar"
              export enableHotswapFlag
              PROXY_SETTINGS="${PROXY_SETTINGS} $1"
              export PROXY_SETTINGS
         esac
         shift
    done
    MEM_DEV_ARGS=""
    export MEM_DEV_ARGS
    if [ "${DOMAIN_PRODUCTION_MODE}" = "true" ] ; then
         PRODUCTION_MODE="${DOMAIN_PRODUCTION_MODE}"
         export PRODUCTION_MODE
    fi
    if [ "${PRODUCTION_MODE}" = "true" ] ; then
         debugFlag="false"
         export debugFlag
         testConsoleFlag="false"
         export testConsoleFlag
         iterativeDevFlag="false"
         export iterativeDevFlag
    fi
    # If you want to override the default Patch Classpath, Library Path and Path for this domain,
    # Please uncomment the following lines and add a valid value for the environment variables
    # set PATCH_CLASSPATH=[myPatchClasspath] (windows)
    # set PATCH_LIBPATH=[myPatchLibpath] (windows)
    # set PATCH_PATH=[myPatchPath] (windows)
    # PATCH_CLASSPATH=[myPatchClasspath] (unix)
    # PATCH_LIBPATH=[myPatchLibpath] (unix)
    # PATCH_PATH=[myPatchPath] (unix)
    . ${WL_HOME}/common/bin/commEnv.sh
    WLS_HOME="${WL_HOME}/server"
    export WLS_HOME
    MEM_ARGS="-Xms256m -Xmx512m"
    export MEM_ARGS
    MEM_PERM_SIZE="-XX:PermSize=48m"
    export MEM_PERM_SIZE
    MEM_MAX_PERM_SIZE="-XX:MaxPermSize=192m"
    export MEM_MAX_PERM_SIZE
    if [ "${JAVA_VENDOR}" = "Sun" ] ; then
         if [ "${PRODUCTION_MODE}" = "" ] ; then
              MEM_DEV_ARGS="-XX:CompileThreshold=8000 ${MEM_PERM_SIZE} "
              export MEM_DEV_ARGS
         fi
    fi
    # Had to have a separate test here BECAUSE of immediate variable expansion on windows
    if [ "${JAVA_VENDOR}" = "Sun" ] ; then
         MEM_ARGS="${MEM_ARGS} ${MEM_DEV_ARGS} ${MEM_MAX_PERM_SIZE}"
         export MEM_ARGS
    fi
    if [ "${JAVA_VENDOR}" = "HP" ] ; then
         MEM_ARGS="${MEM_ARGS} ${MEM_MAX_PERM_SIZE}"
         export MEM_ARGS
    fi
    # IF USER_MEM_ARGS the environment variable is set, use it to override ALL MEM_ARGS values
    if [ "${USER_MEM_ARGS}" != "" ] ; then
         MEM_ARGS="${USER_MEM_ARGS}"
         export MEM_ARGS
    fi
    JAVA_PROPERTIES="-Dplatform.home=${WL_HOME} -Dwls.home=${WLS_HOME} -Dweblogic.home=${WLS_HOME} "
    export JAVA_PROPERTIES
    # To use Java Authorization Contract for Containers (JACC) in this domain,
    # please uncomment the following section. If there are multiple machines in
    # your domain, be sure to edit the setDomainEnv in the associated domain on
    # each machine.
    # -Djava.security.manager
    # -Djava.security.policy=location of weblogic.policy
    # -Djavax.security.jacc.policy.provider=weblogic.security.jacc.simpleprovider.SimpleJACCPolicy
    # -Djavax.security.jacc.PolicyConfigurationFactory.provider=weblogic.security.jacc.simpleprovider.PolicyConfigurationFactoryImpl
    # -Dweblogic.security.jacc.RoleMapperFactory.provider=weblogic.security.jacc.simpleprovider.RoleMapperFactoryImpl
    EXTRA_JAVA_PROPERTIES="-Ddomain.home=${DOMAIN_HOME} -Doracle.home=${ORACLE_HOME} -Doracle.security.jps.config=${DOMAIN_HOME}/config/oracle/jps-config.xml -Doracle.dms.context=OFF -Djava.protocol.handler.pkgs=oracle.mds.net.protocol ${EXTRA_JAVA_PROPERTIES}"
    export EXTRA_JAVA_PROPERTIES
    JAVA_PROPERTIES="${JAVA_PROPERTIES} ${EXTRA_JAVA_PROPERTIES}"
    export JAVA_PROPERTIES
    ARDIR="${WL_HOME}/server/lib"
    export ARDIR
    pushd ${LONG_DOMAIN_HOME}
    # Clustering support (edit for your cluster!)
    if [ "${ADMIN_URL}" = "" ] ; then
         # The then part of this block is telling us we are either starting an admin server OR we are non-clustered
         CLUSTER_PROPERTIES="-Dweblogic.management.discover=true"
         export CLUSTER_PROPERTIES
    else
         CLUSTER_PROPERTIES="-Dweblogic.management.discover=false -Dweblogic.management.server=${ADMIN_URL}"
         export CLUSTER_PROPERTIES
    fi
    if [ "${LOG4J_CONFIG_FILE}" != "" ] ; then
         JAVA_PROPERTIES="${JAVA_PROPERTIES} -Dlog4j.configuration=file:${LOG4J_CONFIG_FILE}"
         export JAVA_PROPERTIES
    fi
    JAVA_PROPERTIES="${JAVA_PROPERTIES} ${CLUSTER_PROPERTIES}"
    export JAVA_PROPERTIES
    # Clear the pre_classpath here in case an application template wants to set it before the larger pre_classpath is invoked below
    PRE_CLASSPATH=""
    export PRE_CLASSPATH
    JAVA_DEBUG=""
    export JAVA_DEBUG
    if [ "${debugFlag}" = "true" ] ; then
         JAVA_DEBUG="-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=${DEBUG_PORT},server=y,suspend=n -Djava.compiler=NONE"
         export JAVA_DEBUG
         JAVA_OPTIONS="${JAVA_OPTIONS} ${enableHotswapFlag} -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole..."
         export JAVA_OPTIONS
    else
         JAVA_OPTIONS="${JAVA_OPTIONS} ${enableHotswapFlag} -da"
         export JAVA_OPTIONS
    fi
    if [ ! -d ${JAVA_HOME}/lib ] ; then
         echo "The JRE was not found in directory ${JAVA_HOME}. (JAVA_HOME)"
         echo "Please edit your environment and set the JAVA_HOME"
         echo "variable to point to the root directory of your Java installation."
         popd
         read _val
         exit
    fi
    if [ "${POINTBASE_FLAG}" = "true" ] ; then
         DATABASE_CLASSPATH="${POINTBASE_CLASSPATH}"
         export DATABASE_CLASSPATH
    else
         DATABASE_CLASSPATH="${POINTBASE_CLIENT_CLASSPATH}"
         export DATABASE_CLASSPATH
    fi
    POST_CLASSPATH=""
    export POST_CLASSPATH
    POST_CLASSPATH="${ORACLE_HOME}/modules/features/adf.share_11.1.1.jar${CLASSPATHSEP}${POST_CLASSPATH}"
    export POST_CLASSPATH
    POST_CLASSPATH="${POST_CLASSPATH}${CLASSPATHSEP}${DATABASE_CLASSPATH}${CLASSPATHSEP}${ARDIR}/xqrl.jar"
    export POST_CLASSPATH
    # PROFILING SUPPORT
    JAVA_PROFILE=""
    export JAVA_PROFILE
    SERVER_CLASS="weblogic.Server"
    export SERVER_CLASS
    JAVA_PROPERTIES="${JAVA_PROPERTIES} ${WLP_JAVA_PROPERTIES}"
    export JAVA_PROPERTIES
    JAVA_OPTIONS="${JAVA_OPTIONS} ${JAVA_PROPERTIES} -Dwlw.iterativeDev=${iterativeDevFlag} -Dwlw.testConsole=${testConsoleFlag} -Dwlw.logErrorsToConsole=${logErrorsToConsoleFlag}"
    export JAVA_OPTIONS
    # -- Setup properties so that we can save stdout and stderr to files
    if [ "${WLS_STDOUT_LOG}" != "" ] ; then
         echo "Logging WLS stdout to ${WLS_STDOUT_LOG}"
         JAVA_OPTIONS="${JAVA_OPTIONS} -Dweblogic.Stdout=${WLS_STDOUT_LOG}"
         export JAVA_OPTIONS
    fi
    if [ "${WLS_STDERR_LOG}" != "" ] ; then
         echo "Logging WLS stderr to ${WLS_STDERR_LOG}"
         JAVA_OPTIONS="${JAVA_OPTIONS} -Dweblogic.Stderr=${WLS_STDERR_LOG}"
         export JAVA_OPTIONS
    fi
    # ADD EXTENSIONS TO CLASSPATHS
    if [ "${EXT_PRE_CLASSPATH}" != "" ] ; then
         PRE_CLASSPATH="${EXT_PRE_CLASSPATH}${CLASSPATHSEP}${PRE_CLASSPATH}"
         export PRE_CLASSPATH
    fi
    if [ "${EXT_POST_CLASSPATH}" != "" ] ; then
         POST_CLASSPATH="${POST_CLASSPATH}${CLASSPATHSEP}${EXT_POST_CLASSPATH}"
         export POST_CLASSPATH
    fi
    if [ "${WEBLOGIC_EXTENSION_DIRS}" != "" ] ; then
         JAVA_OPTIONS="${JAVA_OPTIONS} -Dweblogic.ext.dirs=${WEBLOGIC_EXTENSION_DIRS}"
         export JAVA_OPTIONS
    fi
    JAVA_OPTIONS="${JAVA_OPTIONS}"
    export JAVA_OPTIONS
    # SET THE CLASSPATH
    CLASSPATH="${PRE_CLASSPATH}${CLASSPATHSEP}${WEBLOGIC_CLASSPATH}${CLASSPATHSEP}${POST_CLASSPATH}${CLASSPATHSEP}${WLP_POST_CLASSPATH}"
    export CLASSPATH
    JAVA_VM="${JAVA_VM} ${JAVA_DEBUG} ${JAVA_PROFILE}"
    export JAVA_VM
    Edited by: klogube on Oct 23, 2009 10:58 AM

  • Struggling with Send XML to client

    Hi,
    I am using WL Process Integrator 2.1 with WL 6.1.
    I am trying to do do an example of the "Client Call Addin Response DTD" i.e. pass
    an XML document to an external java
    program.
    As given in docs :
    http://e-docs.bea.com/wli/docs70/devclient/appa.htm#1120726
    1. I have created a template definition
    2. Defined a XML doc. (as per the Client Callin Request DTD) and attached to ActionSendXMLToClient
    event as shown below.
    <call-addin name="mywlpi.addinimpl" mode="async">
    <actionid>959395846210</actionid>
    <parm>itemNumber</parm>
    </call-addin>
    3. "mywlpi.addinimpl" is a java program I created
    4. Now, the problem I run into is when I run from Worklist (Swing client program),
    it errors out saying it cannot find this
    class file:
    ClassNotFoundException: mywlpi.AddInImpl
    java.lang.ClassNotFoundException: mywlpi.AddInImpl
    at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
    5. I have included the class file in a .jar and included in the
    SVRCP of startWebLogic.cmd file. Also, when I create a Business
    Operation from Studio, I can locate this Java class. So, I am
    not sure what is missing. The strange part is when I run from the
    Worklist JSP page, it errors out saying :
    "Cannot execute this task, because it is already done." The task
    is not yet done.
    Is there someone who can help me here? Any suggestions
    appreciated!!
    Thanks,
    SLN

    Hi Sudhar.
    I don't think your workflow will execute the next node before you mark the current
    node as done. Conseqently setting the done in the decision box isn't possible.
    Giora
    "Sudhar" <[email protected]> wrote:
    >
    After I do the Send XML to Client from the exeucte tab of an action...instead
    of
    marking the task as done on the call back actions...i try to mark the
    same task
    as done in the next task after a decision box....it doesnt seem to work?
    any ideas? should you always mark a task as done on the same task?

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

  • SOAP Attachment & performances for WLI

    Dear all,
    I am implementing webservices, accepting a SOAP attachment as parameter. The implementation is based on Workshop / WLI jws file. The web service is RPC style since WorkShop is unable to generate a correct WSDL file with SOAP atttachment & document style (known limitation from BEA).
    My problem is concerning attachments. Indeed, in my mind, attaachement are there in order to prevent extra load into the XML parser and to speedup processing and avoid heavy use of memory.
    So I made some tests with a simple soap request and attachments. Here are the results (I calculate the time to send and receive response from web service), the web service itself just prints the content type, anything else.
    Attachement size | Time
    39 kb 344ms
    78 kb 406ms
    155 kb 484ms
    300 kb 750ms
    463 kb 1000ms
    1389 kb 4600ms
    2700 kb 23609ms
    5500 kb 140000ms
    Of course, the client and server are running on the same machine and are using the loopback interface. So there is no network bootleneck to take into account.
    As conclusion, we can see that for small messages, (<300kb) the curve is good... But performances start to fall drastically with messages larger than 300kb. This is not a problem of memory but CPU usage (fully used diring the 1400 seconds).
    Any idea, any opened cases ?
    Thansk for all,
    Pascal Bourgeois

    This post :
    http://soastuff.wordpress.com/2007/06/06/handling-opaque-datatypes-in-bpelesb/
    Describes how to use the opaque-schema for sending files over the ESB.
    Hope you can use this.
    or do you want to use the soap-headers for this?

  • Invoking wli process as web service

    Hello,
    I've developed a WLI process which I want to access as web service.
    I'm using conversation as explained in
    "How Do I: Tell Developers of Non-WebLogic Workshop Clients How to Participate in Conversations?"
    http://e-docs.bea.com/workshop/docs81/doc/en/core/index.html
    But I don't know how to access this web service and to set the conversationID in the SOAP header.
    Thanks a lot.
    Victor.

    I dont think what is the issue that you have here. Now there are multiple ways to expose a WLI process as a webservice.
    1. The WLI workshop allows you to direcly expose a .jpd file (process file) as a WSDL.
    2. In case you want you Web service to have multiple methods for different processes, create a process control from the .jpd file and then create a Weblogic Webservice using these controls.
    Hope this helps.

  • Transport Headers are not accessible at client

    Hi,
    We are using OSB 11g for sending message to external client.
    we are setting Headers "JMSType" in set Transport Header. but Client is not able to recieve the JMSType header at there side.
    we have read many forums for the same and turned on
    Pass all Headers through Pipeline
    Get All Headers
    then I put one publish action and keep my "Set Transport Header" inside that. still client is not able to find the same
    In out outbound request we can see the header as following.
    $outbound = <con:endpoint name="BusinessService$Notification$BusinessService$external$BUSINESSSERVICE:con="http://www.bea.com/wli/sb/context">
    <con:service/>
    <con:transport>
    <con:uri></con:uri>
    <con:mode>request</con:mode>
    <con:qualityOfService>exactly-once</con:qualityOfService>
    <con:request xsi:type="http:HttpRequestMetaData" xmlns:http="http://www.bea.com/wli/sb/transports/http" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <tran:headers xsi:type="http:HttpRequestHeaders" xmlns:tran="http://www.bea.com/wli/sb/transports">
    <tran:user-header name="JMSType" value="XXXXXXX">
    <http:Content-Type>text/plain; charset=utf-8</http:Content-Type>
    </tran:headers>
    <tran:encoding xmlns:tran="http://www.bea.com/wli/sb/transports">utf-8</tran:encoding>
    </con:request>
    <con:response xsi:type="http:HttpResponseMetaData" xmlns:http="http://www.bea.com/wli/sb/transports/http" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <tran:headers xsi:type="http:HttpResponseHeaders" xmlns:tran="http://www.bea.com/wli/sb/transports">
    <tran:user-header name="content-description" value="SOAP"/>
    <tran:user-header name="content-disposition" value="attachment;filename=&quot;[email protected]&quot;"/>
    <tran:user-header name="content-id" value="&lt;[email protected]>"/>
    <http:Cache-Control>proxy-revalidate</http:Cache-Control>
    <http:Connection>Keep-Alive</http:Connection>
    <http:Content-Length>112</http:Content-Length>
    <http:Content-Type>text/xml; charset=utf-8</http:Content-Type>
    <http:Date>Sun, 02 Sep 2012 04:06:43 GMT</http:Date>
    <http:Server>XXXXXXXXXerver>
    <http:Set-Cookie><![CDATA[<cookie-values xmlns="http://www.bea.com/wli/sb/transports/http">
      <value>JSESSIONID=m2RvGs2_Lvk_AZgyVJIv_e2-vSiFOQFi_mIA_SAPULGAKriCp_hbBD8uC0e8pEXt; Version=1; Path=/</value>
      <value>saplb_*=(spspiq_PIQ_00)6487650; Version=1; Path=/</value>
    </cookie-values>]]></http:Set-Cookie>
    </tran:headers>
    <tran:response-code xmlns:tran="http://www.bea.com/wli/sb/transports">0</tran:response-code>
    <tran:response-message xmlns:tran="http://www.bea.com/wli/sb/transports">OK</tran:response-message>
    <tran:encoding xmlns:tran="http://www.bea.com/wli/sb/transports">utf-8</tran:encoding>
    <http:http-response-code>200</http:http-response-code>
    </con:response>
    </con:transport>
    <con:security>
    <con:doOutboundWss>false</con:doOutboundWss>
    </con:security>
    </con:endpoint>

    It seems like you are setting JMSType header while calling an HTTP business service. What I see is that a header called JMSType is attached as a HTTP transport custom header and the target system should be able to fetch the JMSType as HTTP header. They should try to see on their side what exact message they are receiving.
    Also, why are you setting JMSType header when calling an HTTP service?

  • Cannot Deploy JPD with Timer Event Subscription in WLI 9.2 MP1 cluster

    Has anyone had any luck deploying a JPD with a timer event subscription to a 9.2 MP1 WLI cluster? I am able to deploy Synchronous Client Request JPDs without any trouble but the ones that rely on internal WLI queues for invocation will not deploy in production. I am able to deploy the problematic JPDs to a non-clustered development environment without any issues but when I try to deploy the same artifact to a 9.2 MP1 cluster I see the following error:
    Throwable: java.security.PrivilegedActionException: java.security.PrivilegedActionException: java.security.PrivilegedActionException: javax.management.InstanceNotFoundException: tosipDomain_phase2:Name=cgJMSServer,Type=JMSServer
    Stack Trace:
    java.security.PrivilegedActionException: java.security.PrivilegedActionException: java.security.PrivilegedActionException: javax.management.InstanceNotFoundException: tosipDomain_phase2:Name=cgJMSServer,Type=JMSServer
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:373)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at com.bea.wli.knex.runtime.core.bean.EJBGenerator.deployWorkshopQueues(EJBGenerator.java:178)
         at com.bea.wli.knex.runtime.core.dispatcher.DispResources.deployQueues(DispResources.java:727)
         at com.bea.wli.knex.runtime.core.dispatcher.DispCache.ensureDispUnit(DispCache.java:667)
         at com.bea.wli.knex.runtime.core.dispatcher.DispCache.ensureDispUnitForURI(DispCache.java:1025)
         at com.bea.wli.knex.runtime.core.dispatcher.DispCache.ensureDispUnitForURI(DispCache.java:946)
         at com.bea.wli.management.adminhelper.AdminHelperBean.getDispFile(AdminHelperBean.java:348)
         at com.bea.wli.management.adminhelper.AdminHelperBean.getProcessMetadata(AdminHelperBean.java:94)
         at com.bea.wli.management.adminhelper.AdminHelperSSB_wivmoo_EOImpl.getProcessMetadata(AdminHelperSSB_wivmoo_EOImpl.java:70)
         at com.bea.wli.management.adminhelper.AdminHelperSSB_wivmoo_EOImpl_WLSkel.invoke(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:548)
         at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:224)
         at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:438)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:434)
         at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:57)
         at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicServerRef.java:965)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    I am suprised about this error, b/c we are running out of a vanilla WLI domain created with the Configuration Wizard and the error message has to do with an internal JMS server that we have left with the default configuration. Has anyone else had success with this?
    On a side note, I have to complain about the lack of 9.2 WLI documentation about deploying applications to production. The links on e-docs.bea.com actually redirect you to 8.5 documentation?!? I can't believe that this is the documentation we are left to use for 9.2 because there are so many changes between WLS 8 and 9.

    Hey buddies,
    I have a very similar error on WLI 9.2 MP2 on development mode with a cluster of managed servers on the same machine. I'm afraid that the automatic resource creation feature of dev mode is creating the error.
    The ...processes.UnlockService is jpd called by a JMS Broker thru a channel, and I considering it as the first suspect point.
    Any help is welcome.
    LOG CONTENT:
    <May 15, 2008 8:04:57 PM GMT-03:00> <Notice> <Stdout> <000000> <2008-05-15 20:04:57,575 [PERFO] localServer 10.10.10.10 xMDA  [iid=15899 prd=TC DATA act=INSTALL otp=I onb=00011552111 cid=12345189 mrt=]  END Designar_TCDATA OK>
    <May 15, 2008 8:04:57 PM GMT-03:00> <Error> <WLI> <000000> <Exception processing com.oi.integra.provisioning.lockManager.processes.UnlockService
    java.security.PrivilegedActionException: java.security.PrivilegedActionException: java.security.PrivilegedActionException: javax.management.InstanceNotFoundException: granite_wli_dev:Name=cgJMSServer,Type=JMSServer
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:373)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at com.bea.wli.knex.runtime.core.bean.EJBGenerator.deployWorkshopQueues(EJBGenerator.java:178)
         at com.bea.wli.knex.runtime.core.dispatcher.DispResources.deployQueues(DispResources.java:727)
         at com.bea.wli.knex.runtime.core.dispatcher.DispCache.ensureDispUnit(DispCache.java:671)
         Truncated. see log file for complete stacktrace
    java.security.PrivilegedActionException: java.security.PrivilegedActionException: javax.management.InstanceNotFoundException: granite_wli_dev:Name=cgJMSServer,Type=JMSServer
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:373)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at com.bea.wli.knex.runtime.core.bean.EJBGenerator.ensureQueue(EJBGenerator.java:442)
         at com.bea.wli.knex.runtime.core.bean.EJBGenerator.ensureWorkshopQueues(EJBGenerator.java:412)
         at com.bea.wli.knex.runtime.core.bean.EJBGenerator$3.run(EJBGenerator.java:194)
         Truncated. see log file for complete stacktrace
    java.security.PrivilegedActionException: javax.management.InstanceNotFoundException: granite_wli_dev:Name=cgJMSServer,Type=JMSServer
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:373)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at com.bea.wli.knex.runtime.core.bean.EJBGenerator.doesQueueExist(EJBGenerator.java:359)
         at com.bea.wli.knex.runtime.core.bean.EJBGenerator$6.run(EJBGenerator.java:449)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         Truncated. see log file for complete stacktrace
    javax.management.InstanceNotFoundException: granite_wli_dev:Name=cgJMSServer,Type=JMSServer
         at weblogic.management.mbeanservers.compatibility.internal.MBeanHomeImpl.getProxy(MBeanHomeImpl.java:68)
         at weblogic.management.mbeanservers.compatibility.internal.MBeanHomeImpl.getMBean(MBeanHomeImpl.java:88)
         at weblogic.management.mbeanservers.compatibility.internal.MBeanHomeImpl.getAdminMBean(MBeanHomeImpl.java:265)
         at com.bea.wli.knex.runtime.core.bean.WLSUtil.getWorkshopJMSServer(WLSUtil.java:713)
         at com.bea.wli.knex.runtime.core.bean.EJBGenerator$5.run(EJBGenerator.java:372)
         Truncated. see log file for complete stacktrace
    >
    java.security.PrivilegedActionException: java.security.PrivilegedActionException: java.security.PrivilegedActionException: javax.management.InstanceNotFoundException: granite_wli_dev:Name=cgJMSServer,Type=JMSServer
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:373)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)

  • Jsp implementation of the worklist client for weblogic 6.0

    Hi
    Please find attached a demo version of how you can implement a JSP based
    worklist client. This code is simply for demonstration/reference purposes
    only but it illustrates how to implement a JSP client to the BPM product.
    This application is not covered under support.
    To install the product simply extract the attachment ( a war file ) and
    place it in the applications directory of your weblogic deployment, for
    example
    d:\bea\wlserver6.0\config\mydomain\applications.
    To run the worklist client enter the following url in your browser
    http://localhost:7001/worklist
    This code will also be placed on the BEA development centre.
    Again, it must be re-iterated that although testing of the code has been
    done this is not a production application and it's sole purpose it provide
    examples of how to use the wlpi-worklist api. in a web environment.
    Any questions, comments or updates to this code are welcome and should
    be posted to the newsgroup.
    Thanks and enjoy
    Tony
    [worklist.war]

    Bart
    Yes I do
    Tony
    "Bart Jenkins" <[email protected]> wrote in message
    news:3b8bd563$[email protected]..
    Tony,
    Don't you mean that the target location of the .WAR file should be:
    C:\bea\wlintegration2.0\processintegrator\config\mydomain\applications
    (Assuming you have elected the default folders for the WLI BPMinstallation
    location)
    Bart Jenkins, CTO
    Globeflow SA
    "tony lodge" <[email protected]> wrote in message
    news:[email protected]..
    Hi
    Please find attached a demo version of how you can implement a JSPbased
    worklist client. This code is simply for demonstration/reference
    purposes
    only but it illustrates how to implement a JSP client to the BPMproduct.
    This application is not covered under support.
    To install the product simply extract the attachment ( a war file )and
    place it in the applications directory of your weblogic deployment, for
    example
    d:\bea\wlserver6.0\config\mydomain\applications.
    To run the worklist client enter the following url in your browser
    http://localhost:7001/worklist
    This code will also be placed on the BEA development centre.
    Again, it must be re-iterated that although testing of the code hasbeen
    done this is not a production application and it's sole purpose it
    provide
    examples of how to use the wlpi-worklist api. in a web environment.
    Any questions, comments or updates to this code are welcome andshould
    be posted to the newsgroup.
    Thanks and enjoy
    Tony

  • Exception during commit of transaction in wli when using oracle database

    I have configured oracle Database instead of pointbase in wli 9.2
    While getting the response through callback in wli process (from Worklist console)this errror is coming "Exception occurred during commit of transaction ".
    What should I do to remove this error??
    Stack trace is
    <Jan 6, 2007 5:19:59 PM CST> <Error> <EJB> <BEA-010026> <Exception occurred during commit of transac
    tion Xid=BEA1-012806F477B49C8F6264(7312912),Status=Rolled back. [Reason=weblogic.utils.NestedRuntime
    Exception: Error in beforeCompletion],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=
    0,seconds left=60,XAServerResourceInfo[WLStore_oracle1domain_cgJMSStore]=(ServerResourceInfo[WLStore
    oracle1domaincgJMSStore]=(state=rolledback,assigned=AdminServer),xar=WLStore_oracle1domain_cgJMSSt
    ore1269044,re-Registered = false),XAServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(Ser
    verResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(state=rolledback,assigned=AdminServer),xar
    =weblogic.jdbc.wrapper.JTSXAResourceImpl@14c0a31,re-Registered = false),SCInfo[oracle1domain+AdminSe
    rver]=(state=rolledback),properties=({weblogic.jdbc=t3://199.81.36.226:7001}),local properties=({mod
    ifiedListeners=[weblogic.ejb.container.internal.TxManager$TxListener@1442c7b], class com.bea.wli.bpm
    .runtime.JpdContainer$TxnListener1168125300187=com.bea.wli.bpm.runtime.JpdContainer$TxnListener@1313
    24d}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=AdminServer+199.8
    1.36.226:7001+oracle1domain+t3+, XAResources={WLStore_oracle1domain_cgJMSStore, WLStore_oracle1domai
    n_WseeFileStore, WLStore_oracle1domain__WLS_AdminServer, weblogic.jdbc.wrapper.JTSXAResourceImpl},No
    nXAResources={})],CoordinatorURL=AdminServer+199.81.36.226:7001+oracle1domain+t3+): weblogic.transac
    tion.RollbackException: Unexpected exception in beforeCompletion: sync=weblogic.ejb.container.intern
    al.TxManager$TxListener@1442c7b
    Error in beforeCompletion
    at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java
    :1782)
    at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.
    java:331)
    at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:227
    at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:463)
    at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:335)
    at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:291)
    at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4060)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:3953)
    at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4467)
    at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    .>

    Did you get a solution to this problem ?I am seeing similar exceptions intermittently .
    Thanks,
    Meena.

Maybe you are looking for

  • Presentation Director Monitor Drop Down Menus Blank

    I'm trying to get Presentation Director functioning properly, but there are a couple of screwy things going on: If I check the properties of the "Capture" profile, it has the resolution of external monitor incorrect. (1920 x 1200 Vs Captured 1024X768

  • Sync existing contacts from Adressbook.app with iPhone fails

    Hi! Syncing works as advertised between my Mac, .Mac, Addressbook.app and my iPhone for ALL NEW CONTACTS, no matter where they are created (iPhone or Mac). However ... if I choose to sync an old contact from Adressbook.app with iPhone the sync proces

  • Preparation for Consolidation using EC-CS

    Dear FI/CO experts, We have a huge chunk of  AR/AP/GL open items with wrong or missing values for trading partner (VBUND), profit center(PRCTR) and partner profit center(PPRCTR) fields. We implemented EC-CS in our organization and need to rectify or

  • I've lost the keyboard for texting

    I've lost the keybord for texting

  • How do I get the javax woring....Please help

    Hi, I have a program called "controller.java" Everytime when I commpile it, it keep saying that the package javax.serlet does not exist. I have both the j2sdkee1.3.1 and te j2sdk1.4.0_01. What do I need to do to get the machine recognizing the packag