- Getting Started
-
Administration Guide
- Get Started with Administering Wyn Enterprise
- Configuration Settings
- Account Management
- Security Management
- System Management
- Document Management
-
How To and Troubleshooting
- Change Default Password
- Set Language Preference
- Set Time Zone
- Slack Integration
- MS Teams Integration
- Create Custom Language Packages
- Configure Identity Server
- Configure Single Sign-on
- Convert Crystal Reports/MS Access Reports to Wyn Reports
- Encrypt or Decrypt Connection Strings
- Using ClickHouse as OLAP Database
- Hide Download Link in Scheduled Tasks
- Configure Redis Cluster using Username and Password
-
Deploy and Configure a Custom Data Source
- User Guide
- Developer Guide
Deploy and Configure a Custom Data Source
Deploy a Custom Data Source in Wyn
In addition to the many built-in data sources, Wyn 8.1 administrators can also deploy custom data sources. A developer should provide the administrators with a package of the custom data sources and they can deploy the artifacts to a directory on the machine where Wyn is installed and configure Wyn to make it available for use by data modelers.
The steps to deploy a custom data source involves unzipping the artifacts received from the developer to a folder on the Wyn machine, modifying the Wyn configuration file, and finally restarting the Wyn service.
Unzip the Custom Data Source
The administrator can unzip the custom data source package to a suitable folder on the machine. For example on a Windows machine:
C:\WynCustomProviders\FirebirdProvider\
The path to the DLL inside the folder will be needed for configuration.
Configure Wyn
Open the Wyn.conf configuration file in a text editor. On Windows, the file is located in
<Wyn Installation Path>\Monitor\Conf\Wyn.conf
and on Linux it is located in
<Wyn Installation Path>/Monitor/Conf/Wyn.conf
Add the path to the custom data source DLL file in the package you received from the developer in Wyn.conf. To do that you create an CustomNativeQueryDataProviderAssemblies XML node under the Services\Server node or copy it from the example below. Make sure you have the hierarchy you see in the following XML below. Replace the {/Path/to/CustomProvider.dll} with the path to where your custom data provider assembly is located.
<Services>
<Server>
<DataProviders>
<CustomNativeQueryDataProviderAssemblies>
<sys:string>{/Path/to/CustomProvider.DLL}</sys:string>
</CustomNativeQueryDataProviderAssemblies>
</DataProviders>
</Server>
</Services>
An example with three custom data sources will have configurations as follows. Make sure this node is under the Services\Server nodes:
<DataProviders>
<CustomNativeQueryDataProviderAssemblies>
<sys:string>/imports/FirebirdProvider/FirebirdProvider.dll</sys:string>
<sys:string>/imports/NativeJDBCProvider/NativeJdbcProvider.dll</sys:string>
<sys:string>/imports/JavascriptProvider/JavascriptProvider.dll</sys:string>
</CustomNativeQueryDataProviderAssemblies>
</DataProviders>
Restart Wyn Service.
Restart the Wyn Service according following the procedure for you operating system. After Wyn restarts, the custom data sources should be available and users can create data sources to connect to the custom providers.