As you may know, Laridian offers the SBL Greek New Testament for PocketBible on all platforms except Android. This was due to lack of decent Unicode support in. Robin Good's Master New Media is a daily online magazine targeted at individuals, small businesses, communicators and media professionals passionate about. Pocket Oxford English Dictionary, free download. Pocket Oxford English Dictionary 5.10: Blackberry version of the popular small dictionary. Good Game is an Australian television gaming programme produced by the Australian Broadcasting Corporation (ABC), airing on ABC2. Created by Janet Carr and Jeremy Ray. Change the Way You Look at the Bible. Update – Aug 5, 2. We discovered that the sync server wasn’t running, so you weren’t able to sync your user data even after the DNS changes propagated. This has been fixed. If you had trouble synchronizing your notes, highlights, and bookmarks, try again. This article will mean very little to most of you but some of you might find it slightly interesting. Well, Tanker Bob expanded into the Pocket PC world on March 23, 2005 with a Dell Axim X50v. Originally, I intended to create a new Pocket PC website to parallel my. I don’t like to get off a perfectly good horse midstream. Windows Server 2. SQL Server 2. 00. But Microsoft discontinued support for В Windows Server 2. As a result, our next PCI security scan was doomed to fail, which doesn’t mean your personal data would be at risk. В (any more than passing the PCI scan protects the data), but it doesn’t make for good PR.(PCI is the Payment Card Industry and the scan is required to meet their card security standards. Laridian doesn’t store your card data so the requirements for us are pretty light. You’re at significantly more risk when you hand your card to the clerk at Target, and we all know from experience that even though they passed all the security scans it didn’t do them much good.)Upgrading to Windows Server 2. SQL Server 2. 01. We found it at Single. Hop. com, which offers the type of dedicated server solutions that we need. And they do it for half the price of the company we had previously been with. Laridian maintains several large databases. These contain your customer account, your transaction history, all the user- created data you’ve sync’ed to the Laridian Cloud, and the downloadable files that make up our books and Bibles. In addition to those we have a couple others for in- house purposes. Because SQL Server 2. SQL Server 2. 01. We had to first import them into a SQL Server 2. SQL Server 2. 01. The good news was that having done that, the databases functioned exactly the same. In fact, we were able to simply point the old website to the new database, and it would work just fine. Let me pause for a minute to say this: We cannot build Pocket. Bible 1. 0. 0 for i. OS anymore. Not only would the resulting program not even come close to working on i. OS 8, it would fail in the compilation and linking process. Pocket. Bible 1. 0. September 2. 00. 9, just six years ago. Contrast that with the code that runs on our website. In 1. 99. 8, we contracted with Jomax Technologies — Bob Parsons first Internet company, before he founded Go. Daddy — to create our e- commerce site. В There is a significant amount of code dating from 1. This code is running. В unaltered. В seventeen years later, accessing a database that has been in continuous use for all those years. When you hear me complaining about the unnecessarily rapid pace of development from Apple (and other companies who drive our industry) and how they create problems due to their lack of regression testing and backwards compatibility, this is what I’m talking about. Because Microsoft knows it would be a. В huge problem to break millions of websites, they go out of their way to continue to support the technologies on which the internet is built. But I digress…This move took place over about a four- week period. I actually thought it would take twice that long.) The first step was to move the system we use for source code archival (Source. Gear Vault). This was necessary because we use Vault to maintain the website. We check code out of Vault, make our changes, and check it back in. Vault populates the website folders from the files we check in. It would be most convenient if we could continue to do this the same way on the new website. Because we were running Windows Server 2. Vault, which requires Windows Server 2. And because we were running such an old version of Vault (version 5) we couldn’t upgrade to the latest (version 8) directly. We had to first upgrade to version 6, which upgraded our database, then upgrade to version 8, which upgraded it again. With Vault working on the new server, we were able to move software development and book production to the new server within about two weeks. Prior to moving Vault we had captured a snapshot of the websites and databases and were running those on the new server for testing. This allowed us to do a quick test to verify that the Web pages themselves would run under Windows Server 2. IIS 8. They worked just fine. Next, we knew that during the transition to the new site there would be a period of time while DNS changes were propagating during which we would have to access the new database from the old website. We ran some tests that verified this would work. Last, we had to build the Laridian Sync Server Service code with Visual Studio 2. It did. At this point we spent a couple days locking down the firewall settings. We had a period of just a few hours when we had an open SMTP (email) server that was exposed to the outside world. I was shocked by how quickly the spammers discovered it (by literally rifling through IP addresses and sniffing for servers). We worked with Single. Hop to quickly lock that down. Now. В we just needed a procedure to follow for getting a final copy of the database moved to the new host. The problem was that we couldn’t be writing to it while it was being moved, which meant shutting down all commerce, account updates, product registration, and user- data synchronization for some unknown period of time. Single. Hop. В estimated two hours to move the database, but. В suggested we allow three. I allowed four. (It took five.)Once we knew what needed to be done, we picked a convenient date and time to do it. We were able to configure much of the code to just shut itself down at 8. AM CDT the day of the migration. So, for example, the code to do synchronization of user data from Pocket. Bible for Windows would still be there waiting for connections, but starting at 8. AM (7: 3. 0, actually) it would return an error code to the client saying that the site was down for maintenance. By automating that process, it meant there were fewer manual actions that needed to be taken in the moments before the migration began. In fact, by the night before the move we were down to where it would take only ten check boxes and about 3- 4 button clicks to completely bring Laridian to a stop for the two, three, or four (or five) hours it would take to move the database. The morning of the move, I discovered Single. Hop had left themselves logged into a. В server, which blocked me from getting in to click on two of my ten check boxes. I asked them to do that for me, which was not a problem. Then I discovered that the person who I was told would be doing the migration hadn’t been told about that fact until 3. He was rousted out of bed or wherever he was, and started moving the databases. With that small hurdle overcome, and with the website having automatically stopped processing new transactions to the database, I was able to get in and make three lines of code changes that it took to point the old website to the new database server. That was really all I needed to do during the time while the database was being exported from SQL 2. SQL 2. 00. 8, exported from SQL 2. SQL 2. 01. 2. The last step of the move was to make the. В DNS changes required to point everyone to the new server. It was at this moment that our registrar (Go. Daddy) decided to make buggy changes to their website that kept us from changing our zone file. After two or three hours of attempts, we were finally able to get those changes made. In the end the move turned out to be easier than I thought and was significantly less time- consuming than I had anticipated. I’m sure we’ll discover small things that are broken, but the major functionality of the new servers appears to be working. Thank you for your patience during the move.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
September 2016
Categories |