William Janssen

Not sure what you mean, they are printed unless the JIT compiler has taken the piece of code and compiled/optimzed the code thereby loosing the direct coopling between line numbers in the javasource code and code exceuted.

Since only the latest versions of WebSphere support a 64bit JDK and 5.x only supports a 32bit jdk it is not possible to get a heap size of 45Gb on WAS 5.x. The maximum size depends on the OS WAS runs on, the memory settings on the OS and the amount of native memory used by the JVM (e.g. prepared statements).The golden rule is to check the GC output to see the amount of memory you need for your setup.

Using System.out is a bad practice from a performance and maintannce point of view and those statements can even be disabled by the WebSphere Admin. But the statements are normally logged into the SytemOut.log in the [APPSERVER_INSTALL/logs/[SERVER]/ directory.

This is where the application assembly toolkit comes in, you can open up the ear file delivered to you and before deployment you can add, remove or adjust most resources within the ear file.
Otherwise shared libs or an extra claas path definition.

WAS 5.1 is only withdrawn from marketing by the end of feb., support will last for at least one year.
http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg27004980#ver51

It has announced withdrawn from market(ing) not from support, support will be there for at least one more year.

It has announced withdrawn from market(ing) not from support, support will be there for at least one more year.

It is missing the native libraries which come with the db2 client. The new drivers packaged in db2jcc.jar conatin a type 4 driver which you can use without a db2 client installed.

- Define the JDBC provider (in the admin console, resources -> JDBC providers)
- Within this provider define a datasource pointing to youre database

Call this datasource from your code with the example provided before, that's it.

Because you probally do not have a gateway / proxy locally.
This http header is added by the proxy / gateway to the http request and is not set by the browser.

Unless you set the maximum age of a cookie, with setmaxAge(int sec), the getMaxAge will always return -1 which is the default (for some cookies it can be confiugred within the appserver the application is executed). The scope is only the cookie object on which it is set.

Creating JDBC connections using Microsoft SQL is explained in http://publib.boulder.ibm.com/infocenter/ad51help/index.jsp?topic=/com.ibm.etools.rsc.doc/tasks/tdbconn_sqlserver.htm

From that point, it is like in any other environment, eg:

Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY,
"com.ibm.websphere.naming.WsnInitialContextFactory");
env.put(Context.PROVIDER_URL, "corbaloc:iiop:myhost.mycompany.com:2809");
Context initialContext = new InitialContext(env);
DataSource specificDataSource = (DataSource) initialContext.lookup("java:comp/env/jdbc/myds");

Besides the web.xml there is also a context root, did you check if that's right? Or the port number of the webcontainer or http server (be sure to propagte the plugin, and adjust the virutal host definiton and the webserver)

Agree, just tried to explain it in short.

Using other certificates then the dummy ones provided doesn't make HTTPS traffic or connections more or less secure. Custom certificates can prevent clients from connecting to server components which (also) require client side certificates to cummunicate.