![]()
![]() After doing this restart Weka and try again, your URL should now reflect what’s in your DatabaseUtils.props file. In my case, I needed to copy DatabaseUtils.props to C:\Users\Joanne\wekafiles\props. In order to find out where your user home directory is going to your command prompt and type the following command. By default, this will be in your user home directory /wekafiles/props. If it doesn’t you need to copy your DatabaseUtils.props file and place it in your user’s home folder. Go to Control Panel -> System -> Advanced System Settings -> Environment Variables.Ĭheck if your URL has the value you placed in your DatabaseUtils.props. How to give weka jar correct path install#(Basically what I am saying is don’t install this in your downloads folder).ĭid you finish? Good! Now we need to modify (or create) the CLASSPATH system environment variable. ![]() Installing this in your program files helps with remembering the location and also puts it in a more memorable place. How to give weka jar correct path driver#In this example, the driver will be installed at F:\Program Files\Microsoft JDBC Driver 4.2. Install the driver (right-click -> Run as administrator), preferably you should install the driver to C:\Program Files\Microsoft JDBC Driver 4.2 but any location works. So we need to help Weka find the driver to talk to SQL Server 2016.ĭownload the Microsoft JDBC Driver 4.2. Weka is written in Java and when Java connects to a database it needs to load a JDBC Driver, which then performs the connection. There are some data type mappings: varchar=0Īfter these data type mappings, add some additional ones (to save you some headaches in the future) nvarchar=9Ĭongrats your database property file is now set up! But we aren’t done yet, now we need to set up our classpath. JdbcURL=jdbc:sqlserver://localhost databaseName=blahblahĬhange this to your own, if your SQL Server 2016 is on your local machine it will most likely be (databaseName is not required): # database URL The current file has the database URL as the following: # database URL We now have the groundworks for our properties file, we just need to make a few more changes. Open your 2005 (using a text editor like Notepad/Notepad ) and save it as DatabaseUtils.props file. Weka will only look directly at one DatabaseUtils.prop file (hsql, msaccess, mssqlserver, etc are not accessible by Weka) Otherwise copy this file to make a backup. This is a properties file for Weka (if you want to learn more about Weka property files click here). You can then use the excellent graph visualization package from AT
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |