| Multi server Configuration |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ |
◄ ► |
| Author | Message | |||
| Constantinos Psilogenis New member Username: Constgp Post Number: 14 Registered: 03-2010 |
Hi, I'm trying to set up a multi server(high availability). What are the configuration files to be moved to the shared folder? I'm asking this question because on server after I create the sharedvolume.ini file to point to the shared folder does not start the web interface. Best regards? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5622 Registered: 08-2008 |
Hi, There is a list of files/directories and some explanation here: http://www.nowsms.com/migrating-to-a-multiple-server-mmsc-wap-gateway-or-nowsms- gateway I assume you may have already looked at that, so I'll try to add some clarification. The document that explains the multiple server NowSMS configuration can be downloaded at http://www.nowsms.com/download/nowsms-ft.pdf. That document provides a good basic explanation, but it is more oriented toward a new installation, rather than converting an existing single server installation into a multiple server installation. The conversion process is more difficult because each of the shared NowSMS servers need to access a common data store that contains configuration information, user account databases, and various message queues and data stores. Depending on what version off NowSMS you originally installed (and the version of Windows), there are different default locations for the NowSMS configuration files. So, in determining what to copy, you first need to locate the directory with the SMSGW.INI config file. If SMSGW.INI is in the directory that NowSMS program files were installed to, then you've found it easily. Otherwise it could be in \ProgramData\NowSMS (on many systems ProgramData is a hidden folder). Stop the NowSMS services...or better yet, remove them by unchecking "run as a service". I'd recommend copying the whole directory structure over to the shared volume, and if this process copied over program files, delete *.exe and *.dll from the shared volume. To avoid accidentally running against the old local config, rename the NowSMS program directory (if something goes wrong in this process, you can rename it back). If ProgramData\NowSMS was used, rename that NowSMS folder as well. At this point, I think the rest of the explanation in that first link is good: Re-install NowSMS so that the NowSMS program directory is recreated. When the NowSMS configuration program dialog is displayed at the end of the installation, press Cancel to exit the configuration program. When the prompt is displayed indicating that the “Service is not active”, press No so that the services are not started. In the NowSMS program directory, create a file named SHAREDVOLUME.INI. The contents of this file should be: [SharedVolume] SharedVolume=\server\path Where \server\path is the location of the shared copy of the NowSMS configuration data. If you are using NowSMS as an SMS gateway, we also recommend adding MessageIDPrefix=xxx to this configuration file, where “xxx” is a unique prefix that identifies this server. This prevents a problem where multiple SMS gateways may assign duplicate message IDs. Run the NowSMS configuration program, and you should see your previously existing configuration information, all of which is now being loaded from the shared data storage location. Before you start the NowSMS services to operate off of the shared data storage location, there is one more important consideration. The SMS gateway and MMSC operate under the services context of the Windows operating system. By default, they use the built-in LocalSystem account. If the shared network storage requires a username and password login for access, LocalSystem will attempt to authenticate as “guest” with no password. This should not be a problem in most environments, where the shared data storage server should be protected by firewalls, and/or preferrably on a private IP network accessible only to the NowSMS servers. However, if you need to authenticate to the shared data storage server with a username and password, it is necessary to configure the NowSMS services to login to Windows with a username and password that matches that required by the remote server. To configure this username and password, it is necessary to edit the NowSMS service attributes under the “Services” configuration dialog, which can be found in the “Administrative Tools” area of Windows. Right click on “Now SMS & MMS Gateway“, and select “Properties”, the on the “Log On” page, configure the user account and password to be used. Repeat the process for the “Now MMSC” service. Start the NowSMS services (either through the Windows Services dialog, or via the NowSMS configuration program). Send some test messages to verify that NowSMS is properly using the SHAREDVOLUME.INI settings. It is now possible to add additional servers, configured with the same SHAREDVOLUME.INI settings. -- Des NowSMS Support | |||
| Constantinos Psilogenis New member Username: Constgp Post Number: 15 Registered: 03-2010 |
Hi, I follow the steps you described above but I still have the same problem. 1. The server is working fine as a stand alone without the shared configuration. 2. I follow the steps above. 3. The shared configuration located in a different server "SharedVolume=\server2\smsconfig" 3a. The connection to my smpp provider seems OK. I cant send SMS, I cant access the web interface port 8800 is not coming up. 4. I copy the shared configuration directory to my server (server 1) 5. I modify the shared volume file to point to "SharedVolume=\server1\smsconfig" 6. I start the services and everything is working fine!!! Any ideas? Constantinos Psilogenis | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5623 Registered: 08-2008 |
Make sure the setting is SharedVolume=\\server2\smsconfig (double \\ at the beginning). This forum software doesn't like to display \\ (I have to type \ 4 times to display \\). I suspect it is a network login problem, where the network path can be accessed from the user login, but not the service login. Did you try this part?
| |||
| Constantinos Psilogenis New member Username: Constgp Post Number: 16 Registered: 03-2010 |
Hello, The problem was with service log on account. I change it and is working fine. I have a question about the licensing. How is the licensing counts in multi server configuration? Best Regards | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5624 Registered: 08-2008 |
Hi, Licensing is per server, but there is also the option to split a license...for example, purchase 2 mps and have it issued as two 1 mps licenses. -- Des NowSMS Support | |||
