AutoML Server post-installation procedures
You may find on this page references to VDS acronym (Virtual Data Since). It is former name for AutoML component (Automatic Machine Learning). VDS means AutoML in all cases.
Update models
There may be a need to update the models used in AutoML at some point after the initial installation. To do so:
Make sure you have the updated models package file on the master or standalone server.
Run the uploader utility and let it do the update:
cd <install_dir> # Will update the models, merging the already uploaded with the new ones ./vds_models_uploader.sh <path_to_models_package> # Use -o flag to overwrite everything with the new models instead of merging ./vds_models_uploader.sh -o <path_to_models_package>
Install ML SDK
Since 9.0.0.9
ML-SDK package is a part of AutoML server installation process.
Upload vds-ml-sdk to customer standalone nexus-server
Connect to db server.
Navigate to the
<install_dir>/workfusion-nexus-artifactsdirectory and ensure it contains artifacts.Run the vds-ml-sdk upload script (
<install_dir>/tools/nexus_tool/nexus_tool.py), and specify appropriate options:/usr/bin/env python <install_dir>/tools/nexus_tool/nexus_tool.py update --nexus_host=http://127.0.0.1:{{ nexus_port }} --local_artifact_path={{ workfusion_nexus_artifact_dir }} --username={{ workfusion_nexus_admin }} --password={{ workfusion_nexus_admin_pass }}nexus_host: IP adress of standalone nexus-serverlocal_artifact_path:<install_dir>/workfusion-nexus-artifacts, directories insideworkfusion-nexus-artifactsmust be named same as repositories innexususername: username to access standalone nexus-serverpassword: password to access standalone nexus-server
ML SDK repository fix for non-internet environment
If environment for your developers has no access to internet they can have issue during model generation from archetype using installed ML SDK repository.
Error looks like this:
[ERROR] No plugin found for prefix 'archetype' in the current project and in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available from the repositories
To fix the issue, do as follows:
#Make sure you work under <install_user>
su - <install_user>
# Stop nexus service
wfmanager stop nexus
# Go to nexus storage and rename maven-metadata-central.xml files into maven-metadata.xml
cd <install_dir>/nexus/sonatype-work/nexus/storage/ml-sdk
find ./ -name "*-central.xml" -exec sh -c 'mv "$1" "$(echo "$1" | sed s/central.xml/\.xml/)"' _ {} \;
# Start nexus service
wfmanager start nexus