This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
magik-demo:developer:magik-project [2013/05/29 11:08] alex [Deploy MAGIK on Server or Localhost] |
magik-demo:developer:magik-project [2017/07/06 15:24] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | {{:magik-demo:magik_logo.png?nolink&500|}} | ||
| + | |||
| ====== MAGIK Project ====== | ====== MAGIK Project ====== | ||
| Line 16: | Line 18: | ||
| === Steps === | === Steps === | ||
| - | - If you running Magik on **localhost** you have to set the DLV executable file path | + | - First step is to set the DLV executable file path and PROLOG folder (for the code to execute for the specialization) by setting up environment variable |
| - | - Open the project | + | - Detect where is located the folder magik_libs |
| - | - Open file **index.jsp** in folder WebContent/constraints | + | - Copy the (absolute) entire path (file name included) |
| - | - Go to the line \\ {{:magik-demo:developer:screen_shot_2013-05-29_at_11.01.38_am.png|}} \\ and modify the path on the **else** branch with the absolute path of the DLV executable file | + | - Put in an __ENVIRONMENT VARIABLE__ called **MAGIK_LIBS**. An example: <code> DLV_PATH =/Users/user/Documents/workspace/MAGIK_WEB_3/magik_libs</code> |
| + | - E.g., on Mac OS X or Linux Operating systems, one can set this environment variable the following command in terminal <code>$export MAGIK_LIBS=aboslute_path_to_your_local_magik_libs</code> | ||
| - Deploy WAR file to Apache Tomcat server. \\ There are two ways to do it: | - Deploy WAR file to Apache Tomcat server. \\ There are two ways to do it: | ||
| - Using **Tomcat Web Application Manager** | - Using **Tomcat Web Application Manager** | ||
| Line 43: | Line 47: | ||
| | | ||
| === Steps === | === Steps === | ||
| - | * Download Eclipse 3.x. Choose a workspace folder (not the one using for MEGIK-DEMO SVN). | + | * Download Eclipse 3.x. Choose a workspace folder (not the one using for MAGIK-DEMO SVN). |
| * Install Eclipse plugin ''subversion.tigris.org'' for SVN control (see instruction http://web.mit.edu/6.005/www/fa11/psets/ps0/subclipse.html). Alternatively, one can use any SVN control program (e.g., svn command line tool, SmartSVN, etc.) but here we provide instruction for ''subversion.tigris.org'' only. | * Install Eclipse plugin ''subversion.tigris.org'' for SVN control (see instruction http://web.mit.edu/6.005/www/fa11/psets/ps0/subclipse.html). Alternatively, one can use any SVN control program (e.g., svn command line tool, SmartSVN, etc.) but here we provide instruction for ''subversion.tigris.org'' only. | ||
| * Import MAGIK project: | * Import MAGIK project: | ||
| Line 79: | Line 83: | ||
| * ''[[#it.unibz.inf.magik.db|it.unibz.inf.magik.db]]'' | * ''[[#it.unibz.inf.magik.db|it.unibz.inf.magik.db]]'' | ||
| * ''[[#it.unibz.inf.magik.exception|it.unibz.inf.magik.exception]]'' | * ''[[#it.unibz.inf.magik.exception|it.unibz.inf.magik.exception]]'' | ||
| - | * ''[[#it.unibz.inf.magik.hibernate|it.unibz.inf.magik.hibernate]]'' | + | * ''[[#it.unibz.inf.magik.hibernate|it.unibz.inf.magik.hibernate]]'' |
| * ''[[#it.unibz.inf.magik.test|it.unibz.inf.magik.test]]'' | * ''[[#it.unibz.inf.magik.test|it.unibz.inf.magik.test]]'' | ||
| * ''[[#it.unibz.inf.magik.web|it.unibz.inf.magik.web]]'' | * ''[[#it.unibz.inf.magik.web|it.unibz.inf.magik.web]]'' | ||