|
Before You Begin
Before you begin the installation process, you should plan the setup of your Monarch Server System in a manner suited for your tasks.
Distributable and Non-distributable Components
Monarch Server System is a distributable system. This means that different components of the system can be installed on different machines within a network. There are two types of components: distributable and non-distributable.
Each of the non-distributable components can be installed only once per Monarch Server system.
Distributable components can be installed several times on different computers to form a desired configuration of the Monarch Server system that is tailored to your requirements.
The system consists of five main components:
q Configuration Service
q Agent Service
q Services
q Web Applications (Admin, Client, and RMSClient)
q Repository
The Configuration Service is a non-distributable component. Install only one instance of the Configuration Service per sold copy.
The Agent Service is a distributable component. It should be installed on every server used for MS installation. All instances of Agent Service use one Configuration Service.
The Agent Service launches the following services:
q Datawatch.Config.ConfigServer.exe
q Datawatch.ModulesManagement.Agent.exe
q Datawatch.RemoteServices.AdminServicesHost.exe
q Datawatch.RemoteServices.ClientServicesHost.exe
q Datawatch.RemoteServices.FilingDispatcherServiceHost.exe
q Datawatch.RemoteServices.MaintenanceDispatcherServiceHost.exe
q Datawatch.RemoteServices.NotificationsDispatcherServiceHost.exe
q Datawatch.RemoteServices.VolumeServicesHost.exe
q Datawatch.RemoteServices.DataPumpDispatcherServiceHost
q Datawatch.RemoteServices.DataPumpServicesHost
q Datawatch.RemoteServices.DataPumpStorageServicesHost
q Datawatch.ModulesManagement.Agent.exe
q Datawatch.RemoteServices.RMSClientServicesHost.exe
q Datawatch.RemoteServices.RMSContentServiceHost.exe
These services can run on different servers.
The Web Applications is a distributable component. It can be installed several times on different computers according to the number of instances.
The Repository is a distributable component. It can be installed on different computers. In most cases, only one instance of Repository should be installed.
Database Server Preparation
When the Database Service component is chosen during the installation, the setup will create the Monarch Server database on the database server. You will need to have a special database user that will be used by the Monarch Server setup for database creation and under which Monarch Server will further connect to the database.
SQL Server
There are two levels of security that may be set for the Monarch Server database user in SQL Server. They differ in partitioning maintenance task support.
In a Monarch Server database, servicing Report Warehouse functionality, all report-related data are partitioned by date ranges, and each partition can be managed separately — backed up, removed, joined with another partition, etc. For Monarch Server to perform these operations automatically, partition maintenance tasks were designed.
For these tasks to function properly, the Monarch Server database user will require more rights. This requirement may be considered unsecure in some environments, particularly when the database server is used for several databases and not only for Monarch Server. In this case, these rights may be assigned temporarily as the partitioning maintenance task is performed. Another option is to perform partitioning maintenance operations manually.
For setup to create the Monarch Server database — and support the partitioning maintenance task functionality — you will need the Database Creators server role to be assigned to the user.
|
NOTE |
This role will allow the user to destroy any database in the system (without reading data). Thus, it is recommended to assign this role only during the time of installation and during partitioning maintenance task operations. |
To create the user, login to the database server under System Administrator (sa) user, and execute the following commands:
exec sp_addlogin 'ES_LOGIN', 'ES_PASSWORD'
exec sp_adduser 'ES_LOGIN', 'ES_USER'
exec sp_addrolemember 'db_ddladmin', 'ES_USER'
exec sp_addrolemember 'db_datareader', 'ES_USER'
exec sp_addrolemember 'db_datawriter', 'ES_USER'
exec sp_addsrvrolemember 'ES_LOGIN', 'dbcreator'
If you decide to disable the Database Creator role after the Monarch Server database is created (i.e., after installation is complete), you will need to issue the following command under System Administrator:
exec sp_dropsrvrolemember 'ES_LOGIN', 'dbcreator'
|
NOTE |
The db_owner role may be removed, and the db_executor role may be added. If the db_executor role does not exist, it may be created as follows: CREATE ROLE db_executor GRANT EXECUTE TO db_executor EXEC sp_addrolemember 'db_executor','ES_USER' |
Installer Preparation
Depending on a computer’s local security policies and configuration, the execution of downloaded files might be blocked. In particular, when downloading a file through a Windows OS to an NTFS partition, the Windows OS considers this file as an attachment by default. As a result, the opening, unpacking, or execution of the file is “blocked,” resulting in errors. To avoid the installer file of Monarch Server from being blocked, the following steps are recommended.
To unblock the installer file after download
1. Find the ZIP file of the Monarch Server installer.
2. Right-click on the ZIP file and select Properties in the context menu.
3. Navigate to the Security section of the General tab in the Properties window. Find the Unblock check box beside the text “This file came from another computer and might be blocked to help protect this computer.”
4. Select the Unblock check box to activate it.
5. Click OK to apply the change.