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:
In Jasper Server, you may encounter the following error:
org.hibernate.exception.GenericJDBCException: could not insert: [com.jaspersoft.jasperserver.api.metadata.common.service.impl.hibernate.persistent.ContentRepoFileResource]
This can be caused by having too many automated reports stored in your Content Files directory. Especially if there are number of large .xls (or any type of file).
Just be sure to keep this directory to less than 50 files, and you should be good!
Be the first to comment - What do you think? Posted by
David Dietrich -
February 16, 2010 at 11:25 am
Setting up a classless DNS is critical if you are setting up a mail server on your classless set of IPs. For instance, when my mail users send e-mails to Comcast, Cox, or Time-Warner, my mail is rejected with the following message between the stars:
********************
Subject: Undelivered Mail Returned to Sender
This is the mail system at host melon.skky.net.
I’m sorry to have to inform you that your message could not be delivered to one or more recipients. It’s attached below.
For further assistance, please send mail to postmaster.
If you do so, please include this problem report. You can delete your own text from the attached returned message.
The mail system
<mailto:ddietrich@@socal.rr.com>: host hrndva-smtpin02.mail.rr.com[71.74.56.244] refused to talk to me: 421 4.7.1 – Connection refused. Cannot resolve PTR record for 216.23.169.107
********************
In order to resolve this issue, you must ask your hosting provider to forward reverse DNS queries to your DNS server. Then, you can set up the reverse DNS for your classless range of IPs. Start by editing your named.conf file (/etc/bind/named.conf on Ubuntu, /var/named/chroot/etc/named.conf on Red Hat flavors). Add the following lines–>
zone “96/28.169.23.216.in-addr.arpa” {
type master;
file “/etc/bind/96-28.169.23.216.rev”;
};
In my case, my provider assigned me the range of 216.23.169.23.96-216.23.169.110. This is a /28 set of addresses. Notice how we reverse the zone entry. The Class D first, followed by a /, followed by the .Class C.Class B.Class A.in-addr.arpa. The filename roughly matches this as well. I called the file 96-28.169.23.216.rev. Just put this file in your /etc/bind directory on Ubuntu, or /var/named/chroot/var/named on Red Hat Linux flavors (RH5, CentOS, Fedora Core, etc.)
Now for the actual file 96-28.169.23.216.rev contents between the stars –>
Many times it would be nice to make changes to your /etc/fstab file. The problem is that you must reboot. No longer. Run the following command to remount your /etc/fstab file without rebooting –>
>mount -a
Everything should now be remounted and you can fix any errors that may have occurred with your new /etc/fstab entries.
Be the first to comment - What do you think? Posted by
David Dietrich -
January 26, 2010 at 4:42 pm
When using Samba on Linux, there are times that you want to allow user to have a private user directory, but do not want the “homes” directory share to show up. This is relatively simple.
Edit your /etc/samba/smb.conf file with your favorite Linux editor.
Look for the section [homes] and find the line browseable =
set this line to browseable = no
Restart Samba (>service smb restart) and your users should now see their personal directory without seeing the homes share.
If you do not have a [homes] section, here is an example on for you –>
[homes]
hide dot files = no
comment = Home Directories
writeable = yes
delete readonly = yes
valid users = %S
browseable = no
As a blogger, I spend most of my time writing. But it’s time spent reading that’s most satisfying. Here’s a short (and by no means a complete) list of 10 articles that encapsulate the art of the startup. Most were published during 2009, and I found them educational and full of practical tips that we’ve applied to our business. They’ve also helped me think differently about startups and entrepreneurship. Hope you enjoy reading them as much as I did.
“What Startups Are Really Like” by Paul Graham: This has to be the single best essay I read during 2009. Every entrepreneur should begin the startup journey with this essay. It bottles every essence of entrepreneurship and startups, and is chock-full of practical advise and tips that are applicable to anyone who dares to dream.
“Milestones to Startup Success” by Sean Ellis: Ellis explains the need for minimum viable product, aka MVP, and then outlines how startups can go up his startup pyramid to find success.
“Myth: Entrepreneurship Will Make You Rich” by Eric Ries: “One of the unfortunate side effects of all the publicity and hype surrounding startups is the idea that entrepreneurship is a guaranteed path to fame and riches. It isn’t,” Ries writes in this no-holds-barred essay about the challenges and pitfalls of being a startup founder.
“The Power of Continuous Improvement” by Mike Speiser: In a guest post for us, Mike talks about the importance of metrics, feedback and how they can drive continuous improvement. Mike’s rules have found eager takers among our team.
“The Funnel Principle: Software & Making Money” by Tony Wright: It’s good to build great products, but in order to build great companies one needs to have more — a clear path of monetization, an attention magnet, and in general excellence at things beyond product development.
“Does Every Startup Need a Steve Jobs?” by Andrew Chen: A dissection of how insanely great products are built by combining desirability, feasibility and viability. Read this post after reading Wright’s “Funnel Principle.”
10: “Startup Killer: The Cost of Customer Acquisition” by David Skok: A definitive essay on startup business models, the perils of overoptimism, and the importance of cost of customer acquisitions. Skok is a 3-time entrepreneur with a lifetime of experience.
Occasionally, Jasper Server has an error relating to being unable to write files. The errors show up in the Apache web server log, catalina.out.
You have probably started the service as the user root on accident. This will cause ownership to change to root on some log files. Then when you log back on as user jasper and restart your server, the Apache logs are filling with messages about not being able to write files. Jasper is just not working properly. Run the following command to restore the proper ownership to all files in the Jasper directory. You must run the following command as root:
Linux will overwrite your /etc/resolv.conf in 3 cases. If you have:
Network Manager enabled.
Disable the Network Manager by turning it off with the following commands: >service NetworkManager stop
>chkconfig NetworkManager off
DHCP enabled.
dhcpd will overwrite your /etc/resolv.conf when it acquires an IP address. Convert to a static IP if you are in control of the network.
DNS1, DNS2 or any other DNS# entries in any of your network interface configurations.
If you are the administrator of this machine, check every file matching the following pattern: >find /etc/sysconfig/network-scripts/ifcfg-* and look for any DNS# entries in every matching file. If you find any DNS# lines, and if you are root, remark the lines by inserting a # sign at the beginning of the DNS# line.
Save the file(s).
Then run –> >service network restart
Once you’ve gone through these 3 items, you should be able to now edit and save your /etc/resolv.conf file. Verify that the file no longer is being overwritten. Just execute >cat /etc/resolv.conf a few times for a few minutes and verify the file is no longer changing. Also >reboot the machine to be extra sure nothing changes in the /etc/resolv.conf file.
