- 18 Aug 2025
- 6 Minutes to read
- Print
- DarkLight
- PDF
BrM 7.1 Installation
- Updated on 18 Aug 2025
- 6 Minutes to read
- Print
- DarkLight
- PDF
BrM 7.1 Installation
- Download the BrM7 install from the below link.
https://mayvue.sharefile.com/home/shared/foc21d40-480f-4e40-bf11-624f0a125627
- Right-click on installation exe and click run as administrator. Click yes on any user access warnings. For example, a “Microsoft Defender SmartScreen” might pop up. If encountered, click “More info” then “Run anyway”.
- Click “Next” on the welcome page.

b. On the license agreement page, accept the license terms then click “Next”.

c. Enter your user name and organization on the customer information page and click “Next”.

d. On the Setup Type page, choose "Complete" and click "Next".

e. Click “Install” on the ready to install page.

f. Pay attention to installation process and if any errors pop up, take a screenshot and send to the contractor via Jira service management (https://support.mayvue.com/) or by emailing support@mayvue.com.

g. If everything was successful, you will see the success message and can click “Finish”.

Now that BrM 7.1 is installed you will configure IIS and your database to finalize the BrM 7.1 setup.
- Create the BrM7 Site
- Create a Windows account Brm7User if it does not exist for running the BrM7 app under. This can be done through a CMD prompt or PowerShell. Users only need to run one option.
- CMD ( Run command prompt as an admin )
- net user Brm7Site Brm7SitePwd /add
- With “Brm7SitePwd” being the password you want.
- net localgroup IIS_IUSRS Brm7Site /add
- net user Brm7Site Brm7SitePwd /add
- PowerShell
- New-LocalUser -Name "Brm7Site" -Password (ConvertTo-SecureString "Brm7SitePwd" -AsPlainText -Force) -FullName "Brm7Site" -Description "Local account for Brm7Site"
- Add-LocalGroupMember -Group "Administrators" -Member "Brm7Site"
- Add-LocalGroupMember -Group "IIS_IUSRS" -Member " Brm7Site "
- CMD ( Run command prompt as an admin )
- Create an app pool named “BrM7” and run it under the Brm7User account.
- Open IIS and expand the menu then right-click on “Application Pools” then select “Add Application Pool…”.
- Create a Windows account Brm7User if it does not exist for running the BrM7 app under. This can be done through a CMD prompt or PowerShell. Users only need to run one option.

ii. Name it “BrM7” and click “OK”.

iii. Right-click on your new App Pool and go to advanced settings and locate the “Identity” property. We want to change this to our new user. To do so, click on the ellipsis on the right.

iv. In the Application Pool Identity screen, click the “Custom account" button and then click on “Set…”.

v. This will bring up the credentials window. Enter the username and password from the user we created and click “OK”.

vi. If this was successful, you will now see the user listed in the identity property.

vii. Ensure app pool’s “Load User Profile” = true then click “OK” to close.

c. Right-click on Default Web Site and select "Add Application...".

d. In the “Add Application” set the following then click “OK”.
i. Alias = BrM7
ii. Application pool = BrM7
iii. Physical path = “C:\BrM7Websites\BrM7”

- Add the user permissions to the install directory.
- In your file explorer, browse to the install folder ( C:\BrM7Websites ), right-click on it and go to “Properties”.
- Click on the “Security” tab then click “Edit…”.

c. On the next screen, click on the “Add…” button.

d. On the “Select Users or Group” screen, enter your newly created user and click “OK”.

If you cannot locate the user, click the “Locations” button then browse and select you machine.

e. When back on the permissions page, select your user and make sure they are granted “modify” permission. Click “OK” to close all the property windows.

f. Browse back to IIS and select the BrM7 application under “Sites > Default Web Site” then select “Basic Settings…” on the right-side menu then click on “Test Settings…”.

g. On the “Test Connection” page, make sure you see all green check marks to verify the site is setup correctly.

- Browse to the “C:\Windows\System32\inetsrv\Config” folder and grant the BrM7Site user the same modify access that was granted to the installation directory.

- Update BrM7 appsettings.json ( C:\BrM7Websites\BrM7\appsettings.json ) by default
- "ClientID" = "5F53E05B96A34774BE1D1A863C02385C"

b. Authentication - URLs to be the same as site URL you created in IIS with trailing slash "/"
i. "Authentication": {
"Authority": "https://
"Issuer": "https://
}

c. "Secret" = "Ac)GXGG{B/.AONG{OxD}|#a:M*#'zT&T"

d. Swagger – URL + “oauth2-redirect.html”
i. "Swagger": {
"RedirectUri": " https://
}

e. Telemetry - URLs to be the same as site URL with trailing slash "/"
i. "Telemetry": {
"OtlpEndpoint": " https://
}

f. Verify ReportsHandler path
i. "Report": {
"HandlerPath": "C:\ReportsHandler\bin\Release\ReportsHandler.exe",
"FilePath": "C:\BrM7\Reports\CrystalReports"
}

g. OverrideEmail
i. "OverrideEmail": "",
"BrMWebsitePhysicalPath": "C:\BrM7Websites\BrM7\", // Path to the root of the website.
"BrMWebsiteSiteName": "Default Web Site", // The name of the website in IIS.
"BrMWebsiteApplicationPath": "BrM7", // The path of the BrM app in IIS website.
"EncryptionSettings": {
"EncryptionKey": "0gl2Z8JYqQVa7SgFVux7vvv88qWlmAD/5QUbCiDTVzk="
}

h. Task Service name – Name of task service site it connecting to
i. "TaskServiceSettings": {
"ServiceName": "TaskService"
}

i. "Document360" - Connection information for help
i. "UserName": “document360@mayvue.com”
ii. "FirstName": "Mayvue"
iii. "LastName": "Reader"
iv. "EmailId": document360@mayvue.com
v. "TokenValidity": "120"
vi. "ClientID": "7b8dc7e5-1d46-4848-80dd-ab78b9db12e9"
vii. "ClientSecret": "ht1CtZ0Cw8asiS4cJEzhYZRpF7eM_NioHK0b7dDZNEc"
viii. "TokenUrl": “https://identity.us.document360.io/jwt/generateCode”
ix. "AuthorizeUrl": “https://mayvue-solutions.us.document360.io/jwt/authorize”

j. "CorsSettings": - Domain of application. This is domain only, no app name
i. "CorsSettings": {
"AllowedOrigins": [
"https://laptop-32jtb157/",
"http://localhost/brm7",
"https://mayvue.com"
]
}

k. "BrMFrontendBaseUrl" = site value URL with trailing slash "/"

l. "BrMFrontendBasePath" = site value URL with trailing slash "/"

- Update wwwroot\app_config.json ( C:\BrM7Websites\BrM7\wwwroot ) on a default install
- BASE_URI -> "" empty string

b. VUE_URI -> "/brm7" site Virt Dir with leading "/" slash, without trailing "/" slash

c. API_URI -> site value URL with trailing slash "/"
d. AUTHORITY -> site value URL with trailing slash "/"

- Update TaskService appsettings.json ( C:\BrM7Websites\TaskService\appsettings.json) on a default install
- Task Service name – Name of task service site it connecting to
- "TaskServiceSettings": {
"ServiceName": "TaskService"
}
- "TaskServiceSettings": {
- Task Service name – Name of task service site it connecting to

b. OverrideEmail
i. "OverrideEmail": "",
"BrMWebsitePhysicalPath": "C:\BrM7Websites\BrM7\", // Path to the root of the website.
"BrMWebsiteSiteName": "Default Web Site", // The name of the website in IIS.
"BrMWebsiteApplicationPath": "BrM7", // The path of the BrM app in IIS website.
"EncryptionSettings": {
"EncryptionKey": "0gl2Z8JYqQVa7SgFVux7vvv88qWlmAD/5QUbCiDTVzk="
}

c. Verify ReportsHandler path (can be relative):
i. "Report": {
"HandlerPath": "..\ReportsHandler\bin\Release\ReportsHandler.exe",
"FilePath": "..\BrM7\Reports\CrystalReports"
}

- Add your connection strings to the “appsettings.json” files.
If you have not migrated your database to BrM 7.1 yet, pause here, complete this effort using the BrM Database Migration Guide as a reference, and come back to this step once the database is migrated.
a. Open the BrM “appsettings.json” file ( ~\BrM7Websites\BrM7\appsettings.json on default install ) and locate the "ConnectionStrings" section. By default, the SQL Server connection string is available and the Oracle connection is commented out. Make sure you are using the correct option based on which database you are using.

Example of an SQL Server and Oracle Connection string is below.
SQL SERVER:
"5EC3BC9121DE4581ADCD5105AAA18B1F": "Data Source=LOCALHOST\MSSQLSERVER01;Initial Catalog=BRM7;Integrated Security=False;User Id=pontis;Password=Pontis2020!;Encrypt=false;"
Oracle:
"5EC3BC9121DE4581ADCD5105AAA18B1F": "Data Source=localhost/ORACLE19C;User Id=BrM7;Password=Pontis2020!;"
i. Open the TaskService “appsettings.json” file ( ~\BrM7Websites\TaskService\appsettings.json on default install ) and locate the "ConnectionStrings" section. By default, the SQL Server connection string is available, and the Oracle connection is commented out. Make sure you are using the correct option based on which database you are using.

Starting with the 7.0.3 release, a SchemaOverride key was added to the “appsettings.json” file ( “C:\BrM7Websites\BrM7\appsettings.json” on a default install ). If connecting with a non-schema owner user, you need to define the schema name. Schema override is case-sensitive.

- Register the TaskService
- Open a command prompt as an admin ( must be run as an admin ) and navigate to the Task Service folder ( ~\BrM7Websites\TaskService ) on a default install.
- Run the command below to install the TaskService.
- TaskService.exe -i -n "TaskService"

Update the below script by replacing the “brm.com” domain with yours and then run them on your BrM7 database.
update Application set PostLogoutRedirectUrisJson = '["https://brm.com/BrM7/"]'
where DisplayName = 'Newman';
update Application set PostLogoutRedirectUrisJson = '["https://brm.com/BrM7/","https://brm.com/BrM7/signout-callback-oidc"]'
where DisplayName = 'Serenity API';
update Application set PostLogoutRedirectUrisJson = '["https://brm.com/BrM7/","https://brm.com/BrM7/signout-callback-oidc"]'
where DisplayName = 'Serenity SPA';
update Application set PostLogoutRedirectUrisJson = '["https://brm.com/BrM7/"]'
where DisplayName = 'Swagger';
update Application set RedirectUrisJson = '["https://brm.com/BrM7/signin-oidc "]'
where DisplayName = 'Newman';
update Application set RedirectUrisJson = '["https://brm.com/BrM7/callback","https://brm.com/BrM7/silent-renew.html","https://brm.com/BrM7/api/oauth2-redirect.html"]' where DisplayName = 'Serenity API';
update Application set RedirectUrisJson = '["https://brm.com/BrM7/callback","https://brm.com/BrM7/silent-renew.html","https://brm.com/BrM7/api/oauth2-redirect.html"]' where DisplayName = 'Serenity SPA';
update Application set RedirectUrisJson = '["https://brm.com/BrM7/api/oauth2-redirect.html"]' where DisplayName = 'Swagger';Browse to the site and open dev tools ( F12 ), right-click on the refresh button and do a hard refresh, then try logging in.

