Prerequisites

Meridix Web Application, Meridix Studio Service, Meridix Backend services needs to be installed on a Windows Server 2012 or later with .NET Framework 4.7.x installed or later. The recommended minimum hardware is 4 CPU Cores and 8 GB RAM. The server needs to have network access to the Microsoft SQL Server-which hosts the system database and CDRs database.

...

1. meridix_studio_service_console_binaries.zip or MSI build

2. meridix_studio_webdeploy_package.zip

3. meridix_data.dacpac

4. Theme zipped file.

Install a new system

You need to decide the hosting servers (Web Server, Database Server, and Application Server) and the following guides will assist you through the installation process on each server.

Configuring_the_Database_Server

1. Create an empty database named meridix_sys on the MSSQL server to host the MXSDB (Meridix Studio Database).

   1. Create a SQL Server Authentication login and user with db_owner rights on the meridix_studio database.
      Note: The password for database users should not include the following characters: (<, >,&,",')

2. Copy meridix_data.dacpac master to the database server and do the following steps:

   1. Create an empty database named meridix_data on the MSSQL server to host MXDDB (Meridix Data database).

   2. Meridix_data> tasks> Register as data-tier application

   3. Meridix_data database > tasks > Upgrade Data-tier application > meridix_data.dacpac

   4. Create a SQL Server Authentication login and user with db_owner rights on the meridix_data database.

Configuring the Web Server

1. Make sure the content of the .zip Extract the file VERSION_AND_DATE_meridix_studio_webdeploy_package.zip is extracted to (drive):\meridix\dist\

2. On Web hosting server, Check the Microsoft .net version.
   On Windows Server 2012 or later install Microsoft .NET 4.7 or later (https://www.microsoft.com/net/download/framework).
   On Windows Server 2016 or later .NET 4.7+ is already installed.

3. Install Internet Informations Service (IIS) with the Web Server (IIS) - Role 

   1. Make sure ASP.NET 4.5/4.6 Feature is installed. 

4. Install IIS Web Deploy 3.5 or later (included in the (drive):\meridix\dist\ folder or  http://www.iis.net/downloads/microsoft/web-deploy)

5. Create a folder with the customer name and other two folders beneath the customer folder with the following names: meridixstudio, meridixstudio_service 

6. Create an IIS Site (or reconfigure the default) 

   1. Set the site name to Meridix (can be named differently)

   2. Set the physical path to (drive)the folder you created in step 5 example C:\customer folder\meridixstudio

      

   3. Bind it to port 80 (or any other port) and port 443 and assign the right SSL certificate accordingly.
      It is mandatory to check on Require Server Name Indication if you have different SSL wildcards installed.

      

   4. In the hostname section, you write the full domain name. (Ex. reports.customer.se) 

   5. Add the domain name and server name in your DNS portal.
      
      

7. Create a folder and name it Ex. _webdeploypackage.
   Unzip the file (drive):\meridix\dist\VERSION_AND_DATE_meridix_studio_webdeploy_package.zip into a folder on the server called (drive)you created Ex. F:\meridix\dist\_webdeploypackage.

8. Create a BAT file (drive):\meridix\dist\an empty BAT file, name it deploy_webpackage.bat and , edit it with a text editor (e.g. Notepad++/Notepad)

   1. Add the following command and set the path accordingly

      Code Block
      "F:\meridix\dist\

      PATH

      _

      HERE

      webdeploypackage\meridix_studio_webdeploy.deploy.cmd" /Y -enableRule:DoNotDeleteRule "-setParam:name='IIS Web Application Name',value='NAME_HERE'"

   2. Replace the placeholder placeholder PATH_HERE HERE in the above command with the full rooted path to the the folder you (drive):\meridix\dist\_webdeploypackage folder created in the previous step.

   3. Replace the placeholder NAME_HERE with the IIS Site name (default: Meridix) created in step 6.a.

   4. Save the updated bat file.

9. Execute the bat file with administrator rights (right-click and click Run as administrator)

10. Open the web application folder (defined in step 6.b)

    1. Rename the file NOT_SET.basic.config to basic.config

    2. Open basic.config in a text editor and change the following settings :

       1. Change the connection string to target the meridix_sys database (created in step 1 under Configuring the Database server) using the SQL Server Authentication login (created in step 1.a. under Configuring the Database server)
          
          Example:

          Code Block
          server=DbServer;database=meridix_sys;integrated security=false;user id=DbUser;password=DbPassword;

       2. Define a unique application id (Meridix.Studio.Application.Id) - Can be any value but should be system unique e.g. companyX.reporting etc.

       3. Add a connection string to the Data DB  that should be used as the report data source.

          

       4. Code Block
          <add key="exchange.ModuleName.connectionstring" value="Server=Server,1433;Database=Database;User ID=User ID;Password=Password;Trusted_Connection=False;Encrypt=True;Connection Timeout=30;"/>

11. Open a web browser and browse to the site created in step 6.

    1. The first time the application is started it might take a couple of minutes before it loads due to internal initialization operations, database schema updates, etc.

    2. If everything works as expected a login page will be loaded - Log in with the default credentials U: admin@meridix.se and P: ppn
       If you get an error message open the (drive):\meridix\webapp\App_Data\Logs folder under the web application folder and review the logs. Contact operations@meridix.se if you have any questions about the error.

12. Once logged in, the system must be custom branded which is achieved by applying the default theme package or customer-specific theme.

    1. Read more on custom themes in the following link:

       Branding and theming  

    2. Request the latest Telepo Theme from operations@meridix.seor use your own custom theme.

    3. Upload the theme package to the website by navigating to system administration → Theme settings. Scroll down a bit and press “Välj Fil” and locate your Theme file.

    4. Press “Upload theme package”

       

    5. Change the Theme name to a description of the theme (Ex. CustomTheme) and make sure the Theme package type is set to the Theme package. Click on Save.

       

    6. Press Ctrl+Shift+R or Ctrl+F5 to make sure the new theme package content is loaded. (If that does not work, clear the browser cache manually).

    7. The UI should now have a specific theme look and feel instead of the default Meridix theme.

13. Configure the system by navigating to System administration → Application settings

    1. Define the System location (a descriptive name e.g. Telepo/Customer Reports) - This value will be used in initialization e-mails etc. to identify the system for end-users.

    2. Set the System public URL to the public/internal URI that the end-user will access the system through.

    3. Configure the SMTP server settings to use. Will be used for user initialization e-mails, report distribution, etc.

    4. Verify that the security settings comply with your policy (minimum password lengths etc.).

14. Enable the required module by navigation to System administration → Module settings

    1. Expand the desired module section and check both the Loaded and Enabled checkboxes.

    2. Add a connection string to the Data DB  that should be used as the report data source.
       

       Image RemovedImage Added

       Code Block
       Server=Server,1433;Database=Database;User ID=User ID;Password=Password;Trusted_Connection=False;Encrypt=True;Connection Timeout=30;

    3. Press Save Changes and click on Validate connection to check if the connection to the database is valid.

       

       
       

15. Configure the feature set from System Administration>Feature Set> Add new set. We define two sets, Basic, and Advanced as below:

    •  

      

16. The web application is now installed and configured.

17. Install meridix_studio_service downloaded in STEP 1   (drive):\meridix\dist\VERSION_AND_DATE_meridix_studio_service_setup.msi

    1. ((install it into the default directory specified in the MSI) and browse to the installation directory preferably next to the web application folder created in step 6.b.)

    2. Alternatively, you can unzip the VERSION_AND_DATE_meridix_studio_service_console_binaries.zip into the meridixstudio_service created in step 5

18. Open the installation directory defined in the previous step and do the same configuration with the file NOT_SET.basic.config as described in step 10 and add the same connection string as in step 10. Note that some properties are not available in the non-web context.

19. Open the Meridix Studio Service Administration GUI from the start menu and start the windows service through the GUI or explore the meridixstudio_service folder and start Meridix.Studio.Service.Console.exe and type S + Enter

    1. If it does not start successfully review the log files in the Logs folder under the installation directory.

    2. Create a scheduled task to run Studio.Service.Console.exe with arguments /send every 10 minutes.

20. The back-end service is now installed, configured and started. 
    (It will load additional settings such as SMTP etc. from the same source as the web application).

21. Next step is to create the API ticket/credentials used to synchronize the catalog. 
    Login into the Meridix Web UI and go to System Administration → System API Tickets

    1. Create a new API ticket called Telepo/Customer sync (or any other descriptive name)

       

    2. Check the admin rights checkbox under the newly created ticket and click save.

       

    3. The token and secret will be used in a later step.

22. Extract the (drive):\meridix\dist\CatalogSyncClient_DATE.zip into the directory (drive):\meridix\Telepo_catalog_sync

23. Edit the file (drive):\meridix\Telepo_catalog_sync\CatalogSyncClient.exe.configwith a text editor.
    

    1. Set the telepo_base_url to the IP address of the management node.

    1. Set telepo_token and Telepo_secret to access the management node (provided by customer)

    2. Set the Meridix:server_token to the token created in step 21.

    3. Set the Meridix:server_secret to the secret created in step 21.

    4. Set the customer_name to a descriptive customer name e.g. Company X.

    5. Execute the (drive):\meridix\Telepo_catalog_sync\TelepoCatalogSyncClient.exe executable and verify that it runs successfully.

    6. Any errors are reported both in the console UI and in the subfolder Logs.

    7. After a successful execution log into the Meridix Web UI and verify that a new customer (tenant) is created and contains the users, agents, ACD defined in the Data DB.

    8. Schedule execution of the (drive):\meridix\Telepo_catalog_sync\TelepoCatalogSyncClient.exe with Windows built-in task scheduler with the interval(s) that the sync should be run (usually once every 24 hours). 

24. Add a System administrator user/s. (Ex. administrator@company.com) by navigating to Administration → users and press Add new user.

25. Deactivate admin@meridix.se user

    

26. Under System Administration->Property Management add property force_https and value True to enable https only. 

    

27. If you wish to have a module name other than the default see article : Rebrand Modules to customer preferences

28. If you are in different time zone than Sweden/Europe then you need to update property management and Sync config file accordingly.
    Example: x-Customer system must show in the GMT zone, the data and the organizations we import from x-Customer are saved in Europe time zone so we configured the properties in the property management as the following:

    

29. Provide Technical contact person information to Operations@meridix.se.

Configuring the Application Server

1. Follow the guide on Meridix Import Service setup To configure the application server.

2. Edit the sync application config file created in Meridix Import Service setup and add the following key but replace System Time Zone to the correct time zone.

   Code Block
   <add key="default_time_zone" value="System Time Zone"/>

   The above key will update the customers to the chosen time zone. The time zone list is available at
   https://stackoverflow.com/questions/7908343/list-of-timezone-ids-for-use-with-findtimezonebyid-in-c

3. A Meridix system is now fully set up.

Upgrade an existing system

This section describes how to upgrade an existing system installed using the steps described in the section Install a new system (above).

1. Backup the current system files. 

2. Retrieve the latest release from Meridix.

3. If there is a text file called upgrade_instructions.txt (or. md) in the release_DATE_HERE follow any custom instructions in that document (it has precedence over this content)

4. Unzip the file (drive):\meridix\dist\VERSION_AND_DATE_meridix_studio_webdeploy_package.zip into a folder on the server called (drive):\meridix\dist_webdeploypackage replacing any existing files in the target folder.

5. Execute the the (drive):\meridix\dist\deploy_webpackage.bat file with administrator rights (right click and click Run as administrator).

6. Open a web browser and browse to the Meridix login page.

   1. The first time the application is started after an update it might take a couple of minutes before it loads due to internal initialization operations, database schema updates, etc.

   2. If everything works as expected a login page will be loaded - Log in with the default credentials U: admin@meridix.se and P: ppnIf you get an error message open the (drive):\meridix\webapp\App_Data\Logs folder under the web application folder and review the logs for more information about the error.

7. Unzip the file VERSION_AND_DATE_meridix_studio_service_console_binaries.zip into the folder called Customer\meridixstudio_service.

8. Check Meridix studio if the studio service is running.
   

9. The system is now updated.

Appendix

Available modules :

• TelepoBCS

• Centrex

• Broadworks

• Businessphone

• Cisco

• Cs1000

• Intelligate

• Lg

• Mxone

• Nec

• Servit

• Trio

...