I appears that Fusion expects you to install in a specific directory structure. When I have time, I'll explore this more to see if my understanding is correct. For now use the structure,
/opt/lucidworks/fusion/3.1.2 |
Untar using your serveradmin account,
su - serveradmin cd ~ mkdir lucidworks tar -xvpf fusion-3.1.2.tar.gz mv ./fusion/ ./lucidworks/ exit # exit back to your root enabled staff acount. |
Finally using your root enabled account,
sudo mv /home/serveradmin/lucidwork/ /opt/ |
Modify Java_Home injecting in lines after finding the match,
TRY 1
wget http://www.bonsaiframework.com/tscripts/lucidworks-fusion/fusion_java_home.txt sed '/function check_java() {/r fusion_java_home.txt' /opt/lucidworks/fusion/3.1.2/bin/common.sh > /opt/lucidworks/fusion/3.1.2/bin/common.sh |
TRY 2
sed '/function check_java()/c\ function check_java()\ \ # Bonsaiframework - Modification Start\ # --------------------------------------\ JRE_HOME="$FUSION_HOME"/java\ JAVA_HOME="$FUSION_HOME"/java\ # --------------------------------------\ # Bonsaiframework - Modification End\ ' /opt/lucidworks/fusion/3.1.2/bin/common.sh |
You common.sh file will have the following inserted,
function check_java() { # Bonsaiframework - Modification Start # -------------------------------------- JRE_HOME="$FUSION_HOME"/java JAVA_HOME="$FUSION_HOME"/java # -------------------------------------- # Bonsaiframework - Modification End if [ -z "$JAVA_HOME" ]; then |
Your home directory is considered, /opt/lucidworks/3.1.2 and I'm assuming you want to start from this directory to run properly.
Startup instructions seem to imply that you need to do it from a specific directory. When I have time, I'll try starting from the actual bin/fusion directory to see if the symlinks are properly generated.
cd /opt/lucidworks/fusion/3.1.2 ./bin/fusion start |
After first start, you'll see newly created symbolic link directories created (bin, conf, latest, var),
cd /opt/lucidworks/fusion/ /opt/lucidworks/fusion$ ls -al total 12 drwxr-xr-x 3 serveradmin serveradmin 4096 Nov 11 08:56 . drwxrwxr-x 3 serveradmin serveradmin 4096 Nov 10 21:58 .. drwxr-xr-x 11 serveradmin serveradmin 4096 Nov 11 08:53 3.1.2 lrwxrwxrwx 1 serveradmin serveradmin 10 Nov 11 08:56 bin -> latest/bin lrwxrwxrwx 1 serveradmin serveradmin 11 Nov 11 08:56 conf -> latest/conf lrwxrwxrwx 1 serveradmin serveradmin 5 Nov 11 08:56 latest -> 3.1.2 lrwxrwxrwx 1 serveradmin serveradmin 10 Nov 11 08:56 var -> latest/var |
URL | Function | Comment |
---|---|---|
http://ubuntu.local:8764 | Fusion UI | This is the Admin interface and also includes Tincludes the Fusion Authorization Proxy to allow JSON calls provided you have authenticated. |
http://ubuntu.local:8983/solr/ | Solr UI | Not sure if we should access it directly given Lucidworks has an interface. |
Use the Index Workbench to control how Fusion transforms and enriches your data during import, parsing, and indexing.
Use the Query Workbench to add search features such as facets, signals, and more.
Develop your search application using Fusion’s REST API.
After running the wizard it prompts you to go to the Index Workbench
solrconfig.xml is a key file. Examples are located in,
opt/lucidworks/3.1.2/apps/solr-dist/server/solr/configsets |
Defaults have been found here,
/opt/lucidworks/3.1.2/apps/solr-dist/server/solr/configsets/basic_configs/conf/solrconfig.xml /opt/lucidworks/3.1.2/apps/solr-dist/server/solr/configsets/data_driven_schema_configs/conf/solrconfig.xml /opt/lucidworks/3.1.2/apps/solr-dist/server/solr/configsets/sample_techproducts_configs/conf/solrconfig.xml /opt/lucidworks/3.1.2/data/solr/configsets/basic_configs/conf/solrconfig.xml /opt/lucidworks/3.1.2/data/solr/configsets/data_driven_schema_configs/conf/solrconfig.xml /opt/lucidworks/3.1.2/data/solr/configsets/sample_techproducts_configs/conf/solrconfig.xml |
Your application uses Fusion’s REST API to interact with the Fusion system.
Solr 6.5.1 is the version bundled with Lucidworks 3.1.2