R About.com - Read About IT!

In the last couple of days I was transferring a large WordPress MU website into new servers, and on top of it I wanted to use that opportunity to replace the current domain name with a new one.
Since the domain name appears all over the database, I had to dump the database and create a new database by running the modified queries of the SQL dump.
These instructions were tested on WordPress MU (Multi User edition), but I’m confident it should also work on the standard WordPress.

In the previous post I spoke about how to perform remote calls to Salesforce API using Axis2. I explained how to generate the code using Wsdl2Java and how to query Salesforce and receive SObjects.

After publishing that post I've been asked to provide a code sample that show how to store data into the Salesforce using Axis2.

I had to query my MS Dynamics CRM 3.0 server from a Java based application.
Since Microsoft has no Java based API, initially I thought that the simplest way would be to write a web-service proxy component that will use MS Dynamics SDK, and so the java application will perform remote web-service calls to that proxy component.
While playing around with the .NET SDK Microsoft Dynamics CRM, I noticed that the SDK Microsoft provided is performing web-service calls to the CRM.
At that point I decided that the best way of integration would be to use Axis2 to directly integrate with the CRM.

Many times we find ourselves in situation that we want our Javascript to invoke some Java methods; It can be because of javascript functional limitations, or just because it's more convenient to write complex business-logic in Java instead of Java Script. However, it seems that Firefox has some problems handling invisible applets.

Traditionally, companies used to go with the scaling-up approach. Scaling up means getting a new stronger server or adding power to your existing one (memory, fast storage, CPU’s, etc.)
The alternative of scaling up is scaling it out. Scaling out means adding new servers to your system configuration to help coping with the load. A typical scaling out solution will split the user database into partitions, and route each user to the right partition (server) by his user ID, so each partition will store records for different range of IDs.

Recently I installed the latest release of OpenX 2.4 (2.4.6), and I found a serious problem with serving of flash banners.

On my machine, a click on flash banner served by OpenX caused a popup blocker alert. This problem occurred on Firefox 2 as well as on Internet Explorer 7 (EI7).
I've checked it on some other machines with different configurations, and I discovered that the problem raised only when used by latest versions of adobe Flash player (as 9.0 r124) combined with some specific versions of browsers.

After spending many long hours trying to make remote calls to Salesforce API using Axis2, I decided to share it with you.