=====================================================================
WebSphere Application Server Support Bulletin
=====================================================================
Issue 17 September 2001
--------------------------------------------------------------------
The WebSphere Application Server Support Bulletin highlights the
latest code fixes, support information, and hot tips about your
favorite WebSphere Application Server products.
=====================================================================
IN THIS ISSUE:
---------------------------------------------------------------------
1- Create a User-Defined Service for WebSphere Application Server 4.0
2- Using Microsoft SQLServer as a Persistent Session database
3- Setting up the DB2
JDBC 2.0 Driver Properly
4- Support Resources
5- Subscribe/unsubscribe to this newsletter
6- Newsletter Owner
=====================================================================
1- Create a User-Defined Service for WebSphere Application Server 4.0
---------------------------------------------------------------------
In the Windows version of WebSphere 3.X, the adminserver was started
as a service. However, this is not the case in WebSphere 4.0. In
order to gain this functionality in that version, the following
process (modified from a Microsoft Tech Article
http://support.microsoft.com/support/kb/articles/q137/8/90.asp can be used.
1. Get a copy of instsrv.exe and srvany.exe that are in the
NT Resource Kit.
2. Go to the command line and invoke:
\INSTSRV.EXE \SRVANY.EXE
where path is the path to these files and
is the name you want to call the WebSphere service.
3. You will see a message that the service was successfully installed.
4. Run REGEDT32.EXE, which is the 32-bit version of the Windows
Registry Editor. Please remember that all Microsoft admonitions
about editing the registry on the system apply.
5. Locate the sub key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
6. From the edit menu, click Add Key. Type the following and click OK.
Key Name: Parameters
Class:
7. Select the Parameters key.
8. From the Edit menu, click Add Value. Type the following and click OK:
Value Name: Application
Data Type : REG_SZ
String : \
where \ is the drive and full path to the
application executable including the extension
(i.e., C:\WebSphere\AppServer\bin\startserver.bat)
9. By default, this service is set to start automatically on system
boot. If you wish to change this, go to Services and change the
startup setting.
This will successfully create a service that will allow the service
to automatically restart on system reboot. WebSphere 4.x AEs cannot
be stopped via this service. For that, you will have to use the
stopserver.bat file or call that file from the First Steps application.
=====================================================================
2- Using Microsoft SQLServer as a Persistent Session database
---------------------------------------------------------------------
If you want to use Microsoft SQLServer as a Persistent Session database
(via MERANT SequeLink JDBC Driver) with WAS 3.5.3 or 3.5.4, obtain
and apply the WebSphere latest session efix PQ50656. This efix replaces
PQ40815, PQ42166, PQ44646 and PQ47663. New fixes included are :
- Session counter mInvalidatedSessionCount is not
incremented.
- With security enabled, in 2.2 mode, sessions with
existing sessionid are created whenever unauthorized
access is made.
- Provide options for turning off JCE Id generation.
- In Multi-row persistent sessions don't use
thread id as the key to monitor the changes made to the
session object.
- Create unique index when creating a table to prevent
collisions of the session id's.
- In manual update mode, whenever property is changed,
last access time is not updated in the database.
- Sessions persistence is supported with SQL Server .
=====================================================================
3- Setting up the DB2 JDBC 2.0 Driver Properly
---------------------------------------------------------------------
The JDBC 1.2 driver is the default driver on all operating systems.
To take advantage of the new features of JDBC 2.0, you must install
JDK 1.2.2 or above. Before executing an application that takes
advantage of the new features of JDBC 2.0, you must set up your
environment according to the instructions described below.
For UNIX
You set up your environment to use the JDBC 2.0 driver by sourcing
the usejdbc2 shell script from the sqllib/java12 directory. i.e.
. usejdbc2
If you want your applications to always use the JDBC 2.0 driver,
consider adding the usejdbc2 command to your login profile,
such as .profile, or your shell initialization script,
such as .bashrc or .kshrc (you need to modify the scripts for C shell).
Ensure that this command is placed after the command to run db2profile,
as db2profile sets up your environment to use the default JDBC
driver (i.e. JDBC 1.2). e.g.
. /home/db2inst1/sqllib/db2profile
. /home/db2inst1/sqllib/java12/usejdbc2
To switch back to the JDBC 1.2 driver, execute the following command from
the sqllib/java12 directory:
. usejdbc1
When you source the shell script (". usejdbc1" or ". usejdbc2"),
it modifies the environment variables (CLASSPATH, PATH, and LIBPATH
(AIX), SHLIB_PATH (HP-UX) or LD_LIBRARY_PATH (other UNIX platforms))
to point to the appropriate directories that contain the desired version
of the JDBC driver and the supporting binaries.
For Windows
Ensure the following services are stopped before you perform the set up.
DB2 JDBC
Applet Server
DB2 JDBC Applet Server - Control Center
IBM WS AdminServer
To use the JDBC 2.0 driver, you set it up by issuing the following
command in the sqllib\java12 directory:
usejdbc2
To switch back to the JDBC 1.2 driver, issue the following
command in the sqllib\java12 directory:
usejdbc1
To ensure that you have the version of the JDBC driver
you want set up successfully, you need to make sure that all of
the files are copied to the sqllib\java and the sqllib\bin directories
without errors. In case you get the following messages after you issue
the usejdbc1 or usejdbc2 command,
"Access is denied."
"The process cannot access the file because it is being
used by another process."
it may be because one or more of the above services is still running.
Go to the Windows Services window and stop the services if they are
started. Then try running the usejdbc1 or usejdbc2 command again.
If you are still getting errors, issue the command "db2stop force"
and retry. The worst case is to reboot your system but before you
rerun the usejdbc1 or usejdbc2 command, ensure the above mentioned
processes are stopped. On Windows, usejdbc1.bat and usejdbc2.bat
work differently compared to the shell scripts usejdbc1 and
usejdbc2 on UNIX. The command usejdbc1.bat copies the JDBC 1.2
driver files to the sqllib\java and sqllib\bin directories.
usejdbc2.bat copies the JDBC 2.0 driver files to the sqllib\java
and sqllib\bin directories. i.e. the
Java applications should always
use the db2java.zip file from the sqllib\java directory.
Note: The instructions on setting up the JDBC driver in the
"DB2 UDB Application Building Guide Version 7" is incorrect.
It has been corrected in the release notes for DB2 V7.1 FP3/DB2 V7.2.
You can download the release notes (ReleaseNotes.txt) from the
following URL:
http://www.ibm.com/cgi-bin/db2www/data/db2/udb/winos2unix/support/download.d2w/r\ eport#V7
=====================================================================
4- Support Resources
---------------------------------------------------------------------
Support resources for WebSphere Application Server Standard and
Advanced editions can be found at
http://www.ibm.com/software/webservers/appserv/support.html You will find information about how to get support for specific
WebSphere related questions at
http://www.ibm.com/software/webservers/appserv/support_ask.html Support resources for WAS Enterprise Edition Component Broker
can be found at
http://www.ibm.com/software/webservers/appserv/cb/support/ Be sure to check out the WAS Library page at
http://www.ibm.com/software/webservers/appserv/library.html. This
page contains links to product documentation as well as WebSphere
Application Server white papers and post release developer's
notes which provide useful information to WebSphere Application
Server customers.
=====================================================================
=====================================================================
5- Subscribe/unsubscribe to this newsletter
---------------------------------------------------------------------
-> TO SUBSCRIBE/UNSUBSCRIBE THROUGH THE WEB:
Go to
http://www.ibm.com/software/mailing-lists/ -> TO UNSUBSCRIBE BY EMAIL:
Send an email reply with the
word "Cancel" in the subject
line. Include in the body of the email the text
"email=your email address"
-> TO UNSUBSCRIBE BY REGULAR MAIL:
Send a letter with your email in the text to IBM Software,
Route 100, Building 1, Somers, NY 10589
=====================================================================
6- Newsletter Owner
---------------------------------------------------------------------
------------------
Tony Chen
SCJP, ICS & ICSD (WebSphere)
