Campaign Enterprise 12 is a complete reworking of the Enterprise system. While the basic functionality is the same; you connect your list to Campaign, create your personalized email, and send them through the server, version 12 is much more powerful and scalable than previous versions. Once you download the installation files, it is imperative that you read the readme text file before running the install.
Then new installer is actually a batch file, and there are important modifications you and your network administrator will need to make prior to running that file.
Before installing the program, please contact technical support for information on installation and configuration in your network. Also, check out the demo of the program to look at the new interface.
Campaign Enterprise 12 is used in conjunction with Windows IIS 7 or later. One of the first things you may need to do when configuring your Campaign 12 system, is ensure IIS is enabled and started. Here is how you do that.
By: Chris Lewis
Ports on the internet are like frequencies on your radio. They allow you to use the same "air waves" for a lot of different communication. So, basically, if you try to connect to a service on the internet, like a webserver, then a webserver needs to be eagerly waiting for your request. When you type in HTTP on a browser (along with the URL), your browser assumes you want to connect to the destination Webserver via port 80 (unless you override it). Since Campaign Enterprise has a webserver built into it, it listens for requests. If you put Campaign Enterprise on the same computer as an IIS Webserver there is a possibility that the two might collide if they are both trying to listen to port 80. Actually, what will happen is that the first service that starts up will "win" and take over the listening of port 80. The second service that starts up will try to listen to port 80 and fail because the first service has "binded" to that port. You can see the problem: If two services were allowed to listen and respond to a request, the results would be chaos.
Since port 80 is well-known for website traffic it is almost always let through firewalls, etc. and should be used for response functions. Using port 80 in links within emails also are much more acceptable to SPAM ranking filters than a hyperlink using a "strange" port like 81.
To make Campaign Enterprise use port 80 but "play nice" with other Webservers on your system, you will have to assign multiple IP addresses on your computer so that Campaign Enterprise will bind to one IP and the IIS Server can bind to one or more of the other IPs. It is the pair of IP and Port that makes the traffic coming back to the computer unique. If traffic comes in directed to the computer using the IP and port that Campaign Enterprise is "listening" on, then Campaign Enterprise will respond to it and the IIS Server will ignore it. The opposite applies to the IIS Server traffic where the IIS Server will respond to it's IP and port assigned to it. So overall, if you find Campaign Enterprise when starting says "port in use", you will probably need to make adjustments to Campaign Enterprise and the IIS Server to allow them to co-exist.
"So", you may ask, "why does Campaign Enterprise come with the default ports of 81 and 82?" This is done strictly for demo purposes so that you can be successful demoing the product on a computer with IIS Server running without running into the problems of colliding ports. When you are ready to use Campaign Enterprise for real, change the response port to port 80 so your email will not be marked as SPAM because of the strange ports used in the URLs.
There are two different ports used in Campaign Enterprise, one for the administration of the product and the other is for the traffic coming back to the server. It is probably good to keep the administration port something oddball if you are planning on allowing administration of Campaign Enterprise from outside your firewall because then it is less likely to be crawled by robots out there looking for computers to harass.
Many email professionals use Microsoft's Exchange server to send out their emails from Campaign Enterprise or Email Marketing director. The number one complaint we get is usually that it is very slow even though they are on "a super fast system on a fast internet connection." By default, Exchange Server is not setup to be a mass email system. In fact, they have created many settings by default to stop email from being accepted at a rapid pace. Depending on your Exchange Server version, there are settings you can look at to stop this throttling. A prominent term used is "tarpitting." Now the subject of tarpitting mainly concerns a set of parameters you can set in your Exchange Server so that it will accept emails at a rapid pace. Because of all the version of Exchange Server out there, and with them trying to deal with the SPAM issue through time, there are different settings for each of these versions which we cannot cover, but hopefully this article will uncover a nagging problem you might be having. Now keep in mind, many Exchange Server administrators may not even know what you are talking about because it is a rare occurrence and they probably have not encounter it before, so you may have to prime the pump with some Google service on "Exchange Server SMTP slowness" and show them some of the settings they will have to deal with.
In order to make the most of the features in Campaign Enterprise, you need to configure it correctly in your network. The response event tracking, and web based unsubscribe features all require Campaign Enterprise to be associated with a public IP and domain name. Accessing the program remotely from outside your network also requires you to associate campaign with a public facing address.
When you first open Campaign and log in, you will notice the IP address in the browser window is http://127.0.0.1:81. This IP is the local IP address for your computer; and every computer. The tracking features will only work when implemented or activated on the local machine. This configuration works great for testing the actual functioning of the links you create and ensuring the features write back to your database. However, once you want to go live to your customers, you must change this information to a public address.
Basically, Campaign has a built in web server that serves up its own interface pages and also the click through links and web based unsubscribe page. The image request for the tracking link is made to the Campaign server, if it is not public facing, none of these features will work for your customers. So, in order to configure Campaign for these features, here is what you need to do.
Click on the image below to see one example of how to configure Campaign in your network.
There are as many different possible network configurations as there are networks. This is just one example of the various pathways Campaign uses to connect to your network computers. Your IT personnel may have different requirements for their network. Those differences must be worked out with them and are not necessarily configured in Campaign. Once you get your Campaign Enterprise associated with a public facing address, you can take full advantage of the response events and web based unsubscribe features.