DIVAnet is a distributed application, meaning that it is often installed on multiple systems. Refer to Chapter 2 to understand what systems and servers DIVAnet should be installed on, and what particular DIVAnet services should be installed.
Each DIVArchive site connected to DIVAnet must be running DIVArchive 7.3.1 or later.
DIVAnet can be installed on 64-bit Windows platforms, and can be installed either in the same home directory as DIVArchive, or in its own directory.
Running the DIVAnet installer requires administrator privileges.
By default, the DIVAnet installer handles the installation of the DIVAnet services files, the DIVAnetUI, and a compatible 64-bit Java 8 Java Runtime Environment (JRE). DIVAnet uses the installed JRE for execution. Installing the DIVAnet database requires an Oracle Database 11g release 2 or later, and Oracle SQLPlus (Oracle 11 or later client software) installed directly on the DIVAnet Windows system.
If you are reinstalling DIVAnet, make sure the DIVAnet components are not running.
Launch the DIVAnet installer executable, DIVAnet_V2.0.version.exe.
Select the desired components, and then click Next.
Select Java if you have not previously installed in the target directory.
If you only want to install the DIVAnet user interface, deselect DIVAnet Services.
Specify a target installation directory. This will be the DIVAnet home directory. Then, click Install.
Note:
You can use the DIVArchive installation directory as the DIVAnet home directory. However, Oracle recommends installing DIVAnet in its own directory.The following sections describe additional steps you may need to take to complete the installation. See Chapter 2 for more information.
To create the DIVAnet database, you first create the DIVAnet tables, and then configure the DIVArchive sites.
This step involves creating the DIVAnet database tables that will exist on a running Oracle server. This step is required only for a full DIVAnet install (see Chapter 2).
To run the SQL creation scripts, you must have SQLPlus (Oracle 11 client software) installed on the system you are installing DIVAnet on.
Open a command line window. Change directory to the DIVAnet home directory (the directory where DIVAnet is installed).
Change directory to Program\Database\divanet\Install.
Run the following command:
create_divanet_user.bat syspassword username userpassword oracle_tns_name
In the previous command, syspassword is the Oracle system password, username is the Oracle user name/schema name that will contain the DIVAnet tables, and oracle_tns_name is the Oracle TNS Name for the DIVAnet database you want to use for installation. If there is no TNS Name defined for the database, you can refer to the following section to create a TNS Name real-time.
To delete the DIVAnet database schema, execute the following steps.
Caution:
This will delete all data in the DIVAnet database.Change directory to Program\Database\divanet\Install.
Run the following command:
delete_divanet_user.bat syspassword username oracle_tns_name
In the previous command, syspassword is the Oracle system password, username is the Oracle user name/schema name that will contain the DIVAnet tables, and oracle_tns_name is the Oracle TNS Name for the DIVAnet database you want to use for installation. If there is no TNS Name defined for the database, refer to the following section to create an Oracle connection string for use in the add and delete scripts.
If you do not have a TNS Name defined for your database, you can supply an Oracle connection string. The format for this string is the following:
netaddress:port/remote_servicename
Where:
netaddress: Network Address where the database runs
port: Port where clients can connect
remote_servicename: The Oracle remote service name. This is different from the service name used locally. The default for the DIVA Oracle database installation package is lib5.world. An example full connection string is 183.34.34.67:1521/lib5.world.
After the DIVAnet tables are created, you must configure the DIVA sites in the DIVAnet database. Run the addSites.bat script to configure the sites in the database as follows:
Change to the DIVAnet home directory, and then navigate to the Program\divanet\bin subfolder.
Run the addSites.bat script. This script will walk you through adding sitename records and configuring sitenames, locations, and comments. The network connections to the sites are configured in the ClientAdapter configuration file (see Chapter 4). You should create sitenames that are easy to read and reflect either the physical location, or the function of the site.
Note:
The sitenames you provide in this step will be used when configuring both local and remote DIVAnet services. Ensure the desired sitenames are consistent and agreed upon before running the addSites script. If you make a mistake while running theaddSites.bat command, Oracle recommends that you either recreate the database or contact Oracle Support. After the sitenames are in the database, DIVAnet installation can proceed.Refer to Chapter 2 to determine which DIVAnet services need to be configured, and then refer to Chapter 4 for details on how to configure each service.
Underneath the DIVAnet home directory, in the Program\conf\divanet\templates subdirectory, there are template configuration files for each of the DIVAnet services that need to be configured. Each template file has a .ini extension. You should take each file and copy it to the parent directory (in this case, Program\conf\divanet). When you copy each file, make sure to remove the .ini extension.
At the top of each .ini file, there is documentation of the parameters available. For each DIVAnet site, configure a ManagerAdapterConfig.xml. For a full DIVAnet installation, you also configure the ClientAdapterConfig.xml and DBSyncConfig.xml files.
Many of the parameters can be left at their default value. You should not have to change any of the configuration files in the Program\conf\divanet\wrapper folder. You may optionally add information to the divaEnv.conf file (see Adding Script Variables to a Configuration File for more information).
Note:
If you are unfamiliar with what parameters should be modified from their defaults, contact Oracle Support.See Chapter 2 to determine what services need to be installed and configured.
After the configuration files have been set up properly, install and start the DIVAnet services. Perform each step for every service to be installed at each DIVAnet site.
Change to the DIVAnet home directory (where DIVAnet is installed).
Navigate to the Program\divanet\bin folder.
Run the InstallDivanetService.bat script, providing the wrapper configuration file for the service being installed. For example, to install the ManagerAdapter Service (required at all sites where a Manager to be connected to DIVAnet is running), run the following command:
InstallDivanetService.bat ../../conf/divanet/wrapper/ManagerAdapterWrapper.conf
For the ClientAdapter Service, use the same command and same path, but substitute ClientAdapterWrapper.conf as the file name.
For the DbSync Service, use the file name DBSyncWrapper.conf.
In the Windows Services window, you should see one or more of the following DIVAnet services:
Divanet ManagerAdapter
Divanet ClientAdapter
Divanet DbSync
The services can be started in any order, but keep in mind that after the DbSync Service and the ManagerAdapter Services are both started, the database syncing process will start automatically. Start the ClientAdapter Service to allow new DIVAnet connections and API processing.
The DIVAnet applications produce two main types of logs:
Trace Logs — Located within the DIVAnet home directory, in the Program\log\divanet subfolder. Each of the DIVAnet services (ManagerAdapter, DbSync, and ClientAdapter) create their own subfolder underneath the Program\log\divanet folder, and generate their log files in that subdirectory.
Wrapper Service Logs — Examine these first to make sure the applications are starting correctly. These logs are within the DIVAnet home directory in the Program\log\divanet subfolder. They will be named similar to the Wrapper.conf file, but with a .log file name extension (for example: ManagerAdapterWrapper.log).
The most common errors in configuring DIVAnet are errors in specifying the sitenames. All DIVA sites in the DIVAnet network must use the same set of sitenames. The sitenames must be consistent in all of the configuration files, and in the DIVAnet database. The LocalSitename parameter must be correctly configured in all of the service configuration files.
You should also check the DIVArchive Source/Destination. For example, by default, if site diva1 has a Source/Destination that is named the same as one on site diva2, DIVAnet considers them as pointing to the same logical Source/Destination. If the same Source/Destination name is configured on two different DIVArchive sites, DIVAnet will assume that these Source/Destinations refer to the same place.
When the DbSync service is started, it will attempt to synchronize archived object information by consulting the ManagerAdapter service. The ManagerAdapter service in turn pulls asset information from the DIVArchive site to which it is connected. Therefore, you should start the DbSync service and ManagerAdapter services only when you are ready to begin synchronization.
Note:
If you stop the DbSync service, synchronization will start again where it left off when the service is restarted.The DivanetAdmin command-line tool monitors the status of the database synchronization on a site-by-site basis. If DIVAnet is performing an initial synchronization of a particular site, it will show the percentage complete of that initial sync operation. If the site is up-to-date, DivanetAdmin will indicate that the site is In Sync.
DivanetAdmin can also be used to resynchronize a site. This involves deleting all archived object records previously synchronized from the site, and resynchronizing them from the source. This should only be used in rare circumstances, such as when the source DIVA database has been unexpectedly restored from an out-of-date database backup.