Business

Using Verifone RiTA software with IBM WAS

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.

The Essential Startup Reader: 10 Lessons in Entrepreneurship

Adding custom palettes to Dundas pie charts in .NET 3.5x

One of the new features in Dundas 6.x and above, is the ability to create custom palettes of colors and apply them to pie charts. This way you no longer have to settle for Dundas’s default fluffy colors. In order to change the color palette, create a Color array and assign it to the series like this:

Color[] clrSteps = new Color[] {
Color.Red,
Color.Green,
Color.Magenta,
Color.Blue,
Color.LightBlue,
Color.Coral,
Color.LightCyan,
Color.Goldenrod,
Color.Gray,
Color.GreenYellow,
Color.Honeydew,
Color.Ivory,
Color.Khaki,
Color.Lavender
};
yourPieChart.PaletteCustomColors = clrSteps;

Now your pie chart will start with red for the first slice, then continue to use the clrSteps array for each slice’s color. If there are more slices than colors you’ve provided, don’t worry, Dundas will start at the beginning color in the array and continue through all of the colors as many times as needed.

How to copy Subversion repositories to another server

1. Ensure you have a working Subversion installation with Apache installed on your system.
2. On the source machine, dump each repository:

   > svnadmin dump /path/to/repository > repository-name.dmp

3. Copy repository-name.dmp to the target server.
4. Load the repository into the new server:

   > cd /path/to/new-repository
   > svnadmin create repository-name
   > svnadmin load repository-name < repository-name.dmp
   

5. Reassign apache permissions:

   > chown -R apache.apache repository-name

6. You are now ready to begin using your repository on the new server!

How to install Subversion with Apache HTTPD

1. Ensure you have Apache installed on your system.
2. Ensure you have mod_dav_svn installed:

   > yum -y update mod_dav_svn

3. Edit /etc/httpd/conf.d/subversion.conf and append the following lines to the end of your config file:

   <Location /svn>
   DAV svn
   SVNParentPath /var/svn
   AuthType Basic
   AuthName "Subversion repository"
   AuthUserFile /etc/svn-auth-file
   AuthzSVNAccessFile /etc/svnserve.conf
   Require valid-user
   </Location>
   

4. Create a file called /etc/svn-auth-file
   Assign permission:

   > chown root.root /etc/svn-auth-file
   > chmod 644 /etc/svn-auth-file

5. Add users to /etc/svn-auth-file (one per line) in the form:
   tom:$apr1$hDMIx…$abctozvZbC9J6/heHBBe481You can use htpasswd to do this automatically:

   > ### First time: use -cm to create the file
   > ### Use -m to use MD5 encryption of the password, which is more secure
   > htpasswd -m /etc/svn-auth-file harry
   New password: *****
   Re-type new password: *****
   Adding password for user harry
   > htpasswd /etc/svn-auth-file -m sally
   New password: *******
   Re-type new password: *******
   Adding password for user sally
   >

6. Create a file called /etc/svnserve.conf
   Fill it with:

   [/]
   *=
   svnUser=rw

   The user svnUser is being granted read and write access to all projects, while all other users (*) are being denied access.

7. Assign permissions:

   > chown root.apache /etc/svnserve.conf
   > chmod 640 /etc/svnserve.conf

8. Create /var/svn.

   > mkdir -p /var/svn
   > chmod 755 /var/svn

9. If you are running SELinux, run:

   > chcon -R -h -t httpd_sys_content_t /var/svn

10. You are now ready to being adding Subversion repositories!