π Note: At least one of server-one and server-api-one servers must be running in order to add Datasources, this is required because the driver jar file is deployed against the servers.
Step 1
Add a Datasource:
Go to the Configuration tab.
Select Profiles.
From the Profile dropdown or list, choose full.
In the Subsystem section:
Click on Datasources & Drivers.
Then select Datasources.
In the Datasource section:
Click on Add Datasource.

Step 2
Select Microsoft SQLServer as Template and click Next.
β
Step 3
Type ReportDS as Name and java:/ReportDS as JNDI Name. Click Next.
β
Step 4
Select mssql-jdbc-11.2.3.jre11.jar as Driver Name, com.microsoft as Driver Module Name and com.microsoft.sqlserver.jdbc.SQLServerDriver as Driver Class Name. Click Next.
β οΈ Important: The driver must be selected from the dropdown list. Do not type the driver name yourself.
The dropdown list for the Driver Name field is only available when at least one of the server instances is running.
There is an issue with your configuration if the dropdown list is not available or the driver is not listed as an option.
Step 5
Specify the Connection URL, for example jdbc:sqlserver://localhost:1433;databaseName=mosaic;trustServerCertificate=true
β
Specify the User Name and Password, valid for the database for example fw/<password>. Leave the other fields blank and click Next.
β
Certificates used in database connections
Unless SQL Server has been provisioned with a valid certificate rather than self signed append this parameter to the URL:
;trustServerCertificate=true
β
If a valid certificate signed by a certificate authority has been provisioned in SQL Server this should be omitted. This is required even when the driver is not configured to use encryptions for all JDBC traffic.
Step 6
Click on the Test Connection button.
A connection successful message should be shown. Click Next.
β
Review the configuration and click Finish.
After the Datasource has been created, a message advising that the domain configuration has changed pops up and reloading or restarting the affected servers is required. Restart both servers.







