Jan Kester Blog

Logging in selenium

2012-03-05T11:29:00.000+01:00

For some time I am trying to get more out of Selenium. Lot has changed here: selenium2 is a big improvement, and since 2.15 google also contributed its Advanced User Interactions API to the selenium code base, which seems to be a big improvement for mouse handling.
To get a better understanding of what is happening, and especially why my test scripts are failing, I wanted to control the logging of my webdriver. I noticed that this was a bit of a pain. Selenium firefox driver is using java.util.logging. So you are bound to the mechanisms that java.util.logging offers you for log configuration.

This is the approach I ended up with.

Before I startup my Firefox Webdriver, I used the setLogLevel method to set the Level of logging that is used for all driver logs. When you set this to WARNING, all logs that the driver makes, are considered to be WARNING logs, when you set them to FINE, all logs are considered to be FINE logs. So dependent on the settings inside your logging.properties, you will see these logs appear in your system out or not. I put the level to INFO, and now they are always appearing in my system.out output. During test development I do not mind. I will switch if off though when I move scripts to an automatic build environment.
To change the settings for java.util.logging, you can either configure the file under java_home/jre/lib, or set the config file explicitly over the command line with -Djava.util.logging.config.file=myfile.

I am still interested in routing Java Util Logging (JUL) to log4j. Maybe this is a solution:
http://www.slf4j.org/legacy.html#jul-to-slf4j

Junit4 running parallel junit classes

2011-10-19T08:28:00.000+02:00

To run junit testcases parallel, you can create your own class to run junit with:

Add this tag to your class declaration.

@RunWith(Parallelized.class)

Implementation of this class looks like:

package mypackage;
import java.util.concurrent.ExecutorService;
import java.util.concurrent.Executors;
import java.util.concurrent.TimeUnit;

import org.junit.runners.Parameterized;
import org.junit.runners.model.RunnerScheduler;

public class Parallelized extends Parameterized
{
    
    private static class ThreadPoolScheduler implements RunnerScheduler
    {
        private ExecutorService executor; 
        
        public ThreadPoolScheduler()
        {
            String threads = System.getProperty("junit.parallel.threads", "16");
            int numThreads = Integer.parseInt(threads);
            executor = Executors.newFixedThreadPool(numThreads);
        }
        
        public void finished()
        {
            executor.shutdown();
            try
            {
                executor.awaitTermination(10, TimeUnit.MINUTES);
            }
            catch (InterruptedException exc)
            {
                throw new RuntimeException(exc);
            }
        }

        public void schedule(Runnable childStatement)
        {
            executor.submit(childStatement);
        }
    }

    public Parallelized(Class klass) throws Throwable
    {
        super(klass);
        setScheduler(new ThreadPoolScheduler());
    }
}

Now inside your test class, you will need to create a method with

@Parameters

tag declaration, that feeds the constructor:

    public PocAddPoiTest(String browser) {
        super();
        this.browser = browser;
    }

    @Parameters
    public static Collection browsersStrings() {
        // return Arrays.asList(new Object[][] { { "*firefox" },
        // { "*googlechrome" } });
        return Arrays.asList(new Object[][] { { "*firefox","*iexplore" } });
    }

When junit gets started, it will run two tests parallel.

Not sure how it handles output .. :-).

Run jmeter from eclipse

2011-09-22T17:51:00.001+02:00

Download jmeter source and binaries:http://archive.apache.org/dist/jakarta/jmeter/binaries/jakarta-jmeter-2.3.4.zip http://archive.apache.org/dist/jakarta/jmeter/source/jakarta-jmeter-2.3.4_src.zip

Unpack jmeter source file, and rename eclipse.classpath into .classpath.Add a .project file to the same directory:

<?xml version="1.0" encoding="UTF-8"?>
<projectDescription>
  <name>jakarta-jmeter-2.3.4</name>
  <comment></comment>
  <projects>
  </projects>
  <buildSpec>
    <buildCommand>
      <name>org.eclipse.jdt.core.javabuilder</name>
      <arguments>
      </arguments>
    </buildCommand>
  </buildSpec>
  <natures>
    <nature>org.eclipse.jdt.core.javanature</nature>
  </natures>
</projectDescription>

Now import the source code as eclipse project.

Add all libs of binary distribution (lib/*.jar) to the new project's lib dir.
Add all files, except ApacheJmeter.jar (bin/**/*) to the new project's bin dir.

Clean eclipse project.
Run ant package on the build.xml file to create the RMI jars.

Create a launcher for org.apache.jmeter.NewDriver and set arguments/working directory to: ${workspace_loc:jakarta-jmeter-2.3.4/bin}.
When you start the launcher, jmeter comes up.

With the same configuration you can also debug. Add a debug breakpoint to for instance:org.apache.jmeter.engine.StandardJMeterEngine.runTest()
Start your debug session now, and run example script. It will wait when you start a test run.

To debug your own project (with sampler for instance):

make your own project dependent on jakarta-jmeter project
check that all jars from jakarta-jmeter project are exported
duplicate the launcher of above, but replace project by your own now
make sure your working directory is still pointing to jakarta-jmeter project's bin directory
check that your own src directory of sampler is on the classpath of the launcher
launch jmeter with this project's launcher
add debug breakpoints to sampler's code

Debugging against jmeter

2011-09-22T16:56:00.000+02:00

Inside jmeter startup script, add:


set DEBUGJDWP=-agentlib:jdwp=transport=dt_socket,address=localhost:9009,server=y,suspend=y
set ARGS=%DUMP% %HEAP% %NEW% %SURVIVOR% %TENURING% %EVACUATION% %RMIGC% %PERM% %DDRAW% %DEBUGJDWP%

Now start jmeter. It will hang and wait for debugger.

In eclipse, add a new remote java application debug configuration.Add jmeter source code to it. Connect.Jmeter will start now.

Attach jmeter source code. Lookup class:


org.apache.jmeter.engine.StandardJMeterEngine

Set debug point in runTest() method and start your script.

Good principles of test automation

2011-08-03T14:57:00.000+02:00

Core principles of good tests
When you start automating your tests, there a few important principles to stick to.

Reliable
First your tests must be reliable. This means that they must repeatable and always give the same results. They should not contain any environment dependencies, and be executable on any environment. To get this working, all hard-coded settings must be configurable, a maven or ant script is required to build and configure the test environment, and all code, test date and configuration scripts must be checked in source code repository. Having reliable tests that run everywhere and always, also means that your tests must take care to setup necessary test data, and clean it afterward again.

Fast
Next, it would be nice when your tests are fast. In the lifetime of a project you will build up ever more tests; with every next sprint you will need to run more tests. You can't run all your tests on check-in, and for certain groups of tests need to schedule test execution times at less regular intervals.

Self explaining tests
Also your tests should be easy to understand, and have clean reports. Easy to understand means that an outsider can quickly understand what the test is about. Proper naming helps a lot here, additionally you can add document tags to the comments. It also helps to stick to the domain language so that it is easy to map test cases to use cases.

Clean reports
Test reports should have a clean baseline. Try to avoid including known bugs, as they clog up the test results, and make the news bugs less visible. Also in your asserts add meaningful log statements that help finding the root cause of the failure.

Continous integration
Further you want your tests be integrated in continous integration build process. You will probably want to create several groups and have some of these more frequently executed than others. Once you have them running automatically, you are sure that they actually get executed, and you also make sure that they are really reproducible. Before you add your tests to CI you must make sure though that your test reports have a clean baseline. Else people will ignore the test reports.

Continuous integration of test environment setup
Deployment and execution of tests in CI environments is the easy part. Far more difficult it may be to set up and configure your test environment. This includes setting up your application server, initialising your database, starting your application server, deploying your application and configuration of appl server and application. This will require a lot of specialist knowledge.
One step further you may also want to mock your connection proxies to external connections. This may be for instance a credit card provider. You don't want to send your payments that you generate in tests to a real provider. So you will need to mock the provider's functionality and have your test environment set up with this mock interface instead of the real one.

Testability
A last point of attention concerns testability. Some of your application's functionality may be difficult to test as you can't reach it with your testing code. Examples could be a status of an object that you have just changed, and can only be checked by a UI application. As a tester you would like to have direct access to this functionality, so that you can use it for the asserts of the test. These testability functionalities are additional requests to the developers. They will need to build it in the code, just for the sake of testing. Other important testability examples are: fixed IDs for html elements, or some deleteFunctionality to clean up test generated objects.

Test automation in agile

2011-08-03T14:54:00.000+02:00

Test automation importance
With our change to agile, we have made an important paradigm shift. In the old days we would stick to our planned roadmap, and compromise either on delivery dates or software quality. In Agile software development we are willing to compromise on scope, but not on software quality or delivery dates. This means in short: no code goes out untested.

What tests to execute?
It is nearly impossible to test everything. There are so many types of tests, like: regression, story acceptance, developer, integration, usability, performance, security, upgrade, user acceptance etc. In our release planning, we must make a conscious decision which of those types we want to execute. Some of the test types may require additional experts, some of the tests may not be relevant, some may be just too costly.

The usual scrum testsWithin our sprints, we tend to stick to regression tests, story acceptance tests, developer tests and integration tests. Developer tests are internal component tests, that test a component directly without the need of other components. Integration tests review the interaction between two or more components. Story acceptance tests verify the acceptance criteria. Regression tests are the story acceptance tests of previous sprints and may also include parts of the integration tests.

Which tests to automate?
For some tests it may not make sense to automate. Will the test ever be executed again? If not, then it will probably not pay off to automate it. Also consider the cost of test automation versus the time needed to test manually. Especially for UI tests, it may be cheaper to do manual tests. Drag and drop, and visual control of the result are very hard to automate. For normal webforms or low level service tests, automation is efficient.

What are the risks of not automating?
It is likely, that those tests that we decided not to automate, will not be executed in future sprints. So future sprints may break existing functionality without us knowing it. With less test coverage, we will get afraid to refactor our code. In the extreme case, we would end up with an application that we don't dare to touch. So it is very important to have automated regression tests with good coverage.

SSL handshake failed: Secure connection truncated

2011-03-15T11:41:00.002+01:00

Got this problem on Ubuntu 9.10 and 10.10.


svn co --username=xx https:/yy zz
“SSL handshake failed: Secure connection truncated”

According to this link bug-ubuntuThe solution is:


sudo apt-get install libneon27
cd /usr/lib/
sudo rm libneon-gnutls.so.27
sudo ln -s /usr/lib/libneon.so.27 libneon-gnutls.so.27

Grinderstone under linux

2010-06-05T10:40:00.000+02:00

I am using Ubuntu 9.10


jan@albotek:~/development/eclipse$ more /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=9.10
DISTRIB_CODENAME=karmic
DISTRIB_DESCRIPTION="Ubuntu 9.10"

I installed new eclipse 3.5.2, and inside eclipse used jdk 1.6.0.20 as default JRE, and jython 2.5.1 for my jython. Still I did not manage to get my grinder scripts with proxy working. The failure I was getting:


Java exception initialising test script
 test1.record(grinder.getLogger().output)
 File "/home/jan/development/workspace-grinder/Grinder1/src/HelloWorld3.py", line 7, in Caused by: net.grinder.script.NonInstrumentableTypeException: Failed to wrap 
   at net.grinder.engine.process.instrumenter.MasterInstrumenter.instrument(MasterInstrumenter.java:114)
   at net.grinder.engine.process.TestData.instrument(TestData.java:100)
   at net.grinder.script.Test.record(Test.java:114)

In my output log I was seeing:


6/5/10 10:22:09 a.m. (process albotek-0): The Grinder version 3.4
6/5/10 10:22:09 a.m. (process albotek-0): null 1.5.0: GNU libgcj (4.4.1, GNU libgcj 4.4.1) on Linux i386 2.6.31-21-generic
6/5/10 10:22:09 a.m. (process albotek-0): time zone is GMT+02:00 (+0200)
6/5/10 10:22:21 a.m. (process albotek-0): worker process 0
6/5/10 10:22:21 a.m. (process albotek-0): Java VM does not support instrumentation, DCR unavailable
6/5/10 10:22:21 a.m. (process albotek-0): instrumentation agents: NO INSTRUMENTER COULD BE LOADED
6/5/10 10:22:21 a.m. (process albotek-0): executing "/home/jan/development/workspace-grinder/Grinder1/src/HelloWorld3.py" using Jython 2.5.1 (Release_2_5_1:6813, Sep 26 2009, 13:47:54)

Apparently I was using the wrong java version. Although I set it explicitly inside eclipse, eclipse itself had been started with java from OS, and grinderstone is using that one for its execution.I made a small startup script for my eclipse:


export GDK_NATIVE_WINDOWS=true
./eclipse  -clean -console -consoleLog -vm /usr/lib/jvm/java-6-sun/bin/java -vma
rgs -Xmx400M -XX:MaxPermSize=128M -Dorg.eclipse.swt.browser.XULRunnerPath=/usr/l
ib/xulrunner/xulrunner

and when I now start my eclipse, I get:


6/5/10 10:30:24 AM (process albotek-0): The Grinder version 3.4
6/5/10 10:30:24 AM (process albotek-0): Java(TM) SE Runtime Environment 1.6.0_20-b02: Java HotSpot(TM) Server VM (16.3-b01, mixed mode) on Linux i386 2.6.31-21-generic
6/5/10 10:30:24 AM (process albotek-0): time zone is CEST (+0200)
6/5/10 10:30:29 AM (process albotek-0): worker process 0
6/5/10 10:30:29 AM (process albotek-0): instrumentation agents: byte code transforming instrumenter for Jython 2.5; byte code transforming instrumenter for Java
6/5/10 10:30:29 AM (process albotek-0): executing "/home/jan/development/workspace-grinder/Grinder2/src/HelloWorld3.py" using Jython 2.5.1 (Release_2_5_1:6813, Sep 26 2009, 13:47:54)

Grinderstone and instrumentation

2010-06-04T17:05:00.000+02:00

At least I got my office PC (windows) working now.Script is:


# A simple example using the HTTP plugin that shows the retrieval of a
# single page via HTTP.

from net.grinder.script import Test
from net.grinder.script.Grinder import grinder
from net.grinder.plugin.http import HTTPRequest

test1 = Test(1, "Request resource")
request1 = test1.wrap(HTTPRequest())

class TestRunner:
    def __call__(self):
        result = request1.GET("http://emeafraippqa08:80/")

I used to get failures that had to do with instrumentation.In the end I added a new jdk6 (1.6.0.20) to eclipse, renewed my jython 2.5.1 reference so that it is using these libs, and now got it working.In my console I see the following path:


04.06.10 17:03:42 (agent): The Grinder 3.4
04.06.10 17:03:42 (agent): Worker process command line: java '-javaagent:C:\development\grinder-3.4\lib\grinder-agent.jar' -classpath 'C:\development\jython2.5.1\jython.jar;C:\Dokumente und Einstellungen\jan.kester\workspace\Grinder1/srcC:\development\grinder-3.4\lib\grinder-agent.jar;C:\development\grinder-3.4\lib\grinder.jar;C:\development\eclipse_3.5.2\plugins\org.python.pydev_1.5.7.2010050621\PySrc\pydev_sitecustomize;C:\Dokumente und Einstellungen\jan.kester\workspace\Grinder1\src;C:\development\grinder-3.4\lib\grinder-agent.jar;C:\development\grinder-3.4\lib\grinder.jar;C:\development\jython2.5.1\Lib;C:\development\jython2.5.1\Lib\site-packages;C:\Programme\Java\jdk1.6.0_20\jre\lib\resources.jar;C:\Programme\Java\jdk1.6.0_20\jre\lib\rt.jar;C:\Programme\Java\jdk1.6.0_20\jre\lib\jsse.jar;C:\Programme\Java\jdk1.6.0_20\jre\lib\jce.jar;C:\Programme\Java\jdk1.6.0_20\jre\lib\charsets.jar;C:\Programme\Java\jdk1.6.0_20\jre\lib\ext\dnsns.jar;C:\Programme\Java\jdk1.6.0_20\jre\lib\ext\localedata.jar;C:\Programme\Java\jdk1.6.0_20\jre\lib\ext\sunjce_provider.jar;C:\Programme\Java\jdk1.6.0_20\jre\lib\ext\sunmscapi.jar;C:\Programme\Java\jdk1.6.0_20\jre\lib\ext\sunpkcs11.jar' net.grinder.engine.process.WorkerProcessEntryPoint
04.06.10 17:03:43 (agent): worker emeafralp560-0 started
04.06.10 17:03:45 (process emeafralp560-0): starting threads
04.06.10 17:03:48 (process emeafralp560-0): finished
04.06.10 17:03:49 (agent): finished

My direct grinder output is:


C:\development\grinder-3.4>startAgent_jython251.cmd
C:\development\grinder-3.4\lib\grinder.jar;C:/development/jython2.5.1/jython.jar;C:\development\grinder-3.4\lib\grinder.jar;C:/development/jython2.5.1/jython.jar;C:\development\grinder-3.4\lib\grinder.jar;C:/development/jython2.5.1/jython.jar;C:\development\grinder-3.4\lib\grinder.jar;C:/development/jython2.5.1/jython.jar;C:\development\grinder-3.4\lib\grinder.jar;C:/development/jython2.5.1/jython.jar;C:\development\grinder-3.4\lib\grinder.jar;C:/development/jython2.5.1/jython.jar;C:\development\grinder-3.4\lib\grinder.jar;C:\development\grinder-3.4\lib\grinder.jar;C:/development/jython2.5.1/jython.jar;C:\development\grinder-3.4\lib\grinder.jar;C:\development\grinder-3.4\lib\grinder.jar;C:/development/jython2.5.1/jython.jar;C:\development\grinder-3.4\lib\grinder.jar;C:\development\grinder-3.4\lib\grinder.jar;C:/development/jython2.5.1/jython.jar;C:\development\grinder-3.4\lib\grinder.jar;C:\development\grinder-3.4\lib\grinder.jar;C:\development\grinder-3.4\lib\grinder.jar;C:\development\grinder-3.4\lib\grinder.jar;C:/development/jython2.5.1/jython.jar;C:\development\grinder-3.4\lib\grinder.jar;C:/development/jython2.5.1/jython.jar;C:\development\grinder-3.4\lib\grinder.jar;C:/development/jython2.5.1/jython.jar;C:\development\grinder-3.4\lib\grinder.jar;C:/development/jython2.5.1/jython.jar;C:\development\grinder-3.4\lib\grinder.jar;C:/development/jython2.5.1/jython.jar;C:\development\grinder-3.4\lib\grinder.jar;C:/development/jython2.5.1/jython.jar;C:\development\grinder-3.4\lib\grinder.jar;C:/development/jython2.5.1/jython.jar;C:\development\grinder-3.4\lib\grinder.jar;C:\development\grinder-3.4\lib\grinder.jar;C:\development\grinder-3.4\lib\grinder.jar;C:\development\grinder-3.4\lib\grinder.jar;C:\development\grinder-3.4\lib\grinder.jar;C:\development\grinder-3.4\lib\grinder.jar;C:\development\grinder-3.4\lib\grinder.jar;C:\development\grinder-3.4\lib\grinder.jar;C:\development\grinder-3.4\lib\grinder.jar;C:\development\grinder-3.4\lib\grinder.jar;C:\development\grinder-3.4\lib\grinder.jar;C:\development\grinder-3.4\lib\grinder.jar;C:\development\grinder-3.4\lib\grinder.jar;C:\development\grinder-3.4\lib\grinder.jar;C:\development\grinder-3.4\lib\grinder.jar;.;C:\Programme\Java\jre6\lib\ext\QTJava.zip
6/4/10 2:09:53 PM (agent): The Grinder 3.4
6/4/10 2:09:53 PM (agent): Worker process command line: java '-javaagent:C:\development\grinder-3.4\lib\grinder-agent.jar' '-Dpython.home=C:/development/jython2.5.1' '-Dpython.cachedir=C:\development\grinder-3.4/cachedir' -classpath 'C:/development/jython2.5.1/jython.jar;C:\development\grinder-3.4\lib\grinder.jar;C:/development/jython2.5.1/jython.jar;C:\development\grinder-3.4\lib\grinder.jar;C:/development/jython2.5.1/jython.jar;C:\development\grinder-3.4\lib\grinder.jar;C:/development/jython2.5.1/jython.jar;C:\development\grinder-3.4\lib\grinder.jar;C:/development/jython2.5.1/jython.jar;C:\development\grinder-3.4\lib\grinder.jar;C:/development/jython2.5.1/jython.jar;C:\development\grinder-3.4\lib\grinder.jar;C:/development/jython2.5.1/jython.jar;C:\development\grinder-3.4\lib\grinder.jar;C:\development\grinder-3.4\lib\grinder.jar;C:/development/jython2.5.1/jython.jar;C:\development\grinder-3.4\lib\grinder.jar;C:\development\grinder-3.4\lib\grinder.jar;C:/development/jython2.5.1/jython.jar;C:\development\grinder-3.4\lib\grinder.jar;C:\development\grinder-3.4\lib\grinder.jar;C:/development/jython2.5.1/jython.jar;C:\development\grinder-3.4\lib\grinder.jar;C:\development\grinder-3.4\lib\grinder.jar;C:\development\grinder-3.4\lib\grinder.jar;C:\development\grinder-3.4\lib\grinder.jar;C:/development/jython2.5.1/jython.jar;C:\development\grinder-3.4\lib\grinder.jar;C:/development/jython2.5.1/jython.jar;C:\development\grinder-3.4\lib\grinder.jar;C:/development/jython2.5.1/jython.jar;C:\development\grinder-3.4\lib\grinder.jar;C:/development/jython2.5.1/jython.jar;C:\development\grinder-3.4\lib\grinder.jar;C:/development/jython2.5.1/jython.jar;C:\development\grinder-3.4\lib\grinder.jar;C:/development/jython2.5.1/jython.jar;C:\development\grinder-3.4\lib\grinder.jar;C:/development/jython2.5.1/jython.jar;C:\development\grinder-3.4\lib\grinder.jar;C:\development\grinder-3.4\lib\grinder.jar;C:\development\grinder-3.4\lib\grinder.jar;C:\development\grinder-3.4\lib\grinder.jar;C:\development\grinder-3.4\lib\grinder.jar;C:\development\grinder-3.4\lib\grinder.jar;C:\development\grinder-3.4\lib\grinder.jar;C:\development\grinder-3.4\lib\grinder.jar;C:\development\grinder-3.4\lib\grinder.jar;C:\development\grinder-3.4\lib\grinder.jar;C:\development\grinder-3.4\lib\grinder.jar;C:\development\grinder-3.4\lib\grinder.jar;C:\development\grinder-3.4\lib\grinder.jar;C:\development\grinder-3.4\lib\grinder.jar;C:\development\grinder-3.4\lib\grinder.jar;.;C:\Programme\Java\jre6\lib\ext\QTJava.zip' net.grinder.engine.process.WorkerProcessEntryPoint
6/4/10 2:09:54 PM (agent): worker emeafralp560-0 started
04.06.10 14:09:55 (process emeafralp560-0): starting threads
04.06.10 14:09:55 (process emeafralp560-0): finished
6/4/10 2:09:56 PM (agent): finished

Now I need to get my home PC working still ... (Ubuntu)

record() not wrap()

2010-06-04T14:12:00.002+02:00

With the new jython 2.5.1 instrumentation, you must use record() method of Test proxy, and not wrap(). The old one is deprecated.The difference:old:


from net.grinder.script import Test
from net.grinder.script.Grinder import grinder

test1 = Test(1, "Log method")

# Wrap the output() method with our Test and call the result logWrapper.
logWrapper = test1.wrap(grinder.getLogger().output)

class TestRunner:
    def __call__(self):
        logWrapper("Hello World2")

new:


from net.grinder.script import Test
from net.grinder.script.Grinder import grinder

test1 = Test(1, "Log method")

# Instrument the output() method with our Test.
test1.record(grinder.getLogger().output)

class TestRunner:
    def __call__(self):
        grinder.getLogger().output("Hello World4")

Using grinder 3.4 and jython 2.5.1

2010-06-04T14:01:00.000+02:00

By default grinder 3.4 comes with a jython jar under lib directory. It is version 2.2.1.In order two use a newer jython, you need to change two settings:

add your newest jython jar in front of classpath
add a jvm property that directs python_home to the home of your jython.

You can either do this in grinder.properties or in your bat script that starts the agent. I prefer the latter as I would like to keep grinder.properties as general as possible, independent of machines/environment.My new startAgent_jython251.cmd script looks like:


@echo off
set GRINDERPATH=C:\development\grinder-3.4
call %GRINDERPATH%\setGrinderEnv.cmd
set PYTHON_HOME=C:/development/jython2.5.1
echo %CLASSPATH%
set CLASSPATH=%PYTHON_HOME%/jython.jar;%CLASSPATH%
set JVMARGS="-Dpython.home=%PYTHON_HOME% -Dpython.cachedir=%GRINDERPATH%/cachedir"
java -Duser.language="en" -Dgrinder.jvm.arguments=%JVMARGS% -cp %CLASSPATH% net.grinder.Grinder %GRINDERPROPERTIES%

When I run a script with this agent cmd, my output looks like:


04.06.10 13:53:46 (process emeafralp560-0): The Grinder version 3.4
04.06.10 13:53:46 (process emeafralp560-0): Java(TM) SE Runtime Environment 1.6.0_20-b02: Java HotSpot(TM) Client VM (16.3-b01, mixed mode) on Windows XP x86 5.1
04.06.10 13:53:46 (process emeafralp560-0): time zone is MESZ (+0200)
04.06.10 13:53:48 (process emeafralp560-0): worker process 0
04.06.10 13:53:48 (process emeafralp560-0): instrumentation agents: byte code transforming instrumenter for Jython 2.5; byte code transforming instrumenter for Java
04.06.10 13:53:48 (process emeafralp560-0): executing "C:\development\grinder-3.4\HelloGrinder3.py" using Jython 2.5.1 (Release_2_5_1:6813, Sep 26 2009, 13:47:54) 
[Java HotSpot(TM) Client VM (Sun Microsystems Inc.)]

I think that by default it is already using the new instrumentation implementation that gets used by jython 2.5.1. Manual states namely that if you use the old one, the output shows you

traditional Jython instrumenter

I did not see it, and could not influence the output with parameter

grinder.dcrinstrumentation = true

So I compared behaviour with a grinder using jython 2.2.1. There using this parameter did make an influence. If you included the parameter, regardless the value you are giving it (true|anything|even-false|false), it will use the new way of instrumentation. Only when you leave the parameter out, you will get output:


04.06.10 14:00:34 (process emeafralp560-0): The Grinder version 3.4
04.06.10 14:00:34 (process emeafralp560-0): Java(TM) SE Runtime Environment 1.6.0_20-b02: Java HotSpot(TM) Client VM (16.3-b01, mixed mode) on Windows XP x86 5.1
04.06.10 14:00:34 (process emeafralp560-0): time zone is MESZ (+0200)
04.06.10 14:00:34 (process emeafralp560-0): worker process 0
04.06.10 14:00:34 (process emeafralp560-0): instrumentation agents: traditional Jython instrumenter; byte code transforming instrumenter for Java
04.06.10 14:00:34 (process emeafralp560-0): executing "C:\development\grinder-3.4\HelloGrinder3.py" using Jython 2.2.1

My first grinder runs

2010-06-04T13:19:00.000+02:00

I downloaded grinder 3.4, and unpacked.I installed java jdk 1.6.0.20 on my machine.Inside the root directory of my installation I added following scripts:setGrinderEnv.cmd


set GRINDERPATH=C:\development\grinder-3.4
set GRINDERPROPERTIES=C:\development\grinder-3.4\grinder.properties
set CLASSPATH=%GRINDERPATH%\lib\grinder.jar;%CLASSPATH%
set JAVA_HOME=C:\Programme\Java\jdk1.6.0_20
PATH=%JAVA_HOME%\bin;%PATH%

startProxy.cmd


set GRINDERPATH=C:\development\grinder-3.4
call %GRINDERPATH%\setGrinderEnv.cmd
echo %CLASSPATH%
java -Duser.language="en" -cp %CLASSPATH% net.grinder.TCPProxy -console -http > ipp.py

startConsole.cmd


set GRINDERPATH=C:\development\grinder-3.4
call %GRINDERPATH%\setGrinderEnv.cmd
echo %CLASSPATH%
java -Duser.language="en" -cp %CLASSPATH% net.grinder.Console

startAgent.cmd


set GRINDERPATH=C:\development\grinder-3.4
call %GRINDERPATH%\setGrinderEnv.cmd
echo %CLASSPATH%
java -Duser.language="en" -cp %CLASSPATH% net.grinder.Grinder %GRINDERPROPERTIES%

I also dropped a file grinder.properties in root directory of grinder-3.4:


grinder.script=HelloGrinder2.py
grinder.processes = 1
grinder.threads = 3
grinder.runs = 2
grinder.useConsole = false
grinder.dcrinstrumentation = true
grinder.logDirectory = logs
grinder.numberOfOldLogs = 0
grinder.initialSleepTime=50

With this grinder.properties, an agent will execute the HelloGrinder2.py script:


from net.grinder.script import Test
from net.grinder.script.Grinder import grinder

test1 = Test(1, "Log method")

# Wrap the output() method with our Test and call the result logWrapper.
logWrapper = test1.wrap(grinder.getLogger().output)

class TestRunner:
    def __call__(self):
        logWrapper("Hello World2")

I can execute the script by calling startAgent.cmd.After execution I get a subdirectory called log, with data and output files in it.The output file shows:


04.06.10 10:47:40 (process emeafralp560-0): starting threads
04.06.10 10:47:40 (thread 2): starting, will do 2 runs
04.06.10 10:47:40 (thread 1): starting, will do 2 runs
04.06.10 10:47:40 (thread 0): starting, will do 2 runs
04.06.10 10:47:40 (process emeafralp560-0): start time is 1275641260135 ms since Epoch
04.06.10 10:47:40 (thread 0): sleeping for 10 ms
04.06.10 10:47:40 (thread 1): sleeping for 1 ms
04.06.10 10:47:40 (thread 2): sleeping for 4 ms
04.06.10 10:47:40 (thread 2 run 0 test 1): Hello World2
04.06.10 10:47:40 (thread 1 run 0 test 1): Hello World2
04.06.10 10:47:40 (thread 0 run 0 test 1): Hello World2
04.06.10 10:47:40 (thread 1 run 1 test 1): Hello World2
04.06.10 10:47:40 (thread 1 test 1): finished 2 runs
04.06.10 10:47:40 (thread 0 run 1 test 1): Hello World2
04.06.10 10:47:40 (thread 0 test 1): finished 2 runs
04.06.10 10:47:40 (thread 2 run 1 test 1): Hello World2
04.06.10 10:47:40 (thread 2 test 1): finished 2 runs
04.06.10 10:47:40 (process emeafralp560-0): elapsed time is 22 ms

As my grinder properties file tells to use 3 threads, and 2 runs for each thread, the Hello World2 got written 6 times.My data output shows the test times that the Test Proxy of the script recorded:


Thread, Run, Test, Start time (ms since Epoch), Test time, Errors
0, 0, 1, 1275641260152, 0, 0
1, 0, 1, 1275641260152, 0, 0
2, 0, 1, 1275641260152, 1, 0
1, 1, 1, 1275641260153, 0, 0
0, 1, 1, 1275641260154, 0, 0
2, 1, 1, 1275641260154, 0, 0

This output is a bit boring, as I did not make any http request.With the next file HelloGrinder3.py I do:


from net.grinder.script import Test
from net.grinder.script.Grinder import grinder
from net.grinder.plugin.http import HTTPRequest

test1 = Test(1, "Request resource")
request1 = test1.wrap(HTTPRequest())

class TestRunner:
    def __call__(self):
        result = request1.GET("http://emeafraippqa08:80/")

I need to adapt grinder.properties to use this as grinder.script, and then can run startAgent.cmd again.Now my data output looks like:


Thread, Run, Test, Start time (ms since Epoch), Test time, Errors, HTTP response code, HTTP response length, HTTP response errors, Time to resolve host, Time to establish connection, Time to first byte
1, 0, 1, 1275650338473, 60, 0, 200, 327, 0, 23, 33, 50
1, 1, 1, 1275650338535, 2, 0, 200, 327, 0, 0, 0, 1
2, 0, 1, 1275650338473, 3105, 0, 200, 327, 0, 22, 3085, 3094
0, 0, 1, 1275650338481, 3097, 0, 200, 327, 0, 23, 3085, 3094
2, 1, 1, 1275650341579, 5, 0, 200, 327, 0, 0, 1, 3
0, 1, 1, 1275650341579, 7, 0, 200, 327, 0, 0, 1, 2

Adding your own styles

2010-06-03T20:17:00.000+02:00

To get nice formatting of your blog, you can add your own style elements.Under Customize - Layout - Edit Html you can adapt your style sheet.Find the element:

]]></b:skin>
</head>

and above this add:


pre {
background:#eeeeee;
border:1px solid #A6B0BF;
font-size:120%;
line-height:100%;
overflow:auto;
padding:10px;
color:#000000 }
pre:hover {
border:1px solid #efefef;
}
code {
font-size:120%;
text-align:left;
margin:0;padding:0;
color: #000000;}
.clear { clear:both;
overflow:hidden;
}

Now you have two new styles you can use: pre and code.To use them, switch to Edit HTML mode, and use html tags pre or code.

My first grinderstone project

2010-06-02T16:29:00.002+02:00

I followed instructions to set up grinderstone:

eclipse 3.5.2
pydev from update site
grinderstone from update site
jython 2.5.1 installed
grinder 3.4 installed

Under windows preferences I added a jython 2.5.1 jar as jython interpreter. It asks which libraries to include on the python system path. I choose the defaults, excluding __pyclasspath__ and __classpath__. Not sure where these get used for; probably to include your project's .classpath or python path in the jython execution's classpath.
Also under windows-preferences, I set show whitespace characters to true.

Next I create a python project. I added grinder.jar and grinder-agent.jar to the external libraries of the project build path. Now I can add my first grinder file under src/HelloGrinder.py:


from net.grinder.script.Grinder import grinder



# An instance of this class is created for every thread.

class TestRunner:

    # This method is called for every run.

    def __call__(self):

        # Per thread scripting goes here.

        grinder.getLogger().output("Hello World")

Next I need to add a grinder.properties to the directory as well:


grinder.processes = 1

grinder.threads = 1

grinder.runs = 1

grinder.useConsole = false

grinder.logDirectory = logs

grinder.numberOfOldLogs = 0

grinder.initialSleepTime=50

I can now select my HelloGrinder.py file, and with right mouse button select: Run As - Grinder Run.
Logs will appear under src. You will need to click refresh (F5) on you project before they get visible ..

Output looks like:


02.06.10 16:27:18 (process emeafralp560-0): The Grinder version 3.4

02.06.10 16:27:18 (process emeafralp560-0): Java(TM) 2 Runtime Environment, Standard Edition 1.5.0_06-b05: Java HotSpot(TM) Client VM (1.5.0_06-b05, mixed mode) on Windows XP x86 5.1

02.06.10 16:27:18 (process emeafralp560-0): time zone is CEST (+0200)

02.06.10 16:27:20 (process emeafralp560-0): worker process 0

02.06.10 16:27:20 (process emeafralp560-0): Java VM does not support instrumentation, DCR unavailable

02.06.10 16:27:20 (process emeafralp560-0): instrumentation agents: NO INSTRUMENTER COULD BE LOADED

02.06.10 16:27:20 (process emeafralp560-0): executing "C:\Dokumente und Einstellungen\jan.kester\workspace\Grinder1\src\HelloGrinder.py" using Jython 2.5.1 (Release_2_5_1:6813, Sep 26 2009, 13:47:54) 

[Java HotSpot(TM) Client VM (Sun Microsystems Inc.)]

02.06.10 16:27:20 (process emeafralp560-0): starting threads

02.06.10 16:27:20 (thread 0): starting, will do 1 run

02.06.10 16:27:20 (process emeafralp560-0): start time is 1275488840962 ms since Epoch

02.06.10 16:27:20 (thread 0): sleeping for 38 ms

02.06.10 16:27:20 (thread 0 run 0): Hello World

02.06.10 16:27:20 (thread 0): finished 1 run

02.06.10 16:27:20 (process emeafralp560-0): elapsed time is 58 ms

02.06.10 16:27:20 (process emeafralp560-0): Final statistics for this process:

             Tests        Errors       Mean Test    Test Time    TPS          

                                       Time (ms)    Standard                  

                                                    Deviation                 

                                                    (ms)                      





Totals       0            0            ?            0,00         ?            



  Tests resulting in error only contribute to the Errors column.          

  Statistics for individual tests can be found in the data file, including

  (possibly incomplete) statistics for erroneous tests. Composite tests   

  are marked with () and not included in the totals.                      

02.06.10 16:27:20 (process emeafralp560-0): finished

Setting up ldap on Ubuntu 9.10

2010-05-04T16:20:00.002+02:00

Installing slapd on Ubuntu 9.10 is not enough.The configuration of slapd requires more steps.I refer to article: http://doc.ubuntu.com/ubuntu/serverguide/C/openldap-server.html which apparently also applies to 9.10.Make sure you load the necessary schemas:


ldapadd -Y EXTERNAL -H ldapi:/// -f /etc/ldap/schema/cosine.ldif
ldapadd -Y EXTERNAL -H ldapi:/// -f /etc/ldap/schema/nis.ldif 
ldapadd -Y EXTERNAL -H ldapi:/// -f /etc/ldap/schema/inetorgperson.ldif

My ldif file I wanted to load contains dc=ldap,dc=example,dc=ipp. So I wanted to set up a rootdn starting with same domain.


# Load dynamic backend modules
dn: cn=module,cn=config
objectClass: olcModuleList
cn: module
olcModulepath: /usr/lib/ldap
olcModuleload: back_hdb

# Database settings
dn: olcDatabase=hdb,cn=config
objectClass: olcDatabaseConfig
objectClass: olcHdbConfig
olcDatabase: {1}hdb
olcSuffix: dc=ldap,dc=example,dc=ipp
olcDbDirectory: /var/lib/ldap
olcRootDN: cn=admin,dc=ldap,dc=example,dc=ipp
olcRootPW: secret
olcDbConfig: set_cachesize 0 2097152 0
olcDbConfig: set_lk_max_objects 1500
olcDbConfig: set_lk_max_locks 1500
olcDbConfig: set_lk_max_lockers 1500
olcDbIndex: objectClass eq
olcLastMod: TRUE
olcDbCheckpoint: 512 30
olcAccess: to attrs=userPassword by dn="cn=admin,dc=ldap,dc=example,dc=ipp" write by anonymous auth by self write by * none
olcAccess: to attrs=shadowLastChange by self write by * read
olcAccess: to dn.base="" by * read
olcAccess: to * by dn="cn=admin,dc=ldap,dc=example,dc=ipp" write by * read

Note that I changed the domain, and left password to secret.Load this backend file with:


sudo ldapadd -Y EXTERNAL -H ldapi:/// -f backend.ldap.example.ipp.ldif

You will now need to restart your slapd daemon.Then you can add your own ldif file with data.Afterwards you can test with ldapsearch. As normal user:


ldapsearch -x -b "dc=ldap,dc=example,dc=ipp" uid=User sn ginveName cn
ldapsearch -x -b "dc=ldap,dc=example,dc=ipp" '(objectclass=top)'
ldapsearch -x -b "dc=ldap,dc=example,dc=ipp" '(objectclass=domain)'
ldapsearch -x -b "dc=ldap,dc=example,dc=ipp" '(objectclass=person)'
ldapsearch -x -b "dc=ldap,dc=example,dc=ipp" '(objectclass=organizationalUnit)'

Publishing xml

2010-05-03T11:07:00.001+02:00

I always had the problem in my posts to include xml snippets. A problem other people must have experienced too. I came across the blogger site: http://formatmysourcecode.blogspot.com/. It allows to copy your xml, paste and convert it. An example is below, it should show xml ...

<?xml version="1.0" encoding="UTF-8"?>
<templates>
        <template autoinsert="true" context="gettercomment_context"
                deleted="false" description="Comment for getter method" enabled="true"
                id="org.eclipse.jdt.ui.text.codetemplates.gettercomment"
                name="gettercomment">
                /** * @return the ${bare_field_name} */
        </template>
        <template autoinsert="true" context="delegatecomment_context"
                deleted="false" description="Comment for delegate methods"
                enabled="true"
                id="org.eclipse.jdt.ui.text.codetemplates.delegatecomment"
                name="delegatecomment">
                /** * ${tags} * ${see_to_target} */
        </template>

This is the xml with embedded stylesheet.Without stylesheet and with tab size2, it looks like:

<?xml version="1.0" encoding="UTF-8"?>
<templates>
        <template autoinsert="true" context="gettercomment_context"
                deleted="false" description="Comment for getter method" enabled="true"
                id="org.eclipse.jdt.ui.text.codetemplates.gettercomment"
                name="gettercomment">
                /** * @return the ${bare_field_name} */
        </template>
        <template autoinsert="true" context="delegatecomment_context"
                deleted="false" description="Comment for delegate methods"
                enabled="true"
                id="org.eclipse.jdt.ui.text.codetemplates.delegatecomment"
                name="delegatecomment">
                /** * ${tags} * ${see_to_target} */
        </template>

encrypt directory

2009-10-20T07:57:00.000+02:00

I wanted to encrypt some personal directories I have on my laptop.

I have an encrypted directory:

jan@eee901:~/Documents$ ls /home/jan/.encrypted/

4g1Vb4HRZTsVFGXkeqcIsv3q JgpUH0yio4s6r6QuYYyNEKQVUoXKU1j937UTbHa1YOgQK, qoSuRuAL7FFdp49ZL2J9UgZp

My destination directory /home/jan/Documents/encrypted is empty after a new boot.

Now I can mount with:
encfs /home/jan/.encrypted /home/jan/Documents/encrypted

an@eee901:~/Documents$ encfs /home/jan/.encrypted /home/jan/Documents/encrypted
EncFS Password:
jan@eee901:~/Documents$ ls encrypted/
addresses

To umount:
fusermount -u /home/jan/Documents/encrypted

When you run the command for the first time, it will ask you to set password.

Using sdhc card from boot

2009-10-20T07:36:00.000+02:00

My Eee PC 901 runs Ubuntu. I have no hard disk, but just an internal sd card, and an additional inserted sdhc card in the sd card slot.
I wanted to have all my /home stuff on the external card, so that in case of crash, I can just buy a new card. The internal card is more difficult to replace, so I want to use the external card for whatever possible.

As the ext card has my /home directory, I need it to be available on boot.

With lsusb I found the details of my card, and then added an udev rule

jan@eee901:~/svn/hydra_test$ more /etc/udev/rules.d/01-jankester.rules
#ID_SERIAL_SHORT=058F63356336
#ID_FS_UUID=dd4cb63c-0329-4dc6-8ca8-c2e68b9d233e
BUS=="usb", KERNEL=="sd*", SYSFS{serial}=="058F63356336", NAME="SDHC", OPTIONS+="last_rule", RUN+="/bin/mount /dev/SDHC"

Now I added entry in fstab:
/dev/SDHC /home ext3 defaults,noatime 0

Ubuntu: starting db2 at bootup

2008-05-14T15:41:00.000+02:00

I installed db2 express 9.5 under ubuntu 8.04.
After installation of several packages, it installed well.
Only, after installation, it did not automatically start at boot.

Setting db2set autostart=yes (by db2inst1 user) did not help.

So in the end, I added a /etc/init.d/db2 script:
http://www.tldp.org/HOWTO/DB2-HOWTO/ubuntu704.html#AEN794

#!/bin/sh
#
# Script to start DB2 instances on bootup.
#
set -e

. /lib/lsb/init-functions

case "$1" in
start)
       /opt/ibm/db2exc/V9.1/instance/db2istrt
       ;;
stop|restart|reload)
       ;;
esac

exit 0

Then I installed bum package, and ran System-Administration-Bootup Manager to activate the db2 script at startup.

Websphere 6.1 administrative security + self signed certificates

2008-05-14T15:09:00.000+02:00

I installed websphere 6.1 and chose the default "enable administrative security". Once I finished my installation, I noticed I could not login under https://localhost:9043/admin/console. I got a message about a certificate not being trusted.

First I discovered, that I had renamed my machine, but that /etc/hosts still had old entries for 127.0.0.1. Because of that, my node and cell names were still deduced from the old machine name.
I fixed that and reinstalled.

At login I got the failure: invalid security certificate.
My browser did not trust the self signed certificate that the websphere server uses.

I did following to fix that:

In /bin, started keyman: sudo ./ikeyman.sh
Opened jks file under profiles/AppSrv01/etc/DummyClientTrustFile.jks, password is WebAS.
there I looked up the default_signer, and selected the extract option. I exported cert.arm as base64 ascii.
under firefox, preferences, advanced, view certificates I imported the CA certificate
I restarted firefox.

The url with localhost still did not work, but when I replaced localhost by the machine name, I got access to my adminconsole.

Small remark: the self signed certificate websphere generated is valid for a year. The certificate itself probably too.

Installing websphere 6.1 under hardy-heron

2008-05-09T10:26:00.000+02:00

I had problems to get websphere installed on Ubuntu 8.04.
The install did work, but the configuration of profiles failed.
In the end it turned out, that /bin/sh points to /bin/dash instead of /bin/bash.

I executed following commands:

sudo unlink /bin/sh

sudo ln -s /bin/bash /bin/sh

During installation I set an admin console username/password.
When I start the server, and go to the console page

http://localhost:9060/ibm/console/

I get redirected to

https://localhost:9043/ibm/console/

and get an error that my self signed certificate is not trusted.

Dual screen for Dell D830

2008-01-02T11:57:00.000+01:00

My Dell D830 uses an Intel Graphic Card GM965. To use dualscreen, you must use the package xrandr.
As a normal user you can see your current configuration with:
xrandr -q
When you connect a second monitor (docking station), then by default you will get both screens displaying the same. Example:
jan@southfork:~$ xrandr -q

Screen 0: minimum 320 x 200, current 3600 x 1200, maximum 3600 x 1200

VGA disconnected (normal left inverted right)

LVDS connected 1920x1200+0+0 (normal left inverted right) 331mm x 207mm

1920x1200 60.0*+

1280x800 60.0

1280x768 60.0

1024x768 60.0

800x600 60.3

640x480 59.9

TMDS-1 connected 1680x1050+0+0 (normal left inverted right) 434mm x 270mm

1680x1050 59.9*+

1280x1024 75.0 59.9

1152x864 74.8

1024x768 75.1 60.0

800x600 75.0 60.3

640x480 75.0 60.0

720x400 70.1

TV disconnected (normal left inverted right)

In my example above you will see that both screens start their output at +0+0 (0,0). I would like to put one screen next to the other. That is, I will get a screen that is 1920 + 1680 = 3600 wide. In order to make it fit, I must make sure that the it will fit in the maximum screen size. By default the maximum screen size is set equal to the largest mode: 1920x1920. I increased it to 3600x1200. You do this by adding a xrandr specific parameter to your xorg.conf file:

Section "Screen"

Identifier "Default Screen"

Device "Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller"

Monitor "Generic Monitor"

DefaultDepth 24

SubSection "Display"

# Modes "1920x1200"

Virtual 3600 1200

EndSubSection

EndSection

I needed to comment out the Modes line, else my X would not start any more.
Now you can restart X (logout / login) and change the display to two screens with:

xrandr --output TMDS-1 --mode 1680x1050 --left-of LVDS

Now I will get my laptop screen to the right of my DVI screen.

You can also apply these settings to your xorg.conf file, but that effort I will save for a next time :-).

VPNC

2007-12-04T09:48:00.000+01:00

On Ubuntu 7.10, install vpnc package.

/etc/vpnc/netscreen.conf

IPSec gateway
xxx.xxx.xxx.xxx

IPSec ID "XXXXXXXXXXXXX"

IPSec secret xxxxxxxxxxxx

Vendor netscreen

Perfect Forward Secrecy
dh2

Xauth username xxxxxxxx

Xauth password xxxxxxxx

#Debug 3

In /etc/vpnc/vpnc-script

Put following before set -x

INTERNAL_IP4_DNS=

CISCO_SPLIT_INC=1

CISCO_SPLIT_INC_0_ADDR=xxx.xxx.xxx.0

CISCO_SPLIT_INC_0_MASK=255.255.252.0

CISCO_SPLIT_INC_0_MASKLEN=22

CISCO_SPLIT_INC_0_PROTOCOL=0

CISCO_SPLIT_INC_0_SPORT=0

CISCO_SPLIT_INC_0_DPORT=0

Create a version for
/etc/resolv.conf.thuis, /etc/resolv.conf.sungard.

Create aliases:

alias
sungard-vpn-down='sudo /usr/sbin/vpnc-disconnect; sudo cp
/etc/resolv.conf.thuis /etc/resolv.conf'

alias sungard-vpn-up='sudo
/usr/sbin/vpnc /etc/vpnc/netscreen.conf; sudo cp
/etc/resolv.conf.sungard /etc/resolv.conf'

jboss with embedded derby in network mode

2007-11-24T15:56:00.000+01:00

Embedding derby into Jboss

In this post I want to show how you can
start jboss with an embedded derby network database.

The aim is, that when jboss starts:

it will start derby

open port 1527 for derby to receive
jdbc calls

create a new database if there is
none existing

create a datasource inside jboss

You can now use any derby jdbc client
to communicate with the database, and use derby datasource inside
jboss as well.

I had to implement three components:

an mbean to start the derby network
server

a datasource to connect to derby
database with option create=true

an mbean that will get an initial
connection so that database gets created

Jboss mbean

In Jboss you can deploy mbeans, which
automatically get started on deployment. The implementation of an
Mbean is very simple: you must create an interface that ends with
Mbean and has methods start() and stop(), and implement a class for
this interface that shares the same name without the Mbean part.

Then you create an xml with a reference
to the class implementation, and a name settings. For example:

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
<?xml version="1.0"
encoding="UTF-8"?>

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
<server>

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

<mbean
code="jankester.com.derby.jboss.DerbyDatabase"

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

name="jboss.jdbc:service=DerbyDatabase">

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

</mbean>

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
face="Monospace"></server>

The deployment of an Mbean can be done
in several ways: you can create an xml file, drop it in the deploy
directory and make sure that the java classes are available in the
lib directory, or you can create a .sar file. The latter has the
advantage that you can do hot deployment, so I prefer it.

You must: create a jar file or
directory that ends in .sar (so that jboss recognizes it type on
deployment), and add a jar to this .sar file with the necessary
classes.

The network server Mbean

The interface for this mbean looks
like:

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
package
com.jankester.derby.jboss;

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
public interface
DerbyDatabaseMBean

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
{

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

public void start()
throws Exception;

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

public void stop()
throws Exception;

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
}

The class implementing this interface
has following:

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
package
com.jankester.derby.jboss;

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
import
java.sql.DriverManager;

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
import
java.sql.SQLException;

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
public class
DerbyDatabase implements DerbyDatabaseMBean

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
{

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

public static final
String START_NETWORK_SERVER = "derby.drda.startNetworkServer";

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

public static final
String HOST = "localhost";

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

public static final
String PORT_NUMBER = "1527";

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

public static final
String DRIVER_CLASSNAME = "org.apache.derby.jdbc.EmbeddedDriver";

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

public static final
String SHUTDOWN_URL = "jdbc:derby:;shutdown=true";

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

public static final
String SHUTDOWN_MESSAGE = "Derby system shutdown.";

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

public static final
String MSG_INIT_SUCCESS = "Derby JDBC driver loaded
successfully";

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

public static final
String MSG_INIT_CLASS_NOT_FOUND = "The Derby JDBC driver ("

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
+
DRIVER_CLASSNAME + ") could not be found. Make sure the
appropriate JAR"

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
+ " files
are available.";

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

public static final
String MSG_TERM_SUCCESS = "Derby shutdown was successful.";

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

public static final
String MSG_TERM_FAILURE = "Unexpected Exception was caught from
the Derby shutdown.";

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

public void start()
throws Exception

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
{

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

setSystemProperties();

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

initializeCloudscape();

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
}

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

public void stop()
throws Exception

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
{

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

shutdownCloudscape();

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
}

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

private void
setSystemProperties()

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
{

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

String dataDir =
System.getProperty("jboss.server.data.dir");

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

System.out.println("jboss.server.data.dir="
+ dataDir);

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

System.setProperty(START_NETWORK_SERVER,
"true");

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

System.setProperty("derby.system.home",
dataDir);

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
}

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

private void
initializeCloudscape()

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
{

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

try

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

{

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

Class.forName(DRIVER_CLASSNAME);

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

System.out.println(MSG_INIT_SUCCESS);

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

}

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

catch
(ClassNotFoundException varException)

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

{

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

System.out.println(MSG_INIT_CLASS_NOT_FOUND);

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

varException.printStackTrace();

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

}

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
}

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

private void
shutdownCloudscape()

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
{

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

try

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

{

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

DriverManager.getConnection(SHUTDOWN_URL);

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

}

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

catch
(SQLException varException)

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

{

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

        System.out.println("message="
+         varException.getMessage());

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

        System.out.println("sqlstate="
+     varException.getSQLState());

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

if
(varException.getMessage().equals(SHUTDOWN_MESSAGE))

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

{

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

System.out.println(MSG_TERM_SUCCESS);

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

}

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

else

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

{

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

System.out.println(MSG_TERM_FAILURE);

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

varException.printStackTrace();

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

}

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
}

In initializeCloudscape() it loads the
driver class. Before, in system properties it sets system properties
that will be picked up by the driver class:

network mode is true

the root directory for derby
database storage is the jboss server data dir.

The xml that belong to this mbean is:

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
<?xml version="1.0"
encoding="UTF-8"?>

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
<server>

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

<mbean
code="jankester.com.derby.jboss.DerbyDatabase"

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
name="jboss.jdbc:service=DerbyDatabase">

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

</mbean>

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
face="Monospace"></server>

The xml file must be renamed into
META-INF/jboss-service.xml, the classes added to a jar, and the jar
and META-INF directory together packed into a .sar file. You can now
deploy the file directly in the deploy dir of your server.

The datasource

To create a derby datasource, you can
use the samples that comes with jboss.

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
<?xml version="1.0"
encoding="UTF-8"?>

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
<datasources>

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

<local-tx-datasource>

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

<jndi-name>AuditTrail.DataSource</jndi-name>

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
face="Courier, monospace"><connection-url>jdbc:derby:${jboss.server.data.dir}${/}carnot;create=true</connection-url>

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

<driver-class>org.apache.derby.jdbc.EmbeddedDriver</driver-class>

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

<user-name>carnot</user-name>

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

<password>carnot</password>

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

<min-pool-size>5</min-pool-size>

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

<max-pool-size>20</max-pool-size>

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

<idle-timeout-minutes>5</idle-timeout-minutes>

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

<track-statements/>

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

<depends>jboss.jdbc:service=DerbyDatabase</depends>

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

</local-tx-datasource>

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
</datasources>

Important to note here, is, that the
connection url creates a new database if none is existing and uses
the jboss data directory as its basis for database data.

The datasource has a dependency on the
derbydatabase mbean that we just created. It will not load before
that mbean has been loaded.

The poolfiller MBean

This mbean is necessary as we must make
sure that the database gets created straight away on loading. If we
leave this out, we can have the scenario that an external jdbc client
calls derby, but that the database has not been created yet. The
database only gets created the first time the datasource connection
gets created. So, this mbean will create a connection and close it
again.

Here we an interface PoolFillerMbean:

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
package
jankester.com.derby.jboss;

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
import
javax.management.ObjectName;

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
public interface
PoolFillerMBean

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
{

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

public void start()
throws Exception;

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

public void stop()
throws Exception;

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

public void
setConnectionManager(ObjectName cm);

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
}

and a class PoolFiller:

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
package
jankester.com.derby.jboss;

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
import
java.sql.Connection;

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
import
javax.management.ObjectName;

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
import
javax.naming.InitialContext;

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
import
javax.sql.DataSource;

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
import
org.jboss.system.ServiceMBeanSupport;

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
public class PoolFiller
extends ServiceMBeanSupport implements PoolFillerMBean

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
{

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

public void start()
throws Exception

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
{

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

System.out.println("Starting
PoolFiller");

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

startService();

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
}

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

public void stop()

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
{

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

System.out.println("Stopping
PoolFiller");

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
}

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

private ObjectName
cm;

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

public void
setConnectionManager(ObjectName cm)

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
{

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

this.cm = cm;

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
}

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

protected void
startService() throws Exception

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
{

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

String jndiName =
(String) server.getAttribute(cm, "BindName");

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

DataSource ds =
(DataSource) new InitialContext().lookup(jndiName);

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

System.out.println("Found
datasource for jndiname=" + jndiName);

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

Connection c =
ds.getConnection();

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

c.close();

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
}

Here we had to add an extra method
setConnectionManager to load an existing mbean object. We have to
implement this method in class and interface, so that Jboss can find
it.

Further we extended ServiceMBeanSupport
so that we have access to the Mbean Server. We
need it to find our Mbean that holds the jndi name of our datasource.
With the jndi name, we can find the datasource, and retrieve a
connection. Now the database gets created.

The method BindName is an attribute of
the Mbean that gets passed into the setConnection method. If you use
a different version of Jboss (tested with 4.0.5), then look into
http://localhost:8080/jmx-console,
and find an Mbean that has an attribute that holds the jndi
reference.

The jboss-service.xml looks like:

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
<?xml version="1.0"
encoding="UTF-8"?>

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
<server>

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

<mbean
code="ag.carnot.derby.jboss.PoolFiller"

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
name="jboss.jdbc:service=PoolFiller">

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

<depends
optional-attribute-name="ConnectionManager">jboss.jca:name=AuditTrail.DataSource,service=DataSourceBinding</depends>

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">

</mbean>

style="margin-left: 0.5in; margin-bottom: 0in; page-break-before: auto;">
face="Monospace"></server>

Deployment on jboss

The easiest is to make a copy of the
server/default directory, and create a server/derby directory.

Further you must put the derby.jar and
derbynet.jar files in server/derby/lib.

Copy the two mbeans and datasource.xml
of above in the deploy directory.

Checks

When you have started derby, you should
see that port 1527 got opened, and that the directory carnot has been
created under server/derby/data.

jdbc client

You can use the db2 driver db2jcc.jar,
db2jcc_license_c.jar.

The url looks like:
jdbc:derby:net://localhost/carnot

2007-11-18T17:21:00.000+01:00

Installing ubuntu 7.10 behind a proxy

I installed my laptop Dell D830 behind a proxy with a password. After putting in the install CD, I get a tryout system that shows me how ubuntu will look like.

In this system I already set the proxy, else I will get problems during installation that it cannot find the deb repositories.

I made proxy settings under System - Preference - Network Proxy, and, under Synaptic - Preferences - Network. I think the latter is most important. This will make the installation work.

After the installation I needed to set these proxy settings again.

2007-10-25T21:24:00.000+02:00

Updated Blogger

Finally got a bit further with blogger. It seems that usernames had to be updated, before blog clients would work.

Now I am curious whether xmls will work. That was my problem last time I used it: I could not paste in build.xml files.

Deploying weblogic 9.2 with openldap

2006-11-28T16:12:00.000+01:00

Install weblogic 9.2

Installed under
/usr/local/bea

Admin console:

http://localhost:7001/console

Start / stop

By default weblogic
comes with some preinstalled examples:

/usr/local/bea/weblogic92/samples/domains/wl_server

To start/stop a
weblogic domain:

bin/startWebLogic.sh
bin/stopWebLogic.sh

You can also stop
weblogic by killing the pid.

Also in the admin
console, environment, servers.

Quick start

/usr/local/bea/weblogic92/common/bin/quickstart.sh

Domains

Create domain

Create a new domain
with the configuration wizard

/usr/local/bea/weblogic92/common/bin/config.sh

create a new
domain
generate
automatically for weblogic server
username/password
weblogic/weblogic
development mode,
sun sdk 1.5
additional
configuration: yes
Adminserver
defaults: 7001
Add managed
server: name ms1, 7001
No clusters
No specific
machines
domain name
domain_oraxe, location /usr/local/bea/user_projects/domains

Delete a domain

Delete the directory
/usr/local/bea/user_projects/domains/<domain>

Configure

Configure wl92 for
xxx

Start administration
server for domain_oraxe

/usr/local/bea/user_projects/domains/domain_oraxe/bin/startWebLogic.sh

Jdbc

Jdbc - datasources
- new
name AuditTrail
jndi
AuditTrail.DataSource
type Oracle
driver Default
weblogic Oracle XA driver
connection pool
database xe
server localhost
username/password
xxx/xxx
test configuration
assign to
administration server
open properties
connection pool
maximum capacity
50
Save, activate
changes

Another datasource for
jms messages storage.

Make sure you do not
use a xa-enabled jdbc driver.

Jdbc - datasources
- new

oracleJmsStorageDS
oracleJmsStorageDS
Oracle bea type 4
(not xa)
Do not support
global transactions

Assign to
administration server
open properties
connection pool
maximum capacity
25
Save, activate
changes.

JMS Server

Services, Messaging,
jms server

Create new jms
server
Jms-server-0
New jdbc store
JDBCStore-Jms
AdminServer
oracleJmsStorageDS
prefix name jms
Persistent store -
JDBCStore-Jms
Target AdminServer

Jms Modules

Services,
Messaging, jms modules
New system module:
JmsModulexxx
default descriptor
and location
Target adminserver
Add resources: no
(doing later).
Save, activate.

Subdeployment

Add a subdeployment to the created jms module.
This will link the jms module to the jms server.

Edit
JmsModulexxx
Tab
subdeployments: New
Name JmsServer0
Target
Jms-Server-0
Save, activate

Queues and connectionfactory

Connection factory

xxxConnectionFactory,
jndi: xxxConnectionFactory
Advanced targets:
subdpeloyment JmsServer0
Edit
xxxConnectionFactory: Transactions: xa enabled
Save, activate

Queues

xxxApplicationQueue

xxxDaemonQueue

xxxSystemQueue

TestJMSQueue

All with same name
and jndi.
All with
subdeployment JmsServer0.
After creating
each queue, open its properties again and go to the delivery failure
tab; set redelivery delay override to 1000 and redelivery limit to
10.
Save, activate

Save configuration

Create template

/usr/local/bea/weblogic92/common/bin/config_builder.sh

Saves template under
/usr/local/bea/user_templates

Client setup

java.home must be
a jdk 1.5
Add
server/lib/weblogic.jar to the client's classpath.

It seems that wl92 does
not recognise a client's jndi.properties, so add jndi properties
hard-coded in a hash-table:

Hashtable
ht = new Hashtable();

ht.put(Context.INITIAL_CONTEXT_FACTORY,

"weblogic.jndi.WLInitialContextFactory");

ht.put(Context.PROVIDER_URL,

"t3://localhost:7001");

Context
ctx = new InitialContext(ht);

Setting up a different authentication provider

Ldap

In security realm,
myrealm, providers tab, authentication

Add a new openldap
provider.

Edit the properties

Name
openldap-provider
Control flag:
optional
Group base dn:
ou=groups, dc=de, dc=xxx, dc=ag, dc=test
User name
attribute: uid
Static group
object class: groupOfnames
Port: 389
User base dn:
ou=people, dc=de, dc=xxx, dc=ag, dc=test
User object class:
person
Static group name
attribute: cn
Principal:
cn=Manager, dc=de, dc=xxx, dc=ag, dc=test
Host: localhost
Credential:
carldap
Static Group DNs
from Member DN Filter: (&(member=%M)(objectclass=groupofnames))
Static Member DN
Attribute: member
User from name
filter: (&(uid=%u)(objectclass=person))
Group from name
filter: (&(cn=%g)(objectclass=groupofnames))

This is based on an
openldap with rootdn cn=Manager, dc=de, dc=xxx, dc=ag, dc=test and
password carldap.

To get this working,
load a ldif into ldap that contains following:

dn:
dc=de,dc=xxx,dc=ag,dc=test

objectclass:
top

objectclass:
dcObject

objectclass:
organization

dc:
de

o:
xxx

dn:
ou=People,dc=de,dc=xxx,dc=ag,dc=test

objectclass:
top

objectclass:
organizationalUnit

ou:
People

dn:
uid=weblogic,ou=People,dc=de,dc=xxx,dc=ag,dc=test

objectClass:
top

objectclass:
uidObject

objectclass:
person

sn:
Weblogic

cn:
Weblogic System Account

uid:
weblogic

userpassword:
weblogic

dn:
ou=Groups,dc=de,dc=xxx,dc=ag,dc=test

objectclass:
top

objectclass:
organizationalUnit

ou:
Groups

dn:
cn=Administrators,ou=Groups,dc=de,dc=xxx,dc=ag,dc=test

objectClass:
groupOfNames

objectClass:
top

cn:
Administrators

description:
Administrators group for weblogic

member:
uid=weblogic,ou=People,dc=de,dc=xxx,dc=ag,dc=test

That is, make sure you
have at least the admin weblogic user defined (the user you defined
when setting up the domain), and that this admin user belongs to a
group called Administrators.

When weblogic server
boots, it will read the file <domain>/servers/AdminServer/security/

boot.properties.If you
want to use a different user, make sure you adapt this file too.

To load the above file
(myldap.ldif)

/etc/init.d/ldap
stop && rm /var/lib/ldap/* && /etc/init.d/ldap start

ldapadd
-xv -D 'cn=Manager,dc=de,dc=xxx,dc=ag,dc=test' -w carldap -f
myldap.ldif

Test optional ldap authentication provider

We put the control flag
on OPTIONAL first. If configuration is not right, we should still be
able to login into the admin console.

The easiest is to add
an extra group to the ldif file, and make weblogic member of it:

dn:
cn=TestGroup,ou=Groups,dc=de,dc=xxx,dc=ag,dc=test

objectClass:
groupOfNames

objectClass:
top

cn:
TestGroup

description:
TestGroup for weblogic

member:
uid=weblogic,ou=People,dc=de,dc=xxx,dc=ag,dc=test

In the security realm
providers now add a audit provider that audits all security related
information. It will create a logfile under server/AdminServer/logs.

Now reboot the server.

In the audit log file
you can find the principals that get assigned to a successful login.
If all is well, you should also see a principal TestGroup now ( the
Administrators principal was already created by the default
authentication).

If you do not see then
you will need to debug the ldap connection. If all is well, you can
set the ldap authentication provider to required and the default to
optional.

Debug ldap problems

Under environment,
servers, adminserver you can set debugs.

Set debugs for

weblogic.security.adjudicator
weblogic.security.atn
weblogic.security.atz
weblogic.security.rolemap
debug security

This is the same as
adding a section to the config/config.xml file:

<name>AdminServer</name>

<server-debug>

<debug-scope>

<name>weblogic.security.adjudicator</name>

</debug-scope>

<debug-scope>

<name>weblogic.security.atn</name>

</debug-scope>

<debug-scope>

<name>weblogic.security.atz</name>

</debug-scope>

<debug-scope>

<name>weblogic.security.rolemap</name>

</debug-scope>

<debug-security>true</debug-security>

</server-debug>

<listen-address></listen-address>

</server>

Now restart the server,
and you will find a ldap trace file and extensive log files.

Deploying xxx

Settings for weblogic 92

Client:

<wsp>/lib:

weblogic.jar

<wsp>/etc/xxx.properties

JNDI.InitialContextFactory
= weblogic.jndi.WLInitialContextFactory

JNDI.URL
= t3://localhost:7001

JNDI.User
= weblogic

JNDI.Password
= weblogic

JNDI.PackagePrefixes
= -

Server:

xxx-engine.jar/xxx.properties

EJB.ServerVendor
= WEBLOGIC

JMS.MessageListener.ProcessingFailure.Pause
= 1000

Client.ServiceFactory
= ag.xxx.workflow.ejb.EjbEnvServiceFactory

Settings for weblogic 92 with ldap

Client:

<wsp>/lib:

weblogic.jar
weblogic-auth.jar
(this jar holds the xxx specific weblogic authentication classes
from xxx_HOME/examples/weblogic-auth)

<wsp>/etc/xxx.properties

JNDI.InitialContextFactory
= weblogic.jndi.WLInitialContextFactory

JNDI.URL
= t3://localhost:7001

JNDI.User
= weblogic

JNDI.Password
= weblogic

JNDI.PackagePrefixes
= -

Credential.Provider
=

Secure.Session.Factory
=
ag.xxx.examples.authentication.weblogic.WeblogicSecureSessionFactory

Security.Authentication.ConfigurationName
=

server

xxx.ear/ldap-sync.jar
(from xxx_HOME/examples/ldap-sync)
xxx.ear/xxx-engine.jar/xxx.properties

EJB.ServerVendor
= WEBLOGIC

JMS.MessageListener.ProcessingFailure.Pause
= 1000

Security.Authentication.Mode
= principal

Security.Authorization.SynchronizationProvider
= ag.xxx.examples.authorization.ldap.LDAPSynchronizationProvider

LDAPSynchronization.ServerName
= localhost

LDAPSynchronization.ServerPort
= 389

LDAPSynchronization.RootDN
= dc=de,dc=xxx,dc=ag,dc=test

LDAPSynchronization.UserFilter
= (&(uid=%v)(objectclass=inetOrgPerson))

LDAPSynchronization.ParticipantFilter
=
(&(objectClass=groupOfUniqueNames)(uniqueMember=uid=%v,ou=People,dc=de,dc=xxx,dc=ag,dc=test))

Client.ServiceFactory
= ag.xxx.workflow.ejb.EjbEnvServiceFactory

Problem with cleanup runtime / synchronization
caches

Currently some tests fail as the synchronization
between ldap and audittrail occurs too late. Timerbasedstrategy is
set at 10s.

If your run a cleanup, but cache is still there,
the engine might think audittrail is uptodate, where in fact it is
empty.

deployment of ejb under jboss

2005-11-25T16:18:00.000+01:00

Jboss deployment of HelloWorld EJB example

Deployment under jboss is relatively simple:
pack classes and deployment descriptors in jar
create ear
copy ear into deploy directory of jboss

Then to run the client:

create client java file that calls util class of HelloWorld ejb example
create client jar with proper jndi.properties
call client

To create the jar/ear we need to add the following to our build.xml file:

<target name="jar" depends="compile">

    <mkdir dir="${samples.jar.dir}" />

    <jar jarfile="${samples.jar.dir}/ejb-hello.jar">

    <fileset dir="${samples.classes.dir}" includes="**" excludes="**/client/**" />

    <metainf dir="${samples.meta-inf.dir}"

        includes="**"

        excludes="application.xml" />

    </jar>

</target>

<target name="ear" depends="jar">

    <mkdir dir="${samples.ear.dir}" />

    <copy file="etc/application.xml" todir="${samples.meta-inf.dir}" />

    <jar jarfile="${samples.ear.dir}/helloworld.ear">

        <fileset dir="${samples.jar.dir}" includes="**/*" excludes="**/client*.jar" />

        <metainf dir="${samples.meta-inf.dir}" includes="application.xml" />

    </jar>

</target>

<target name="deploy-jboss" depends="ear">

    <copy todir="${jboss4.deploy.dir}">

        <fileset dir="${samples.ear.dir}" includes="helloworld.ear" />

    </copy>

</target>

You also need to add some properties to your build-dist.properties file:

jboss4.deploy.dir=/usr/local/jboss-4.0.2/server/default/deploy

jboss4.client.j2ee.jar=/usr/local/jboss-4.0.2/client/jbossall-client.jar

The ear target also uses an application.xml file. This is a general file, and not propiety for jboss. It contains:

<?xml version="1.0" encoding="ISO-8859-1"?>
    <!DOCTYPE application PUBLIC '-//Sun Microsystems, Inc.//DTD J2EE Application 1.2//EN'     'http://java.sun.com/j2ee/dtds/application_1_2.dtd'>
    <application>
        <display-name>HelloWorld</display-name>
        <description>J2EE application to helloworld</description>
        <module>
            <ejb>ejb-hello.jar</ejb>
        </module>
    </application>

Ears could also have propiety deployment descriptors, for example when you want to deploy mbeans. However, my example is simple, and does not need it.

Now when you start jboss (jboss 4), and run ant deploy-jboss, you should see a successful deployment.

To make use of the newly deployed EJB, you will need to write a client file:

/**
* $Id$
*/
package com.jankester.tryout.client;

import java.rmi.RemoteException;
import javax.ejb.CreateException;
import javax.naming.NamingException;
import com.jankester.tryout.ejb.session.HelloWorld;
import com.jankester.tryout.ejb.session.HelloWorldHome;
import com.jankester.tryout.ejb.session.HelloWorldUtil;

/**
* @author jkester
*
*/
public class HelloWorldEjb
{

/**
* @param args
*/
    public static void main(String[] args)
    {
        System.out.println("calling client of HelloWorld");
        try
        {
            HelloWorldHome helloHome = HelloWorldUtil.getHome();
            System.out.println("Got HelloWorld home");
          HelloWorld hw = helloHome.create();
          String answer1 = hw.helloWorld();
          String answer2 = hw.helloWorld("It's me again ..");
          System.out.println("answer1=" + answer1 + " answer2=" + answer2);
        }
        catch (NamingException ne)
        {
          System.out.println("Failed getting home: " + ne.getMessage());
          System.out.println("exception=" + ne);
        }
        catch (RemoteException re)
        {
          System.out.println("Failed calling getHome: " + re.getMessage());
        }
        catch (CreateException ce)
        {
          System.out.println("Failed creating HelloWorld proxy: " + ce.getMessage());
        }
    }
}

The client file makes use of the interfaces that have been generated by xdoclet. We will pack all classes into a client-hello.jar.

Further we need to add a jndi.properties file for jboss. It contains:

java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory

java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces

java.naming.provider.url=localhost

This file will also be packed into the client-hello.jar. We need to add the following targets to our build.xml:

<target name="client-jar-jboss" depends="compile">
    <mkdir dir="${samples.jar.dir}" />
    <jar jarfile="${samples.jar.dir}/client-hello.jar">
        <fileset dir="${samples.classes.dir}">
            <include name="**/client/**" />
            <include name="**/ejb/**" />
          <exclude name="**/ejb/**/*Local*" />
            <exclude name="**/ejb/**/*Bean*" />
            <exclude name="**/ejb/**/*Session*" />
        </fileset>
        <fileset dir="etc/jboss" includes="*.properties" />
    </jar>
</target>
<target name="helloworld-jboss" depends="client-jar-jboss">
    <java classname="com.jankester.tryout.client.HelloWorldEjb"
        failonerror="yes"
        fork="yes"
        spawn="no">
        <classpath>
            <pathelement location="${samples.jar.dir}/client-hello.jar" />
            <pathelement location="${jboss4.client.j2ee.jar}" />
        </classpath>
    </java>
</target>

Now you can call the client file with “ant helloworld-jboss”. You should see output like this:

[java] calling client of HelloWorld

[java] Got HelloWorld home

[java] answer1=Hello world from HelloWorldBean! answer2=Hello It's me again ..!

generating ejb with xdoclet 1.2.3

2005-11-25T11:57:00.000+01:00

Testing jms client connections to sun8

2005-11-11T13:10:00.000+01:00

Here I had the problem that I did not know whether my jms on sun8 application server was properly configured.

This is what to do to call a queue defined in sun8, send a message and receive a message.
I used an example from sun java tutorial SimpleProducer.java and SimpleSynchConsumer.

import javax.jms.*;
import javax.naming.*;
import java.util.Properties;

public class SimpleProducer {
/**
* Main method.
*
* @param args the destination used by the example
* and, optionally, the number of
* messages to send
*/
public static void main(String[] args) {
final int NUM_MSGS;

if ((args.length <> 2)) {
System.out.println("Program takes one or two arguments: " +
" []");
System.exit(1);
}

String destName = new String(args[0]);
System.out.println("Destination name is " + destName);

if (args.length == 2) {
NUM_MSGS = (new Integer(args[1])).intValue();
} else {
NUM_MSGS = 1;
}

/*
* Create a JNDI API InitialContext object if none exists
* yet.
*/
Properties prop = new Properties();
prop.put(Context.INITIAL_CONTEXT_FACTORY,"com.sun.appserv.naming.S1ASCtxFactory");
prop.put(Context.PROVIDER_URL,"iiop://localhost:3700");
Context jndiContext = null;

System.out.println("Created initial context");

/*
* Look up connection factory and destination. If either
* does not exist, exit. If you look up a
* TopicConnectionFactory or a QueueConnectionFactory,
* program behavior is the same.
*/
ConnectionFactory connectionFactory = null;
Destination dest = null;

String connFactName = "XXXConnectionFactory";
try {
System.out.println("Trying to get connection factory");
connectionFactory =
(ConnectionFactory) jndiContext.lookup(connFactName);
} catch (Exception e) {
System.out.println("JNDI API lookup for " + connFactName + " failed: " + e.toString());
e.printStackTrace();
System.exit(1);
}
System.out.println("Retrieved connection factory");

try {
System.out.println("Trying to get destination");
dest = (Destination) jndiContext.lookup(destName);
} catch (Exception e) {
System.out.println("JNDI API lookup for " + destName + " failed: " + e.toString());
e.printStackTrace();
System.exit(1);
}
System.out.println("Retrieved destination");

/*
* Create connection.
* Create session from connection; false means session is
* not transacted.
* Create producer and text message.
* Send messages, varying text slightly.
* Send end-of-messages message.
* Finally, close connection.
*/
Connection connection = null;
MessageProducer producer = null;

try {
connection = connectionFactory.createConnection();

Session session =
connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
producer = session.createProducer(dest);

TextMessage message = session.createTextMessage();

for (int i = 0; i < NUM_MSGS; i++) {
message.setText("This is message " + (i + 1));
System.out.println("Sending message: " + message.getText());
producer.send(message);
}

/*
* Send a non-text control message indicating end of
* messages.
*/
//producer.send(session.createMessage());
} catch (JMSException e) {
System.out.println("Exception occurred: " + e.toString());
} finally {
if (connection != null) {
try {
connection.close();
} catch (JMSException e) {
}
}
}
}
}

I changed some small things with respect to the original:

I explicitly added some properties before building up the InitialContext; it probably works without as well
the factory connection name is here specific.
Factory and destination are retrieved separately for ease of debugging.
I removed the sending of an empty message.

The program compiles with:

javac -classpath j2ee.jar SimpleProducer.java

To run the program I used the following command line:

java -Dcom.sun.appserv.iiop.endpoints=localhost:3700 -classpath appserv-rt.jar:imqjmsra.jar:j2ee.jar:appserv-admin.jar:. SimpleProducer TestJMSQueue 3

All libraries except the j2ee.jar are specific for the sun8 jms. The jmvarg is also specific for this jms implementation. The program creates 3 messages on TestJmsQueue, and then actually hangs. With ctrl-c I stop it :-).

To read out the messages, I use almost literally:

import javax.jms.*;
import javax.naming.*;

public class SimpleSynchConsumer {
/**
* Main method.
*
* @param args the destination name and type used by the
* example
*/
public static void main(String[] args) {
String destName = null;
Context jndiContext = null;
ConnectionFactory connectionFactory = null;
Connection connection = null;
Session session = null;
Destination dest = null;
MessageConsumer consumer = null;
TextMessage message = null;

if (args.length != 1) {
System.out.println("Program takes one argument: ");
System.exit(1);
}

destName = new String(args[0]);
System.out.println("Destination name is " + destName);

/*
* Create a JNDI API InitialContext object if none exists
* yet.
*/
try {
jndiContext = new InitialContext();
} catch (NamingException e) {
System.out.println("Could not create JNDI API context: " +
e.toString());
System.exit(1);
}

/*
* Look up connection factory and destination. If either
* does not exist, exit. If you look up a
* TopicConnectionFactory or a QueueConnectionFactory,
* program behavior is the same.
*/
try {
connectionFactory =
(ConnectionFactory) jndiContext.lookup("XXXConnectionFactory");
dest = (Destination) jndiContext.lookup(destName);
} catch (Exception e) {
System.out.println("JNDI API lookup failed: " + e.toString());
System.exit(1);
}

/*
* Create connection.
* Create session from connection; false means session is
* not transacted.
* Create consumer, then start message delivery.
* Receive all text messages from destination until
* a non-text message is received indicating end of
* message stream.
* Close connection.
*/
try {
connection = connectionFactory.createConnection();
session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
consumer = session.createConsumer(dest);
connection.start();

while (true) {
Message m = consumer.receive(1);

if (m != null) {
if (m instanceof TextMessage) {
message = (TextMessage) m;
System.out.println("Reading message: " +
message.getText());
} else {
break;
}
}
}
} catch (JMSException e) {
System.out.println("Exception occurred: " + e.toString());
} finally {
if (connection != null) {
try {
connection.close();
} catch (JMSException e) {
}
}
}
}
}

Here I only changed the original connection factory name.
This program compiles/runs in similar way.

javac -classpath j2ee.jar SimpleSynchConsumer.java

java -Dcom.sun.appserv.iiop.endpoints=localhost:3700 -classpath appserv-rt.jar:imqjmsra.jar:j2ee.jar:appserv-admin.jar:. SimpleSynchConsumer TestJMSQueue

The program gets the messages created with the program before.

To test for other environments, make sure you use the implementation specific initial context properties, and have the implementation specific jars in your classpath.

Compiling with jdk1.3.1

2005-11-09T11:05:00.000+01:00

Recently I tried to build a project under Suse 9.3 with jdk1.3.1. Normally I use 1.4.2, and all went well. However when I set my java to jdk1.3.1 and start up the compile, I get the following error:

[javac] Compiling 1634 source files to /home/jan/workspace/release/build.bak/xxxx/build/classes
[javac] error: compiler message file broken: key=compiler.err.sun.io.MalformedInputException arguments=null, null, null, null, null, null, null

I found out that it was while the original charset of the files was different as the locale of my current shell.
The command locale shows:
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
..

When I made an explicit `export LANG=en_US.ISO-8859-1` I could run my compile again. Strangely, jdk1.4 does not suffer from this problem.

To change my environment to jdk1.3.1 and another ant, I use a source script change-java-ant-1_3_1.source:
export JAVA_HOME=/usr/local/jdk1.3.1_16
export ANT_HOME=/usr/local/apache-ant-1.6.3
export PATH=$JAVA_HOME/bin:$PATH
export PATH=$ANT_HOME/bin:$PATH
alias ant="ant --noconfig"
export LANG=en_US.ISO-8859-1

echo "run with source, and not as shell; else it gets forked"
echo "alias of ant set to ant --noconfig"
echo "LANG set to en_US.ISO-8859-1 so that latakia compile works"
echo
echo "test with java -version"
echo " ant -version"
echo " locale"

The --noconfig is needed so that the /etc/ant.conf will not be read. This ant.conf file has already been set to my suse rpm-based ant.
To load the source script I must use source. When I would use a shell to execute it, the new settings would only be valid inside the new shell.

Websphere 6 on Linux

2005-11-04T16:38:00.000+01:00

Yesterday I started with the installation of websphere on Linux, Suse 9.3. I downloaded was.cd.6000.trial.base.linux.ia32.tar.gz from the ibm website, and unpacked it.

As logged in user, I issued a xhost + command.
Then as root, I ran WAS/install to start the installation.
I chose defaults, and a full installation, which installs under /opt/IBM/WebSphere/AppServer/.

At the end of the installation, the install program asks to run firststeps. I started that, and asked to check the installation. This check succeeded, amongst it also started the AppServer.
The links of Sample Gallery and AdminConsole however did not work. Probably it is not capable of starting up a webbrowser by itself. So, I just stopped the AppServer again from the firststeps, and finished the installation.

The server can be started now as root from /opt/IBM/WebSphere/AppServer/ :
bin/startServer.sh server1
and stopped again with
bin/stopServer.sh server1

You can see that the server is running with the command
netstat -an | grep LISTEN
you should see ports 9080, 9060, 9443, ..

To start the adminconsole, open a browser with
http://localhost:9060/ibm/console/
Examples applications can be opened with
http://localhost:9080/WSsamples/en/index.html
http://localhost:9080/hitcount
http://localhost:9080/PlantsByWebSphere/

Next: how to do a simple deployment.

Autostart in kde

2005-09-27T18:37:00.000+02:00

To make programs start automatically in kde, drag the icon inside ~/.kde/Autostart directory and choose "Link here".

rsync with ssh

2005-09-26T20:48:00.000+02:00

Setup rsync from laptop to a remote server.
To get this done, I followed the steps described in http://www.jdmz.net/ssh/

The commands that I used:
rsync -avz -e ssh Documents/gnupg-data/ jan@www.jankester.com:/home/jan/backup_rsync
ssh-keygen -t dsa -b 2048 -f .ssh/ewing_ssh_rsync_key

added entry in commands in authorized keys remote
added validate-rsync script on remote under /home/jan/cron

Test again whether new key works
rsync -avz -e ssh -i /home/jan/.ssh/ewing_ssh_rsync_key Documents/gnupg-data/ jan@www.jankester.com:/home/jan/backup_rsync

Now add a script to sync anything you like /home/jan/cron/backup-ewing-on-vs01-05.sh:

#!/bin/sh

RSYNC=/usr/bin/rsync
SSH=/usr/bin/ssh
KEY=/home/jan/.ssh/ewing_ssh_rsync_key
RUSER=jan
RHOST=www.jankester.com
RPATH=/home/jan/backup_rsync

LPATH=/home/jan/Documents/gnupg-data
$RSYNC -azv -e "$SSH -i $KEY" $LPATH $RUSER@$RHOST:$RPATH

LPATH=/home/jan/.ssh
$RSYNC -azv -e "$SSH -i $KEY" $LPATH $RUSER@$RHOST:$RPATH

LPATH=/home/jan/ssh
$RSYNC -azv -e "$SSH -i $KEY" $LPATH $RUSER@$RHOST:$RPATH

LPATH=/home/jan/vnc
$RSYNC -azv -e "$SSH -i $KEY" $LPATH $RUSER@$RHOST:$RPATH

LPATH=/home/jan/Documents/technical_tips
$RSYNC -azv -e "$SSH -i $KEY" $LPATH $RUSER@$RHOST:$RPATH

LPATH=/home/jan/Documents/personal
$RSYNC -azv -e "$SSH -i $KEY" $LPATH $RUSER@$RHOST:$RPATH

LPATH=/home/jan/.bash*
$RSYNC -azv -e "$SSH -i $KEY" $LPATH $RUSER@$RHOST:$RPATH

Opening

2005-09-15T10:36:00.000+02:00

Welcome
my first new blog page. I will put some work comments etc, tips and tricks, and maybe even some funny stories.

Jan Kester Blog

Logging in selenium

Junit4 running parallel junit classes

Run jmeter from eclipse

Debugging against jmeter

Good principles of test automation

Test automation in agile

SSL handshake failed: Secure connection truncated

Grinderstone under linux

Grinderstone and instrumentation

record() not wrap()

Using grinder 3.4 and jython 2.5.1

My first grinder runs

Adding your own styles

My first grinderstone project

Setting up ldap on Ubuntu 9.10

Publishing xml

encrypt directory

Using sdhc card from boot

Ubuntu: starting db2 at bootup

Websphere 6.1 administrative security + self signed certificates

Installing websphere 6.1 under hardy-heron

Dual screen for Dell D830

VPNC

jboss with embedded derby in network mode

Deploying weblogic 9.2 with openldap

Install weblogic 9.2

Admin console:

Start / stop

Quick start

Domains

Create domain

Delete a domain

Configure

Jdbc

JMS Server

Jms Modules

Subdeployment

Queues and connectionfactory

Connection factory

Queues

Save configuration

Client setup

Setting up a different authentication provider

Ldap

Test optional ldap authentication provider

Debug ldap problems

Deploying xxx

Settings for weblogic 92

Client:

Server:

Settings for weblogic 92 with ldap

Client:

server

Problem with cleanup runtime / synchronizationcaches

deployment of ejb under jboss

generating ejb with xdoclet 1.2.3

Testing jms client connections to sun8

Compiling with jdk1.3.1

Websphere 6 on Linux

Autostart in kde

rsync with ssh

Opening

Problem with cleanup runtime / synchronization
caches