Virtual Box Implementation of a custom built Summa Link Server Network Built on Visual C# and C++ 2005
In short, I have a complete backup of the drive used on a Windows 2005 server which I need restored and operational on an Oracle VirtualBox. The resulting VirtualBox need to then run on my Windows 11 machine and allow me to access all the services on the original Windows 2005 server. If possible, I would then like to have all the services migrated to a Windows 2022 server, also run from an Oracle VirtualBox.
I envision four milestones:
- A VirtualBox with all the files from the original server on the virtual machine with the host domain (in ASPX) active which allows new users to create an account, download the Summa Mail Client and access the Summa Mail Server which is hosted by the network server and any necessary administrator scripts to support minimal functionality.
- Activation of the Summa Marketing Server, account creating, and related backend services.
- Activation of the Clearing House Server and web based mail client.
- Migration, if possible, to a newer Windows Network server, preferably Windows 2022.
Development Environment
Summa was developed in the 2005 Microsoft .Net Framework using the following development tools:
- Microsoft Visual Studio 2005
- Visual C# 2005
- Visual C++ 2005
- Visual Basic 2005
- ASP.NET framework for web pages
Data storage and access are handled via SQL Server 2005.
Details Summa Environment
Summa as a whole has a number of functions. These are described below with a description of how the various pieces interact.
Summa Mail – The typical Summa user will use the product as an email application with the added functionality of being able to send money by way of email. The user will use the client application on their PC to sign into the Summa client, which will verify login and account information with the Mail Server, utilizing the Mail Client API. They can then use the application to download any messages they have received from the product, again using the Mail Client API to connect to the Mail Server. They then will compose their message and include any monetary transfers using the message editing function of the application. When ready to send, the user will activate the appropriate command and the Mail Client API will again connect to the Mail Server both to find the proper message and to ensure the sender has the funds necessary to complete the transaction.
This functionality can be broken down into the following interrelated components:
Mail Client/API – The Mail Client portion of the product will be similar in nature to various existing email applications, such as Outlook, AOL mail, etc. Sending/receiving of email, spell-checking, calendaring and other functions will all be included. The importation of email from other internet accounts will be part of the system, negating the need for a user of the Summa product to discontinue that account or change email addresses completely. In addition, the product will allow for the transference of money from one client to the other by simply sending an email and using the application to record the transaction. This function will only be available between two users with Summa accounts. The client application also contains encryption and compression functions to increase the efficiency of the product. It uses SummaMailAPI.DLL to communicate with the Summa Mail Server.
The Mail API is resident on the individual user’s Mail Client and controls the connection between the Mail Client and the Mail Server. It is invoked when the user activates any number of functions that are required to be stored on the Mail Server or Clearinghouse.
Mail Server – The Mail Servers of the product consist of storage areas where Summa mail messages are stored after being composed by the Summa user and moved there from the mail client as a result of processing requests from Summa mail API and other, outside servers. They contain the rules which determine how the mail servers should react to the destination of each specific message, a database of user accounts that the Summa mail servers recognize and will deal with locally and communications modules that handle the transfer of messages to and from other mail servers and email clients. Each also will contain a Summa corporate account and the processes to handle the receipt, delivery and balancing of accounts as they are moved from one server to another.
Marketing Client/API – The Marketing Client portion of the product allows an advertising partner to create and maintain a marketing campaign, collect and analyze the results of that campaign and modify that campaign based on those results. It will also allow for the download/update of mailing list and marketing information from clients they have contacted using the Summa product.
The Marketing API is resident on the advertising user’s Marketing Client and controls the connection between the Marketing Client and the Marketing Server. It is invoked when the user activates any number of functions that are required to be stored on the Marketing Server or Clearinghouse. It also encrypts any messages transmitted up to the Marketing Server to ensure security.
Marketing Server – The Marketing Servers of the product consist of storage areas where Summa Welcome and Marketing messages are stored after being composed by the Summa advertiser and moved there from the marketing client as a result of processing requests from Summa marketing API. Each also will contain a Summa corporate advertiser account and the processes to handle the receipt, delivery and balancing of accounts as they are moved from one server to another. Finally, they also contain profile data on the advertisers.
Clearinghouse - The Clearinghouse is designed to perform verification and validation functions for the accounts and transactions of the Summa product. All “approvals” for financial transactions must be verified through the Clearinghouse before any accounts will be affected. The Clearinghouse also acts as coordinator for the information kept on the individual Marketing and Mail Servers, ensuring all are kept up-to-date with the same information in terms of codes and accounts throughout Summa.