This file includes instructions for runnig, using, and compiling the TOVE IN environment.

1 REQUIREMENTS

Configuration used at development time:

- Windows NT 4.0 SP3
- nmake
- SUN JDK 1.1.6 (or Inprise JBuilder 2)
- Swing 1.0.2 
- Orbacus 3.0

Other JDK's, ORB's and operation systems may also work (not tested).

2 RUNNIG THE SOFTWARE

Check that name service is running (in Linux) and src/orbacus.cfg has correct IP address.
The TOVE main software must be also up and running (SSP).

Following bat files use absolute paths for JDK and ORB. Change these to your configuration.

1) Go to src/tove/scp and type startsce.bat. This starts service creation and 
   management software (SCE/SMS). 

2) Start new dosbox and go to src/tove/scp and type startslee.bat. 
   This starts service execution environment software (SLEE). 

3) Start new dosbox and go to src directory and type startgui.bat. 
   This starts SCE GUI software.

3 USING THE GUI
When the GUI starts double click the SCE node in a RMI registry tree. New window
is opened. You should see "Example Services" icon. Right click to get pop up menu. Select
properties. In the properties window set correct values: switchPointCode number should be
same as the point code for the SSP.

Double click "Example Services" icon. New layer shoud appear. If the screen
is not updated properly resize the whole window to force update. You should see
TOVE-shop subscriber. Set its subscriber number to the called party number you want to
use. If number is over 10 characters long use only last 10 characters. Configure 
"to store" and "to call center" translate SIBs. Set translate filter property to a number
you want the called party number to be translated.

Go back to service level and right click "Example Services" icon and select install.
Node name is slee1. Whole service gategory is now installed to slee1.

4 COMPILING THE SOFTWARE

4.1 CONFIGURATION
Check that config/Make.rules.mak contains correct paths and programs.
Makefiles must have absolute path to the Make.rules.mak file.

4.2 COMPILE
All makefiles are Microsoft makefiles, so NMAKE must be in the path.
Open dosbox and type nmake.

**IMPORTANT NOTE**
Orbacus C++ client and Java server combination
has a problem with ob_ids. Some classes generated by jidl tool must
be changed by hand to enable communication between C++ client and 
Java server. Directory: idl/inap/tove/idl/toveinap.

_TcUserFactoryImplBase:
    static final String[] _ob_ids_ =
    {
        /* generated
        "IDL:idl.tove/toveinap/TcUserFactory:1.0",
        "IDL:omg.org/TcSignaling/TcUserGenericFactory:1.0"
        */
        // new, ids without package
        "IDL:toveinap/TcUserFactory:1.0",
        "IDL:omg.org/TcSignaling/TcUserGenericFactory:1.0"
    };

SSF_SCF_responderHelper:
    public static String id()
    {
        /* generated
        return "IDL:idl.tove/toveinap/SSF_SCF_responder:1.0";
        */
        // new, ids without package
        return "IDL:toveinap/SSF_SCF_responder:1.0";
    }

SSF_SCF_initiatorHelper:
    public static String id()
    {
        /* generated
        return "IDL:idl.tove/toveinap/SSF_SCF_initiator:1.0";
        */
        // new, ids without package
        return "IDL:toveinap/SSF_SCF_initiator:1.0";
    }


4.3 RUNNING AFTER COMPILATION
Check that nameservice is running (in Linux) and src/orbacus.cfg has correct IP address.

Go to src/tove/scp and type nmake sce1 (point code = 1). This starts service creation and 
management software. 

Start new dosbox and go to src/tove/scp and type nmake slee1 (point code =1). This starts service execution software. 

Start new dosbox and go to src and type nmake gui. This starts GUI software.