Ruud Steeghs

Hi Guys,

Imagine you've built a Service Oriented Architecture, including business services implemented with BPEL. This BPEL service calls several other webservices.
Imagine you want to test your BPEL service with a time far from the current time. You want to test your service as if it's the year 2123 (or midnight, or Christmas); you want to travel in time.
How can you achieve a situation where all services (maybe even third-party services) act like it's the year 2123, or as if it's midnight, the end of the year)

Has anyone experience in this? Any idea's? Suggestions? Clues?

Thanks in advance,
Ruud

A friend told me:

IBM DB2 8.2 jdbc driver is db2jcc.jar.

dbFailOverEnabled ==> This flag should be set to true only if the backend database is configured with failover capability. This flag will indicate to WebSphere to validate connections when they first get created and to keep trying to get a good connection from the database when the validation fails.

connRetriesDuringDBFailover ==> This is useful only if dbFailOverEnabled flag is true. This property controls how many times WebSphere will try to get a connection from the database before giving up

connRetryIntervalDuringDBFailover ==> This is useful only if dbFailOverEnabled flag is true. This property controls the interval between retries to retrieve a connection from the database.

hi all,

Weblogic jdbc driver for db2 specifies the following properties (source: http://edocs.bea.com/wls/docs81/jdbc_drivers/db2.html):

Are these properties available for IBM DB2 XA enabled drivers?

ConnectionRetryCount:
The number of times the driver retries connection attemptsuntil a successful connection is established. Valid values are 0 and any positive integer.

ConnectionRetryDelay:
The number of seconds the driver will wait between connection retry attempts when ConnectionRetryCount is set to a positive integer.

Cheers,

Ruud.

Passed the SCEA pt I exam last thursday with 84%

Cheers,

Ruud.
SCJP
SCJD
SCBCD
SCWCD
SCEA pt I

We've got a clustered environment with two (maybe three) machines with 2 WAS instances on it. So we've got 4, maybe 6 WAS instances with the whole application deployed on each WAS instance.
There's a load balancer taking care of balancing the load of all requests to the WAS instances.

Is there any reason to use Remote SLSB's (being called from the web app)?

Cheers,

Ruud.

Hi,

Our system is a web application using SLSB's in a clustered environment on WAS 5.0 (with an upcoming upgrade to WAS 5.1)
Untill now we have used Remote SessionBeans.

Correct me if I am mistaken:
we can use Local EJB's (SLSB) when the web container and EJB container are running in the same JVM.

How can I determine if the web container and EJB container are running in the same JVM?
Is this something I can configure in WAS, where?

Regards,

Ruud
[ August 22, 2005: Message edited by: Ruud Steeghs ]

Hi,
Just passes Sun Certified Business Component Developer exam today with a 91% score.
I used Head First EJB to prepare for the exam and all of the non-commercial mock exams listed on the certification links page of the SCBCD-forum at javaranch (especially ejbcertificate.com)
In my opinion the exams in HFEJB and most of the mock-exams were more difficult than the real one. So if you pass the exam in HFEJB and ejbcertificate.com, feel sure to take the exam.
Regards,
Ruud Steeghs
SCJP, SCJD, SCWCD, SCBCD

hi JiaPei Jen:
here's an example of a config file:
log4j.category.com.company.myapp=DEBUG, FILE
log4j.category.com.company.myapp.Additivity=false
log4j.appender.FILE.Threshold=ERROR
log4j.appender.FILE=org.apache.log4j.RollingFileAppender
log4j.appender.FILE.File=E:/logging/MyApp/trace.log
log4j.appender.FILE.layout=org.apache.log4j.PatternLayout
log4j.appender.FILE.layout.ConversionPattern=MyApp %-5p %.25c %d{yyyyMMddHHmmss} %m%n
log4j.appender.FILE.MaxFileSize=5MB
log4j.appender.FILE.MaxBackupIndex=4
[ June 25, 2003: Message edited by: Ruud Steeghs ]

problem solved.
we've built an intranet application according to j2ee
architecure. log4j was being configured in an init-servlet and
that happens after ejb's are loaded (i guess...)
anyway, Loggers were initialised before log4j was
initialised properly.
solution: we're using a custom made wrapper for our
logging, in this wrapper object we initialise log4j
properly the first time a Logger is desired.

Hi,
I've configured log4j to log only error messages and info messages to a RollingFileAppender. Nice. However, all messages are also logged to the console and I would like to stop that, but don't know how.
Does anyone know how to stop logging to console?
Regards,
Ruud.

see jsptags.com
for a nice taglib

:-)
OJB is a JDO compliant API. (that's why I mentioned it here in this thread)
It is an Object Relational Mapping framework.
the pro's:
- You can easily program your queries and OJB returns classes or collections to you.
- No more converting JDBC results into Java classes.
- Queries are reduced to very little code.
- Transaction / locking management is easy.
cons:
Not all queries can be written using OJB. Some difficult queries (joins, date transformations) are still performed using JDBC. I' m not quite sure if those queries cannot be performed using OJB or it's just our inexperience.
However, over 90% of our queries are written using OJB
Cheers,
Ruud.

are you using any bc4j specific code or imports? then it won't be possible. if not, it should be possible.

the only way to add parameters to a request in code is to put them in the query string...
that means you have to obtain a request dispatcher and forward to youraction.do?par1=value1&par2=value2
Ruud.

right now we're using apchache OJB. I'm really enthusiastic about it.