RODOPI On-line Documentation: Installation

The RODOPI ISP Suite consists of several modules, which could be installed separately. Please follow the installation procedure described below or you may fail to install RODOPI properly. Note that this procedure assumes that you have some network administering experience.

The RODOPI ISP Suite requires:

• Microsoft Windows NT 4.0 Server with NT 4.0 Service Pack 3 (or greater) installed
• Microsoft SQL 7.0 (recommended) or SQL Server 6.5 with SQL Server Service Pack 4 (or greater)  installed.
• Internet Explorer 4.01 SP1 (or greater) installed on the SQL Server system and on the computer where the web interface is installed.
• Microsoft Data Access Components - v2.1 or higher.
• A Web server for MS Windows NT 4.0 Server. Microsoft IIS 3.0 Web server (or greater) is required.
• ICVerify for Windows is required for automated credit card charging.

1. First, decide how to organize your RODOPI installation. Generally, RODOPI consists of two parts - SQL database and Web interface. Each of them requires a corresponding server to be installed. The database requires Microsoft SQL Server 7.0 or 6.5 and ICVerify for Windows and the Web interface requires a Web server, preferably Microsoft IIS 4.0. These two servers can run on different machines, depending on your configuration, however you may have these servers run on one and the same machine. The case with the SQL and the Web servers running on different machines is discussed later in this documentation.
   
   
2. Microsoft SQL Server is an application that uses your hardware resources extensively. There are cases when it will crash without any reason, and it is very likely that this is due to a hardware incompatibility problem. Microsoft has created an "SQL Server File System Stress Utility" which will check the stability of your system. Look for it at http://support.microsoft.com/support/downloads/LNP220.asp. It is highly recommended to run this test before installing the RODOPI database - it will save you problems in the future. Note that you might have used the machine for a long time before, and it might have passed other hardware tests, but still fail this test.
   
   
3. You must be the local network administrator or at least you must have administrator rights on the Web and SQL servers, and you need to know the System Administrator (SA) password on the SQL server.
   
   
4. Download RODOPI self-extracting executable file from our download page.
   
   
5. MS SQL Server Login Security Mode must be standard or mixed. Integrated mode is not supported. SQL Server must be installed with default sort order and character set. The default character set is "ANSI (ISO 8859-1)", the default sort order is "Dictionary order, case insensitive".
   
   
6. Internet Explorer 4.01 with Service Pack 1 or later must be installed on the SQL server (IE 4 recommended).
   
   

1. Start RODOPI.EXE ( or what the name of the current version is) and follow the installation instructions.
   
   
2. In the Setup Type dialogue:
   • Select New -- if you don't have installed  RODOPI before, and your SQL and Web servers are on one and the same machine;
   • Select Upgrade -- if you have installed RODOPI and your SQL and Web servers are on one and the same machine;
   • Select Custom -- when your SQL and Web servers are not on the same machine or you have to install only a separate component.  On the SQL Server install the "New Database" component and on the web server install the "Rodopi Server" and "Web Interface" components. 
3. After you select New, Upgrade or any of the Database components, you will be asked for the SQL Server SA's password. The SA's password may be empty, but cannot contain spaces. Then the setup software will try to verify the connection to the SQL Server.
   
   
4. The setup will copy all existing HTML pages from the previous RODOPI installations into HTML backup sub-directory.
   
   
5. Restart the computer when asked.
   
   
6. If you want to be sure that the database installation was successful, you should check for any errors in these files in RODOPI directory: UNINSTALLDB.LOG, INSTALLDB0.LOG, INSTALLDB1.LOG, INSTALLDB2.LOG UPGRADEDB1.LOG and UPGRADEDB2.LOG (Note that not all of these files might be in the directory). These files contain the results of all the commands in the installation scripts. If you notice some errors or just don't know what to look for you can send these files to support@rodopi.com, and we'll check them for you.
   
   
   

1. To configure the connection between the web interface or the RodopiServer service and the SQL database you need to use the "RODOPI Server Configuration utility" from Start / Programs / Rodopi / Rodopi Server Configuration. Also you will need to to use the "RODOPI Server Configuration utility" if you change the password for the SQL login 'rodopi'  (recommended).
   
2. Enter the name of your SQL server or the IP address, the SQL login name and password that RODOPI CGIs have to use to connect to the RODOPI databases. By default the installation connects CGIs to the windows name of the computer  (the local host) and creates a SQL login 'Rodopi' with password 'rodopi'. It has all the required permissions in the RODOPI and other databases. The protocol used is named pipes. You can change it to TCP/IP sockets ( TCP/IP sockets connection should be enabled in the SQL Server Setup).
   
   
3. Click 'Save' to make sure that the connection is OK and to save the settings.
   
   
4. If you have Microsoft IIS 3.0 or 4.0 (with Windows Scripting Host installed) Web server, the virtual mappings listed below will be created automatically. You will need only to restart the WEB Service if the web server is IIS 3. Otherwise  you must create these virtual mappings manually (replace C:\RODOPI with the directory where you have installed the modules).
   
   

   Physical directory	Virtual directory	Permissions
   C:\RODOPI\olsmaint	/olsmaint	Read
   C:\RODOPI\olsmaint-cgi	/cgi-bin/olsmaint	Read, Execute
   C:\RODOPI\olsadmin-cgi	/cgi-bin/olsadmin	Read, Execute
   C:\RODOPI\olsplus	/olsplus	Read
   C:\RODOPI\olsplus-cgi	/cgi-bin/olsplus	Read, Execute
   C:\RODOPI\usage-cgi	/cgi-bin/usage	Read, Execute

1. Make sure that you have configured SQL Executive Service (SQL ServerAgent in 7.0) to start automatically when your SQL Server starts. You can check this from the Control Panel | Services, look for SQLExecutive (SQL ServerAgent).
   
   
2. RODOPI comes with two scheduled tasks RODOPI Daily Billing and RODOPI Procedures You must enable them if they are not enabled from Server | Scheduled tasks pull-down menu in the SQL Enterprise Manager. In SQL 7.0 it is in Management / SQL Server Agent / Jobs. By default the tasks will be enabled so you don't need to do this manually.
   
   
3. The Daily Billing task maintains an internal billing date. It is incremented by 1 day each time the task has run successfully. The task will not run more than once for the same billing date. Also it will not run for future dates. The Daily Billing task will be scheduled by default to run at midnight. You can change the scheduled time from the SQL Enterprise Manager.
   
   
   IMPORTANT!!! If for some reason the Daily Billing task is not running you will have some billing days missing. The reason for this can be that the SQL Executive (SQL ServerAgent in 7.0) service is not running or the scheduled task RODOPI Daily Billing is not enabled or the task is failed (you will see the reason in the history of the scheduled task). Indicator that the Daily Billing task was not running can be that there are no rows in the statements of the new customers. Also there will be no automatic credit card charges and no reoccurring charges will be calculated.
   To correct this you need to run the task RODOPI Daily Billing once for every missing day. If you need to run this task more than once (you missed more than one day of billing) you need to run the task , wait until it finished and check the history (status). If successful run it again. Do NOT run two instances of the task at the same time, because double billing can occur. When you receive message in the history: "Invalid Billing time" this means that the billing date is correct and the task will not start for future dates.
   
   
4. The Procedures task takes care for creation of RADIUS users file, uploading event scripts, etc. This task should always be in running state. The task is scheduled to run every minute, but when the task run for the first time it will enter loop and will never exit. You should not start this task manually. The task will be started automatically from the SQL Executive Service (SQL ServerAgent in 7.0). When you go to "Running Tasks" you should find this task there. In the history of the task you may find error messages like "Failure" or "Canceled", but until the task is running the messages are not important. The error will be generated when you restart the SQL Server or when you try to stop the task manually.
   NOTE When the SQL Server is restarted the task RODOPI Procedures may be disabled. You need to enable it manually from the SQL Enterprise Manager.
   
   

1. The URL of the main RODOPI page will be http://YourWebServer/olsplus/rodopi.html. It contains links to all the modules. As network and RODOPI administrator you can use this page as a reference to the URLs of all modules. Then you can add bookmarks or links to these modules in the appropriate places. For example, links to the pages of the Subscription module may be placed on your home page to be available to your customers, and a bookmark of the Tech Support module -  in the browsers of your tech support staff.
   
   
2. The URL of the RODOPI administration page will be http://YourWebServer/cgi-bin/olsadmin/MainMenu.exe. Use the links there to configure all RODOPI settings.

You need to set up proper security on all program components so only the proper departments of your organization can access them.

In Microsoft IIS server you can do this by changing the file permissions. You can set permissions only on NTFS drives.  on the directories under the directory where you installed the RODOPI.

Web Server security:

You have to secure the following physical sub-directories in the main Rodopi directory on the Web Server (usually C:\Rodopi):
-- olsmaint
-- olsmaint-cgi
-- olsadmin-cgi

You can set Administrators access only for the 'olsadmin-cgi' folder. Administrators and Billing for the 'olsmaint' and 'olsmaint-cgi' folders. Administrators should have "Full Control" and the Billing users needs only "Read&Execute". You can apply security only on NTFS drives.

You have to allow anonymous access to the following physical
sub-directories:
-- olsplus,
-- olsplus-cgi,
-- usage-cgi,
-- inettech
If the anonymous user (usually IUSR_COMPUTERNAME) does not have access to 'olsplus-cgi' then the SQL Server will not be able to send invoices and statements by email.

The following physical sub-directories are not published from the WEB
server and they may have Everyone "Full Control":
-- backup
-- log
In this directories the SQL Server is doing backups so make sure that the system account have full control.

The main Rodopi folder ( i.e C:\Rodopi ) and the files in this main folder should have Everyone Read&Execute, because the DLL's are accessed from the CGI's and the Rodopi Server service is running from this folder.

For security reasons do not allow any web hosting or shell access on the computer where Rodopi is installed.

See Chapter 5, "Securing Your Site Against Intruders", in the IIS product documentation for more details.

SQL Server security:

You need to change the password for the SQL login rodopi. To do this you need to go to the SQL Enterprise Manager, open your SQL Server, open Logins, double click on the rodopi login and change the password. After this you need to go to your Web Server computer and open the Rodopi Server Configuration Utility. Change the password with the new one. Save. You need to do this also on the computer where the 'Rodopi Server' component is installed if it is on different machine.
Also make sure that the Sa login in the SQL Server is not with empty password. The default SQL Server installation will create Sa login with empty password, so you need to change it later.

You should install ICVerify for Windows on the SQL Server if you want to verify and charge credit cards automatically (this assumes a modem installed on same the machine).

Version 2.xx

• Install Icverify on your SQL Server. Setup ICVerify with your bank processor. Make sure ICVerify works properly from the default installation. You should be able to charge credit cards from the ICVerify Windows Interface and perform settlement.
  
  
• Copy the ICVERIFY.SET file to ICVE0001.SET
  (from Command Prompt)
  copy ICVERIFY.SET ICVE0001.SET
  
  
• Check the "Multiple Merchants Mode" option in the "Edit / Options" menu of the ICVerify.exe program. If you have already been using ICVerify in multiple merchant mode, the merchant number that Rodopi will use is 0001, so make sure it is the right one.
  
  
• Create data directory for merchant 0001 in the system32 directory with name DATA0001
  (from Command Prompt)
  cd \winnt\system32
  mkdir DATA0001
  
  
• Set the data directory in the ICVE0001.SET file. It's important to type the full path to the data directory. For example C:\WINNT\SYSTEM32\DATA0001 . For each merchant you need to create a separate data directory. For merchant 0001 it should be DATA0001.
  
  
• Copy all the files from the ICVERIFY directory into the SYSTEM32 directory.
  (example from Command Prompt)
  
  cd \ICWIN225
  xcopy *.* C:\Winnt\System32\  /h/v
  
  
  In the main system32 directory now you should have all files from the ICVerify directory. If you are using Windows Explorer to copy the files, make sure you see the hidden and system files, otherwise not all files will be copied. To enable this option in your Windows Explorer go to View / Folder Options / View / in the section 'Hidden files' click 'Show all files'.
  
  
• Run the ICVOLE32.EXE executable from the SYSTEM32 directory once to register the ICVerify ActiveX object.When ICVOLE32.EXE starts (ICVerify OLE Interface), press the button Initialize and then Exit to finish. This way the ICVerify COM object will be registered and Rodopi will call directly ICVerify using OLE interface and you don't need to have running any ICVerify program.
  
  
• Start icverify.exe from the system32 directory. Switch to merchant 0001. Make test credit card transaction. If the test is successful Rodopi will charge automatically credit cards.
  
  
• In Control Panel | Services check how the MSSQLServer service is configured - it should log on with the system account, as is the default setting.
  
  

NOTE: If you need to use the windows interface of ICVerify you should start the executable: icverify.exe from the system32 folder, NOT from the old ICVerify folder. All transactions logs for the merchant 0001 will be in the DATA0001 in the system32 directory.

NOTE: You can choose not to use ICVerify and charge the credit cards by other means. In this case you must contact RODOPI support in order to receive further instructions!

For Rodopi 4.01 and older versions please follow the instructions here.

If you have Rodopi version 4.02 or greater, you can use new import utility, that will check your import file for errors and import it. The new import format is described here.

Download RodopiImport.exe and save it in the main Rodopi directory ( C:\Rodopi for example). Open Command Prompt and go to the Rodopi directory. Type:

RodopiImport.exe -help

for command line options.

RodopiImport v1.031: WinNT console utility for importing customers in Rodopi.
by Intranet Software
        http://www.rodopi.com
syntax:
  RodopiImport -backup -p SaPassword
  RodopiImport -f <filename> <-test|-import|-forceimport> [-setup] [-nolog]
  RodopiImport -help

-backup : do backup of the Rodopi database (Sa password required).
-f filename : file to import, tab delimited format is supported
-test   : will only test your import file for errors
-import : test your import file and if no warnings or error are found
         do import
-forceimport : import your file directly without checking for errors or
          warnings. You should use this option if you previously checked your
        import file and the warnings are not important for you.
-setup  : charge the customers in the import file for setup fee.
          This option can be used to subscribe new customers.
-nolog  : use this option if you import more than 100 users at once,
          You will need to do backup of the Rodopi database after this.

Note that the RodopiImport utility should be in the Rodopi
main directory.

Example of using the import utility:

rodopiimport -backup -p SaPassword
rodopiimport -f demoimportnew.txt -import -nolog
rodopiimport -backup

The second backup in this case is important, because the -nolog option was used.

In case of accident during the import process, you can restore the backup copy of the AbacBill database by the following standard restore procedure in the Enterprise Manager. Here are the steps of this procedure.

(SQL Server 6.5)

• Open Enterprise Manager, login as SA and expand the Databases branch under your SQL server.
• Right-click on the AbacBill database and select Backup/Restore...
• Click on the Restore tab, then click the From Device... button.
• Click the Add File... button and type or browse to the AbacBill_db_dump.199901051716 (the number of your file will be different) file which should be located in the backup subdirectory under your RODOPI directory.
• Click the Restore now button to start restoring the database.
  NOTE*  You may receive error message when you try to restore: "[SQL Server] Database is in use. System Administrator must have exclusive use of database to run load." To fix this you need to kill all SQL processes attached to the AbacBill database. Go to Server/Scheduled Tasks and disable the "RODOPI Procedures" task. Go to Control Panel / Services and Stop the RodopiServer Service. Restart the SQL Server from Services or From the SQL Enterprise Manager. Connect to the SQL Server with the Enterprise Manager and try to restore again. When successful enable the Scheduled task "RODOPI Procedures" and Start the RodopiServer Service.

Backups

The "Rodopi Daily Billing" task will do backups of the Rodopi databases. The backup is full when the task is run Sunday and incremental every other day. To restore you need one full backup and all incremental backups created after the full backup.

The backup files are placed in the \Rodopi\backup folder on the SQL Server computer.
The name of the full backup file will be similar to this one:

07/25/99 02:53a      85,457,408       AbacBill_db_199907250251.BAK

The incremental backups will have names like:

07/26/99 01:43a      38,060,544       AbacBill_tlog_199907260141.BAK
07/27/99 01:41a      7,307,776         AbacBill_tlog_199907270141.BAK
07/28/99 06:26a      24,546,816       AbacBill_tlog_199907280625.BAK
07/29/99 02:31p      4,407,808         AbacBill_tlog_199907291431.BAK

These names are generated from SQL 7.0. In SQL 6.5 the file names may be different.

We recommend you to frequently to check are the backups created.. Also you can copy the backups to a tape or other computer.

For more backup options please read the section Backup and Restore from the SQL Administrator books.

If you want to implement custom backups contact us to disable the default Rodopi backup.

Back to the table of contents