migRaven.one consists of three programs and five services. The installer installs the components. The migration client, like its predecessor, is used to migrate NTFS permissions. With the new Web Client, you can evaluate the scanned directory and authorization data.
Background services include the database, two controlling services, and one each for scanning Active Directories and scanning file servers (resources).
The components of migRaven.one and their interaction.
In addition comes the migRavenInstaller with whom the migRavenComponents are installed.
* Browser and Internet Information Service are not included.
Table of Contents
- 1. The programs (front-ends).
- 2. The services
- 3. The used ports
1. The programs (front-ends).
migRaven.one consists of three programs:
|1||Installer||It installs all components, but not the ResourceScanService.||migRaveninstall|
|2||Migration client||The migration client migrates permissions to a Windows Share. Sources can be a Windows Share, a Novell Server or authorization data from a table.||migRaven|
|3||Web Client||This provides evaluations of the data collected by the Migration Client. It can also be used by data owners (area administrators).||migRavenWeb|
1.1. migRaven Installer
The migRavenInstall.msi installs the migRavenInstall.exe and put the icon for this "migRavenInstall "on the desktop.
With this installer you can install most of the components automatically.
When requesting a license, you must enter the license key and your email address.
Installing the Web Client requires that you have previously installed Internet Information Services.
The installer can not install the ResourceScanService. This is created in the migration client.
With the installer, the components installed here can also be uninstalled again.
It also removes the license key and the database. You should therefore use the uninstall only if you migRaven want to remove completely.
A new installer detects the existing components and allows the update to the new version.
The installer himself can by calling the migRavenInstall.msi or through the system administration.
1.2. Migration Client (desktop app)
The migration client is the evolution of the migRaven Version 5. It remains the migration tool that performs authorization migrations. Scanning the domains and project shares provides a wealth of information, such as object data, permissions, directory structures, and file sizes.
From this, the idea was born to make the data accessible for analysis by the administrator.
The first time the migration client runs, a migravenResourceScanHost must be installed after the AD scan.
1.3. Web Client (Data Owner Client, Web App)
The Web Client is a development that makes it possible to analyze and analyze the scanned AD and project data. For this the data from the migRavenDatabase.
Prerequisite is a separate Internet Information Services (IIS).
The Web Client provides numerous analysis functions that can be used to evaluate the scanned AD data and directory information.
In the migration client it is possible to set up data owners. These are selected employees from specialist departments who receive authorizations for the database data of their department. These data owners can analyze the scanned data of their department with the Web Client.
It is possible to operate several web clients and thus enable several data owners to carry out these evaluations.
2. The services
The following services are required migRaven:
|No.||Service||>Description<||service name||Port (The Harbour District)|
|1||Database||It contains the scanned AD and project data||migRavenDB - aikuxGraph||7687|
|2||Database Service||He coordinates the access to the database.||migRavenDBServiceHost||10291|
|3||Core service||He controls the presence of all necessary services and controls their cooperation.||migRavenCore Service Host||8999|
|4||AD Scan Service||It executes the AD scan initiated in the migration client and transfers the data to the database service.||migRavenADScanServiceHost||8099|
|5||Resource Scan Service||It performs the scan of a share or directory initiated in the migration client for a project and passes the data to the database service.||migRavenResource Scan Service Host||8077|
Important to the services is that they are started in the correct order shown here. The ports must be enabled in existing firewalls if necessary.
In the installer directory you will find the msi files for the services. Nevertheless, the services must be installed via the installer, because only then they are registered in the database. Unregistered services are migRaven unknown. However, you can stop and restart registered services, eg in the service management.
The service management with the migRavenServices. Here to recognize the migRavenResourceScanServiceHost, the last one, runs under the specified account, not under the local system account.
2.1.1. Database: migRavenDB - aikuxGraph
This service is not new. It's the longest of migRaven used graph database Neo4J, of course in the current version.
Core of migRaven remains the graph database where the AD objects and project data are stored.
These data do not have to be deleted when changing the version. In the future, they will be updated and thus enable the development of authorizations to be documented and evaluated over longer periods of time.
The database is controlled by a service, the migRavenDBServiceHost.
2.1.2. System Requirements
The database absolutely needs a 64bit-Windows and the current 64bit-Java.
migRaven is a database program with a very fast database.
The database requires a fast hard drive, preferably an SSD, and a lot of memory to cache, at least 8 GB.
Insufficient memory, a slow disk, and a virtual machine slow down the database.
2.1.3. Backup and Restore
The database can be backed up with the following command:
"C: \ Program Files \migRavenDB \ bin \ Neo4j-Backup.bat "-host localhost -to d: / temp / backup
At d: / temp / backup you can specify your desired destination directory.
This saves the data of your database subdirectory "graph.db". It contains your AD and project data.
For the restore, stop the service "migRavenDB - aikuxGraph "and replace the data in the subdirectory" graph.db "with the backed up files. Then the service must be restarted.
2.1.4. Access to the database via a web browser
The database can be accessed using any web browser and the URL http: // servername: 7474 or http: // ip_address: 7474.
With the username "migRavenDBReader "and password" migR75% "(entry without quotation marks) you can execute read commands.
For information and sample queries about this interface, see migRaven Report API.
2.2. Database service
The database service service: migRavenDBServiceHost
This service controls access to the database.
Like the database, this service is unique.
2.3. Core Service (configuration service)
The configuration service: migRavenCore Service Host
This service checks if all the necessary services are available.
The service is unique.
2.4. AD Scan Service
The AD Scanner service: migRavenADScanServiceHost
This service scans the in migRaven selected domains.
The mentioned services are automatically installed and started by the installer.
The migration client can be used to create additional AD-Scan services for other domain controllers.
2.5. Resource Scan Service
The file server scanner service: migRavenResource Scan Service Host
This service scans within one migRavenProject the specified source share or the source directory with subdirectories.
He is exclusively in the Migration client configuration installed and started, not by the installer.
For each file server, a resource scanning service can be installed.
* We use the English spelling of "Resource" for this service, not the German "Resource".
3. The used ports
|Port (The Harbour District)||Minutes||>Description<|
|outgoing (on DC or Filer)|
|8999||TCP||for the core service|
|10291||TCP||for the Database Service|
|8099||TCP||for the AD Scan Service|
|8077||TCP||for the Resource Scan Service|
|7687||TCP||between DB and DBHost|
|10413||TCP||for the archiving workflow|
The of migRaven used ports