急急！！！DB2,Websphere,AIX的安装与配置！！

ddlldd2000

各位DX，有谁在AIX上安装配置过Websphere及DB2的请帮忙：
1.如果Websphere 与DB2 在一个机器上，怎么配置？在DB2中如何配置Websphere的部分，在Websphere中如何配置DB2?

2.如果在HA的环境下，比较理想的资源方式应该是一台RS/6000装Websphere,另一台装DB2,又该如何配置Websphere与DB2? 但是当双机进行切换，比如DB2的主机Down了，备机(Websphere)上应该如何配置？只需要在ha_startup shell中加入DB2的启动吗？反过来，Websphere的机器Down了呢？（在IBM上见到有Websphere Cluster的文档，但是上面的例子举例用了4台机器，大部分HA的情况下，我们只有双机，这种情况下怎么办？）。我想，如何这样不行，是不是只有将DB2和Websphere放在一台机器上了？资源利用不好呀！

本人对AIX与DB2较熟，对Websphere很陌生，希望大家帮助！

因为有个面试可能要问到Websphere在AIX下与DB2配置，所以比较急，请在这个环境下有经验的人指导一下。

ddlldd2000

自己Up一下，并将自己找到的文档share 一下，并希望有安装更新版本的DX根据下面的东西多补充，让大家都有提高，谢谢！

Introduction

This document outlines very briefly the steps required to deploy
WebSphere on AIX/NT in a stand alone configuration  whereby DB2,
WebSphere and HTTP Server all reside on the same machine.


While this document is targeted towards installation on AIX machines,
and does include some information specific to this platform, the
general procedure is applicable to any target hardware / operating
system.
Required Software

The installation process is described herein for the following software
levels, and all the software listed below should be considered pre-
requisites for this install procedure:

 DB2 6.1
 Latest (or supported) fixpack for DB2 6.1, e.g. fixpack 3
 JDK 1.1.8
 Latest (or supported) PTF for JDK 1.1.8 JRE, e.g. PTF 7
 WebSphere 3.0.2
 Latest (or supported) fixpack for WebSphere 3.0.2, e.g. fixpack
3.0.2.2
 IBM HTTP Server 1.3.6.2

This guide may apply equally well to later versions of any of the
software components, but the versions listed above were the ones used
in compiling this document.

Install Procedure

Shutdown db2/apache/existing websphere services for each
install/update.

Reboot after each install/update whether or not you are prompted.

Install all components(httpserver/jdk/db2/websphere) separately.


HTTP Server

HTTP Server(the IBM derivative of Apache) should be installed
separately   Install either from the HTTP download or the WebSphere CD
by selecting custom install/http server.  Do not install the plugin at
this stage.

Reboot after installation and start.  On NT HTTP server is installed as
a service and starts automatically.  Enter "localhost".  This should
display the welcome page.  The HTTP server is now active.


Database Server

Install DB2.

Record the DB2 admin id that will be given to Websphere.

Ensure that the db2 install directory does not contain spaces.  Spaces
generate an NT2140 error on WebSphere initial startup when WebSphere
tries to find the DB2 install directory.  In general avoid spaces in
directory/file names.

1. Install the DB2 fixpack;
2. Migrate the DB2 instance;
3. Create the WAS database:
‘db2 create db was’
4. Update configuration for WAS database:
‘db2 update db cfg for was using applheapsz 256’

5. Start db2 command line processor  “c:>;db2cmd”

6. Set db2 diaglevel(error messaging) to 4.  “db2 update dbm
config using diaglevel 4”

7 Tail/monitor db2diag.log.

8.Connect to was manually to prove conectivity.  “db2 connect to was”
   Db2diag.log shows was database starting.


WebSphere Application Server
5. If JDK 1.1.8 was not installed with AIX/NT, install it(free download
from IBM Website.
6. Install the PTF for the Java JRE (AIX typically ships with JDK 1.1.8
GA version);
7. Create the WAS userid with NT administrator permissions.
8. Ensure the JAVA_HOME environment variable is set:
9. Echo %JAVA_HOME%
10. Check java jdk version by typing java –fullversion from command
line.
11. Check classpath  echo %classpath%.  JDK root dir should be on
classpath.
12. Check path  “echo %path%.  JDK bin directory shuld be on class path.
13. Ensure that there is no conflict with other JDKs.
14. Ignore message about jdk exceeding requirements.
15. export JAVA_HOME=/usr/jdk_base’
16. Create a userid for the WebSphere installation (this should be
common across all WebSphere nodes as it is used for security);
17 Stop HTTP Server.
18 Choose Custom installation.

19 Select all options except db2 and http server.  Select http
server plugin.

20 Select other for JDK.

21 Browse to and select jdk118 directory.

22 Select desired install path (or leave default);

23 Select the default app.  This will verify the installation.

24 Reboot after install.

25 Install the WebSphere fixpack (always ensure that both HTTP
Server and WebSphere are stopped before installing the fixpack or it
will break and still report a successful install – on NT disable the
HTTP Server and WebSphere services and reboot the machine to ensure
DLLs are not locked).  Check the readme.txt file.

26 Ensure environmental variable java_home is set to jdk directory.

27 Check install log file in appserver directory for errors.

28 Start Websphere.  Db2diag.log shows table creates.  Check the
java.exe processes in task manager.  There is one for the admin server,
the adminconsole and one per application server.  Check memory usage.

28 Check db2 log and and tail appserver/logs/tracefile.

29 Ignore spurious sqlcodes.  Check for table creates.

30 Check tracefile for “available for e-business message”.

Indicates that websphere is up.  You are nearly there.

31 Start the console.

32 Start the default server.

33 Check localhost:80 on browser.

34 Check loclhost/servlet/snoop - installation verification
servlet.

35 Check localhost/webapp/examples - installation verification
servlet.

36 Stop default server application server.

37 Stop admin server from console.  This stops the admin server
service.

Check in task manager that the java.exe processes have stopped.

Kill java process if necessary.

If one remains then NT will generate a 1067 error on subsequent
WebSphere startup.

38 Download and apply 3.0.2.2 efixes from websphere support
website or apply fixpack 3 using same procedure as fixpack 2.

Modify admin.config file to include efixes at start of adminserver
classpath

For xml transformation copy xerces and xlan jar files to appserver/lib
directory.

Add xerces/xlan directories to admin classpath.

Add ivjejb302.jar to dependent class path.

And that's it.

TOP TIP.  For your initial application deployments put all classpaths
on dependant class path rather than application classpath.

Good luck!

ddlldd2000

自己再UP一下，看到另外一个写得比较详细的说明,share出来：
I presume you are following the document supplied by IBM for installing WAS
3.5 & DB2 6.1 on AIX

To set up DB2 as a client to a remote database.
On the machine with the database that you want to connect to:
1. Configure the database manager to use TCP/IP on AIX:
   On the server machine, log in as the DB2 instance owner.
   Set DB2COMM to TPC/IP, e.g.,
                db2set DB2COMM=tcpip
2. Edit /etc/services file to include DB2 connection and
   interrupt service ports if they do not already exist, e.g.,
        db2cdb2inst1     50000/tcp   # DB2 connection service port
        db2idb2inst1     50001/tcp   # DB2 interrupt connection
where  db2cdb2inst1 if you are following the default userid db2inst1 for the
installation

3. Update the database manager configuration, e.g.,
                db2 update dbm cfg using svcename db2cdb2inst1
   the arguement after svcename must match the name of the service that you
placed in /etc/services.


4. Add the following line in the db2profile which is located in the
/home/db2instance_owner/sqllib directory :
               export DB2COMM=tcpip

5. Catalog the node, e.g.,
       db2 catalog tcpip node loop remote <hostname>; server
<DB2_connection_service_port>;
where <DB2_connection_service_port>; is  db2cdb2inst1 if you are following
the default userid for the installation & loop is just a alias name of the
node,

6. Catalog the database, e.g.,
       db2 catalog database was as wasloop at node loop
where wasloop is as dbalias of was db which is created as part of
installation
7. Stop and start DB2.
       % db2stop
       % db2start
8. Make sure admin.config has the dbURL point to the database alias  ie,
com.ibm.ejs.sm.adminServer.dbUrl=jdbc\:db2\:<dbAliasName>;
The db alias should be wasloop in this case if you have entered the command
in step 6

Now, you can start your admin server. You won't see any error in your
tracefile.

大连老K

1、如果webspher或db2安装在同一台机器上，值得注意的是要把websphere使用的db2数据库catalog成一个远程的数据库
2、要看采用何种HA方式，一、一种方式是一台主机，一台备份机，另一种方式是两台互为备份，这两种方式都可以实现。

ddlldd2000

老大,我现在非常想知道在HA的两种方式下,你如何实现的？可以email: ddlldd2000@yahoo.com，谢谢老大！

好象你今天上网特早呀！

ddlldd2000

老大

ddlldd2000

老大，另外，有两个问题请教一下。

第一、在HA的情况下，如果将DB2安装在陈列盘上，在生产机与备份机上安装完DB2，如何在生产机上配置完后，让备份机有相同的配置？也即是说，配置文件有哪几个？如果拷贝到备份机上，还需要做一些什么修改？

第二、websphere使用的db2数据库catalog成一个远程的数据库，在catalog时用的是远程主机名，当db2的机器down，websphere的机器接管，这时db2所在的主机名不见了，websphere是否要重新catalog？那就是在HA的启动脚本里加入stop websphere,startup db2, catalog database,startup websphere?

先谢谢了！

大连老K

DB2和Websphere的双机我没有实践过！
第二个问题我说的是当db2和websphere安装在同一台机器上时要这么作，所谓的远程机器其实就是本地机器，只是用catalog远程机器的方式而已。（was4＋db2 7），was5.0的参数都保存在了XML文件中，所以不需要用DB2来保存参数了。

ddlldd2000

谢谢老大！

又问过一哥们，他说应该是：
在本机上装DB2,阵列上放数据库。在主机上建库，然后在备机上catalog dbname，注意修改database manager的参数，让主备机相同。

看来比较合理，但我有点怀疑，DB2这个智能？备机上没有相应的配置，只catalog一下就行了（当然，这个时候sharevg应该在备机上varyon了）？

有没有人能更明白的解释一下？

vlife

如果采用主机和备机的形式，明确的以下：
1、应用和数据库是分开的，两台机器上都装有websphere的应用，这个保持同步应该很简单，发布的时候两台机器同时发布就可以了。
2、数据库放在阵列上，切换的时候，数据库方面需要做的只是catalog一下就可以了。