find . -name knp*
./aix536/cq/sqllib/knp.his
./aix536/cq/sqllib/knp_kcj.sql
./aix536/cq/sqllib/knppackage.xml
./aix536/cw/classes/candle/knp
./aix536/cw/classes/candle/knp/resources/help/de/knp_contents.htm
./aix536/cw/classes/candle/knp/resources/help/de/knp_home.htm
./aix536/cw/classes/candle/knp/resources/help/de/knp_notices.htm
./aix536/cw/classes/candle/knp/resources/help/de/knp_trademarks.htm
./aix536/cw/classes/candle/knp/resources/help/es/knp_contents.htm
./aix536/cw/classes/candle/knp/resources/help/es/knp_home.htm
./aix536/cw/classes/candle/knp/resources/help/es/knp_notices.htm
./aix536/cw/classes/candle/knp/resources/help/es/knp_trademarks.htm
./aix536/cw/classes/candle/knp/resources/help/fr/knp_contents.htm
./aix536/cw/classes/candle/knp/resources/help/fr/knp_home.htm
./aix536/cw/classes/candle/knp/resources/help/fr/knp_notices.htm
./aix536/cw/classes/candle/knp/resources/help/fr/knp_trademarks.htm
./aix536/cw/classes/candle/knp/resources/help/hu/knp_contents.htm
./aix536/cw/classes/candle/knp/resources/help/hu/knp_home.htm
./aix536/cw/classes/candle/knp/resources/help/hu/knp_notices.htm
./aix536/cw/classes/candle/knp/resources/help/hu/knp_trademarks.htm
./aix536/cw/classes/candle/knp/resources/help/it/knp_contents.htm
./aix536/cw/classes/candle/knp/resources/help/it/knp_home.htm
./aix536/cw/classes/candle/knp/resources/help/it/knp_notices.htm
./aix536/cw/classes/candle/knp/resources/help/it/knp_trademarks.htm
./aix536/cw/classes/candle/knp/resources/help/ja/knp_contents.htm
./aix536/cw/classes/candle/knp/resources/help/ja/knp_home.htm
./aix536/cw/classes/candle/knp/resources/help/ja/knp_notices.htm
./aix536/cw/classes/candle/knp/resources/help/ja/knp_trademarks.htm
./aix536/cw/classes/candle/knp/resources/help/knp_contents.htm
./aix536/cw/classes/candle/knp/resources/help/knp_home.htm
./aix536/cw/classes/candle/knp/resources/help/knp_notices.htm
./aix536/cw/classes/candle/knp/resources/help/knp_trademarks.htm
./aix536/cw/classes/candle/knp/resources/help/ko/knp_contents.htm
./aix536/cw/classes/candle/knp/resources/help/ko/knp_home.htm
./aix536/cw/classes/candle/knp/resources/help/ko/knp_notices.htm
./aix536/cw/classes/candle/knp/resources/help/ko/knp_trademarks.htm
./aix536/cw/classes/candle/knp/resources/help/pl/knp_contents.htm
./aix536/cw/classes/candle/knp/resources/help/pl/knp_home.htm
./aix536/cw/classes/candle/knp/resources/help/pl/knp_notices.htm
./aix536/cw/classes/candle/knp/resources/help/pl/knp_trademarks.htm
./aix536/cw/classes/candle/knp/resources/help/pt_BR/knp_contents.htm
./aix536/cw/classes/candle/knp/resources/help/pt_BR/knp_home.htm
./aix536/cw/classes/candle/knp/resources/help/pt_BR/knp_notices.htm
./aix536/cw/classes/candle/knp/resources/help/pt_BR/knp_trademarks.htm
./aix536/cw/classes/candle/knp/resources/help/ru/knp_contents.htm
./aix536/cw/classes/candle/knp/resources/help/ru/knp_home.htm
./aix536/cw/classes/candle/knp/resources/help/ru/knp_notices.htm
./aix536/cw/classes/candle/knp/resources/help/ru/knp_trademarks.htm
./aix536/cw/classes/candle/knp/resources/help/zh_CN/knp_contents.htm
./aix536/cw/classes/candle/knp/resources/help/zh_CN/knp_home.htm
./aix536/cw/classes/candle/knp/resources/help/zh_CN/knp_notices.htm
./aix536/cw/classes/candle/knp/resources/help/zh_CN/knp_trademarks.htm
./aix536/cw/classes/candle/knp/resources/help/zh_TW/knp_contents.htm
./aix536/cw/classes/candle/knp/resources/help/zh_TW/knp_home.htm
./aix536/cw/classes/candle/knp/resources/help/zh_TW/knp_notices.htm
./aix536/cw/classes/candle/knp/resources/help/zh_TW/knp_trademarks.htm
./aix536/cw/classes/knp_resources.jar
./aix536/cw/knp.inf
./config/.ConfigData/.tmp/knpenv
./config/.ConfigData/knpenv

Check if the applet.html is properly updated, grep for knp on your applet.html. This file is located in different directories in each platform, if you are unsure where it is just do a find for it:

find . -name applet.html
./aix536/cw/applet.html

grep -i knp ./aix536/cw/applet.html

optimizeArchiveOrder( ‘<PARAM NAME = CACHE_ARCHIVE VALUE=”cnp_vbjorball.jar, kjrall.jar,         util.jar,  chart.jar, ae.jar,             cnp_jviewsall.jar, terminal.jar, browser.jar, browser-@P.jar, browser-core-@P.jar, icu4jm32.jar, deploy.jar,         cnp_ps.jar, cnp.jar,            kum_resources.jar,  kdy_resources.jar,  kis_resources.jar, koq_resources.jar, kqb_resources.jar, kq7_resources.jar, kqf_resources.jar, koy_resources.jar, kq5_resources.jar, klz_resources.jar,  kno_resources.jar, kqp_resources.jar, ism.jar, kp5_resources.jar, kqr_resources.jar, kqv_resources.jar, ka4_resources.jar,  kex_resources.jar, kph_resources.jar, nvnways.jar,         kqx_resources.jar, kdp_resources.jar,  kib_resources.jar, kr2_resources.jar, log4j-1.1.1.jar,     kr6_resources.jar, km5.jar,  kpx_resources.jar, ksy_resources.jar, kmq_resources.jar, kr4_resources.jar, jrim.jar,            console.jar,         kgw_resources.jar,  kud_resources.jar, kpv_resources.jar, k99_resources.jar, kul_resources.jar,  kip_resources.jar,  kn3_resources.jar,  khd_resources.jar, kor_resources.jar, kcp_resources.jar,  klo_resources.jar, commons-codec-1.3.jar, k3z_resources.jar, kcf.jar, k87_resources.jar, jsafe.zip,           kqi_resources.jar, kux_resources.jar,  ibmjsse.jar,         kht_resources.jar, kva_resources.jar, ks3.jar,            jcf.jar,             kmc.jar, kgb_resources.jar, kpk_resources.jar, km5_resources.jar, ks3_resources.jar,  tec_tap.jar,         khv_resources.jar, uif.jar,             knt_resources.jar,  nways_dep.jar,       launch.jar,          kr3_resources.jar, kvm_resources.jar, jhall.jar,           kyn_resources.jar, kit.jar,             kr5_resources.jar, k07_resources.jar, knp_resources.jar,”>’ );

/opt/IBM/ITM/bin/cinfo -i

Look for the product from the list.

np      IBM Tivoli Network Manager
tps     Version: 03.90.00.00
tpw     Version: 03.90.00.00

/opt/IBM/ITM/bin/tacmd listworkspaces |grep knp

Application Type: knp
Application Type: knp
Application Type: knp
Application Type: knp
Application Type: knp

If there knp can not be found in applet.html or in the listworkspaces the TEPS server will have to be reconfigured. This will kick off the InstallPresentation.sh script which will then configure the support correctly. This can be achieved in the following 2 ways:

/opt/IBM/ITM/bin/itmcmd config -A cq <- this will reconfig the entire TEPS server

./itmcmd execute cq <ITMHOME>/arch/cq/bin/InstallPresentation.sh <- this will only configure the things you need and it can also be run as a non-root user.

Notice: Undefined variable: nb_products in /var/www/html/shopname/tools/smarty/sysplugins/smarty_internal_data.php on line 291 There are no products.

We are using the Matrice theme which is truly amazing however there seems to be an issue here with it. If you run into the same as a quick fix just change the following in the category.tpl:

{if $nb_products == 0}{l s=’There are no products.’}

{else}

{if $nb_products == 1}{l s=’There is’}{else}{l s=’There are’}{/if}&#160;
{$nb_products}&#160;
{if $nb_products == 1}{l s=’product.’}{else}{l s=’products.’}{/if}

{/if}

to

<!–

{if $nb_products == 0}{l s=’There are no products.’}

{else}

–>

{if $nb_products == 1}{l s=’There is’}{else}{l s=’There are’}{/if}&#160;
{$nb_products}&#160;
{if $nb_products == 1}{l s=’product.’}{else}{l s=’products.’}{/if}
<!–

{/if}

–>

Make sure that you are changing the Matrice theme not the default one

I was playing around with phpLDAPadmin and finally got to this solution:

First create a mail user using your iRedMail backend. I am not going into detail on how to do this it is quite self explanatory.

After iRedMail installation there is a very helpful summary file in the folder where you are kicking of the installation from. It contains all passwords, userids, and URLs you might need to use iRedMail and all underlying products. I does in fact installs many including Dovecot, Postfix, phpLDAPadmin, etc. This summary file is iRedMail.tips

Get your phpLDAPadmin URL, password and master user id from this file and log in to phpLDAPadmin backend. The URL is usually:

https://www.yourdomain.com/phpldapadmin/htdocs/cmd.php

Log in go to and drill down to the email user you have previously created and click on it.

You will have a couple of options on the right panel, select default, then select add new attribute.

Select mailForwardingAddress from the dropdown list and fill in the email address where you would like to forward emails from this account. Please note that you can set both internal or external email addresses. Click on Update Object at the bottom of the page.

Click on Commit at the next screen to confirm changes and it is done

There are other ways to enable this and if you use iRedAdmin-Pro you can even do it from the Admin backend. I am only covering the phpLDAPadmin part. Please read this post for more information:

http://www.iredmail.org/forum/post9958.html#p9958

Jun 11 18:13:55 ProcessingEngine postfix/smtpd[13562]: connect from gateway01.websitewelcome.com[69.41.242.19]
Jun 11 18:13:56 ProcessingEngine postfix-policyd: rcpt=16, greylist=abuse, host=69.41.242.19 (gateway01.websitewelcome.com), from=ORIGIN@EMAILREMOVED.COM, to=DESTINATION@EMAILREMOVED.COM, size=0
Jun 11 18:13:56 ProcessingEngine postfix/smtpd[13562]: NOQUEUE: reject: RCPT from gateway01.websitewelcome.com[69.41.242.19]: 450 4.7.1 : Re cipient address rejected: Policy Rejection- Please try later.; from= to= proto=SMTP helo=
Jun 11 18:13:56 ProcessingEngine postfix/smtpd[13562]: disconnect from gateway01.websitewelcome.com[69.41.242.19]

After a bit of a research I have figured that the postfix-policyd configuration file contains the entry where you can disable greylisting. Once I have done that I have been able to send and receive mails instantly.

The config file on my ubuntu 10.4.2 LTS server is located at:

/etc/postfix-policyd.conf

Just set the GREYLISTING paramter to 0

#####################################################################
#
# enable greylisting                                  default: on
#
#   whether greylisting should be enabled or disabled.
#
#                                                     1=on  0=off
GREYLISTING=0

array(‘id’ => ’0′, ‘name’ => $this->l(‘Product name’)),
array(‘id’ => ’1′, ‘name’ => $this->l(‘Product price’)),
array(‘id’ => ’2′, ‘name’ => $this->l(‘Product added date’)),
array(‘id’ => ’4′, ‘name’ => $this->l(‘Position inside category’)),
array(‘id’ => ’5′, ‘name’ => $this->l(‘Manufacturer’)),
array(‘id’ => ’3′, ‘name’ => $this->l(‘Product modified date’))

which is missing option “6″ that stands for the “In-stock first” option.

Simply modify the following two database configuration options:

Change the PS_CONFIGURATION table PS_PRODUCTS_ORDER_BY option to “6″

Change the PS_CONFIGURATION table PS_PRODUCTS_ORDER_WAY option to “1″

That’s it

You have to tell php what encoding to use you can achieve this either using the HTML or the PHP definition. Whichever suits you. Add this to the header section of the HTML code:

<meta http-equiv=”content-type” content=”text/html; charset=UTF-8″ >

You can achieve the same using the header php command:

header(“Content-Type: text/html; charset=utf-8″);

Now we have to make sure that the data coming from the mysql database is UTF-8 encoded. Add this right after the database connection line.

$conn = mysql_connect($dbhost, $dbuser, $dbpass) or die (‘Error connecting to mysql’); // Add UTF-8 converting after this line
mysql_query(“SET NAMES UTF8″);

Make sure that the php file itself is saved from the editor in UTF-8 format. Each progamming editor has the capability to change the character encoding.

Finally check your database if  the tables and the database are utf8_hungarian_ci encoded. MySQL connection collation should be set to utf8_general_ci.

That should be it

Check how many products have been uploaded successfully using Google Merchant Center’s “feed” option:

In my case 1009 products are indexed correctly. To find out what went wrong open your generated XML feed and find the relevant id.

<item>
<title>CAESARS by Caesars</title>
<g:brand>Caesars</g:brand>
<g:condition>new</g:condition>
<description><![CDATA[Gift Set -- 3.3 oz Eau De Cologne Spray + 3.3 oz Body Cream + 3.3 oz Body Wash]]></description>
<g:expiration_date>2010-10-22</g:expiration_date>
<g:id>pcen-1009</g:id>
<guid>pcen-1009</guid>
<g:image_link>http://www.megaperfumeshop.com/img/p/1009-1009-large.jpg</g:image_link>
<link>http://www.megaperfumeshop.com/1009-caesars-by-caesars.html</link>
<g:price>38.4</g:price>
<g:product_type>Brands A-Z &gt; Caesars</g:product_type>
</item>

Then see the next product:

<item>
<title>caf&iuml;&iquest;&frac12; by Cofinluxe</title>
<g:brand>Cofinluxe</g:brand>
<g:condition>new</g:condition>
<description><![CDATA[Parfum De Toilette Spray 3 oz]]></description>
<g:expiration_date>2010-10-22</g:expiration_date>
<g:id>pcen-1010</g:id>
<guid>pcen-1010</guid>
<g:image_link>http://www.megaperfumeshop.com/img/p/1010-1010-large.jpg</g:image_link>
<link>http://www.megaperfumeshop.com/1010-caf-by-cofinluxe.html</link>
<g:price>16.64</g:price>
<g:product_type>Brands A-Z &gt; Cofinluxe</g:product_type>
</item>

The junk characters in the product name cause the feed import to stop and not to load products any further. Simply remove the defected products and upload the feed again. So this wasn’t the problem of the feed generator but it was a problem with the data quality. Good stuff that it can easily be fixed.

I could change the URL by simply changing the following in the wordpress database using PhpMyAdmin:
I opened the wp_options table and changed the siteurl and home fields to www.solutioning.eu from blog.solutioning.eu

The website was working again right after this, no hassles, not other configurations…