Weblogic Integration - Timer Event

(Sorry about my english, but it isn't my native language)
Hi, I'm working with weblogic integration 8.1 sp6 and I didn't found enough documentation about Timer Event. When I'm creating a new Timer Event Generator, Weblogic Integration Administrative Console required 2 parameters (Generator Name and JMS Connection Factory JNDI Name), and JMS Connection Factory JNDI Name show three options (weblogic.jws.jms.QueueConnectionFactory, wli.internal.egrdms.XAQueueConnectionFactory and com.bea.wli.b2b.server.TopicConnectionFactory). My question is: What is the best "JMS Connection Factory JNDI Name" option?.
Thanks in advance.

Similar Messages

New article: Exploring the WebLogic Integration 8.1 RDBMS Event Generator

Dev2Dev has just published an article that you may be interested in:
Exploring the WebLogic Integration 8.1 RDBMS Event Generator
http://dev2dev.bea.com/pub/a/2007/02/rdbms-event-generator.html
If you'd like to write for Dev2Dev on a WebLogic Integration (or any other) topic, please contact me!
Regards,
Jon
Jon Mountjoy - Editor, Dev2Dev - http://dev2dev.bea.com/pub/au/13

If you are using a cluster you need to make sure the connection pool and data source are deployed on the admin server. I have had this problem many times before.

Weblogic Timer Event Generator - How it works?

Hello everyone!
I have wrote simple wli-application, that subscribes to the message broker channel.
I have deployed it to the cluster (managed servers 1 (ms1) and 2(ms2)). (I use Weblogic Server 10.3, cluster contains 1 admin server and 2 managed servers.)
Than I have created the timer event generator (EG) via wliconsole and rule for this EG - to send message to the MB-channel every 30 seconds.
Then I redeploy EG application via console (WLS Admin Console) from managed server 1 to cluster (m.servers 1 and 2) and start it.
Everything started ok - I got messages to both instatnces of my application in the following way:
15:30:00 - to instance on ms1
15:30:30 - to instance on ms2
15:31:00 - to instance on ms1
15:31:30 - to instance on ms2
...and so on
when I shut down ms2 - I started to receive messages to instance of my application on ms1 every 30 secodns. Here Everything is OK.
Then I start ms 2 and got the picture like:
15:30:00 - to instance on ms1
15:30:30 - to instance on ms2
15:31:00 - to instance on ms1
15:31:30 - to instance on ms2
...and so on
Then I shutdown ms1... And that's all - no messages to instance on ms2 :(
I started ms1 and no messages on both instances - on ms1 and ms2..
Can you explain me how Timer Event Generator works? What resources it uses? And how can I setup it to get load-balancing while both instances running and failover - when one of the instances shutdowned?
Thanks in advance,
Vladimir.

Hi Vladimir, it seems like we must have different environments. I don't know if you used the latest version of wli or not...
So, not exactly for you, but for someone who happens to read this post, and has the same problems we did...
-- I've configured the cluster address using the IP i've assigned to the servers.
--- it means that it is like: 192.168.70.120:8013,192.168.70.120:8113 - ip's & PORT, yes?
Yes, that's the format we are using (http://download.oracle.com/docs/cd/E13222_01/wls/docs92/cluster/setup.html#wp751583)
-- Configured the FrontEndHost and FrontEndPort with that same values as the AdminServer.
--- and you have the http-proxy deployed on your admin server? 'cause front-end host and port - must be the host and port of http-proxy that performs load-balancing for requests to your processes on your managed servers.
Actually we don't need the HTTP load balance, we only start the process via EG events, so we only benifit from load balancing on the JMS queues, but i had to configure this to be able to start the process. We had errors if we didn't configure this. We used the AdminServer address and port.
-- Relocated the Persistent Stores and JMS Servers since some were incorrectly pointing to the AdminServer.
---I didn't understand about what p.stores you are talking about.. I meant that you must create new JDBC p.store with table in cgDataSource and targeted to migratable target. And than you must create a new jms-server, which hosted to this p.store.
...But I didn't retarget any existing p.stores......
Once the domain was created (didn't do anything but to follow the wizard) we had the persistent stores (and underlying JMS servers) targeted to the AdminServer (obviously incorrect). So we retargeted them to the Managed Server.
-- Created the JSP_<PROCESS> table in the database.
--- and what is this? :)
We had to create a table to persist the wli process state, because it is a statefull process (http://download.oracle.com/docs/cd/E13214_01/wli/docs102/dbtuning/wliTuning.html)
The matter of fact is everything works fine, despite the exceptions i mentioned in the AdminServer, once it gets started... But it seems to have no negative impact on the application, and migration is done successfully
I will continue to work on figuring out what the origin of those exceptions is, and if i manage to find a solution i, most surely, will post it here... One thing i find to be strange is that the exceptions start even before i have anything deployed to the Migratable Target... Once i create it and restart the server i get those messages, and we tried the Concensus configuration with NodeManager, as well as the Database configuration.
I guess that what's really important for us now is that we do have fail over and load balancing working... :D
I don't know if it would be abusive to ask you for that document of yours, maybe it has some clue on what's wrong in our config, but again, i understand if you can't share that =)
By the way, i'm portuguese, but since google made the translator available, i guess i can manage russian documentation as well ;)
I can't tell you how gratefull i am for your help, and for sharing your previous experience with the rest of us. If it wasn't for your altruism i guess i would be stuck with this for much longer... you sure saved my day... BIG BIG thank you..
Once again, thank you and i wish you all the best !!! I just wished i could be helpfull to you sometime =)

Time event C019 integration with results recording

Hi ,
Posted this in the QM forum and got no response so reposting it here. I am asking for a discrete manufacturing scenario. Does any one know how to integrate CO19 time event confirmation with the results recording transaction. Usually on the mfg floor the mfg people will do in process inspection. They are used to more of a clock in clock out way of working. They clock into the operation, they do the manufacturing activities and then they do the inspection activities. Once both are done they clock out and the material moves to the next operation. I knoe we can tie in manufacturing confirmation (CO11N) transaction with the results recording for inspection points. But I am looking to tie in the CO19 time event transaction to do the clock in clock out and tie it with the inspection point results recording transaction. The operators on the floor do not want to go to mutliple transactions to record thier time on that operation. Do you know how that can be done and if its even possible ?
Also do we have to use inspection points or can we do it without inspection points ?.
Thanks

GS, Time events are always tied to a record group technically and this prohibits free/extended usage of the transaction compared to say CO11N.
Explore further on the details provided in the sap help site which states,
'You can only confirm quantities when you confirm processing time events.
You can only confirm activities that cannot be assigned to a particular record type group (Set-up,processing, teardown) by using the time event ‘Variable activity’. The confirmed value is assigned to corresponding value in the standard value key parameters'..

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)

Error in Timer Event.

Hi.
          I'm using WLI 9.2.1 and I need to start a process through a timer event, i.e. at a given time with no need for any special message.
          I've set up a timer event using "/WorklistEvent", the only one available, and it's message type is "rawData".
          The problem I have is that it seems that the message cannot be of rawData:
                    ####<10/Dez/2007 19H04m GMT> <Error> <WLI-Core> <wkasgff37> <AdminServer> <[ACTIVE] ExecuteThread: '19' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-16D1E0FC7E5929510567> <> <1197313440015> <BEA-489030> <Error publishing Timer Event message for amGFF : java.security.PrivilegedActionException: com.bea.wli.broker.MessageBrokerException: [WLI-Core:481031]The message-type for channel "/WorklistEvent" is defined as "rawData", which is not type-compatible with the message being published.>
                              I've tried to create another channel of type string but was unnable of doing so, since I could not find such an option on Sever Administrator Console and on Integration Administrator Console.
          What am I doing wrong?
          All help is welcome.

Hi,
          I recommend posting to a WLI newsgroup. This looks like a WLI specific code and error message and is not directly JMS related.
          Tom

Using WLST: Unable to create WLI Timer Event Generator

Hello,
I'm trying to create a WLST script, whcih will create Timer Event Generator on WLI 9.2 MP2.
Though to some extent script runs perfect, but it gives error when calling MBean egCfgMBean = getTarget("TimerEventGeneratorss/TimerEventGenerators")
Here is my script:-
import weblogic.Deployer
import com.bea.wli.mbconnector.timer as timereggen
import com.bea.wli.mbconnector.file as fileeggen
import com.bea.wli.management.configuration as wlicfg #Must have wli.jar in classpath
import java.lang.Boolean as bool
import jarray
import sys
print 'Starting the Timer Event Generation Configuration script .... '
if connected != 'true':
print 'Connecting to weblogic server .... '
connect(userName,passWord,URL)
else:
print 'Connected'
try:
print "Creating Timer EG ", timerEgName
timereggen.TimerConnGenerator.main(["-inName", timerEgName,"-outfile", domaindir + "/" + "WLITimerEG_" + timerEgName + ".jar"])
#timereggen.TimerConnGenerator.main(["-inName", timerEgName,"-outfile", domaindir,"-destJNDIName",jndiName])
#timereggen.TimerConnGenerator.main(["-inName", timerEgName,"-outfile", domaindir])
#wlst.config()
custom()
#egCfgMBean = wlst.getTarget("TimerEventGenerators/TimerEventGenerators")
egCfgMBean = getTarget("TimerEventGeneratorss/TimerEventGenerators")
egMBean = egCfgMBean.newTimerEventGenConfigurationMBean(timerEgName)
#egMBean = cmo.getTimerEventGenConfigurationMBeans()
cData = jarray.zeros(1, wlicfg.TimerEventGenChannelConfiguration)
print 'pass one'
cData[0] = wlicfg.TimerEventGenChannelConfiguration()
cData[0].setChannel(channel)
cData[0].setEffective(effectiveTime)
#cData[0].setExpiry(expiryTime)
cData[0].setFrequency(frequency)
cData[0].setMessageContent(message)
cData[0].setCalendarName(calendar)
cData[0].setPublishAsUser(publishAsUser)
egMBean.setChannels(cData);
appName = "WLITimerEG_" + timerEgName
deploy( appName, domaindir + "/" + appName + ".jar", adminServerName, "nostage" )
cd("Applications/" + appName)
set("LoadOrder", 1500)
cd("../..")
print "script returns SUCCESS"
except:
print "ERROR: configuration"
#dumpStack()
# Finished
print 'Disconnecting from server...'
disconnect('y')
print 'Finished.'
exit()
I really need some help to fix this issue.
Thanks
dig

Hi,
RDBMS Event Generator Channel Rule Definition
When you are creating channel rule definitions in the WebLogic Integration Administration Console, it is recommended that you do not use the Back button if you want to resubmit the details on a page.
You should always use the navigation links provided and create a new channel rule definition.
http://download.oracle.com/docs/cd/E13214_01/wli/docs85/deploy/cluster.html
http://download.oracle.com/docs/cd/E13214_01/wli/docs81/relnotes/relnotesLimit.html
http://otndnld.oracle.co.jp/document/products/owli/docs10gr3/pdf/deploy.pdf
This problem has been seen in the past when defining the channel rule for an RDBMS Event Generator if schema name was specified with the incorrect case (i.e. lowercase when it should have been uppercase or vice versa). To that end, it is suggested to change the case of the schema when creating the channel rule
Regards,
Kal

Issue with creating array of custom data type - WebLogic Integration

Hi,
We are doing WebLogic integration with Siebel for which from Siebel side we have generated java wrapper class which has all the methods, input\outputs defined and in\out params are serialized along with get\set methods. Following are the details of the input\output args.
Account_EMRIO.java
public class Account_EMRIO implements Serializable, Cloneable, SiebelHierarchy {
protected String fIntObjectFormat = null;
protected String fMessageType = "Integration Object";
protected String fMessageId = null;
protected String fIntObjectName = "Account_EMR";
protected String fOutputIntObjectName = "Account_EMR";
protected ArrayList <AccountIC> fintObjInst = null;
Above class also includes constructors\overloaded constructor\getters\setters
public AccountIC getfintObjInst() {
if(fintObjInst != null) {
return (AccountIC)fintObjInst.clone();
}else{
return null;
public void setfintObjInst(AccountIC val) {
if(val != null) {
if(fintObjInst == null) {
fintObjInst = new ArrayList<AccountIC>();
fintObjInst.add(val);
For the nested user defined data type AccountIC, it is defined in another java class as below
AccountIC.java
public class AccountIC implements Serializable, Cloneable, SiebelHierarchy {
protected String fname = null;
protected String fParent_Account_Id= null;
protected String fPrimary_Organization = null;
With the above, I was able to get all the AccountIC in the wsdl correctly and using this I was able to set the input param in the client
WSDL:
<xs:complexType name="accountEMRIO">
<xs:sequence>
<xs:element name="fIntObjectFormat" type="xs:string" minOccurs="0"/>
<xs:element name="fIntObjectName" type="xs:string" minOccurs="0"/>
<xs:element name="fMessageId" type="xs:string" minOccurs="0"/>
<xs:element name="fMessageType" type="xs:string" minOccurs="0"/>
<xs:element name="fOutputIntObjectName" type="xs:string" minOccurs="0"/>
<xs:element name="fintObjInst" type="tns:accountIC" minOccurs="0"/>
</xs:sequence>
<xs:complexType name="accountIC">
<xs:sequence>
<xs:element name="fName" type="xs:string" minOccurs="0"/>
<xs:element name="fParent_Account_Id" type="xs:string" minOccurs="0"/>
<xs:element name="fPrimary_Organization" type="xs:string" minOccurs="0"/>
minOccurs="0"/>
</xs:sequence>
</xs:complexType>
Now, I wanted to make slight difference in getter method of class Account_EMRIO method getfintObjInst so that an array of AccountIC is retured as output.
public ArrayList<AccountIC> getfintObjInst() {
if(fintObjInst != null) {
return (ArrayList<AccountIC>)fintObjInst.clone();
}else{
return null;
With the above change, once the wsdl is generated, I am no longer getting fintObjInst field for AccountIC due to which I am unable to get the array list of accountIC
WSDL:
<xs:complexType name="accountEMRIO">
<xs:sequence>
<xs:element name="fIntObjectFormat" type="xs:string" minOccurs="0"/>
<xs:element name="fIntObjectName" type="xs:string" minOccurs="0"/>
<xs:element name="fMessageId" type="xs:string" minOccurs="0"/>
<xs:element name="fMessageType" type="xs:string" minOccurs="0"/>
<xs:element name="fOutputIntObjectName" type="xs:string" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
The issue that I am facing here is, we have a custom data type(AccountIC) which has several fields in it. In the output I need a array of AccountIC. In the java bean, when this type was defined as
protected ArrayList <AccountIC> fintObjInst = null; I was unable to get a array of AccountIC. this gets complicated as inside a AccountIC there is array of contacts as well and all the time I am getting just the first records and not a array.
To summarize: How to get xsd:list or maxoccurs property for a field in WSDL for the user defined\custom datatype?
Can someone help me with this.
Thanks,
Sudha.

can someone help with this??

Weblogic Integration 10r3 error in msg-header-2_0.xml

Hello,
I am trying to go through te WLI workshops, but cannot publish a WLI process.
The Tutorial_Process_Application RequestQoute.java has the following error in the msg-header-2_0.xml:
Severity and Description Path Resource Location Creation Time Id
Referenced file contains errors (http://www.w3.org/TR/1999/REC-html401-19991224/strict.dtd). For more information, right click on the message and select "Show Details..." Tutorial_Process_Application_Utility/schemas/system msg-header-2_0.xsd line 1 1257804610777 410
A new WLI project from scratch gives te same error, it is as if the msg-header-2_0.xml is not correctly generated when the WLI process is created.

Aha! problem solved :)
The tutorial states : 'Select the Add WebLogic Integration System and Control Schemas to Utility Project check box to add the system schemas to the Schemas folder under the Utility project.'
If you do that it does not work, and i get the errors I discribed in the post, howerver if ypu leave it blanked out, the process can be published, without error or warnings.
As I am new to WLI (use to work with Oracle Bpel) I have no idea about the importance of adding the Integration system and control schemas to the utility project.
However as my goal is to work through the workshops, I wil worry about it later.
Edited by: DaveVQ on 14-nov-2009 5:39

Understanding Weblogic Integration 9.2

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

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

Weblogic Integration failed to build Cluster ENV

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

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

I need set up a timer Event for a Channel created

hi,
i need help set up the Timer Event in the Integrator Domain, the Channel is created
as is showed bellow :
<channels xmlns="http://www.bea.com/wli/broker/channelfile"
          channelPrefix="/CanalWicho"
          xmlns:eg="http://www.bea.com/wli/eventGenerator"
          xmlns:dp="http://www.bea.com/wli/control/dynamicProperties"
          xmlns:oagpo="http://www.openapplications.org/003_process_po_007">
     <channel name ="Samples" messageType="none">
     <channel name ="SampleEGTimerChannel" messageType="xml"
qualifiedMessageType="oagpo:PROCESS_PO_007"
     qualifiedMetadataType="eg:TimerEventGenerator"/>
the Timer Event is seting with period of 5 second, but this not execute in the
time expected, otherwise it´s execute only when i click submit on the timer Event
in the Integrator Console....

Are you sure you're using Adobe Reader? This code should work fine there.
On Feb 24, 2015 12:04 AM, "christies3837445" <[email protected]>

Weblogic Integration WLI adapters for Siebel

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

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

WebLogic Integrated Commons Logging - Necessary?

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

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

Weblogic Integration WLW Message Queue Problem

I am using BEA Weblogic Integration (BEA WLI). While testing processes, I get the following error on Weblogic Server Console:
<Feb 27, 2006 10:56:55 AM CET> <Warning> <WLW> <000000>
A message was unable to be delivered from a WLW Message Queue. Attempting to deliver the onAsyncFailure event
Please can you suggest what can be the problem.

The bridge does not do anything to the properties on the messages. It just sends the messages that it received from the WLS JMS queue to MQSeries queue.
Have you tried to receive directly from the WLS JMS queue and see if the receiver can retrieve the String property?
Dongbo

Weblogic Integration - Timer Event

Similar Messages

Maybe you are looking for