Prerequisites

• Supported Hardware:
• DataSplice is supported on all current Windows operating systems: Windows Server 2003/8, Windows XP, Vista and Windows 7
• Note that Windows Server 2000 is not supported
  
• Any server with moderate specs should be sufficient - back end data sources are typically the performance bottlenecks
• At least 1gb RAM and 1gb free disk space
  
• DataSplice is a 32bit application, but both the server and clients work on 64bit versions of Windows
• Microsoft .NET Framework 2.0 or greater is needed
• If connecting to Oracle databases an Oracle ODP.NET client 10g or greater, available from Oracle's website
• The tnsnames.ora and other configuration files will need to be modified to for this client to reference the Oracle instances that will be accessed
  
• If using the Maximo Integration Plug-in a compatible Java Development Kit is needed
  
• Account information - prior to proceeding, the following account information will be needed:
• Installation Account - The user installing DataSplice will need local administrator permissions.
  
• DataSplice Service Account - The service will run as a local machine or domain account. By default the Local System account is used. This account must have permission to modify files in the root DataSplice server folder and to modify the system registry (HKLM\Software\DataSplice).
• Database Account(s) - A valid account for each target database is needed. In most cases these accounts can be restricted to read only permissions if desired.
• Maximo Account - If using the Maximo Integration Plug-in, the server needs an account it can use to obtain various basic information from the Maximo application server.
  

Installation Steps

Use the following steps to create a new DataSplice Server Instance:

1. Create the root instance folder.
2. Unzip the contents of the DataSplice package into this folder.
3. Likewise, unzip the contents of any plug-in packages being used into the folder. You can safely overwrite all directories and files when prompted.
4. Run the Server\Resources\Scripts\post_install_setup.bat script to create initial configuration files.
5. Open Server\dssplicer.exe.config in a text editor to update the instance details. Modify as necessary the following keys in the appSettings section:
   
• ServerInstanceName - Each instance on a machine needs a unique name. This is also displayed on clients when connecting, so changing this to DEV, TEST, PROD, etc. will add additional confirmation when connecting in the future. Server instance names are case sensitive, we recommend the use of all caps for instance names.
• ServerPort - Each instance will also listen on a unique TCP port.

 

<?xml version ="1.0"?>
<configuration>
  <configSections>
    <section name="pluginEvents" type="System.Configuration.IgnoreSectionHandler" />
    <section name="log4net" type="System.Configuration.IgnoreSectionHandler" />
  </configSections>
  <startup>
    <supportedRuntime version="v2.0.50727" />
  </startup>
  <appSettings>
    <add key="ServerInstanceName" value="DEFAULT" />
    <add key="ServerPort" value="4100" />
  </appSettings>
...

 

6. Register the DataSplice service by opening a command prompt at the <DataSplice Instance>\Server folder and running "DSService.exe -install <InstanceName>", where <InstanceName> matches (case-sensitive) the value specified in the config file.
• Each service is named "DataSplice 3.1 Server Instance = <InstanceName>", which allows multiple services to be distinguished easily when running on the same machine.
  
• The service is installed by default to start manually and run as the Local System account. Use the services control panel application to change these if desired.

Maximo Integration Plug-in

If using the Maximo plug-in in, some additional installation steps are required in order to get it connected to a Maximo application server. Refer to the Maximo Plug-in Configuration section for details on the actions that need to be taken.