David Dietrich's Business Technology Blog » IBM

Using Verifone RiTA software with IBM WAS

David Dietrich — Mon, 22 Feb 2010 21:53:32 +0000

If you are running the RiTA software by Verifone, you may encounter a number of issues configuring the software to work in an IBM WebSphere environment. There are two issues you want to avoid:

Not being able to find the tid.jcc file
Not having the .jar files in the correct location

First, the tid.jcc needs to be in the default server directory for IBM WAS. On Linux, this will most likely be the /opt/IBM/WebSphere/AppServer/profiles/AppSrv01 directory.

To add the tid.jcc reference, you will want to link it from your RiTA installation directory (the default directory being /opt/rita). Run these commands:

>cd /opt/IBM/WebSphere/AppServer/profiles/AppSrv01
>ln -s /opt/rita/tid.jcc

Next, you will need to link all of the RiTA .jar files to your extensions directory in the Java Runtime Engine. Run these commands:

>cd /opt/IBM/WebSphere/AppServer/java/jre/lib/ext
>find /opt/rita/lib/rita -name ‘*.jar’ -exec ln -s {} \;

You will now have symbolic links to all of the RiTA .jar files and it will be accessible to WebSphere and all other Java applications.

Changing the host name in IBM WAS

David Dietrich — Thu, 18 Jun 2009 23:05:42 +0000

Many times in a virtual environment, it is advantageous to be able to change the host name. But if you have a virtual guest with IBM WAS installed, cloning the guest may result in the new guest being unable to stop the server, run CORBA properly, or gain access to your message queues within WAS. Therefore, you need to reset the host name for WAS.

To do this, go to the wsadmin.sh prompt. If you don’t know where wsadmin.sh is, run >locate wsadmin.sh. Then change directory (cd) into the directory that locate returned. To start WAS admin, type the following commands (assuming your server is called server1 and the node is named oldMachineNameNode01):

./wsadmin.sh -profile server1 -lang jacl

Once inside the WAS admin tool, run the following commands:

wsadmin>$AdminTask changeHostName { -nodeName oldMachineNameNode01 -hostName newwasVMmachineName };
wsadmin>$AdminConfig save
wsadmin>exit

Restart WAS, and your new machine name should work fine.

Updating a database option in DB2

David Dietrich — Thu, 21 May 2009 02:58:40 +0000

Sometimes after a database has been created, you may want to move where the default log path is. Or you may want to change DB2 places the log path in the home directory, and you may want to have the logs stored on another storage device.

> db2 UPDATE DB CFG FOR MyDB USING NEWLOGPATH>

Stop and restart DB2 (db2stop force and db2start). Your new log path is now active.

Updating the log path in DB2

David Dietrich — Wed, 20 May 2009 23:25:07 +0000

Sometimes after a database has been created, you may want to move where the default log path is. DB2 places the log path in the home directory, and you may want to have the logs stored on another storage device.

Login as the DB2 adminstrative user, then type the following command to change your log path:

> db2 UPDATE DB CFG FOR MyDB USING NEWLOGPATH /db2data/AnyDirectory/NODE0000/logdir

Stop and restart DB2 (db2stop force and db2start) and the your new log path will now be active.

Dropping a DB2 database

David Dietrich — Thu, 12 Feb 2009 21:39:26 +0000

Normally, to drop a database in DB2, you run the following command:

>db2 drop db YourDb

If you run into errors trying to drop the database, you may need to recatalog the database. You can run the following series of commands:

>db2 uncatalog db YourDb
>db2 catalog database

Restart DB2.

Then run:

>db2 drop db YourDb

Changing a DB2 server name

David Dietrich — Wed, 11 Feb 2009 23:57:51 +0000

If you find DB2 not being able to start because of a server name problem, it most likely is caused by moving a virtual machine and not renaming the DB2 database.

To update DB2 to the proper name:

Stop DB2 as administrator (db2inst user).
>su – db2inst
>db2stop
If there are open database connections, then force them off.
>db2stop force

Go to the sqllib directory.

Edit the db2nodes.cfg file. The file is usually read-only, so make enable writing first.
>chmod u+w db2nodes.cfg
>vi db2nodes.cfg

In the db2nodes.cfg file, rename the existing computer name to that of the new computer name.

Save the file.

Reset the permissions to read-only.
>chmod u-w db2nodes.cfg

Start DB2.
>db2start

You should no longer see any error messages about finding the database.