Configuring the Data Sources

This step is not required if you are using Nectari Cloud.

Environments and Data Sources

Tip

The description given to a data source created for the first time is used throughout the environments to describe this specific data source.

Give a generic description for the first time (e.g., ERP Data Source, Cube Data Source) and if necessary, rename it after the first environment has been created.

The following information is needed to configure the data sources:

  • Database server credentials: Server name, Instance, Authentication strategy.
  • Main ERP database information: Database and schema name.
  • Users: Make sure to have created SQL or Oracle users beforehand.

ERP Data Source

  1. In the upper-right hand corner, click on the to access the Administration section.

  2. On the left pane, select Env. & Data Sources.

  3. By default, there is already an environment called Production, which you can rename by double-clicking in the name box. Once changed, press the Enter key.

  4. In the Data Sources section, click Add to create the first data source.

  5. Complete the ERP Data Source configuration. See instructions for MS SQL Server below.

  6. Click Validate and then Save to complete the configuration of the data source.

ERP Data Source Fields for SQL Server Description
Data Source Description Sage 300 Data Source
Type SQLSERVER
Server Database server of the data warehouse where Sage 300 has been synchronized in the DataSync configuration.
Database Name

Name of the data warehouse where Sage 300 has been synchronized in the DataSync configuration (beware of the case sensitivity).
Database Schema Name

Create the two following entries by clicking on the icon (replace DatabaseName by the appropriate value):

DatabaseName.dbo

DatabaseName.NEC_CUSTOM_SCHEMA (replace CUSTOM_SCHEMA with the schema name)

Note

The second line contains the Nectari Custom Schema. We highly recommend following this naming convention:

  • Start with NEC
  • Use all capitals
  • Separate words by an underscore
Note  

The application searches for tables in the same order as the schemas are listed. As soon as a table is found in a schema, the application stops searching. Therefore, if you have multiple tables with the same name in different schemas, make sure that the schema containing the table you want to use appears first.

Important

Choose a unique Custom Schema name for each environment.
Nectari schema

Enter NEC_CUSTOM_SCHEMA (replace CUSTOM_SCHEMA with the schema name)
Authentication Strategy UseSpecific
User Name

Name of the SQL user accessing the data warehouse. For example, sa.

This is the same user you created in Creating SQL Users .
Password The user's password.
Example

We are using a hybrid scenario (scenario 3) where we use both live data from two companies (named FW Construction Ltd and HomeStyle Kicthens Ltd respectively) and we use a consolidation environment to combine data from both companies.

Thus we have three environments: one environment per company (FW Cons. (Live) and HomeStyle (Live)) and the Consolidation environment.

After importing the template, you will be able to select these environments from the title bar drop-down list and easily view their data.